links update
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Mon, 08 Apr 2013 22:11:00 +0100
changeset 6073 de403cd7171b
parent 6072 39f8b28868e8
child 6074 e77fc1b3f7af
links update
links/comments/review-khalid.txt
links/comments/review-simon.txt
links/comments/review-tom.txt
links/diff.html
links/prov-links.html
links/releases/NOTE-prov-links-20130430/Overview.html
links/releases/NOTE-prov-links-20130430/diff.html
--- a/links/comments/review-khalid.txt	Mon Apr 08 21:34:35 2013 +0100
+++ b/links/comments/review-khalid.txt	Mon Apr 08 22:11:00 2013 +0100
@@ -13,12 +13,22 @@
 > specification." Some text that explains why you are interested in
 > doing so, may help the reader follow.
 > 
+
+
+This was explained in the previous paragraph: "Instead, a consumer
+wants to refer to the description as created by the producer in situ
+and specialize it, allowing the consumer to add their own view on this
+entity. "  Following which ... we want to be able to refer to a description ...
+
 > C2. The second paragraph in Section 2 states that "Some applications
 > may want to augment the descriptions of entity e1 found in bundle b
 > with other information. They cannot add these descriptions to bundle b
 > since this would result in a different bundle." Here too, it may not
 > be clear for the reader what the problem in creating a new bundle 2.
 > 
+
+I have added a sentence here. HOpefully, this clarifies this point.
+
 > C3. I think that the introduction as well as the beginning of Section
 > 2, where the concept of Mention is introduced, as a bit dry, in the
 > sense that they are not accompanied by examples that can help the
@@ -26,16 +36,29 @@
 > this respect, Example 1 can be introduced earlier and used as a means
 > of motivating the need for a construct like mentionOf in the beginning
 > of Section 2.
+
+The structure of the presentation follows that of prov-dm: definition
+followed by example.
+
 > 
 > C4. In the second paragraph in Section 2, "found in bundle b" ->
 > "found in a bundle b". Later on in the same section, "the entity e1
 > may described" -> "the entity e1 may be described"
+
+Done
+
 > 
 > C5. I found Example  2 slightly difficult to follow. In particular,
 > the reader is not taken through the first turtle excerpt, which
 > contains both the specification of the bundle obs:bundle1, and
 > provenance records specifying the provenance of such a bundle as a
+
+I have added a brief description of the first bundle.
+
 > whole. In example 2, "it may useful" -> "it may be useful"
+
+Done
+
 > 
 > 
 > On 28 March 2013 10:55, Luc Moreau <[email protected]> wrote:
--- a/links/comments/review-simon.txt	Mon Apr 08 21:34:35 2013 +0100
+++ b/links/comments/review-simon.txt	Mon Apr 08 22:11:00 2013 +0100
@@ -97,6 +97,9 @@
 > tion of the meaning of the property itself? What does prov:mentionOf mean w=
 > hen asserted?
 > 
+
+The specification does not define the meaning of prov:mentionOf by itself.
+
 > 
 > 
 > thanks,
--- a/links/comments/review-tom.txt	Mon Apr 08 21:34:35 2013 +0100
+++ b/links/comments/review-tom.txt	Mon Apr 08 22:11:00 2013 +0100
@@ -15,12 +15,18 @@
 > provide context about the specialized entity. Changing this to "sets of
 > provenance" or "named sets of provenance" is clearer in my opinion, and
 > consistent with the PROV-DM definition.
+
+OK Done.
+
 > - I assume this note will be dropped in the final document? "The concept
 > Mention<https://dvcs.w3.org/hg/prov/raw-file/default/links/prov-links.html#concept-mention>is
 > experimental, and for this reason was not defined in PROV
 > recommendation-track documents. The Provenance Working Group is seeking
 > feedback from the community on its usefulness in practical scenarios. "
 > 
+
+No, I was intending to keep it, since it is really its status: it's experimental.
+
 > 2. Conceptual Definition
 > - I was confused by the following paragraph:
 > 
@@ -39,6 +45,11 @@
 > would either put it lower, together with the examples, or drop it.
 > If you do keep it, there is a small typo in "multiple other bundle bi" (the
 > 's' of bundles is missing).
+
+I moved it up, just after the definition, and added a sentense stating
+that mention cannot be inferred from Specialization.
+
+
 > 
 > 3. Ontological Definition
 > the text "When :x prov:mentionOf :y and :y is described in Bundle :b, the
@@ -68,6 +79,9 @@
 > >
 > 
 > Or something similar to make it just that tad bit cleaner.
+
+Followed your suggestion, mostly.
+
 > 
 > And that is it. Great job on this document!
 > 
--- a/links/diff.html	Mon Apr 08 21:34:35 2013 +0100
+++ b/links/diff.html	Mon Apr 08 22:11:00 2013 +0100
@@ -945,12 +945,13 @@
 represented in various <span class="delete">representations,</span><span class="insert">ways,</span> and interchanged between systems across the Web. 
 </p>
 
