section 3
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Mon, 13 Feb 2012 09:50:31 +0000
changeset 1529 fb9c77f7f97b
parent 1528 4e73d0406a71
child 1530 61c689662e1f
section 3
model/working-copy/towards-wd4.html
--- a/model/working-copy/towards-wd4.html	Mon Feb 13 09:47:17 2012 +0000
+++ b/model/working-copy/towards-wd4.html	Mon Feb 13 09:50:31 2012 +0000
@@ -696,7 +696,7 @@
 who the provenance is attributed to, and when it was
 generated, etc. In other words, we need to be able to express the provenance of provenance.</p>
 
-<p>No new mechanism is required.  PROV-DM only assumes that provenance statements have been bundled up, and named. For instance, in this case, provenance statements were put in a file and exposed on the Web, respectively at <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/examples/w3c-publication1.prov-asn">ex:prov1</a> and <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/examples/w3c-publication3.prov-asn">ex:prov3</a>.   To express their respective provenance, these resources must be seen as entities, and all the constructs of PROV-DM are now available to characterize their provenance. In the example below, <span class="name">ex:prov1</span> is attributed to the agent <span class="name">w3:Consortium</span>, whereas <span class="name">ex:prov3</span> to <span class="name">ex:Simon</span>.
+<p>No new mechanism is required to support this requirement.  PROV-DM makes the assumption that provenance statements have been bundled up, and named, by some mechanism outside the scope of PROV-DM. For instance, in this case, provenance statements were put in a file and exposed on the Web, respectively at <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/examples/w3c-publication1.prov-asn">ex:prov1</a> and <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/working-copy/examples/w3c-publication3.prov-asn">ex:prov3</a>.   To express their respective provenance, these resources must be seen as entities, and all the constructs of PROV-DM are now available to characterize their provenance. In the example below, <span class="name">ex:prov1</span> is attributed to the agent <span class="name">w3:Consortium</span>, whereas <span class="name">ex:prov3</span> to <span class="name">ex:Simon</span>.
 
 <pre>
 entity(ex:prov1, [prov:type="prov:AccountEntity" %% xsd:QName ])