--- a/links/diff.html Tue Mar 26 21:45:36 2013 +0000
+++ b/links/diff.html Thu Mar 28 10:39:42 2013 +0000
@@ -921,7 +921,7 @@
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#term-mention" class="tocxref"><span class="secno">2. </span>Conceptual Definition of Mention</a></li><li class="tocline"><a href="#mention-ontology" class="tocxref"><span class="secno">3. </span>Ontological Definition of Mention</a></li><li class="tocline"><a href="#mention-xml" class="tocxref"><span class="secno">4. </span>XML Schema for Mention</a></li><li class="tocline"><a href="#mention-constraints" class="tocxref"><span class="secno">5. </span>Constraints associated with Mention</a></li><li class="tocline"><a href="#change-log-since-first-public-working-draft" class="tocxref"><span class="secno">A. </span>Change Log Since First Public Working Draft</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">B. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#term-mention" class="tocxref"><span class="secno">2. </span>Conceptual Definition of Mention</a></li><li class="tocline"><a href="#mention-ontology" class="tocxref"><span class="secno">3. </span>Ontological Definition of Mention</a></li><li class="tocline"><a href="#mention-xml" class="tocxref"><span class="secno">4. </span>XML Schema for Mention</a></li><li class="tocline"><a href="#mention-constraints" class="tocxref"><span class="secno">5. </span>Constraints associated with Mention</a></li><li class="tocline"><a href="#change-log" class="tocxref"><span class="secno"><span class="insert">A. </span></span><span class="insert">Change Log</span></a><ul class="toc"><li class="tocline"><a href="#change-log-since-wd-working-draft-12-march-2013" class="tocxref"><span class="secno"><span class="insert">A.1 </span></span><span class="insert">Change Log Since WD Working Draft 12 March 2013</span></a></li><li class="tocline"><a href="#change-log-since-first-public-working-draft" class="tocxref"><span class="secno"><span class="delete">A.</span><span class="insert">A.2</span> </span>Change Log Since First Public Working Draft</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">B. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
@@ -942,17 +942,17 @@
[<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>], and [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>] 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.
+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 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>] 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 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>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>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>This document 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. The document 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>
+<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>
<div class="note"><div class="note-title"><span>Note</span></div><div class="">The concept <a href="#concept-mention" class="internalDFN">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></div>
@@ -984,8 +984,13 @@
<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 augment
-the descriptions of entity <span class="name">e1</span> found in bundle <span class="name">b</span> with other information.
+</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>
+
+<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>
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>.
(The term 'aspect' should be understood informally as "a particular part or feature of something"; the term is used in [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]'s definitions of
@@ -1036,7 +1041,7 @@
<ul>
<li><span class="attribute" id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
of the entity that is a mention of the general entity (<span class="name">supra</span>);</li>
-<li><span class="attribute" id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) for an entity that appears in bundle <span class="name">b</span>.</li>
+<li><span class="attribute" id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) for an entity that <span class="delete">appears</span><span class="insert">is described</span> in bundle <span class="name">b</span>.</li>
<li><span class="attribute" id="mention.bundle">bundle</span>: an identifier (<span class="name">b</span>) of a bundle that contains a description of <span class="name">supra</span> and further constitutes one additional aspect presented by <span class="name">infra</span>.</li>
</ul>
</div>
@@ -1067,7 +1072,7 @@
</tbody></table>
</div>
-<p>We note that the concept <a href="#concept-mention" class="internalDFN">Mention</a> is an extension of [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>], and therefore has to be prefixed,
+<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>
@@ -1085,12 +1090,12 @@
<pre class="codeexample">bundle ex:run1
activity(ex:a1, 2011-11-16T16:00:00, 2011-11-16T17:00:00) //duration: 1hour
- wasAssociatedWith(ex:a1, ex:Bob, [prov:role="controller"])
+ wasAssociatedWith(ex:a1, ex:Bob, <span class="delete">[prov:role="controller"])</span><span class="insert">[prov:role='ex:controller'])</span>
endBundle
bundle ex:run2
activity(ex:a2, 2011-11-17T10:00:00, 2011-11-17T17:00:00) //duration: 7hours
- wasAssociatedWith(ex:a2, ex:Bob, [prov:role="controller"])
+ wasAssociatedWith(ex:a2, ex:Bob, <span class="delete">[prov:role="controller"])</span><span class="insert">[prov:role='ex:controller'])</span>
endBundle
</pre>
<p>The performance rating tool reads these bundles, and rates the performance of the agent described in these bundles. The performance rating tool creates a new bundle <span class="name">tool:analysis01</span> containing the following. A new agent <span class="name">tool:Bob-2011-11-16</span> is declared as a mention of <span class="name">ex:Bob</span> as described in bundle <span class="name">ex:run1</span>, and likewise for <span class="name">tool:Bob-2011-11-17</span> with respect to <span class="name">ex:run2</span>. The tool adds a domain-specific performance attribute to each of these specialized entities as follows: the performance of the agent in the first bundle is judged to be good since the duration of <span class="name">ex:a1</span> is one hour, whereas it is judged to be bad in the second bundle since <span class="name">ex:a2</span>'s duration is seven hours. The attribute <span class="name">perf:rating</span> is an example of additional attribute of the specialized agents <span class="name">tool:Bob-2011-11-16</span> and <span class="name">tool:Bob-2011-11-17</span>.</p>
@@ -1109,13 +1114,13 @@
<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, in which derivation and generations have been identified.
+<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><pre class="codeexample">
bundle obs:bundle1
entity(ex:report1, [ prov:type="report", ex:version=1 ])
- wasGeneratedBy(ex:g1; ex:report1, -, 2012-05-24T10:00:01)
+ <span class="delete">wasGeneratedBy(ex:g1; ex:report1,</span><span class="insert">wasGeneratedBy(ex:report1,</span> -, 2012-05-24T10:00:01)
entity(ex:report2, [ prov:type="report", ex:version=2 ])
- wasGeneratedBy(ex:g2; ex:report2, -, 2012-05-25T11:00:01)
+ <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
entity(obs:bundle1, [ prov:type='prov:Bundle' ])
@@ -1243,7 +1248,7 @@
<div class="anexample" typeof="prov:Entity" data-about="#example-for-property-mentionOf" id="example_3"><div class="anexampleTitle">Example 3<sup><a class="internalDFN" href="#example_3"><span class="diamond"> ◊</span></a></sup></div>
<span resource="http://www.w3.org/ns/prov#mentionOf" data-rel="dcterms:subject"></span>
-<p>We revisit <a href="#anexample-mention-rating" class="anexample-ref"><span>Example 1</span></a>, encoding in RDF the rating of Bob in the context of the second activity. For this, we use teh TRIG notation to express bundles
+<p>We revisit <a href="#anexample-mention-rating" class="anexample-ref"><span>Example 1</span></a>, encoding in RDF the rating of Bob in the context of the second activity. For this, we use <span class="delete">teh</span><span class="insert">the</span> TRIG notation to express bundles
<span class="name">:run2</span> and
<span class="name">tool:analysis01</span>.</p>
@@ -1273,10 +1278,10 @@
.
# This is inferred from prov:mentionOf
- tool:bob-2011-11-17 prov:specializationOf :bob .
+ tool:bob-2011-11-17 prov:specializationOf :bob .<span class="delete">
# This is inferred from prov:specializationOf
- tool:bob-2011-11-17 prov:alternateOf :bob .
+ tool:bob-2011-11-17 prov:alternateOf :bob .</span>
}
</pre>
@@ -1317,7 +1322,7 @@
<prov:wasAssociatedWith>
<prov:activity prov:ref="ex:a1" />
<prov:agent prov:ref="ex:Bob" />
- <prov:role xsi:type="xsd:QName">controller</prov:role>
+ <prov:role <span class="delete">xsi:type="xsd:QName">controller</prov:role></span><span class="insert">xsi:type="xsd:QName">ex:controller</prov:role></span>
</prov:wasAssociatedWith>
</prov:bundleContent>
@@ -1330,13 +1335,13 @@
<prov:wasAssociatedWith>
<prov:activity prov:ref="ex:a2" />
<prov:agent prov:ref="ex:Bob" />
- <prov:role xsi:type="xsd:QName">controller</prov:role>
+ <prov:role <span class="delete">xsi:type="xsd:QName">controller</prov:role></span><span class="insert">xsi:type="xsd:QName">ex:controller</prov:role></span>
</prov:wasAssociatedWith>
</prov:bundleContent>
<prov:bundleContent prov:id="tool:analysis01">
<prov:agent prov:id="tool:Bob-2011-11-16">
- <ex:perfrating>good</ex:perfrating>
+ <span class="delete"><ex:perfrating>good</ex:perfrating></span><span class="insert"><perf:rating>good</perf:rating></span>
</prov:agent>
<b><prov:mentionOf>
@@ -1346,7 +1351,7 @@
</prov:mentionOf></b>
<prov:agent prov:id="tool:Bob-2011-11-17">
- <ex:perfrating>bad</ex:perfrating>
+ <span class="delete"><ex:perfrating>bad</ex:perfrating></span><span class="insert"><perf:rating>bad</perf:rating></span>
</prov:agent>
<b><prov:mentionOf>
@@ -1396,22 +1401,37 @@
</section>
-<section class="appendix" id="change-log-since-first-public-working-draft">
- <h2><span class="secno">A. </span>Change Log Since First Public Working Draft</h2>
+
+ <section class="appendix" id="change-log">
+<h2><span class="secno">A. </span>Change Log</h2>
+<section id="change-log-since-wd-working-draft-12-march-2013">
+ <h3><span class="secno"><span class="insert">A.1 </span></span><span class="insert">Change Log</span> Since <span class="delete">First Public</span><span class="insert">WD</span> Working Draft<span class="insert"> 12 March 2013</span></h3>
<ul>
-<li> Checked all internal fragments resolved.
-</li><li> Changed the status of this document section: added new documents to the PROV Family of Document, and removed the how to read section, referring instead to PROV-OVERVIEW.
+<li> <span class="delete">Checked all internal fragments resolved.
+</span> Changed the status of this document <span class="delete">section: added new documents to the PROV Family of Document, and removed the how to read section, referring instead to PROV-OVERVIEW.</span><span class="insert">section.</span>
</li><li> Changed all URLs to PROV documents.
-</li><li> Updated XML schema definition.
-</li><li> Updated affiliations.
-</li><li> Added namespace and convention sections.
-</li><li> Updated grammar to make prov prefix explicit.
-</li><li> Added new paragraph in introduction.
-</li><li> Moved "inferred statements" into named graph tool:analysis01 in Example 3.
-</li><li> Added comment on TRIG notation.
-</li><li> Updated xml example with new syntax of bundles.
+</li><li><span class="delete"> Updated XML schema definition.</span><span class="insert"> Minor editorial changes in section 1 and section 2.</span>
+</li><li><span class="delete"> Updated affiliations.</span><span class="insert"> In both prov-n and prov-xml examples, used role 'ex:controler'
+</span></li></ul>
+</section>
+
+<section id="change-log-since-first-public-working-draft">
+ <h3><span class="secno"><span class="insert">A.2 </span></span><span class="insert">Change Log Since First Public Working Draft</span></h3>
+<ul>
+<li><span class="insert"> Checked all internal fragments resolved.</span>
+</li><li> <span class="delete">Added namespace</span><span class="insert">Changed the status of this document section: added new documents to the PROV Family of Document,</span> and <span class="delete">convention sections.</span><span class="insert">removed the how to read section, referring instead to PROV-OVERVIEW.</span>
+</li><li> <span class="delete">Updated grammar</span><span class="insert">Changed all URLs</span> to<span class="delete"> make prov prefix explicit.</span><span class="insert"> PROV documents.</span>
+</li><li> <span class="delete">Added new paragraph in introduction.</span><span class="insert">Updated XML schema definition.</span>
+</li><li> <span class="delete">Moved "inferred statements" into named graph tool:analysis01 in Example 3.</span><span class="insert">Updated affiliations.</span>
+</li><li> Added <span class="delete">comment on TRIG notation.</span><span class="insert">namespace and convention sections.</span>
+</li><li> Updated <span class="insert">grammar to make prov prefix explicit.
+</span></li><li><span class="insert"> Added new paragraph in introduction.
+</span></li><li><span class="insert"> Moved "inferred statements" into named graph tool:analysis01 in Example 3.
+</span></li><li><span class="insert"> Added comment on TRIG notation.
+</span></li><li><span class="insert"> Updated </span>xml example with new syntax of bundles.
</li></ul>
</section>
+</section>
<section class="appendix" id="acknowledgements">
<h2><span class="secno">B. </span>Acknowledgements</h2>
--- a/links/prov-links.html Tue Mar 26 21:45:36 2013 +0000
+++ b/links/prov-links.html Thu Mar 28 10:39:42 2013 +0000
@@ -783,17 +783,17 @@
[[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.
+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 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]] 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 are independent 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 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> [[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 are independent 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 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>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>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>
+<p>This specification introduces a new concept <a>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>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>
@@ -823,9 +823,13 @@
<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 augment
-the descriptions of entity <span class="name">e1</span> found in bundle <span class="name">b</span> with other information.
+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>
+
+<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>
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>.
(The term 'aspect' should be understood informally as "a particular part or feature of something"; the term is used in [[PROV-DM]]'s definitions of
@@ -876,7 +880,7 @@
<ul>
<li><span class='attribute' id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
of the entity that is a mention of the general entity (<span class="name">supra</span>);</li>
-<li><span class='attribute' id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) for an entity that appears in bundle <span class="name">b</span>.</li>
+<li><span class='attribute' id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) for an entity that is described in bundle <span class="name">b</span>.</li>
<li><span class='attribute' id="mention.bundle">bundle</span>: an identifier (<span class="name">b</span>) of a bundle that contains a description of <span class="name">supra</span> and further constitutes one additional aspect presented by <span class="name">infra</span>.</li>
</ul>
</div>
@@ -907,7 +911,7 @@
</table>
</div>
-<p>We note that the concept <a>Mention</a> is an extension of [[PROV-DM]], and therefore has to be prefixed,
+<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,
<span class="name">prov:mentionOf</span>, according the extensibility
rules of the provenance notation [[PROV-N]].</p>
@@ -926,12 +930,12 @@
<pre class="codeexample">
bundle ex:run1
activity(ex:a1, 2011-11-16T16:00:00, 2011-11-16T17:00:00) //duration: 1hour
- wasAssociatedWith(ex:a1, ex:Bob, [prov:role="controller"])
+ wasAssociatedWith(ex:a1, ex:Bob, [prov:role='ex:controller'])
endBundle
bundle ex:run2
activity(ex:a2, 2011-11-17T10:00:00, 2011-11-17T17:00:00) //duration: 7hours
- wasAssociatedWith(ex:a2, ex:Bob, [prov:role="controller"])
+ wasAssociatedWith(ex:a2, ex:Bob, [prov:role='ex:controller'])
endBundle
</pre>
<p>The performance rating tool reads these bundles, and rates the performance of the agent described in these bundles. The performance rating tool creates a new bundle <span class="name">tool:analysis01</span> containing the following. A new agent <span class="name">tool:Bob-2011-11-16</span> is declared as a mention of <span class="name">ex:Bob</span> as described in bundle <span class="name">ex:run1</span>, and likewise for <span class="name">tool:Bob-2011-11-17</span> with respect to <span class="name">ex:run2</span>. The tool adds a domain-specific performance attribute to each of these specialized entities as follows: the performance of the agent in the first bundle is judged to be good since the duration of <span class="name">ex:a1</span> is one hour, whereas it is judged to be bad in the second bundle since <span class="name">ex:a2</span>'s duration is seven hours. The attribute <span class="name">perf:rating</span> is an example of additional attribute of the specialized agents <span class="name">tool:Bob-2011-11-16</span> and <span class="name">tool:Bob-2011-11-17</span>.</p>
@@ -951,13 +955,13 @@
<div class="anexample" id="aexample-mention-viz">
-<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
+<p>Consider the following bundle of descriptions.
<pre class="codeexample">
bundle obs:bundle1
entity(ex:report1, [ prov:type="report", ex:version=1 ])
- wasGeneratedBy(ex:g1; ex:report1, -, 2012-05-24T10:00:01)
+ wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01)
entity(ex:report2, [ prov:type="report", ex:version=2 ])
- wasGeneratedBy(ex:g2; ex:report2, -, 2012-05-25T11:00:01)
+ wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
wasDerivedFrom(ex:report2, ex:report1)
endBundle
entity(obs:bundle1, [ prov:type='prov:Bundle' ])
@@ -1085,7 +1089,7 @@
<div class="anexample" typeof="prov:Entity" data-about="#example-for-property-mentionOf">
<span resource="http://www.w3.org/ns/prov#mentionOf" data-rel="dcterms:subject"></span>
-<p>We revisit <a href="#anexample-mention-rating" class="anexample-ref"><span>Example REF</span></a>, encoding in RDF the rating of Bob in the context of the second activity. For this, we use teh TRIG notation to express bundles
+<p>We revisit <a href="#anexample-mention-rating" class="anexample-ref"><span>Example REF</span></a>, encoding in RDF the rating of Bob in the context of the second activity. For this, we use the TRIG notation to express bundles
<span class="name">:run2</span> and
<span class="name">tool:analysis01</span>.</p>
@@ -1116,9 +1120,6 @@
# This is inferred from prov:mentionOf
tool:bob-2011-11-17 prov:specializationOf :bob .
-
- # This is inferred from prov:specializationOf
- tool:bob-2011-11-17 prov:alternateOf :bob .
}
</pre>
@@ -1159,7 +1160,7 @@
<prov:wasAssociatedWith>
<prov:activity prov:ref="ex:a1" />
<prov:agent prov:ref="ex:Bob" />
- <prov:role xsi:type="xsd:QName">controller</prov:role>
+ <prov:role xsi:type="xsd:QName">ex:controller</prov:role>
</prov:wasAssociatedWith>
</prov:bundleContent>
@@ -1172,13 +1173,13 @@
<prov:wasAssociatedWith>
<prov:activity prov:ref="ex:a2" />
<prov:agent prov:ref="ex:Bob" />
- <prov:role xsi:type="xsd:QName">controller</prov:role>
+ <prov:role xsi:type="xsd:QName">ex:controller</prov:role>
</prov:wasAssociatedWith>
</prov:bundleContent>
<prov:bundleContent prov:id="tool:analysis01">
<prov:agent prov:id="tool:Bob-2011-11-16">
- <ex:perfrating>good</ex:perfrating>
+ <perf:rating>good</perf:rating>
</prov:agent>
<b><prov:mentionOf>
@@ -1188,7 +1189,7 @@
</prov:mentionOf></b>
<prov:agent prov:id="tool:Bob-2011-11-17">
- <ex:perfrating>bad</ex:perfrating>
+ <perf:rating>bad</perf:rating>
</prov:agent>
<b><prov:mentionOf>
@@ -1247,7 +1248,19 @@
</section>
<section class="appendix">
- <h2>Change Log Since First Public Working Draft</h2>
+<h2>Change Log</h2>
+<section>
+ <h3>Change Log Since WD Working Draft 12 March 2013</h3>
+<ul>
+<li> Changed the status of this document section.
+<li> Changed all URLs to PROV documents.
+<li> Minor editorial changes in section 1 and section 2.
+<li> In both prov-n and prov-xml examples, used role 'ex:controler'
+</ul>
+</section>
+
+<section>
+ <h3>Change Log Since First Public Working Draft</h3>
<ul>
<li> Checked all internal fragments resolved.
<li> Changed the status of this document section: added new documents to the PROV Family of Document, and removed the how to read section, referring instead to PROV-OVERVIEW.
@@ -1262,6 +1275,7 @@
<li> Updated xml example with new syntax of bundles.
</ul>
</section>
+</section>
<section class="appendix">
<h2>Acknowledgements</h2>
--- a/links/releases/NOTE-prov-links-20130430/Overview.html Tue Mar 26 21:45:36 2013 +0000
+++ b/links/releases/NOTE-prov-links-20130430/Overview.html Thu Mar 28 10:39:42 2013 +0000
@@ -897,7 +897,7 @@
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#term-mention" class="tocxref"><span class="secno">2. </span>Conceptual Definition of Mention</a></li><li class="tocline"><a href="#mention-ontology" class="tocxref"><span class="secno">3. </span>Ontological Definition of Mention</a></li><li class="tocline"><a href="#mention-xml" class="tocxref"><span class="secno">4. </span>XML Schema for Mention</a></li><li class="tocline"><a href="#mention-constraints" class="tocxref"><span class="secno">5. </span>Constraints associated with Mention</a></li><li class="tocline"><a href="#change-log-since-first-public-working-draft" class="tocxref"><span class="secno">A. </span>Change Log Since First Public Working Draft</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">B. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#term-mention" class="tocxref"><span class="secno">2. </span>Conceptual Definition of Mention</a></li><li class="tocline"><a href="#mention-ontology" class="tocxref"><span class="secno">3. </span>Ontological Definition of Mention</a></li><li class="tocline"><a href="#mention-xml" class="tocxref"><span class="secno">4. </span>XML Schema for Mention</a></li><li class="tocline"><a href="#mention-constraints" class="tocxref"><span class="secno">5. </span>Constraints associated with Mention</a></li><li class="tocline"><a href="#change-log" class="tocxref"><span class="secno">A. </span>Change Log</a><ul class="toc"><li class="tocline"><a href="#change-log-since-wd-working-draft-12-march-2013" class="tocxref"><span class="secno">A.1 </span>Change Log Since WD Working Draft 12 March 2013</a></li><li class="tocline"><a href="#change-log-since-first-public-working-draft" class="tocxref"><span class="secno">A.2 </span>Change Log Since First Public Working Draft</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">B. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
@@ -918,17 +918,17 @@
[<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>], and [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>] 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.
+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 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>] 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 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>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>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>This document 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. The document 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>
+<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>
<div class="note"><div class="note-title"><span>Note</span></div><div class="">The concept <a href="#concept-mention" class="internalDFN">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></div>
@@ -959,9 +959,13 @@
<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 augment
-the descriptions of entity <span class="name">e1</span> found in bundle <span class="name">b</span> with other information.
+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>
+
+<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>
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>.
(The term 'aspect' should be understood informally as "a particular part or feature of something"; the term is used in [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]'s definitions of
@@ -1012,7 +1016,7 @@
<ul>
<li><span class="attribute" id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
of the entity that is a mention of the general entity (<span class="name">supra</span>);</li>
-<li><span class="attribute" id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) for an entity that appears in bundle <span class="name">b</span>.</li>
+<li><span class="attribute" id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) for an entity that is described in bundle <span class="name">b</span>.</li>
<li><span class="attribute" id="mention.bundle">bundle</span>: an identifier (<span class="name">b</span>) of a bundle that contains a description of <span class="name">supra</span> and further constitutes one additional aspect presented by <span class="name">infra</span>.</li>
</ul>
</div>
@@ -1043,7 +1047,7 @@
</tbody></table>
</div>
-<p>We note that the concept <a href="#concept-mention" class="internalDFN">Mention</a> is an extension of [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>], and therefore has to be prefixed,
+<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,
<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>
@@ -1061,12 +1065,12 @@
<pre class="codeexample">bundle ex:run1
activity(ex:a1, 2011-11-16T16:00:00, 2011-11-16T17:00:00) //duration: 1hour
- wasAssociatedWith(ex:a1, ex:Bob, [prov:role="controller"])
+ wasAssociatedWith(ex:a1, ex:Bob, [prov:role='ex:controller'])
endBundle
bundle ex:run2
activity(ex:a2, 2011-11-17T10:00:00, 2011-11-17T17:00:00) //duration: 7hours
- wasAssociatedWith(ex:a2, ex:Bob, [prov:role="controller"])
+ wasAssociatedWith(ex:a2, ex:Bob, [prov:role='ex:controller'])
endBundle
</pre>
<p>The performance rating tool reads these bundles, and rates the performance of the agent described in these bundles. The performance rating tool creates a new bundle <span class="name">tool:analysis01</span> containing the following. A new agent <span class="name">tool:Bob-2011-11-16</span> is declared as a mention of <span class="name">ex:Bob</span> as described in bundle <span class="name">ex:run1</span>, and likewise for <span class="name">tool:Bob-2011-11-17</span> with respect to <span class="name">ex:run2</span>. The tool adds a domain-specific performance attribute to each of these specialized entities as follows: the performance of the agent in the first bundle is judged to be good since the duration of <span class="name">ex:a1</span> is one hour, whereas it is judged to be bad in the second bundle since <span class="name">ex:a2</span>'s duration is seven hours. The attribute <span class="name">perf:rating</span> is an example of additional attribute of the specialized agents <span class="name">tool:Bob-2011-11-16</span> and <span class="name">tool:Bob-2011-11-17</span>.</p>
@@ -1085,13 +1089,13 @@
<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, in which derivation and generations have been identified.
+<p>Consider the following bundle of descriptions.
</p><pre class="codeexample">
bundle obs:bundle1
entity(ex:report1, [ prov:type="report", ex:version=1 ])
- wasGeneratedBy(ex:g1; ex:report1, -, 2012-05-24T10:00:01)
+ wasGeneratedBy(ex:report1, -, 2012-05-24T10:00:01)
entity(ex:report2, [ prov:type="report", ex:version=2 ])
- wasGeneratedBy(ex:g2; ex:report2, -, 2012-05-25T11:00:01)
+ wasGeneratedBy(ex:report2, -, 2012-05-25T11:00:01)
wasDerivedFrom(ex:report2, ex:report1)
endBundle
entity(obs:bundle1, [ prov:type='prov:Bundle' ])
@@ -1219,7 +1223,7 @@
<div class="anexample" typeof="prov:Entity" data-about="#example-for-property-mentionOf" id="example_3"><div class="anexampleTitle">Example 3<sup><a class="internalDFN" href="#example_3"><span class="diamond"> ◊</span></a></sup></div>
<span resource="http://www.w3.org/ns/prov#mentionOf" data-rel="dcterms:subject"></span>
-<p>We revisit <a href="#anexample-mention-rating" class="anexample-ref"><span>Example 1</span></a>, encoding in RDF the rating of Bob in the context of the second activity. For this, we use teh TRIG notation to express bundles
+<p>We revisit <a href="#anexample-mention-rating" class="anexample-ref"><span>Example 1</span></a>, encoding in RDF the rating of Bob in the context of the second activity. For this, we use the TRIG notation to express bundles
<span class="name">:run2</span> and
<span class="name">tool:analysis01</span>.</p>
@@ -1250,9 +1254,6 @@
# This is inferred from prov:mentionOf
tool:bob-2011-11-17 prov:specializationOf :bob .
-
- # This is inferred from prov:specializationOf
- tool:bob-2011-11-17 prov:alternateOf :bob .
}
</pre>
@@ -1293,7 +1294,7 @@
<prov:wasAssociatedWith>
<prov:activity prov:ref="ex:a1" />
<prov:agent prov:ref="ex:Bob" />
- <prov:role xsi:type="xsd:QName">controller</prov:role>
+ <prov:role xsi:type="xsd:QName">ex:controller</prov:role>
</prov:wasAssociatedWith>
</prov:bundleContent>
@@ -1306,13 +1307,13 @@
<prov:wasAssociatedWith>
<prov:activity prov:ref="ex:a2" />
<prov:agent prov:ref="ex:Bob" />
- <prov:role xsi:type="xsd:QName">controller</prov:role>
+ <prov:role xsi:type="xsd:QName">ex:controller</prov:role>
</prov:wasAssociatedWith>
</prov:bundleContent>
<prov:bundleContent prov:id="tool:analysis01">
<prov:agent prov:id="tool:Bob-2011-11-16">
- <ex:perfrating>good</ex:perfrating>
+ <perf:rating>good</perf:rating>
</prov:agent>
<b><prov:mentionOf>
@@ -1322,7 +1323,7 @@
</prov:mentionOf></b>
<prov:agent prov:id="tool:Bob-2011-11-17">
- <ex:perfrating>bad</ex:perfrating>
+ <perf:rating>bad</perf:rating>
</prov:agent>
<b><prov:mentionOf>
@@ -1372,8 +1373,20 @@
</section>
-<section class="appendix" id="change-log-since-first-public-working-draft">
- <!--OddPage--><h2><span class="secno">A. </span>Change Log Since First Public Working Draft</h2>
+<section class="appendix" id="change-log">
+<!--OddPage--><h2><span class="secno">A. </span>Change Log</h2>
+<section id="change-log-since-wd-working-draft-12-march-2013">
+ <h3><span class="secno">A.1 </span>Change Log Since WD Working Draft 12 March 2013</h3>
+<ul>
+<li> Changed the status of this document section.
+</li><li> Changed all URLs to PROV documents.
+</li><li> Minor editorial changes in section 1 and section 2.
+</li><li> In both prov-n and prov-xml examples, used role 'ex:controler'
+</li></ul>
+</section>
+
+<section id="change-log-since-first-public-working-draft">
+ <h3><span class="secno">A.2 </span>Change Log Since First Public Working Draft</h3>
<ul>
<li> Checked all internal fragments resolved.
</li><li> Changed the status of this document section: added new documents to the PROV Family of Document, and removed the how to read section, referring instead to PROV-OVERVIEW.
@@ -1388,6 +1401,7 @@
</li><li> Updated xml example with new syntax of bundles.
</li></ul>
</section>
+</section>
<section class="appendix" id="acknowledgements">
<!--OddPage--><h2><span class="secno">B. </span>Acknowledgements</h2>
--- a/links/releases/NOTE-prov-links-20130430/diff.html Tue Mar 26 21:45:36 2013 +0000
+++ b/links/releases/NOTE-prov-links-20130430/diff.html Thu Mar 28 10:39:42 2013 +0000
@@ -921,7 +921,7 @@
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#term-mention" class="tocxref"><span class="secno">2. </span>Conceptual Definition of Mention</a></li><li class="tocline"><a href="#mention-ontology" class="tocxref"><span class="secno">3. </span>Ontological Definition of Mention</a></li><li class="tocline"><a href="#mention-xml" class="tocxref"><span class="secno">4. </span>XML Schema for Mention</a></li><li class="tocline"><a href="#mention-constraints" class="tocxref"><span class="secno">5. </span>Constraints associated with Mention</a></li><li class="tocline"><a href="#change-log-since-first-public-working-draft" class="tocxref"><span class="secno">A. </span>Change Log Since First Public Working Draft</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">B. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
+</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#prov-namespace" class="tocxref"><span class="secno">1.1 </span>PROV Namespace</a></li><li class="tocline"><a href="#conventions" class="tocxref"><span class="secno">1.2 </span>Conventions</a></li></ul></li><li class="tocline"><a href="#term-mention" class="tocxref"><span class="secno">2. </span>Conceptual Definition of Mention</a></li><li class="tocline"><a href="#mention-ontology" class="tocxref"><span class="secno">3. </span>Ontological Definition of Mention</a></li><li class="tocline"><a href="#mention-xml" class="tocxref"><span class="secno">4. </span>XML Schema for Mention</a></li><li class="tocline"><a href="#mention-constraints" class="tocxref"><span class="secno">5. </span>Constraints associated with Mention</a></li><li class="tocline"><a href="#change-log" class="tocxref"><span class="secno"><span class="insert">A. </span></span><span class="insert">Change Log</span></a><ul class="toc"><li class="tocline"><a href="#change-log-since-wd-working-draft-12-march-2013" class="tocxref"><span class="secno"><span class="insert">A.1 </span></span><span class="insert">Change Log Since WD Working Draft 12 March 2013</span></a></li><li class="tocline"><a href="#change-log-since-first-public-working-draft" class="tocxref"><span class="secno"><span class="delete">A.</span><span class="insert">A.2</span> </span>Change Log Since First Public Working Draft</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">B. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">C. </span>References</a><ul class="toc"><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">C.1 </span>Informative references</a></li></ul></li></ul></section>
@@ -942,17 +942,17 @@
[<cite><a class="bibref" href="#bib-PROV-N">PROV-N</a></cite>], and [<cite><a class="bibref" href="#bib-PROV-XML">PROV-XML</a></cite>] 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.
+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 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>] 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 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>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>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>This document 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. The document 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>
+<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>
<div class="note"><div class="note-title"><span>Note</span></div><div class="">The concept <a href="#concept-mention" class="internalDFN">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></div>
@@ -984,8 +984,13 @@
<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 augment
-the descriptions of entity <span class="name">e1</span> found in bundle <span class="name">b</span> with other information.
+</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>
+
+<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>
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>.
(The term 'aspect' should be understood informally as "a particular part or feature of something"; the term is used in [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>]'s definitions of
@@ -1036,7 +1041,7 @@
<ul>
<li><span class="attribute" id="mention.specificEntity">specificEntity</span>: an identifier (<span class="name">infra</span>)
of the entity that is a mention of the general entity (<span class="name">supra</span>);</li>
-<li><span class="attribute" id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) for an entity that appears in bundle <span class="name">b</span>.</li>
+<li><span class="attribute" id="mention.generalEntity">generalEntity</span>: an identifier (<span class="name">supra</span>) for an entity that <span class="delete">appears</span><span class="insert">is described</span> in bundle <span class="name">b</span>.</li>
<li><span class="attribute" id="mention.bundle">bundle</span>: an identifier (<span class="name">b</span>) of a bundle that contains a description of <span class="name">supra</span> and further constitutes one additional aspect presented by <span class="name">infra</span>.</li>
</ul>
</div>
@@ -1067,7 +1072,7 @@
</tbody></table>
</div>
-<p>We note that the concept <a href="#concept-mention" class="internalDFN">Mention</a> is an extension of [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>], and therefore has to be prefixed,
+<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>
@@ -1085,12 +1090,12 @@
<pre class="codeexample">bundle ex:run1
activity(ex:a1, 2011-11-16T16:00:00, 2011-11-16T17:00:00) //duration: 1hour
- wasAssociatedWith(ex:a1, ex:Bob, [prov:role="controller"])
+ wasAssociatedWith(ex:a1, ex:Bob, <span class="delete">[prov:role="controller"])</span><span class="insert">[prov:role='ex:controller'])</span>
endBundle
bundle ex:run2
activity(ex:a2, 2011-11-17T10:00:00, 2011-11-17T17:00:00) //duration: 7hours
- wasAssociatedWith(ex:a2, ex:Bob, [prov:role="controller"])
+ wasAssociatedWith(ex:a2, ex:Bob, <span class="delete">[prov:role="controller"])</span><span class="insert">[prov:role='ex:controller'])</span>
endBundle
</pre>
<p>The performance rating tool reads these bundles, and rates the performance of the agent described in these bundles. The performance rating tool creates a new bundle <span class="name">tool:analysis01</span> containing the following. A new agent <span class="name">tool:Bob-2011-11-16</span> is declared as a mention of <span class="name">ex:Bob</span> as described in bundle <span class="name">ex:run1</span>, and likewise for <span class="name">tool:Bob-2011-11-17</span> with respect to <span class="name">ex:run2</span>. The tool adds a domain-specific performance attribute to each of these specialized entities as follows: the performance of the agent in the first bundle is judged to be good since the duration of <span class="name">ex:a1</span> is one hour, whereas it is judged to be bad in the second bundle since <span class="name">ex:a2</span>'s duration is seven hours. The attribute <span class="name">perf:rating</span> is an example of additional attribute of the specialized agents <span class="name">tool:Bob-2011-11-16</span> and <span class="name">tool:Bob-2011-11-17</span>.</p>
@@ -1109,13 +1114,13 @@
<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, in which derivation and generations have been identified.
+<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><pre class="codeexample">
bundle obs:bundle1
entity(ex:report1, [ prov:type="report", ex:version=1 ])
- wasGeneratedBy(ex:g1; ex:report1, -, 2012-05-24T10:00:01)
+ <span class="delete">wasGeneratedBy(ex:g1; ex:report1,</span><span class="insert">wasGeneratedBy(ex:report1,</span> -, 2012-05-24T10:00:01)
entity(ex:report2, [ prov:type="report", ex:version=2 ])
- wasGeneratedBy(ex:g2; ex:report2, -, 2012-05-25T11:00:01)
+ <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
entity(obs:bundle1, [ prov:type='prov:Bundle' ])
@@ -1243,7 +1248,7 @@
<div class="anexample" typeof="prov:Entity" data-about="#example-for-property-mentionOf" id="example_3"><div class="anexampleTitle">Example 3<sup><a class="internalDFN" href="#example_3"><span class="diamond"> ◊</span></a></sup></div>
<span resource="http://www.w3.org/ns/prov#mentionOf" data-rel="dcterms:subject"></span>
-<p>We revisit <a href="#anexample-mention-rating" class="anexample-ref"><span>Example 1</span></a>, encoding in RDF the rating of Bob in the context of the second activity. For this, we use teh TRIG notation to express bundles
+<p>We revisit <a href="#anexample-mention-rating" class="anexample-ref"><span>Example 1</span></a>, encoding in RDF the rating of Bob in the context of the second activity. For this, we use <span class="delete">teh</span><span class="insert">the</span> TRIG notation to express bundles
<span class="name">:run2</span> and
<span class="name">tool:analysis01</span>.</p>
@@ -1273,10 +1278,10 @@
.
# This is inferred from prov:mentionOf
- tool:bob-2011-11-17 prov:specializationOf :bob .
+ tool:bob-2011-11-17 prov:specializationOf :bob .<span class="delete">
# This is inferred from prov:specializationOf
- tool:bob-2011-11-17 prov:alternateOf :bob .
+ tool:bob-2011-11-17 prov:alternateOf :bob .</span>
}
</pre>
@@ -1317,7 +1322,7 @@
<prov:wasAssociatedWith>
<prov:activity prov:ref="ex:a1" />
<prov:agent prov:ref="ex:Bob" />
- <prov:role xsi:type="xsd:QName">controller</prov:role>
+ <prov:role <span class="delete">xsi:type="xsd:QName">controller</prov:role></span><span class="insert">xsi:type="xsd:QName">ex:controller</prov:role></span>
</prov:wasAssociatedWith>
</prov:bundleContent>
@@ -1330,13 +1335,13 @@
<prov:wasAssociatedWith>
<prov:activity prov:ref="ex:a2" />
<prov:agent prov:ref="ex:Bob" />
- <prov:role xsi:type="xsd:QName">controller</prov:role>
+ <prov:role <span class="delete">xsi:type="xsd:QName">controller</prov:role></span><span class="insert">xsi:type="xsd:QName">ex:controller</prov:role></span>
</prov:wasAssociatedWith>
</prov:bundleContent>
<prov:bundleContent prov:id="tool:analysis01">
<prov:agent prov:id="tool:Bob-2011-11-16">
- <ex:perfrating>good</ex:perfrating>
+ <span class="delete"><ex:perfrating>good</ex:perfrating></span><span class="insert"><perf:rating>good</perf:rating></span>
</prov:agent>
<b><prov:mentionOf>
@@ -1346,7 +1351,7 @@
</prov:mentionOf></b>
<prov:agent prov:id="tool:Bob-2011-11-17">
- <ex:perfrating>bad</ex:perfrating>
+ <span class="delete"><ex:perfrating>bad</ex:perfrating></span><span class="insert"><perf:rating>bad</perf:rating></span>
</prov:agent>
<b><prov:mentionOf>
@@ -1396,22 +1401,37 @@
</section>
-<section class="appendix" id="change-log-since-first-public-working-draft">
- <h2><span class="secno">A. </span>Change Log Since First Public Working Draft</h2>
+
+ <section class="appendix" id="change-log">
+<h2><span class="secno">A. </span>Change Log</h2>
+<section id="change-log-since-wd-working-draft-12-march-2013">
+ <h3><span class="secno"><span class="insert">A.1 </span></span><span class="insert">Change Log</span> Since <span class="delete">First Public</span><span class="insert">WD</span> Working Draft<span class="insert"> 12 March 2013</span></h3>
<ul>
-<li> Checked all internal fragments resolved.
-</li><li> Changed the status of this document section: added new documents to the PROV Family of Document, and removed the how to read section, referring instead to PROV-OVERVIEW.
+<li> <span class="delete">Checked all internal fragments resolved.
+</span> Changed the status of this document <span class="delete">section: added new documents to the PROV Family of Document, and removed the how to read section, referring instead to PROV-OVERVIEW.</span><span class="insert">section.</span>
</li><li> Changed all URLs to PROV documents.
-</li><li> Updated XML schema definition.
-</li><li> Updated affiliations.
-</li><li> Added namespace and convention sections.
-</li><li> Updated grammar to make prov prefix explicit.
-</li><li> Added new paragraph in introduction.
-</li><li> Moved "inferred statements" into named graph tool:analysis01 in Example 3.
-</li><li> Added comment on TRIG notation.
-</li><li> Updated xml example with new syntax of bundles.
+</li><li><span class="delete"> Updated XML schema definition.</span><span class="insert"> Minor editorial changes in section 1 and section 2.</span>
+</li><li><span class="delete"> Updated affiliations.</span><span class="insert"> In both prov-n and prov-xml examples, used role 'ex:controler'
+</span></li></ul>
+</section>
+
+<section id="change-log-since-first-public-working-draft">
+ <h3><span class="secno"><span class="insert">A.2 </span></span><span class="insert">Change Log Since First Public Working Draft</span></h3>
+<ul>
+<li><span class="insert"> Checked all internal fragments resolved.</span>
+</li><li> <span class="delete">Added namespace</span><span class="insert">Changed the status of this document section: added new documents to the PROV Family of Document,</span> and <span class="delete">convention sections.</span><span class="insert">removed the how to read section, referring instead to PROV-OVERVIEW.</span>
+</li><li> <span class="delete">Updated grammar</span><span class="insert">Changed all URLs</span> to<span class="delete"> make prov prefix explicit.</span><span class="insert"> PROV documents.</span>
+</li><li> <span class="delete">Added new paragraph in introduction.</span><span class="insert">Updated XML schema definition.</span>
+</li><li> <span class="delete">Moved "inferred statements" into named graph tool:analysis01 in Example 3.</span><span class="insert">Updated affiliations.</span>
+</li><li> Added <span class="delete">comment on TRIG notation.</span><span class="insert">namespace and convention sections.</span>
+</li><li> Updated <span class="insert">grammar to make prov prefix explicit.
+</span></li><li><span class="insert"> Added new paragraph in introduction.
+</span></li><li><span class="insert"> Moved "inferred statements" into named graph tool:analysis01 in Example 3.
+</span></li><li><span class="insert"> Added comment on TRIG notation.
+</span></li><li><span class="insert"> Updated </span>xml example with new syntax of bundles.
</li></ul>
</section>
+</section>
<section class="appendix" id="acknowledgements">
<h2><span class="secno">B. </span>Acknowledgements</h2>
--- a/model/respec2html.js Tue Mar 26 21:45:36 2013 +0000
+++ b/model/respec2html.js Thu Mar 28 10:39:42 2013 +0000
@@ -50,4 +50,4 @@
}
}, 1000);
}
-});
+});
\ No newline at end of file