-<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it.  To support this, provenance itself should be trusted, and therefore, provenance of provenance is itself a critical aspect of an information infrastructure such as the Web. To this end, PROV introduces the concept of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-bundle">Bundle</a>: defined as a<span class="insert"> named</span> set of provenance descriptions;  it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite><span class="insert">], </span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-bundle"><span class="insert">Bundle</span></a><span class="insert"> [</span><cite><a class="bibref" href="#bib-PROV-N"><span class="insert">PROV-N</span></a></cite>] and <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/#term-Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>]). With bundles, blobs of provenance descriptions can be given names and can themselves be regarded as entities, whose provenance can in turn be described using PROV. These blobs of provenance descriptions are independent of each other, as formalized by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#bundle-constraints">validity</a> by examining them in isolation of each other. </p>
+<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it.  To support this, provenance itself should be trusted, and therefore, provenance of provenance is itself <span class="insert">an important aspect of establishing trust in an information infrastructure such as the Web. To this end, PROV introduces the concept of </span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-bundle"><span class="insert">Bundle</span></a><span class="insert">: defined as </span>a <span class="delete">critical aspect of an information infrastructure such as the Web. To this end, PROV introduces the concept of </span><span class="delete">Bundle</span><span class="delete">: defined as a</span><span class="insert">named</span> set of provenance descriptions;  it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite><span class="insert">], </span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-bundle"><span class="insert">Bundle</span></a><span class="insert"> [</span><cite><a class="bibref" href="#bib-PROV-N"><span class="insert">PROV-N</span></a></cite>] and <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/#term-Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>]). With bundles, <span class="delete">blobs</span><span class="insert">sets</span> of provenance descriptions can be given names and can themselves be regarded as entities, whose provenance can in turn be described using PROV. These <span class="delete">blobs</span><span class="insert">sets</span> of provenance descriptions <span class="delete">are independent</span><span class="insert">stand independently</span> of each other, as formalized by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#bundle-constraints">validity</a> by examining them in isolation of each other. </p>
 
 
-<p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party creates some data and its provenance, whereas another party consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by another producer.  For the consumer, it is not suitable to repeat the provenance created by the producer, and augment it according to their need. Instead, a consumer wants to <em>refer</em> to the description as created by the producer <em>in situ</em>, i.e. in its bundle, and <em>specialize it</em>, allowing the consumer to add their own view on this entity. Such a capability would allow parties to "stitch together" provenance descriptions that would otherwise be disconnected.</p> 
+<p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party <span class="insert">(a producer) </span>creates some data and its provenance, whereas another party <span class="insert">(a consumer) </span>consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by <span class="delete">another </span><span class="insert">the
+ </span>producer.  For the consumer, it is not suitable to repeat the provenance created by the producer, and augment it according to their need. Instead, a consumer wants to <em>refer</em> to the description as created by the producer <em>in situ</em><span class="delete">, i.e. in its bundle,</span> and <em>specialize it</em>, allowing the consumer to add their own view on this entity. <span class="insert">(The notion of </span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-specialization"><span class="insert">specialization</span></a><span class="insert"> is defined in [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">].) </span>Such a capability would allow parties to "stitch together" provenance descriptions that would otherwise be disconnected.<span class="insert"> For this to work, this specification assume that provenance created by the producer is contained in a bundle, so that others such as the consumer, can refer to it, by means of the bundle identifier. </span></p> 
 
-<p>While URIs are the Web mechanism by which entities can be assigned identities, URIs alone are not sufficient for our purpose. Indeed, the entity produced by the producer is given a URI, but the same entity, with the same URI, could also be described in other bundles, by this producer or third parties. It is the capability of referring to the description of the entity, as created by the producer in this specific bundle, that is of interest to us in this specification. </p>
+<p>While URIs are the Web mechanism by which entities can be assigned identities, URIs alone are not sufficient for our purpose. Indeed, the entity produced by the producer is given a URI, but the same entity, with the same URI, could also be described in other bundles, by this producer or third parties. It is the capability of referring to the description of the entity, as created by the producer in <span class="delete">this </span><span class="insert">a </span><em>specific <span class="delete">bundle,</span><span class="insert">bundle</span></em><span class="insert">,</span> that is of interest to us in this specification. </p>
 
 <p>This <span class="delete">document</span><span class="insert">specification</span> introduces a new concept <a href="#concept-mention" class="internalDFN">Mention</a> allowing an entity to be described as the specialization of another entity, itself described in another bundle. <span class="delete">The document</span><span class="insert">This specification</span> provides not only a conceptual definition  of <a href="#concept-mention" class="internalDFN">Mention</a>, but also the corresponding ontological, schema, and notational definitions, for the various representations of PROV. It also includes constraints that apply to this construct specifically. It is our aim to promote  interoperability by defining <a href="#concept-mention" class="internalDFN">Mention</a> conceptually and in the representations of PROV.</p>
 
@@ -987,8 +988,8 @@
 </p>
 
 <p>Some applications may want to augment
-the descriptions of entity <span class="name">e1</span>  found in  bundle <span class="name">b</span> with other information.<span class="insert"> They
-cannot add these descriptions to bundle </span><span class="name"><span class="insert">b</span></span><span class="insert"> since this would result in a different bundle. </span></p>
+the descriptions of entity <span class="name">e1</span>  found in  <span class="insert"> a </span>bundle <span class="name">b</span> with other information.<span class="insert"> They
+cannot add these descriptions to bundle </span><span class="name"><span class="insert">b</span></span><span class="insert"> since this would result in a different bundle. Alternatively, they may create a new bundle with descriptions from bundle </span><span class="name"><span class="insert">b</span></span><span class="insert"> and novel descriptions, but this results in an undesirable </span><em><span class="insert">copy</span></em><span class="insert"> of the bundle.</span></p>
 
 <p>
 To this end, PROV allows a new entity <span class="name">e2</span> to be created and defined as a specialization of the preceding entity <span class="name">e1</span>, and which presents at least an additional aspect:  the bundle <span class="name">b</span> containing some descriptions of <span class="name">e1</span>.  With this relation, applications that process <span class="name">e2</span>
@@ -1075,16 +1076,25 @@
 
 
 
