ISSUE-72: Provenance Data Category

Hi all,

> i) Can an element have both local provenance data (either inline or 
> via local standoff markup) and also reference global provenance data 
> (declared via global standoff markup) using the attribute specified 
> globally via provenanceRecordsRefPointer?  The draft does not specify.

I don't think so. Overriding rules takes care of that: any provenanceRecordsRefPointer of a global rule would be overridden by the local provenanceRecordsRef. In other words, one cannot have in the same node: provenancerecordsRef and an another attribute that is declared as having the same semantics via a provenanceRecordsRefPointer in a global rule.


> ii) Similarly, does the ordering of provenance records within a 
> <provenanceRecords> element make a statement about the (temporal) 
> order in which the records were created?  If an ordering is implied, 
> it raises questions about the implied ordering in a document where 
> provenance records are declared both globally and via local markup.
>
> iii) More generally, we observe that provenance records lack a 
> date/time attribute, which makes their semantics as a form of history 
> somewhat muddy.  In practice, a single tool/agent may edit a single 
> document multiple times in succession over an arbitrary period of 
> time.  Should these multiple "sessions" be represented by a single 
> logical provenance record?  Or is it the intention of the spec that 
> the agent add a provenance record for each of these sessions in which 
> a modification is made to the document?

Good points. Hopefully the Provenance champions have answers.

cheers,
-yves

Received on Saturday, 12 January 2013 14:41:12 UTC