--- a/links/prov-links.html Thu Nov 29 16:30:16 2012 +0000
+++ b/links/prov-links.html Thu Nov 29 16:34:30 2012 +0000
@@ -711,10 +711,10 @@
involved in producing a piece of data or thing, which can be used to
form assessments about its quality, reliability or trustworthiness.
<a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/#dfn-bundle">Bundles</a>,
-defined in [[!PROV-DM]] as sets of provenance descriptions, were
+defined in [[PROV-DM]] as sets of provenance descriptions, were
introduced in PROV as the mechanism by which provenance of provenance
can be expressed. Bundles, whose validity is established
-independently of each other [[!PROV-CONSTRAINTS]], are essentially
+independently of each other [[PROV-CONSTRAINTS]], are essentially
independent of each other, acting as islands of provenance
descriptions.
</p>
@@ -734,10 +734,10 @@
<ul>
<li> <a href="http://www.w3.org/TR/2012/WD-prov-overview-20121211/">PROV-OVERVIEW</a> (To be published as Note), an overview of the PROV family of documents [[PROV-OVERVIEW]];</li>
<li> <a href="http://www.w3.org/TR/2012/WD-prov-primer-20121211/">PROV-PRIMER</a> (To be published as Note), a primer for the PROV data model [[PROV-PRIMER]];</li>
-<li> <a href="http://www.w3.org/TR/2012/CR-prov-o-20121211/">PROV-O</a> (Candidate Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [[!PROV-O]];</li>
-<li> <a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/">PROV-DM</a> (Candidate Recommendation), the PROV data model for provenance [[!PROV-DM]];</li>
-<li> <a href="http://www.w3.org/TR/2012/CR-prov-n-20121211/">PROV-N</a> (Candidate Recommendation), a notation for provenance aimed at human consumption [[!PROV-N]];</li>
-<li> <a href="http://www.w3.org/TR/2012/CR-prov-constraints-20121211/">PROV-CONSTRAINTS</a> (Candidate Recommendation), a set of constraints applying to the PROV data model [[!PROV-CONSTRAINTS]];</li>
+<li> <a href="http://www.w3.org/TR/2012/CR-prov-o-20121211/">PROV-O</a> (Candidate Recommendation), the PROV ontology, an OWL2 ontology allowing the mapping of PROV to RDF [[PROV-O]];</li>
+<li> <a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/">PROV-DM</a> (Candidate Recommendation), the PROV data model for provenance [[PROV-DM]];</li>
+<li> <a href="http://www.w3.org/TR/2012/CR-prov-n-20121211/">PROV-N</a> (Candidate Recommendation), a notation for provenance aimed at human consumption [[PROV-N]];</li>
+<li> <a href="http://www.w3.org/TR/2012/CR-prov-constraints-20121211/">PROV-CONSTRAINTS</a> (Candidate Recommendation), a set of constraints applying to the PROV data model [[PROV-CONSTRAINTS]];</li>
<li> <a href="http://www.w3.org/TR/2012/WD-prov-aq-20120619/">PROV-AQ</a> (To be published as Note), the mechanisms for accessing and querying provenance [[PROV-AQ]]; </li>
<li> <a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211/">PROV-XML</a> (To be published as Note), an XML schema for the PROV data model [[PROV-XML]];</li>
<li> <a href="http://www.w3.org/TR/2012/WD-prov-links-20121211/">PROV-LINKS</a> (To be published as Note), introduces a mechanism to link across bundles (this document).</li>
@@ -747,11 +747,11 @@
<ul>
<li>[[PROV-OVERVIEW]] overviews the PROV family of documents. </li>
<li>The primer [[PROV-PRIMER]] is the entry point to PROV offering an introduction to the provenance model.</li>
-<li>The Linked Data and Semantic Web community should focus on [[!PROV-O]] defining PROV classes and properties specified in an OWL2 ontology. For further details, [[!PROV-DM]] and [[!PROV-CONSTRAINTS]] specify the constraints applicable to the data model, and its interpretation. </li>
-<li>The XML community should focus on [[PROV-XML]] defining an XML schema for PROV. Further details can also be found in [[!PROV-DM]] and [[!PROV-CONSTRAINTS]].</li>
+<li>The Linked Data and Semantic Web community should focus on [[PROV-O]] defining PROV classes and properties specified in an OWL2 ontology. For further details, [[PROV-DM]] and [[PROV-CONSTRAINTS]] specify the constraints applicable to the data model, and its interpretation. </li>
+<li>The XML community should focus on [[PROV-XML]] defining an XML schema for PROV. Further details can also be found in [[PROV-DM]] and [[PROV-CONSTRAINTS]].</li>
<li>Developers seeking to retrieve or publish provenance should focus on [[PROV-AQ]].</li>
<li>Readers seeking to implement other PROV serializations
-should focus on [[!PROV-DM]] and [[!PROV-CONSTRAINTS]]. [[!PROV-O]], [[!PROV-N]], and [[PROV-XML]] offer examples of mapping to RDF, text, and XML, respectively.</li>
+should focus on [[PROV-DM]] and [[PROV-CONSTRAINTS]]. [[PROV-O]], [[PROV-N]], and [[PROV-XML]] offer examples of mapping to RDF, text, and XML, respectively.</li>
</ul>
</section>
@@ -768,19 +768,19 @@
<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
+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 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/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 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 illustrated by [[!PROV-CONSTRAINTS]] which determines their <a href="http://www.w3.org/TR/2012/CR-prov-constraints-20121211/#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 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 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 illustrated by [[PROV-CONSTRAINTS]] which determines their <a href="http://www.w3.org/TR/2012/CR-prov-constraints-20121211/#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>This document introduces a new concept <a>Mention</a> allowing an entity to be described as the specialization of another entity, itself described in another bundle. The document provides not only a conceptual definition of <a>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 inter-operability by defining <a>Mention</a> conceptually and in the representations of PROV.</p>
+<p>This document introduces a new concept <a>Mention</a> allowing an entity to be described as the specialization of another entity, itself described in another bundle. The document provides not only a conceptual definition of <a>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>Mention</a> conceptually and in the representations of PROV.</p>
<div class="note">The concept <a>Mention</a> 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.
</div>