W3C home > Mailing lists > Public > public-prov-wg@w3.org > May 2012

PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]

From: Provenance Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 28 May 2012 19:01:37 +0000
Message-Id: <E1SZ5CD-0002ix-In@tibor.w3.org>
To: public-prov-wg@w3.org
PROV-ISSUE-385 (haProvenanceIn-complexity): The hasProvenbanceIn relation is over-complicated [prov-dm]


Raised by: Graham Klyne
On product: prov-dm

I'm raising this issue as a placeholder and for discussion.  I didn't notice the arrival of prov:hasProvenanceIn, but based on its appearance in http://dvcs.w3.org/hg/prov/raw-file/default/model/releases/ED-prov-dm-20120525/prov-dm.html (which AFAIK is not a currently active draft, but a proposal) is rather over-complicated and a bit obscure.

My sense is that, especially as this is motivated by PROV-AQ, there are just too many identifiers floating around.

Instead of:

  hasProvenanceIn(id, subject, bundle, target, attrs)

Why not just:

  hasProvenanceIn(subject, bundle)

Where subject is based on the URI of an entity, and bundle is based on the URI of a provenance bundle with information about that entity.

I would like to understand what  real scenario justifies all the added machinery that has been included with this relation.
Received on Monday, 28 May 2012 19:01:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:51:14 UTC