+<p>
+We note that<span class="delete"> the concept </span><span class="delete">Mention</span><span class="delete"> is an extension of [</span><span class="delete">PROV-DM</span><span class="delete">], and therefore has to be prefixed,
+</span>  <span class="name">prov:mentionOf</span><span class="delete">, according the extensibility
+rules of the provenance notation [</span><span class="delete">PROV-N</span><span class="delete">].</span>
 
 
-<p>We note that the concept <a href="#concept-mention" class="internalDFN">Mention</a> is an extension of<span class="insert"> the PROV data model</span> [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite><span class="delete">], and therefore</span><span class="insert">]; therefore, its textual notation</span> has to be prefixed,
-<span class="name">prov:mentionOf</span>, according the extensibility
-rules of the provenance notation [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>].</p>
+<span class="delete">
+Let</span><span class="insert"> cannot be inferred from Specialization. Indeed,
+let</span> us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle.   The entity <span class="name">e1</span> may <span class="insert">be </span>described in multiple other <span class="delete">bundle</span><span class="insert">bundles</span> <span class="name">b<sub>i</sub></span>.
+From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">prov:mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which  <span class="name">b<sub>i</sub></span>'s descriptions were used to <span class="delete">computed</span><span class="insert">compute</span> additional aspects of   <span class="name">e2</span>. Hence, <span class="name">prov:mentionOf</span> has to be asserted. </p>
 
 
-<p>
-Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle.   The entity <span class="name">e1</span> may described in multiple other bundle <span class="name">b<sub>i</sub></span>.
-From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">prov:mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which  <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of   <span class="name">e2</span>. Hence, <span class="name">prov:mentionOf</span> has to be asserted. </p>
+
+
+<p><span class="insert">We note that the concept </span><a href="#concept-mention" class="internalDFN"><span class="insert">Mention</span></a><span class="insert"> is an extension of the PROV data model [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]; therefore, its textual notation has to be prefixed,
+</span><span class="name"><span class="insert">prov:mentionOf</span></span><span class="insert">, according the extensibility
+rules of the provenance notation [</span><cite><a class="bibref" href="#bib-PROV-N"><span class="insert">PROV-N</span></a></cite><span class="insert">].</span></p>
+
+
 
 <p><a href="#mention-constraints" class="section-ref"><span>Section 5.</span></a> presents constraints applicable to <a href="#concept-mention" class="internalDFN">Mention</a>, and in particular, the fact that an entity can be a <a href="#mention.specificEntity">specific entity</a> of a <a href="#concept-mention" class="internalDFN">Mention</a> at most once.</p>
 
@@ -1119,7 +1129,7 @@
 
 
 <div class="anexample" id="aexample-mention-viz"><div class="anexampleTitle">Example 2<sup><a class="internalDFN" href="#aexample-mention-viz"><span class="diamond"> ◊</span></a></sup></div>
-<p>Consider the following bundle of <span class="delete">descriptions, in which derivation and generations have been identified.</span><span class="insert">descriptions.</span>
+<p>Consider the following bundle of <span class="delete">descriptions, in which derivation and generations have been identified.</span><span class="insert">descriptions.  It describes how </span><span class="name"><span class="insert">ex:report2</span></span><span class="insert"> was derived from </span><span class="name"><span class="insert">ex:report1</span></span><span class="insert">.</span>
 </p><pre class="codeexample"> 
 bundle obs:bundle1
   entity(ex:report1, [ prov:type="report", ex:version=1 ])
@@ -1128,10 +1138,13 @@
   <span class="delete">wasGeneratedBy(ex:g2; ex:report2,</span><span class="insert">wasGeneratedBy(ex:report2,</span> -, 2012-05-25T11:00:01)
   wasDerivedFrom(ex:report2, ex:report1)
 endBundle
+</pre><span class="insert">
+Bundle </span><span class="name"><span class="insert">obs:bundle1</span></span><span class="insert"> was attributed to agent </span><span class="name"><span class="insert">ex:observer01</span></span><span class="insert">, as described by the following:
+</span><pre class="codeexample"> 
 entity(obs:bundle1, [ prov:type='prov:Bundle' ])
 wasAttributedTo(obs:bundle1, ex:observer01)
 </pre>
-Bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may useful for the visualization layout of 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.
+<span class="delete">Bundle</span><span class="insert">Let us assume that bundle</span> <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may<span class="insert"> be</span> useful for the visualization layout of 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:bundle2
   entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
@@ -1181,7 +1194,8 @@
 
 
     <div class="description">
-      <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
+      <div class="comment "><p><span class="delete">When :x</span> prov:mentionOf <span class="delete">:y and :y </span>is <span class="insert">used to specialize an entity as </span>described in <span class="delete">Bundle :b, the triple :x prov:asInBundle :b</span><span class="insert">another
+bundle. It</span> is <span class="delete">also asserted </span>to <span class="delete">cite the Bundle</span><span class="insert">be used</span> in <span class="delete">which :y was described.</span><span class="insert">conjuction with prov:asInBundle. </span></p>
       </div>
       <div class="comment "><p>prov:asInBundle is used to cite the Bundle in which the generalization was mentioned.</p>
       </div>
@@ -1226,6 +1240,9 @@
 
 
     <div class="description">
+      <div class="comment "><p><span class="insert">prov:asInBundle is used to specify which bundle the general entity of a
+ prov:mentionOf property is described. </span></p>
+      </div>
       <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
       </div>
       <dl>
@@ -1511,16 +1528,16 @@
 
  
 
-<section id="references" class="appendix"><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
-</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</span></a>
-</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
-</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</span></a>
-</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-n-20130430/</span></a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-o-20130430/</span></a>
-</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</span></a>
-</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-sem-20130312</span><a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</span></a>.
-</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</span></a>
+<section id="references" class="appendix"><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
+</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</span></a>
+</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</span></a>
+</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-n-20130430/</span></a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-o-20130430/</span></a>
+</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
+</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</span></a>
+</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-sem-20130312</span><a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</span></a>.
+</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</span></a>
 </dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 
 </dd></dl></section></section></body></html>
--- a/links/prov-links.html	Mon Apr 08 21:34:35 2013 +0100
+++ b/links/prov-links.html	Mon Apr 08 22:11:00 2013 +0100
@@ -786,7 +786,7 @@
 represented in various ways, and interchanged between systems across the Web. 
 </p>
 
-<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it.  To support this, provenance itself should be trusted, and therefore, provenance of provenance is itself an important aspect of establishing trust in an information infrastructure such as the Web. To this end, PROV introduces the concept of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-bundle">Bundle</a>: defined as a named set of provenance descriptions;  it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Bundle">Bundle</a> [[PROV-O]], <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-bundle">Bundle</a> [[PROV-N]] and <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/#term-Bundle">Bundle</a> [[PROV-XML]]). With bundles, blobs of provenance descriptions can be given names and can themselves be regarded as entities, whose provenance can in turn be described using PROV. These blobs of provenance descriptions stand independently of each other, as formalized by [[PROV-CONSTRAINTS]] which determines their <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#bundle-constraints">validity</a> by examining them in isolation of each other. </p>
+<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it.  To support this, provenance itself should be trusted, and therefore, provenance of provenance is itself an important aspect of establishing trust in an information infrastructure such as the Web. To this end, PROV introduces the concept of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-bundle">Bundle</a>: defined as a named set of provenance descriptions;  it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Bundle">Bundle</a> [[PROV-O]], <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-bundle">Bundle</a> [[PROV-N]] and <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/#term-Bundle">Bundle</a> [[PROV-XML]]). With bundles, sets of provenance descriptions can be given names and can themselves be regarded as entities, whose provenance can in turn be described using PROV. These sets of provenance descriptions stand independently of each other, as formalized by [[PROV-CONSTRAINTS]] which determines their <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#bundle-constraints">validity</a> by examining them in isolation of each other. </p>
 
 
 <p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party (a producer) creates some data and its provenance, whereas another party (a consumer) consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by the
