addressing ISSUE-208
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Tue, 17 Jan 2012 09:25:17 +0000
changeset 1373 a551e9259b8d
parent 1372 996046cd8e38
child 1374 312911932910
addressing ISSUE-208
model/ProvenanceModel.html
--- a/model/ProvenanceModel.html	Mon Jan 16 23:29:50 2012 +0000
+++ b/model/ProvenanceModel.html	Tue Jan 17 09:25:17 2012 +0000
@@ -894,7 +894,7 @@
 
 
 <p>Concretely, PROV-DM consists of a set of constructs to formulate representations of the world and constraints that must be satisfied by them.
-A PROV-DM construct is referred to as a <em>record</em>, a body of information about something which is of interest from a provenance viewpoint.   PROV-DM records may be asserted directly or may be inferred from others.  
+A PROV-DN <dfn id="dfn-Record">record</dfn> is a body of information about something which is of interest from a provenance viewpoint.   PROV-DM records may be asserted directly or may be inferred from others.  
 </p>
 
 <p>
@@ -2598,9 +2598,7 @@
 <section id="RecordContainer">
 <h4>Record Container</h4>
 
-<p>A <dfn id="dfn-RecordContainer">record container</dfn> is a house-keeping construct of PROV-DM, also capable of bundling PROV-DM records. A record container is the root of a provenance record and can be exploited to package up prov-dm records in response to a request for the provenance of something ([[!PROV-AQ]]). Given that a record container is the root of a provenance record, it is not defined as a PROV-DM record (production <span class="nonterminal">record</span>), since otherwise it could appear arbitrarily nested inside accounts.</p> 
-
-<p>
+<p>A <dfn id="dfn-RecordContainer">record container</dfn> is a house-keeping construct of PROV-DM, also capable of bundling PROV-DM <a title="record">records</a>. A record container is the root of a provenance record and can be exploited to package up PROV-DM <a title="record">records</a> in response to a request for the provenance of something ([[!PROV-AQ]]). Given that a record container is the root of a provenance record, it is not defined as a PROV-DM record (production <span class="nonterminal">record</span>), since otherwise it could appear arbitrarily nested inside accounts.</p> 
 
 
 <p>A record container, written <span class="name">container decls  recs endContainer</span> in PROV-ASN, contains:
@@ -2624,6 +2622,26 @@
 
 <div class="anexample">
 <p>
+The following container contains records related to the provenance of entity 
+<span class="name">e2</span>.
+</p>
+<pre class="codeexample">
+container
+  prefix ex: http://example.org/,
+  entity(e2, [ prov:type="File", ex:path="/shared/crime.txt", ex:creator="Alice", 
+             ex:content="There was a lot of crime in London last month."])
+  activity(a1, 2011-11-16T16:05:00,,[prov:type="edit"])
+  wasGeneratedBy(e2, a1, [ex:fct="save"])     
+  wasAssociatedWith(a1, ag2, [prov:role="author"])
+  agent(ag2, [ prov:type="prov:Person" %% xsd:QName, ex:name="Bob" ])
+endContainer
+</pre>
+<p>This container could for instance be returned by querying a provenance store for the provenance of entity <span class="name">e2</span> [[!PROV-AQ]].  All these assertions are implicitly wrapped in a default account.  In the absence of an explicit account, such provenance records remain unattributed.
+</p>
+</div>
+
+<div class="anexample">
+<p>
 The following container </p>
 <pre class="codeexample">
 container