--- a/model/working-copy/wd6-bundle.html Thu May 10 10:15:06 2012 +0100
+++ b/model/working-copy/wd6-bundle.html Thu May 10 10:48:22 2012 +0100
@@ -283,7 +283,7 @@
<li> Drop the term 'account' from prov-dm.
<li> Instead, introduce the notion of bundle, as defined here.
<li> Drop the component on annotation.
-<li> Instead, introduce a component on bundles, as described here.
+<li> Introduce a component on bundles, as described here.
</ul>
</div>
</section>
@@ -358,7 +358,7 @@
<section id="section-example-c">
<h3>Attribution of Provenance</h3>
-<p>The two previous sections offer two different perspectives on the provenance of a document. PROV allows for multiple source to provide the provenance of a subject. For users to decide whether they can place their trust in the document, they may want to analyze its provenance, but also determine who the provenance is attributed to, and when it was
+<p>The two previous sections offer two different perspectives on the provenance of a document. PROV allows for multiple sources to provide the provenance of a subject. For users to decide whether they can place their trust in the document, they may want to analyze its provenance, but also determine 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>PROV-DM offers a construct to name a bundle of provenance descriptions. </p>
@@ -458,13 +458,11 @@
<div class="attributes" id="attributes-bundle">
A <dfn title="dfn-bundle" id="dfn-bundle-declaration">bundle declaration</dfn>, written <span class="pnExpression">bundle id description_1 ... description_n</span>, consists of:
<ul>
-<li><span class='attribute' id="bundle.declaration.id">id</span>: an OPTIONAL identifier for the bundle;</li>
+<li><span class='attribute' id="bundle.declaration.id">id</span>: an identifier for the bundle;</li>
<li><span class='attribute' id="bundle.declaration.descriptions">descriptions</span>: a set of provenance descriptions <span class="name">
description_1</span>, ..., <span class="name">description_n</span>.</li>
</ul>
-<p>When specified, the identifier <span class="name">id</span> identifies a unique set of descriptions.</p>
-
-<p>A bundle without identifier is referred to as an anonymous bundle. Since anonymous bundles lack identifiers, it becomes harder to associate provenance descriptions with such them. An anonymous bundle is merely a packaging mechanism for provenance descriptions when provenance of provenance does not have to be expressed. Provenance descriptions that are not explicitly included in a named bundle implicitly belong to the anonymous bundle. </p>
+<p>A bundle's identifier <span class="name">id</span> identifies a unique set of descriptions.</p>
</section>
@@ -475,7 +473,7 @@
<h3>Bundle Description</h3>
-<p>As a named bundle is a set of descriptions, it also an entity so that its provenance can be described. </p>
+<p>As a named bundle is a set of descriptions, it is also an entity so that its provenance can be described. </p>
PROV defines the following type for bundles:
<ul>
@@ -530,7 +528,6 @@
wasGeneratedBy(bob:bundle1, -, 2012-05-24T10:30:00)
wasAttributedTo(bob:bundle1, ex:Bob)
</pre>
-<p>These descriptions implicitly belong to an anonymous bundle.</p>
<p>In contrast, the second bundle is attributed to Alice who
observed the derivation of <span class="name">ex:report2</span> from <span class="name">ex:report1</span>.</p>
@@ -539,7 +536,6 @@
wasGeneratedBy(alice:bundle2, -, 2012-05-25T11:15:00)
wasAttributedBTo(alice:bundle2, ex:Bob)
</pre>
-<p>Likewise, these descriptions also implicitly belong to an anonymous bundle.</p>
</div>
<div class="anexample" id="anexample-provenance-aggregation">
@@ -642,42 +638,58 @@
a provenance locator pointing to bundle <span class="name">bob:bundle4</span>.
The locator indicates that some provenance description for <span class="name">ex:report1</span> can be found in bundle <span class="name">bob:bundle4</span>. The purpose of the locator is twofold. First, it allows for <a href="http://www.w3.org/TR/prov-aq/#incremental-provenance-retrieval">incremental navigation</a> of provenance [[PROV-AQ]]. Second, it makes entity <span class="name">ex:report1</span> described in <span class="name">alice:bundle5</span> an <a>alternate</a> of <span class="name">ex:report1</span> described in <span class="name">bob:bundle4</span>.
</p>
+</div>
+
+<div class="anexample" id="anexample-provenance-locator3">
+<p>Alternatively, Alice may have decided to use a different identifier for <span class="name">ex:report1</span>.</p>
+<pre class="codeexample">
+bundle alice:bundle6
+ entity(alice:report1)
+ hasProvenanceIn(alice:report1, bob:bundle4, ex:report1, -, -)
+ entity(ex:report2, [ prov:type="report", ex:version=2 ])
+ wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
+ wasDerivedFrom(ex:report2, alice:report1)
+end
+</pre>
+<p>Alice can specify the <a href="#prov.locator.target">target</a> in the provenance locator to be <span class="name">ex:report1</span>.
+With such a statement, Alice states that provenance information about <span class="name">alice:report1</span> can be found in bundle
+<span class="name">bob:bundle4</span> under the name <span class="name">ex:report1</span>. In effect, <span class="name">alice:report1</span> and <span class="name">ex:report1</span> are declared to be alternate.</p>
</div>
<div class="anexample" id="aexample-note">
<p>Consider that the following bundle of descriptions, in which derivation and generations have been identified.
<pre class="codeexample">
-bundle obs:bundle6
+bundle obs:bundle7
entity(ex:report1, [prov:type="report", ex:version=1])
wasGeneratedBy(ex:g1; ex:report1,-,2012-05-24T10:00:01)
entity(ex:report2, [prov:type="report", ex:version=2])
wasGeneratedBy(ex:g2; ex:report2,-,2012-05-25T11:00:01)
wasDerivedFrom(ex:d; ex:report2, ex:report1)
endBundle
-entity(obs:bundle6, [ prov:type='prov:Bundle' ])
-wasAttributedTo(obs:bundle6, ex:observer01)
+entity(obs:bundle7, [ prov:type='prov:Bundle' ])
+wasAttributedTo(obs:bundle7, ex:observer01)
</pre>
-Bundle <span class="name">obs:bundle6</span> is rendered by a visualisation tool. It may useful for the tool configuration for this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered. The original bundle obviously cannot be changed. However, one can create a new bundle, as follows.
+Bundle <span class="name">obs:bundle7</span> is rendered by a visualisation tool. It may useful for the tool configuration for this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered. The original bundle obviously cannot be changed. However, one can create a new bundle, as follows.
<pre class="codeexample">
-bundle tool:bundle7
- entity(tool:bundle7, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
- wasAttributedTo(tool:bundle7, viz:Visualizer)
+bundle tool:bundle8
+ entity(tool:bundle8, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
+ wasAttributedTo(tool:bundle8, viz:Visualizer)
entity(ex:report1, [viz:color="orange"])
- hasProvenanceIn(ex:report1, obs:bundle6, -, -, -)
+ hasProvenanceIn(ex:report1, obs:bundle7, -, -, -)
entity(ex:report2, [viz:color="blue"])
- hasProvenanceIn(ex:report2, obs:bundle6, -, -, -)
+ hasProvenanceIn(ex:report2, obs:bundle7, -, -, -)
wasDerivedBy(ex:d; ex:report2, ex:report1, [viz:style="dotted"])
- hasProvenanceIn(ex:d, obs:bundle6, -, -, -)
+ hasProvenanceIn(ex:d, obs:bundle7, -, -, -)
endBundle
</pre>
-<p>In bundle <span class="name">tool:bundle7</span>, the prefix <span class="name">viz</span> is used for naming visualisation-specific attributes, types or values.</p>
+<p>In bundle <span class="name">tool:bundle8</span>, the prefix <span class="name">viz</span> is used for naming visualisation-specific attributes, types or values.</p>
-<p>Bundle <span class="name">tool:bundle7</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualisation tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
+<p>Bundle <span class="name">tool:bundle8</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualisation tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
</p>
<p>Alternates of the entities <span class="name">ex:report1</span> and <span class="name">ex:report2</span> have a visualization attribute for the color to be used when rendering these entities.