@@ -827,8 +827,8 @@
 Other bundles may contain other descriptions about the same entity <span class="name">e1</span>.</p>
 
 <p>Some applications may want to augment
-the descriptions of entity <span class="name">e1</span>  found in  bundle <span class="name">b</span> with other information. They
-cannot add these descriptions to bundle <span class="name">b</span> since this would result in a different bundle. </p>
+the descriptions of entity <span class="name">e1</span>  found in a bundle <span class="name">b</span> with other information. They
+cannot add these descriptions to bundle <span class="name">b</span> since this would result in a different bundle. Alternatively, they may create a new bundle with descriptions from bundle <span class="name">b</span> and novel descriptions, but this results in an undesirable <em>copy</em> of the bundle.</p>
 
 <p>
 To this end, PROV allows a new entity <span class="name">e2</span> to be created and defined as a specialization of the preceding entity <span class="name">e1</span>, and which presents at least an additional aspect:  the bundle <span class="name">b</span> containing some descriptions of <span class="name">e1</span>.  With this relation, applications that process <span class="name">e2</span>
@@ -913,6 +913,10 @@
 </div>
 
 
+<p>
+We note that  <span class="name">prov:mentionOf</span> cannot be inferred from Specialization. Indeed,
+let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle.   The entity <span class="name">e1</span> may be described in multiple other bundles <span class="name">b<sub>i</sub></span>.
+From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">prov:mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which  <span class="name">b<sub>i</sub></span>'s descriptions were used to compute additional aspects of   <span class="name">e2</span>. Hence, <span class="name">prov:mentionOf</span> has to be asserted. </p>
 
 
 <p>We note that the concept <a>Mention</a> is an extension of the PROV data model [[PROV-DM]]; therefore, its textual notation has to be prefixed,
@@ -920,9 +924,6 @@
 rules of the provenance notation [[PROV-N]].</p>
 
 
-<p>
-Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle.   The entity <span class="name">e1</span> may described in multiple other bundle <span class="name">b<sub>i</sub></span>.
-From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">prov:mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which  <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of   <span class="name">e2</span>. Hence, <span class="name">prov:mentionOf</span> has to be asserted. </p>
 
 <p><a href="#mention-constraints" class="section-ref"><span>TBD</span></a> presents constraints applicable to <a>Mention</a>, and in particular, the fact that an entity can be a <a href="#mention.specificEntity">specific entity</a> of a <a>Mention</a> at most once.</p>
 
@@ -959,7 +960,7 @@
 
 
 <div class="anexample" id="aexample-mention-viz">
-<p>Consider the following bundle of descriptions.
+<p>Consider the following bundle of descriptions.  It describes how <span class="name">ex:report2</span> was derived from <span class="name">ex:report1</span>.
 <pre class="codeexample"> 
 bundle obs:bundle1
   entity(ex:report1, [ prov:type="report", ex:version=1 ])
@@ -968,10 +969,13 @@
   wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
   wasDerivedFrom(ex:report2, ex:report1)
 endBundle
+</pre>
+Bundle <span class="name">obs:bundle1</span> was attributed to agent <span class="name">ex:observer01</span>, as described by the following:
+<pre class="codeexample"> 
 entity(obs:bundle1, [ prov:type='prov:Bundle' ])
 wasAttributedTo(obs:bundle1, ex:observer01)
 </pre>
-Bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may useful for the visualization layout of 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.
+Let us assume that bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may be useful for the visualization layout of 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:bundle2
   entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
@@ -1021,7 +1025,8 @@
 
 
     <div class="description">
-      <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
+      <div class="comment "><p> prov:mentionOf is used to specialize an entity as described in another
+bundle. It is to be used in conjuction with prov:asInBundle. </p>
       </div>
       <div class="comment "><p>prov:asInBundle is used to cite the Bundle in which the generalization was mentioned.</p>
       </div>
@@ -1066,6 +1071,9 @@
 
 
     <div class="description">
+      <div class="comment "><p>prov:asInBundle is used to specify which bundle the general entity of a
+ prov:mentionOf property is described. </p>
+      </div>
       <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
       </div>
       <dl>
--- a/links/releases/NOTE-prov-links-20130430/Overview.html	Mon Apr 08 21:34:35 2013 +0100
+++ b/links/releases/NOTE-prov-links-20130430/Overview.html	Mon Apr 08 22:11:00 2013 +0100
@@ -921,12 +921,13 @@
 represented in various ways, and interchanged between systems across the Web. 
 </p>
 
