--- a/mention/prov-mention.html Mon Nov 26 11:08:57 2012 +0000
+++ b/mention/prov-mention.html Mon Nov 26 11:09:21 2012 +0000
@@ -1039,7 +1039,7 @@
which provenance of provenance can be expressed.</p>
<p>
-In applications where provenance is created by multiple parties over time, it is useful for provenance descriptions of one party to link to provenance descriptions of another party. To address this issue, this document introduces a relation allowing an entity description to be linked to another entity description occurring in another bundle.
+In applications where provenance is created by multiple parties over time, it is useful for provenance descriptions created by one party to link to provenance descriptions created by another party. To address this issue, this document introduces a relation allowing an entity description to be linked to another entity description occurring in another bundle.
</p>
<p>The <a href="http://www.w3.org/TR/2012/WD-prov-overview-20121211/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents.</p>
@@ -1080,8 +1080,57 @@
- <section id="introduction">
- <h2>Introduction</h2>
+<section id="introduction">
+<h2>Introduction</h2>
+
+<p>
+<a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/">Provenance</a>
+is a record that describes the people, institutions, entities, and
+activities involved in producing, influencing, or delivering a piece
+of data or a thing. The specifications [[!PROV-O]], [[!PROV-DM]],
+[[!PROV-N]], and [[PROV-XML]] have respectively defined the PROV
+ontology, the PROV conceptual model, the PROV notation, and the PROV
+XML schema, allowing provenance descriptions to be expressed,
+represented in various representations, 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 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/2012/CR-prov-dm-20121211/#concept-bundle">Bundle</a>: defined as a 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/2012/CR-prov-o-20121211/#Bundle">Bundle</a> [[!PROV-O]] and <a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211/#term-Bundle">Bundle</a> [[PROV-XML]]). With bundles, blobs of provenance descriptions can be given names and can itself be regarded as entities, whose provenance can be described using PROV. </p>
+
+
+<verbatim>
+the key aspect of mention of is that you name the entity and the bundle in which the entity is described. The Bundle IS the specialization. ←
+… without mention, you can still link the entities, but you lose the ability to mention the bundle. ←
+
+Timothy Lebo: mentionOf's power comes in when you don't have control over the entire system. ←
+
+ a lab with multiple documents and multiple people. You just want to mention it, not repeat the provenance. ←
+… it's interesting to provide your own view on the entity that you're using. ←
+
+… as a primary producer, I wont' use mention of, but for anyone that wants to augment my Entiteis, they need mentionOf to do it. ←
+
+Curt Tilmes: when yoiu do your own provenance, you ond't need it, but metnionOf lets you "reach into" someone else's bundle. ←
+
+Hook Hua: having it formally in DM would uniformly manifest implementations in different encodigns. we're not relying on serializations to do the linking. ←
+
+
+Graham Klyne: in IETF, "experimental track", mention of is in this. ←
+
+Curt Tilmes: the key is not provenance expression/represtionation, ti's for analysis. ←
+
+
+Hook Hua: it is very important. ←
+
+… each bundle is handled by different institutions, gov entities. ←
+
+… interop is key here. ←
+
+Curt Tilmes: we have a lot of cases where data is processed, then next org processes. each uses their own bundles. ←
+
+… each needs a way to reference across those bundles. ←
+
+… seems that mentionOf provides a capability that will be needed at some point. ←
+
+</verbatim>
</section>
@@ -1095,7 +1144,7 @@
<p>An entity <span class="name">e1</span> may be mentioned in a bundle <span class="name">b</span>, which contains some
descriptions about this entity <span class="name">e1</span>: how <span class="name">e1</span> was generated and used, which activities <span class="name">e1</span> is involved with, the agents <span class="name">e1</span> is attributed to, etc. Other bundles may contain other descriptions about the same entity <span class="name">e1</span>.
Some applications may want to interpret
-this entity <span class="name">e1</span> with respect to the descriptions found in the bundle <span class="name">b</span> it occurs in. To this end, PROV allows a new entity <span class="name">e2</span> to be created, which is a specialization of the preceding entity <span class="name">e1</span>, and which presents 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>
+the latter descriptions of entity <span class="name">e1</span> with respect to the descriptions found in the bundle <span class="name">b</span> it occurs in. To this end, PROV allows a new entity <span class="name">e2</span> to be created, which is a specialization of the preceding entity <span class="name">e1</span>, and which presents 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>
can know that the attributes of <span class="name">e2</span> may have been computed according to the descriptions of <span class="name">e1</span> in <span class="name">b</span>.</p>