-<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it.  To support this, provenance itself should be trusted, and therefore, provenance of provenance is itself a critical aspect of an information infrastructure such as the Web. To this end, PROV introduces the concept of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-bundle">Bundle</a>: defined as a named set of provenance descriptions;  it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>], <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] and <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/#term-Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>]). With bundles, blobs of provenance descriptions can be given names and can themselves be regarded as entities, whose provenance can in turn be described using PROV. These blobs of provenance descriptions are independent of each other, as formalized by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#bundle-constraints">validity</a> by examining them in isolation of each other. </p>
+<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it.  To support this, provenance itself should be trusted, and therefore, provenance of provenance is itself an important aspect of establishing trust in an information infrastructure such as the Web. To this end, PROV introduces the concept of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-bundle">Bundle</a>: defined as a named set of provenance descriptions;  it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>], <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>] and <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/#term-Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>]). With bundles, sets of provenance descriptions can be given names and can themselves be regarded as entities, whose provenance can in turn be described using PROV. These sets of provenance descriptions stand independently of each other, as formalized by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#bundle-constraints">validity</a> by examining them in isolation of each other. </p>
 
 
-<p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party creates some data and its provenance, whereas another party consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by another producer.  For the consumer, it is not suitable to repeat the provenance created by the producer, and augment it according to their need. Instead, a consumer wants to <em>refer</em> to the description as created by the producer <em>in situ</em>, i.e. in its bundle, and <em>specialize it</em>, allowing the consumer to add their own view on this entity. Such a capability would allow parties to "stitch together" provenance descriptions that would otherwise be disconnected.</p> 
+<p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party (a producer) creates some data and its provenance, whereas another party (a consumer) consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by the
+ producer.  For the consumer, it is not suitable to repeat the provenance created by the producer, and augment it according to their need. Instead, a consumer wants to <em>refer</em> to the description as created by the producer <em>in situ</em> and <em>specialize it</em>, allowing the consumer to add their own view on this entity. (The notion of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-specialization">specialization</a> is defined in [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>].) Such a capability would allow parties to "stitch together" provenance descriptions that would otherwise be disconnected. For this to work, this specification assume that provenance created by the producer is contained in a bundle, so that others such as the consumer, can refer to it, by means of the bundle identifier. </p> 
 
-<p>While URIs are the Web mechanism by which entities can be assigned identities, URIs alone are not sufficient for our purpose. Indeed, the entity produced by the producer is given a URI, but the same entity, with the same URI, could also be described in other bundles, by this producer or third parties. It is the capability of referring to the description of the entity, as created by the producer in this specific bundle, that is of interest to us in this specification. </p>
+<p>While URIs are the Web mechanism by which entities can be assigned identities, URIs alone are not sufficient for our purpose. Indeed, the entity produced by the producer is given a URI, but the same entity, with the same URI, could also be described in other bundles, by this producer or third parties. It is the capability of referring to the description of the entity, as created by the producer in a <em>specific bundle</em>, that is of interest to us in this specification. </p>
 
 <p>This specification introduces a new concept <a href="#concept-mention" class="internalDFN">Mention</a> allowing an entity to be described as the specialization of another entity, itself described in another bundle. This specification provides not only a conceptual definition  of <a href="#concept-mention" class="internalDFN">Mention</a>, but also the corresponding ontological, schema, and notational definitions, for the various representations of PROV. It also includes constraints that apply to this construct specifically. It is our aim to promote  interoperability by defining <a href="#concept-mention" class="internalDFN">Mention</a> conceptually and in the representations of PROV.</p>
 
@@ -962,8 +963,8 @@
 Other bundles may contain other descriptions about the same entity <span class="name">e1</span>.</p>
 
 <p>Some applications may want to augment
-the descriptions of entity <span class="name">e1</span>  found in  bundle <span class="name">b</span> with other information. They
-cannot add these descriptions to bundle <span class="name">b</span> since this would result in a different bundle. </p>
+the descriptions of entity <span class="name">e1</span>  found in a bundle <span class="name">b</span> with other information. They
+cannot add these descriptions to bundle <span class="name">b</span> since this would result in a different bundle. Alternatively, they may create a new bundle with descriptions from bundle <span class="name">b</span> and novel descriptions, but this results in an undesirable <em>copy</em> of the bundle.</p>
 
 <p>
 To this end, PROV allows a new entity <span class="name">e2</span> to be created and defined as a specialization of the preceding entity <span class="name">e1</span>, and which presents at least an additional aspect:  the bundle <span class="name">b</span> containing some descriptions of <span class="name">e1</span>.  With this relation, applications that process <span class="name">e2</span>
@@ -1048,6 +1049,10 @@
 </div>
 
 
+<p>
+We note that  <span class="name">prov:mentionOf</span> cannot be inferred from Specialization. Indeed,
+let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle.   The entity <span class="name">e1</span> may be described in multiple other bundles <span class="name">b<sub>i</sub></span>.
+From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">prov:mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which  <span class="name">b<sub>i</sub></span>'s descriptions were used to compute additional aspects of   <span class="name">e2</span>. Hence, <span class="name">prov:mentionOf</span> has to be asserted. </p>
 
 
 <p>We note that the concept <a href="#concept-mention" class="internalDFN">Mention</a> is an extension of the PROV data model [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]; therefore, its textual notation has to be prefixed,
@@ -1055,9 +1060,6 @@
 rules of the provenance notation [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>].</p>
 
 
-<p>
-Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle.   The entity <span class="name">e1</span> may described in multiple other bundle <span class="name">b<sub>i</sub></span>.
-From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">prov:mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which  <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of   <span class="name">e2</span>. Hence, <span class="name">prov:mentionOf</span> has to be asserted. </p>
 
 <p><a href="#mention-constraints" class="section-ref"><span>Section 5.</span></a> presents constraints applicable to <a href="#concept-mention" class="internalDFN">Mention</a>, and in particular, the fact that an entity can be a <a href="#mention.specificEntity">specific entity</a> of a <a href="#concept-mention" class="internalDFN">Mention</a> at most once.</p>
 
@@ -1092,7 +1094,7 @@
 
 
 <div class="anexample" id="aexample-mention-viz"><div class="anexampleTitle">Example 2<sup><a class="internalDFN" href="#aexample-mention-viz"><span class="diamond"> ◊</span></a></sup></div>
-<p>Consider the following bundle of descriptions.
+<p>Consider the following bundle of descriptions.  It describes how <span class="name">ex:report2</span> was derived from <span class="name">ex:report1</span>.
 </p><pre class="codeexample"> 
 bundle obs:bundle1
   entity(ex:report1, [ prov:type="report", ex:version=1 ])
@@ -1101,10 +1103,13 @@
   wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
   wasDerivedFrom(ex:report2, ex:report1)
 endBundle
+</pre>
+Bundle <span class="name">obs:bundle1</span> was attributed to agent <span class="name">ex:observer01</span>, as described by the following:
+<pre class="codeexample"> 
 entity(obs:bundle1, [ prov:type='prov:Bundle' ])
 wasAttributedTo(obs:bundle1, ex:observer01)
 </pre>
-Bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may useful for the visualization layout of 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.
+Let us assume that bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may be useful for the visualization layout of 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:bundle2
   entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
@@ -1154,7 +1159,8 @@
 
 
     <div class="description">
-      <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
+      <div class="comment "><p> prov:mentionOf is used to specialize an entity as described in another
+bundle. It is to be used in conjuction with prov:asInBundle. </p>
       </div>
       <div class="comment "><p>prov:asInBundle is used to cite the Bundle in which the generalization was mentioned.</p>
       </div>
@@ -1199,6 +1205,9 @@
 
 
     <div class="description">
+      <div class="comment "><p>prov:asInBundle is used to specify which bundle the general entity of a
+ prov:mentionOf property is described. </p>
+      </div>
       <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
       </div>
       <dl>
@@ -1479,16 +1488,16 @@
 
  
 
-<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
-</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 Avril 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
-</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
-</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 Avril 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
-</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 Avril 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. 30 Avril 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">http://www.w3.org/TR/2013/REC-prov-o-20130430/</a>
-</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</a>
-</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</a>.
-</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. 30 Avril 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</a>
+<section id="references" class="appendix"><!--OddPage--><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</a>
+</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</a>
+</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</a>
+</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</a>
+</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/">http://www.w3.org/TR/2013/REC-prov-n-20130430/</a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. 30 April 2013, W3C Recommendation. URL: <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/">http://www.w3.org/TR/2013/REC-prov-o-20130430/</a>
+</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</a>
+</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</a>
+</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</a>.
+</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. 30 April 2013, W3C Note. URL: <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</a>
 </dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 
 </dd></dl></section></section></body></html>
\ No newline at end of file
--- a/links/releases/NOTE-prov-links-20130430/diff.html	Mon Apr 08 21:34:35 2013 +0100
+++ b/links/releases/NOTE-prov-links-20130430/diff.html	Mon Apr 08 22:11:00 2013 +0100
@@ -945,12 +945,13 @@
 represented in various <span class="delete">representations,</span><span class="insert">ways,</span> and interchanged between systems across the Web. 
 </p>
 
-<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it.  To support this, provenance itself should be trusted, and therefore, provenance of provenance is itself a critical aspect of an information infrastructure such as the Web. To this end, PROV introduces the concept of <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-bundle">Bundle</a>: defined as a<span class="insert"> named</span> set of provenance descriptions;  it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite><span class="insert">], </span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-bundle"><span class="insert">Bundle</span></a><span class="insert"> [</span><cite><a class="bibref" href="#bib-PROV-N"><span class="insert">PROV-N</span></a></cite>] and <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/#term-Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>]). With bundles, blobs of provenance descriptions can be given names and can themselves be regarded as entities, whose provenance can in turn be described using PROV. These blobs of provenance descriptions are independent of each other, as formalized by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#bundle-constraints">validity</a> by examining them in isolation of each other. </p>
+<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it.  To support this, provenance itself should be trusted, and therefore, provenance of provenance is itself <span class="insert">an important aspect of establishing trust in an information infrastructure such as the Web. To this end, PROV introduces the concept of </span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-bundle"><span class="insert">Bundle</span></a><span class="insert">: defined as </span>a <span class="delete">critical aspect of an information infrastructure such as the Web. To this end, PROV introduces the concept of </span><span class="delete">Bundle</span><span class="delete">: defined as a</span><span class="insert">named</span> set of provenance descriptions;  it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite><span class="insert">], </span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/#prod-bundle"><span class="insert">Bundle</span></a><span class="insert"> [</span><cite><a class="bibref" href="#bib-PROV-N"><span class="insert">PROV-N</span></a></cite>] and <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/#term-Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>]). With bundles, <span class="delete">blobs</span><span class="insert">sets</span> of provenance descriptions can be given names and can themselves be regarded as entities, whose provenance can in turn be described using PROV. These <span class="delete">blobs</span><span class="insert">sets</span> of provenance descriptions <span class="delete">are independent</span><span class="insert">stand independently</span> of each other, as formalized by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/#bundle-constraints">validity</a> by examining them in isolation of each other. </p>
 
 
-<p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party creates some data and its provenance, whereas another party consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by another producer.  For the consumer, it is not suitable to repeat the provenance created by the producer, and augment it according to their need. Instead, a consumer wants to <em>refer</em> to the description as created by the producer <em>in situ</em>, i.e. in its bundle, and <em>specialize it</em>, allowing the consumer to add their own view on this entity. Such a capability would allow parties to "stitch together" provenance descriptions that would otherwise be disconnected.</p> 
+<p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party <span class="insert">(a producer) </span>creates some data and its provenance, whereas another party <span class="insert">(a consumer) </span>consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by <span class="delete">another </span><span class="insert">the
+ </span>producer.  For the consumer, it is not suitable to repeat the provenance created by the producer, and augment it according to their need. Instead, a consumer wants to <em>refer</em> to the description as created by the producer <em>in situ</em><span class="delete">, i.e. in its bundle,</span> and <em>specialize it</em>, allowing the consumer to add their own view on this entity. <span class="insert">(The notion of </span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/#concept-specialization"><span class="insert">specialization</span></a><span class="insert"> is defined in [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">].) </span>Such a capability would allow parties to "stitch together" provenance descriptions that would otherwise be disconnected.<span class="insert"> For this to work, this specification assume that provenance created by the producer is contained in a bundle, so that others such as the consumer, can refer to it, by means of the bundle identifier. </span></p> 
 
-<p>While URIs are the Web mechanism by which entities can be assigned identities, URIs alone are not sufficient for our purpose. Indeed, the entity produced by the producer is given a URI, but the same entity, with the same URI, could also be described in other bundles, by this producer or third parties. It is the capability of referring to the description of the entity, as created by the producer in this specific bundle, that is of interest to us in this specification. </p>
+<p>While URIs are the Web mechanism by which entities can be assigned identities, URIs alone are not sufficient for our purpose. Indeed, the entity produced by the producer is given a URI, but the same entity, with the same URI, could also be described in other bundles, by this producer or third parties. It is the capability of referring to the description of the entity, as created by the producer in <span class="delete">this </span><span class="insert">a </span><em>specific <span class="delete">bundle,</span><span class="insert">bundle</span></em><span class="insert">,</span> that is of interest to us in this specification. </p>
 
 <p>This <span class="delete">document</span><span class="insert">specification</span> introduces a new concept <a href="#concept-mention" class="internalDFN">Mention</a> allowing an entity to be described as the specialization of another entity, itself described in another bundle. <span class="delete">The document</span><span class="insert">This specification</span> provides not only a conceptual definition  of <a href="#concept-mention" class="internalDFN">Mention</a>, but also the corresponding ontological, schema, and notational definitions, for the various representations of PROV. It also includes constraints that apply to this construct specifically. It is our aim to promote  interoperability by defining <a href="#concept-mention" class="internalDFN">Mention</a> conceptually and in the representations of PROV.</p>
 
@@ -987,8 +988,8 @@
 </p>
 
 <p>Some applications may want to augment
-the descriptions of entity <span class="name">e1</span>  found in  bundle <span class="name">b</span> with other information.<span class="insert"> They
-cannot add these descriptions to bundle </span><span class="name"><span class="insert">b</span></span><span class="insert"> since this would result in a different bundle. </span></p>
+the descriptions of entity <span class="name">e1</span>  found in  <span class="insert"> a </span>bundle <span class="name">b</span> with other information.<span class="insert"> They
+cannot add these descriptions to bundle </span><span class="name"><span class="insert">b</span></span><span class="insert"> since this would result in a different bundle. Alternatively, they may create a new bundle with descriptions from bundle </span><span class="name"><span class="insert">b</span></span><span class="insert"> and novel descriptions, but this results in an undesirable </span><em><span class="insert">copy</span></em><span class="insert"> of the bundle.</span></p>
 
 <p>
 To this end, PROV allows a new entity <span class="name">e2</span> to be created and defined as a specialization of the preceding entity <span class="name">e1</span>, and which presents at least an additional aspect:  the bundle <span class="name">b</span> containing some descriptions of <span class="name">e1</span>.  With this relation, applications that process <span class="name">e2</span>
@@ -1075,16 +1076,25 @@
 
 
 
+<p>
+We note that<span class="delete"> the concept </span><span class="delete">Mention</span><span class="delete"> is an extension of [</span><span class="delete">PROV-DM</span><span class="delete">], and therefore has to be prefixed,
+</span>  <span class="name">prov:mentionOf</span><span class="delete">, according the extensibility
+rules of the provenance notation [</span><span class="delete">PROV-N</span><span class="delete">].</span>
 
 
-<p>We note that the concept <a href="#concept-mention" class="internalDFN">Mention</a> is an extension of<span class="insert"> the PROV data model</span> [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite><span class="delete">], and therefore</span><span class="insert">]; therefore, its textual notation</span> has to be prefixed,
-<span class="name">prov:mentionOf</span>, according the extensibility
-rules of the provenance notation [<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>].</p>
+<span class="delete">
+Let</span><span class="insert"> cannot be inferred from Specialization. Indeed,
+let</span> us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle.   The entity <span class="name">e1</span> may <span class="insert">be </span>described in multiple other <span class="delete">bundle</span><span class="insert">bundles</span> <span class="name">b<sub>i</sub></span>.
+From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">prov:mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which  <span class="name">b<sub>i</sub></span>'s descriptions were used to <span class="delete">computed</span><span class="insert">compute</span> additional aspects of   <span class="name">e2</span>. Hence, <span class="name">prov:mentionOf</span> has to be asserted. </p>
 
 
-<p>
-Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle.   The entity <span class="name">e1</span> may described in multiple other bundle <span class="name">b<sub>i</sub></span>.
-From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">prov:mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which  <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of   <span class="name">e2</span>. Hence, <span class="name">prov:mentionOf</span> has to be asserted. </p>
+
+
+<p><span class="insert">We note that the concept </span><a href="#concept-mention" class="internalDFN"><span class="insert">Mention</span></a><span class="insert"> is an extension of the PROV data model [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">]; therefore, its textual notation has to be prefixed,
+</span><span class="name"><span class="insert">prov:mentionOf</span></span><span class="insert">, according the extensibility
+rules of the provenance notation [</span><cite><a class="bibref" href="#bib-PROV-N"><span class="insert">PROV-N</span></a></cite><span class="insert">].</span></p>
+
+
 
 <p><a href="#mention-constraints" class="section-ref"><span>Section 5.</span></a> presents constraints applicable to <a href="#concept-mention" class="internalDFN">Mention</a>, and in particular, the fact that an entity can be a <a href="#mention.specificEntity">specific entity</a> of a <a href="#concept-mention" class="internalDFN">Mention</a> at most once.</p>
 
@@ -1119,7 +1129,7 @@
 
 
 <div class="anexample" id="aexample-mention-viz"><div class="anexampleTitle">Example 2<sup><a class="internalDFN" href="#aexample-mention-viz"><span class="diamond"> ◊</span></a></sup></div>
-<p>Consider the following bundle of <span class="delete">descriptions, in which derivation and generations have been identified.</span><span class="insert">descriptions.</span>
+<p>Consider the following bundle of <span class="delete">descriptions, in which derivation and generations have been identified.</span><span class="insert">descriptions.  It describes how </span><span class="name"><span class="insert">ex:report2</span></span><span class="insert"> was derived from </span><span class="name"><span class="insert">ex:report1</span></span><span class="insert">.</span>
 </p><pre class="codeexample"> 
 bundle obs:bundle1
   entity(ex:report1, [ prov:type="report", ex:version=1 ])
@@ -1128,10 +1138,13 @@
   <span class="delete">wasGeneratedBy(ex:g2; ex:report2,</span><span class="insert">wasGeneratedBy(ex:report2,</span> -, 2012-05-25T11:00:01)
   wasDerivedFrom(ex:report2, ex:report1)
 endBundle
+</pre><span class="insert">
+Bundle </span><span class="name"><span class="insert">obs:bundle1</span></span><span class="insert"> was attributed to agent </span><span class="name"><span class="insert">ex:observer01</span></span><span class="insert">, as described by the following:
+</span><pre class="codeexample"> 
 entity(obs:bundle1, [ prov:type='prov:Bundle' ])
 wasAttributedTo(obs:bundle1, ex:observer01)
 </pre>
-Bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may useful for the visualization layout of 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.
+<span class="delete">Bundle</span><span class="insert">Let us assume that bundle</span> <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may<span class="insert"> be</span> useful for the visualization layout of 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:bundle2
   entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
@@ -1181,7 +1194,8 @@
 
 
     <div class="description">
-      <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
+      <div class="comment "><p><span class="delete">When :x</span> prov:mentionOf <span class="delete">:y and :y </span>is <span class="insert">used to specialize an entity as </span>described in <span class="delete">Bundle :b, the triple :x prov:asInBundle :b</span><span class="insert">another
+bundle. It</span> is <span class="delete">also asserted </span>to <span class="delete">cite the Bundle</span><span class="insert">be used</span> in <span class="delete">which :y was described.</span><span class="insert">conjuction with prov:asInBundle. </span></p>
       </div>
       <div class="comment "><p>prov:asInBundle is used to cite the Bundle in which the generalization was mentioned.</p>
       </div>
@@ -1226,6 +1240,9 @@
 
 
     <div class="description">
+      <div class="comment "><p><span class="insert">prov:asInBundle is used to specify which bundle the general entity of a
+ prov:mentionOf property is described. </span></p>
+      </div>
       <div class="comment "><p>When :x prov:mentionOf :y and :y is described in Bundle :b, the triple :x prov:asInBundle :b is also asserted to cite the Bundle in which :y was described.</p>
       </div>
       <dl>
@@ -1511,16 +1528,16 @@
 
  
 
-<section id="references" class="appendix"><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
-</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</span></a>
-</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
-</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
-</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</span></a>
-</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-n-20130430/</span></a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-o-20130430/</span></a>
-</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</span></a>
-</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-sem-20130312</span><a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</span></a>.
-</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. <span class="delete">12 March</span><span class="insert">30 Avril</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</span></a>
+<section id="references" class="appendix"><h2><span class="secno">C. </span>References</h2><section id="informative-references"><h3><span class="secno">C.1 </span>Informative references</h3><dl class="bibliography"><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>Graham Klyne; Paul Groth; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><cite>Provenance Access and Query</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-aq-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-aq-20130430/</span></a>
+</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>James Cheney; Paolo Missier; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><cite>Constraints of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-constraints-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-constraints-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-constraints-20130430/</span></a>
+</dd><dt id="bib-PROV-DC">[PROV-DC]</dt><dd>Daniel Garijo; Kai Eckert; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><cite>Dublin Core to PROV Mapping</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dc-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dc-20130430/</span></a>
+</dd><dt id="bib-PROV-DICTIONARY">[PROV-DICTIONARY]</dt><dd>Tom De Nies; Sam Coppens; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><cite>PROV Dictionary</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-dictionary-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-dictionary-20130430/</span></a>
+</dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><cite>PROV-DM: The PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-dm-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-dm-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-dm-20130430/</span></a>
+</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>Luc Moreau; Paolo Missier; eds. <a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><cite>PROV-N: The Provenance Notation</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-n-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-n-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-n-20130430/</span></a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>Timothy Lebo; Satya Sahoo; Deborah McGuinness; eds. <a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><cite>PROV-O: The PROV Ontology</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, W3C <span class="delete">Proposed </span>Recommendation. URL: <span class="delete">http://www.w3.org/TR/2013/PR-prov-o-20130312/</span><a href="http://www.w3.org/TR/2013/REC-prov-o-20130430/"><span class="insert">http://www.w3.org/TR/2013/REC-prov-o-20130430/</span></a>
+</dd><dt id="bib-PROV-OVERVIEW">[PROV-OVERVIEW]</dt><dd>Paul Groth; Luc Moreau; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><cite>PROV-OVERVIEW: An Overview of the PROV Family of Documents</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-overview-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-overview-20130430/</span></a>
+</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>Yolanda Gil; Simon Miles; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><cite>PROV Model Primer</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-primer-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-primer-20130430/</span></a>
+</dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney; ed. <a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><cite>Semantics of the PROV Data Model</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-sem-20130312</span><a href="http://www.w3.org/TR/2013/NOTE-prov-sem-20130430"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-sem-20130430</span></a>.
+</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>Hook Hua; Curt Tilmes; Stephan Zednik; eds. <a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><cite>PROV-XML: The PROV XML Schema</cite></a>. <span class="delete">12 March</span><span class="insert">30 April</span> 2013, <span class="delete">Working Draft.</span><span class="insert">W3C Note.</span> URL: <span class="delete">http://www.w3.org/TR/2013/WD-prov-xml-20130312/</span><a href="http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/"><span class="insert">http://www.w3.org/TR/2013/NOTE-prov-xml-20130430/</span></a>
 </dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119.  URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a> 
 </dd></dl></section></section></body></html>