--- a/links/diff.html Wed Feb 27 01:53:19 2013 -0700
+++ b/links/diff.html Wed Feb 27 10:13:34 2013 +0000
@@ -931,8 +931,9 @@
<h2><span class="secno">1. </span>Introduction</h2>
<p>
-<a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">Provenance</a>
-is a record that describes the people, institutions, entities, and
+<span class="delete">Provenance</span><span class="delete">
+is</span><span class="insert">The PROV data model [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">] defines </span><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/"><span class="insert">provenance</span></a><span class="insert">
+as</span> 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 [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>], [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>],
[<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
@@ -941,11 +942,13 @@
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/2013/PR-prov-dm-20130312/#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/PR-prov-o-20130312/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>] and <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/#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 illustrated by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/#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/PR-prov-dm-20130312/#concept-bundle">Bundle</a>: defined as a set of provenance <span class="delete">descriptions,</span><span class="insert">descriptions;</span> it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>] and <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/#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 <span class="delete">illustrated</span><span class="insert">formalized</span> by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/#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><span class="insert">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. </span></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>
<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.
@@ -955,7 +958,7 @@
<section id="prov-namespace">
<h3><span class="secno"><span class="insert">1.1 </span></span><span class="insert">PROV Namespace</span></h3>
-<p><span class="insert">The PROV namespace is </span><span class="name"><span class="insert">http://www.w3.org/ns/prov#</span></span><span class="insert">.</span></p>
+<p><span class="insert">The PROV namespace URI is </span><span class="name"><span class="insert">http://www.w3.org/ns/prov#</span></span><span class="insert"> and prefix </span><span class="name"><span class="insert">prov</span></span><span class="insert">.</span></p>
<p><span class="insert"> All the concepts, reserved names, classes, properties, attributes introduced in this specification belong to the PROV namespace.</span></p>
</section>
@@ -993,7 +996,7 @@
<p>
<a href="#figure-component5">Figure 1</a> depicts
-the relation MentionOf (<a href="#concept-mention" class="internalDFN"><span class="delete">mention</span><span class="insert">Mention</span></a>) as a ternary relation.
+the relation MentionOf <span class="delete">(</span><span class="insert">(concept </span><a href="#concept-mention" class="internalDFN"><span class="delete">mention</span><span class="insert">Mention</span></a>) as a ternary relation.
</p>
@@ -1005,7 +1008,7 @@
</div>
-<p>Thus, Mention is a relation between two entities with regard to a bundle.
+<p>Thus, <span class="delete">Mention is </span>a <span class="delete">relation between</span><span class="insert">mention relates</span> two entities with regard to a bundle.
It is a special case of specialization.</p>
@@ -1064,15 +1067,15 @@
<p>
-Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle. The entity <span class="name">e1</span> may described im multiple other bundle <span class="name">b<sub>i</sub></span>.
-From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of <span class="name">e2</span>. Hence, <span class="name">mentionOf</span> has to be asserted. </p>
+Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle. The entity <span class="name">e1</span> may described <span class="delete">im</span><span class="insert">in</span> multiple other bundle <span class="name">b<sub>i</sub></span>.
+From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name"><span class="delete">mentionOf(e2,e1,b)</span><span class="insert">prov:mentionOf(e2,e1,b)</span></span> for a given <span class="name">b</span>, since it is unknown which <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of <span class="name">e2</span>. Hence, <span class="name"><span class="delete">mentionOf</span><span class="insert">prov:mentionOf</span></span> has to be asserted. </p>
<p><a href="#mention-constraints" class="section-ref"><span>Section 5.</span></a> presents constraints applicable to <a href="#concept-mention" class="internalDFN">Mention</a>, and in particular, the fact that an entity can be a <a href="#mention.specificEntity">specific entity</a> of a <a href="#concept-mention" class="internalDFN">Mention</a> at most once.</p>
<div class="anexample" id="anexample-mention-rating"><div class="anexampleTitle">Example 1<sup><a class="internalDFN" href="#anexample-mention-rating"><span class="diamond"> ◊</span></a></sup></div>
<p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
-<p>As an illustration, we consider that two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
+<p>As an illustration, we consider <span class="delete">that </span>two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span><span class="insert"> that</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
<pre class="codeexample">bundle ex:run1
activity(ex:a1, 2011-11-16T16:00:00, 2011-11-16T17:00:00) //duration: 1hour
@@ -1149,7 +1152,7 @@
<section id="mention-ontology">
<h2><span class="secno">3. </span>Ontological Definition of Mention</h2>
-<p>The ternary relation <a href="#dfn-mentionof" class="internalDFN">mentionOf</a> is encoded as two properties:
+<p>The ternary relation <span class="delete">mentionOf</span><a title="mentionOf" href="#dfn-mentionof" class="internalDFN"><span class="insert">prov:mentionOf</span></a> is encoded as two properties:
<a href="#mentionOf">prov:mentionOf</a> and
<a href="#asInBundle">prov:asInBundle</a>, defined as follows.</p>
@@ -1195,11 +1198,13 @@
</ul>
</dd>
- <dt>PROV-DM term</dt>
- <dd>
- <a href="#term-mention" title="prov-dm">mention</a> </dd>
+ <span class="delete">PROV-DM term</span>
+
+ <span class="delete">mention</span>
- </dl>
+
+
+ </dl>
</div>
</div>
@@ -1233,18 +1238,22 @@
</ul>
</dd>
- <dt>PROV-DM term</dt>
- <dd>
- <a href="#term-mention" title="prov-dm">mention</a> </dd>
+ <span class="delete">PROV-DM term</span>
+
+ <span class="delete">mention</span>
- </dl>
+
+
+ </dl>
</div>
</div>
<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.</p>
+<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.<span class="insert"> For this, we use teh TRIG notation to express bundles
+</span><span class="name"><span class="insert">:run2</span></span><span class="insert"> and
+</span><span class="name"><span class="insert">tool:analysis01</span></span><span class="insert">.</span></p>
<pre property="prov:value" resource="http://dvcs.w3.org/hg/prov/raw-file/tip/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_mentionOf.ttl" data-rel="prov:wasQuotedFrom">@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@@ -1263,21 +1272,29 @@
.
}
-tool:analysis_01 {
+<span class="delete">tool:analysis_01</span><span class="insert">tool:analysis01</span> {
tool:bob-2011-11-17
a prov:Agent;
prov:mentionOf :bob;
prov:asInBundle :run2;
perf:rating perf:very-slow;
- .
+ .<span class="delete">
}
-# This is inferred from prov:mentionOf
-tool:bob-2011-11-17 prov:specializationOf :bob .
+</span>
-# This is inferred from prov:specializationOf
-tool:bob-2011-11-17 prov:alternateOf :bob .
-</pre>
+ # 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 .
+<span class="insert">}
+
+</span></pre>
</div>
</section>
@@ -1306,7 +1323,7 @@
xmlns:perf="http://example.com/ns/perf#"
xmlns:tool="http://example.com/ns/tool#">
- <prov:bundle prov:id="ex:run1">
+ <span class="delete"><prov:bundle</span><span class="insert"><prov:bundleContent</span> prov:id="ex:run1">
<prov:activity prov:id="ex:a1">
<prov:startTime>2011-11-16T16:00:00</prov:startTime>
<prov:endTime>2011-11-16T17:00:00</prov:endTime>
@@ -1317,9 +1334,9 @@
<prov:agent prov:ref="ex:Bob" />
<prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
- </prov:bundle>
+ <span class="delete"></prov:bundle></span><span class="insert"></prov:bundleContent></span>
- <prov:bundle prov:id="ex:run2">
+ <span class="delete"><prov:bundle</span><span class="insert"><prov:bundleContent</span> prov:id="ex:run2">
<prov:activity prov:id="ex:a2">
<prov:startTime>2011-11-17T10:00:00</prov:startTime>
<prov:endTime>2011-11-17T17:00:00</prov:endTime>
@@ -1330,9 +1347,9 @@
<prov:agent prov:ref="ex:Bob" />
<prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
- </prov:bundle>
+ <span class="delete"></prov:bundle></span><span class="insert"></prov:bundleContent></span>
- <prov:bundle prov:id="tool:analysis01">
+ <span class="delete"><prov:bundle</span><span class="insert"><prov:bundleContent</span> prov:id="tool:analysis01">
<prov:agent prov:id="tool:Bob-2011-11-16">
<ex:perfrating>good</ex:perfrating>
</prov:agent>
@@ -1352,7 +1369,7 @@
<prov:generalEntity prov:ref="ex:Bob" />
<prov:bundle prov:ref="ex:run2" />
</prov:mentionOf></b>
- </prov:bundle>
+ <span class="delete"></prov:bundle></span><span class="insert"></prov:bundleContent></span>
</prov:document></pre></div>
</section>
@@ -1408,6 +1425,10 @@
</span></li><li><span class="insert"> Updated affiliations.
</span></li><li><span class="insert"> Added namespace and convention sections.
</span></li><li><span class="insert"> Updated 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 xml example with new syntax of bundles.
</span></li></ul>
</section>
--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/links/examples/Makefile Wed Feb 27 10:13:34 2013 +0000
@@ -0,0 +1,4 @@
+SCHEMA = ../../examples/eg-40-xml-examples-by-term/xml/ex.xsd
+
+validate:
+ xmllint --noout --schema $(SCHEMA) *.provx
--- a/links/examples/Mention_45.provx Wed Feb 27 01:53:19 2013 -0700
+++ b/links/examples/Mention_45.provx Wed Feb 27 10:13:34 2013 +0000
@@ -10,7 +10,7 @@
xmlns:perf="http://example.com/ns/perf#"
xmlns:tool="http://example.com/ns/tool#">
- <prov:bundle prov:id="ex:run1">
+ <prov:bundleContent prov:id="ex:run1">
<prov:activity prov:id="ex:a1">
<prov:startTime>2011-11-16T16:00:00</prov:startTime>
<prov:endTime>2011-11-16T17:00:00</prov:endTime>
@@ -21,9 +21,9 @@
<prov:agent prov:ref="ex:Bob" />
<prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
- </prov:bundle>
+ </prov:bundleContent>
- <prov:bundle prov:id="ex:run2">
+ <prov:bundleContent prov:id="ex:run2">
<prov:activity prov:id="ex:a2">
<prov:startTime>2011-11-17T10:00:00</prov:startTime>
<prov:endTime>2011-11-17T17:00:00</prov:endTime>
@@ -34,9 +34,9 @@
<prov:agent prov:ref="ex:Bob" />
<prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
- </prov:bundle>
+ </prov:bundleContent>
- <prov:bundle prov:id="tool:analysis01">
+ <prov:bundleContent prov:id="tool:analysis01">
<prov:agent prov:id="tool:Bob-2011-11-16">
<ex:perfrating>good</ex:perfrating>
</prov:agent>
@@ -56,6 +56,6 @@
<prov:generalEntity prov:ref="ex:Bob" />
<prov:bundle prov:ref="ex:run2" />
</prov:mentionOf>
- </prov:bundle>
+ </prov:bundleContent>
</prov:document>
--- a/links/examples/Mention_46.provx Wed Feb 27 01:53:19 2013 -0700
+++ b/links/examples/Mention_46.provx Wed Feb 27 10:13:34 2013 +0000
@@ -11,7 +11,7 @@
xmlns:viz="http://example.com/ns/viz#"
xmlns:obs="http://example.com/ns/obs#">
- <prov:bundle prov:id="obs:bundle1">
+ <prov:bundleContent prov:id="obs:bundle1">
<prov:entity prov:id="ex:report1">
<prov:type xsi:type="xsd:QName">report</prov:type>
<ex:version>1</ex:version>
@@ -36,7 +36,7 @@
<prov:generatedEntity prov:ref="ex:report2"/>
<prov:usedEntity prov:ref="ex:report1"/>
</prov:wasDerivedFrom>
- </prov:bundle>
+ </prov:bundleContent>
<prov:entity prov:id="obs:bundle1">
<prov:type xsi:type="xsd:QName">prov:Bundle</prov:type>
@@ -47,7 +47,7 @@
<prov:agent prov:ref="ex:observer01"/>
</prov:wasAttributedTo>
- <prov:bundle prov:id="tool:bundle2">
+ <prov:bundleContent prov:id="tool:bundle2">
<prov:entity prov:id="tool:bundle2">
<prov:type xsi:type="xsd:QName">viz:Configuration</prov:type>
<prov:type xsi:type="xsd:QName">prov:Bundle</prov:type>
@@ -78,6 +78,6 @@
<prov:bundle prov:ref="obs:bundle1"/>
</prov:mentionOf>
- </prov:bundle>
+ </prov:bundleContent>
</prov:document>
--- a/links/prov-links.html Wed Feb 27 01:53:19 2013 -0700
+++ b/links/prov-links.html Wed Feb 27 10:13:34 2013 +0000
@@ -762,8 +762,8 @@
<h2>Introduction</h2>
<p>
-<a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">Provenance</a>
-is a record that describes the people, institutions, entities, and
+The PROV data model [[PROV-DM]] defines <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">provenance</a>
+as 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
@@ -772,11 +772,13 @@
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/2013/PR-prov-dm-20130312/#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/PR-prov-o-20130312/#Bundle">Bundle</a> [[PROV-O]] and <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/#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/2013/PR-prov-constraints-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-o-20130312/#Bundle">Bundle</a> [[PROV-O]] and <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/#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/PR-prov-constraints-20130312/#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>
<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.
@@ -785,7 +787,7 @@
<section id="prov-namespace">
<h3>PROV Namespace</h3>
-<p>The PROV namespace is <span class="name">http://www.w3.org/ns/prov#</span>.</p>
+<p>The PROV namespace URI is <span class="name">http://www.w3.org/ns/prov#</span> and prefix <span class="name">prov</span>.</p>
<p> All the concepts, reserved names, classes, properties, attributes introduced in this specification belong to the PROV namespace.</p>
</section> <!-- end prov-namespace -->
@@ -822,7 +824,7 @@
<p>
<a href="#figure-component5">Figure 1</a> depicts
-the relation MentionOf (<a>Mention</a>) as a ternary relation.
+the relation MentionOf (concept <a>Mention</a>) as a ternary relation.
</p>
@@ -834,7 +836,7 @@
</div>
-<p>Thus, Mention is a relation between two entities with regard to a bundle.
+<p>Thus, a mention relates two entities with regard to a bundle.
It is a special case of specialization.</p>
@@ -893,15 +895,15 @@
<p>
-Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle. The entity <span class="name">e1</span> may described im multiple other bundle <span class="name">b<sub>i</sub></span>.
-From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of <span class="name">e2</span>. Hence, <span class="name">mentionOf</span> has to be asserted. </p>
+Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle. The entity <span class="name">e1</span> may described in multiple other bundle <span class="name">b<sub>i</sub></span>.
+From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">prov:mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of <span class="name">e2</span>. Hence, <span class="name">prov:mentionOf</span> has to be asserted. </p>
<p><a href="#mention-constraints" class="section-ref"><span>TBD</span></a> presents constraints applicable to <a>Mention</a>, and in particular, the fact that an entity can be a <a href="#mention.specificEntity">specific entity</a> of a <a>Mention</a> at most once.</p>
<div class="anexample" id="anexample-mention-rating">
<p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
-<p>As an illustration, we consider that two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
+<p>As an illustration, we consider two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> that refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
<pre class="codeexample">
bundle ex:run1
@@ -980,7 +982,7 @@
<section id="mention-ontology">
<h2>Ontological Definition of Mention</h2>
-<p>The ternary relation <a>mentionOf</a> is encoded as two properties:
+<p>The ternary relation <a title="mentionOf">prov:mentionOf</a> is encoded as two properties:
<a href="#mentionOf">prov:mentionOf</a> and
<a href="#asInBundle">prov:asInBundle</a>, defined as follows.</p>
@@ -1026,11 +1028,6 @@
</ul>
</dd>
- <dt>PROV-DM term</dt>
- <dd>
- <a href="#term-mention" title="prov-dm">mention</a> </dd>
-
- </dl>
</div>
</div>
@@ -1064,18 +1061,15 @@
</ul>
</dd>
- <dt>PROV-DM term</dt>
- <dd>
- <a href="#term-mention" title="prov-dm">mention</a> </dd>
-
- </dl>
</div>
</div>
<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.</p>
+<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
+<span class="name">:run2</span> and
+<span class="name">tool:analysis01</span>.</p>
<pre property="prov:value" resource="http://dvcs.w3.org/hg/prov/raw-file/tip/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_mentionOf.ttl" data-rel="prov:wasQuotedFrom">@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@@ -1094,20 +1088,21 @@
.
}
-tool:analysis_01 {
+tool:analysis01 {
tool:bob-2011-11-17
a prov:Agent;
prov:mentionOf :bob;
prov:asInBundle :run2;
perf:rating perf:very-slow;
.
+
+ # 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 .
}
-# 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>
</div>
</section>
@@ -1137,7 +1132,7 @@
xmlns:perf="http://example.com/ns/perf#"
xmlns:tool="http://example.com/ns/tool#">
- <prov:bundle prov:id="ex:run1">
+ <prov:bundleContent prov:id="ex:run1">
<prov:activity prov:id="ex:a1">
<prov:startTime>2011-11-16T16:00:00</prov:startTime>
<prov:endTime>2011-11-16T17:00:00</prov:endTime>
@@ -1148,9 +1143,9 @@
<prov:agent prov:ref="ex:Bob" />
<prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
- </prov:bundle>
+ </prov:bundleContent>
- <prov:bundle prov:id="ex:run2">
+ <prov:bundleContent prov:id="ex:run2">
<prov:activity prov:id="ex:a2">
<prov:startTime>2011-11-17T10:00:00</prov:startTime>
<prov:endTime>2011-11-17T17:00:00</prov:endTime>
@@ -1161,9 +1156,9 @@
<prov:agent prov:ref="ex:Bob" />
<prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
- </prov:bundle>
+ </prov:bundleContent>
- <prov:bundle prov:id="tool:analysis01">
+ <prov:bundleContent prov:id="tool:analysis01">
<prov:agent prov:id="tool:Bob-2011-11-16">
<ex:perfrating>good</ex:perfrating>
</prov:agent>
@@ -1183,7 +1178,7 @@
<prov:generalEntity prov:ref="ex:Bob" />
<prov:bundle prov:ref="ex:run2" />
</prov:mentionOf></b>
- </prov:bundle>
+ </prov:bundleContent>
</prov:document></pre></div>
</section>
@@ -1243,6 +1238,10 @@
<li> Updated affiliations.
<li> Added namespace and convention sections.
<li> Updated grammar to make prov prefix explicit.
+<li> Added new paragraph in introduction.
+<li> Moved "inferred statements" into named graph tool:analysis01 in Example 3.
+<li> Added comment on TRIG notation.
+<li> Updated xml example with new syntax of bundles.
</ul>
</section>
--- a/links/releases/WD-prov-links-20130312/Overview.html Wed Feb 27 01:53:19 2013 -0700
+++ b/links/releases/WD-prov-links-20130312/Overview.html Wed Feb 27 10:13:34 2013 +0000
@@ -903,8 +903,8 @@
<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2>
<p>
-<a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">Provenance</a>
-is a record that describes the people, institutions, entities, and
+The PROV data model [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>] defines <a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">provenance</a>
+as 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 [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>], [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>],
[<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
@@ -913,11 +913,13 @@
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/2013/PR-prov-dm-20130312/#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/PR-prov-o-20130312/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>] and <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/#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 illustrated by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/#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/PR-prov-dm-20130312/#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/PR-prov-o-20130312/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>] and <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/#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/PR-prov-constraints-20130312/#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>
<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.
@@ -926,7 +928,7 @@
<section id="prov-namespace">
<h3><span class="secno">1.1 </span>PROV Namespace</h3>
-<p>The PROV namespace is <span class="name">http://www.w3.org/ns/prov#</span>.</p>
+<p>The PROV namespace URI is <span class="name">http://www.w3.org/ns/prov#</span> and prefix <span class="name">prov</span>.</p>
<p> All the concepts, reserved names, classes, properties, attributes introduced in this specification belong to the PROV namespace.</p>
</section> <!-- end prov-namespace -->
@@ -964,7 +966,7 @@
<p>
<a href="#figure-component5">Figure 1</a> depicts
-the relation MentionOf (<a href="#concept-mention" class="internalDFN">Mention</a>) as a ternary relation.
+the relation MentionOf (concept <a href="#concept-mention" class="internalDFN">Mention</a>) as a ternary relation.
</p>
@@ -976,7 +978,7 @@
</div>
-<p>Thus, Mention is a relation between two entities with regard to a bundle.
+<p>Thus, a mention relates two entities with regard to a bundle.
It is a special case of specialization.</p>
@@ -1035,15 +1037,15 @@
<p>
-Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle. The entity <span class="name">e1</span> may described im multiple other bundle <span class="name">b<sub>i</sub></span>.
-From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of <span class="name">e2</span>. Hence, <span class="name">mentionOf</span> has to be asserted. </p>
+Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle. The entity <span class="name">e1</span> may described in multiple other bundle <span class="name">b<sub>i</sub></span>.
+From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">prov:mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of <span class="name">e2</span>. Hence, <span class="name">prov:mentionOf</span> has to be asserted. </p>
<p><a href="#mention-constraints" class="section-ref"><span>Section 5.</span></a> presents constraints applicable to <a href="#concept-mention" class="internalDFN">Mention</a>, and in particular, the fact that an entity can be a <a href="#mention.specificEntity">specific entity</a> of a <a href="#concept-mention" class="internalDFN">Mention</a> at most once.</p>
<div class="anexample" id="anexample-mention-rating"><div class="anexampleTitle">Example 1<sup><a class="internalDFN" href="#anexample-mention-rating"><span class="diamond"> ◊</span></a></sup></div>
<p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
-<p>As an illustration, we consider that two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
+<p>As an illustration, we consider two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> that refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
<pre class="codeexample">bundle ex:run1
activity(ex:a1, 2011-11-16T16:00:00, 2011-11-16T17:00:00) //duration: 1hour
@@ -1120,7 +1122,7 @@
<section id="mention-ontology">
<!--OddPage--><h2><span class="secno">3. </span>Ontological Definition of Mention</h2>
-<p>The ternary relation <a href="#dfn-mentionof" class="internalDFN">mentionOf</a> is encoded as two properties:
+<p>The ternary relation <a title="mentionOf" href="#dfn-mentionof" class="internalDFN">prov:mentionOf</a> is encoded as two properties:
<a href="#mentionOf">prov:mentionOf</a> and
<a href="#asInBundle">prov:asInBundle</a>, defined as follows.</p>
@@ -1166,12 +1168,7 @@
</ul>
</dd>
- <dt>PROV-DM term</dt>
- <dd>
- <a href="#term-mention" title="prov-dm">mention</a> </dd>
-
- </dl>
- </div>
+ </dl></div>
</div>
@@ -1204,18 +1201,15 @@
</ul>
</dd>
- <dt>PROV-DM term</dt>
- <dd>
- <a href="#term-mention" title="prov-dm">mention</a> </dd>
-
- </dl>
- </div>
+ </dl></div>
</div>
<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.</p>
+<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
+<span class="name">:run2</span> and
+<span class="name">tool:analysis01</span>.</p>
<pre property="prov:value" resource="http://dvcs.w3.org/hg/prov/raw-file/tip/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_mentionOf.ttl" data-rel="prov:wasQuotedFrom">@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@@ -1234,20 +1228,21 @@
.
}
-tool:analysis_01 {
+tool:analysis01 {
tool:bob-2011-11-17
a prov:Agent;
prov:mentionOf :bob;
prov:asInBundle :run2;
perf:rating perf:very-slow;
.
+
+ # 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 .
}
-# 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>
</div>
</section>
@@ -1277,7 +1272,7 @@
xmlns:perf="http://example.com/ns/perf#"
xmlns:tool="http://example.com/ns/tool#">
- <prov:bundle prov:id="ex:run1">
+ <prov:bundleContent prov:id="ex:run1">
<prov:activity prov:id="ex:a1">
<prov:startTime>2011-11-16T16:00:00</prov:startTime>
<prov:endTime>2011-11-16T17:00:00</prov:endTime>
@@ -1288,9 +1283,9 @@
<prov:agent prov:ref="ex:Bob" />
<prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
- </prov:bundle>
+ </prov:bundleContent>
- <prov:bundle prov:id="ex:run2">
+ <prov:bundleContent prov:id="ex:run2">
<prov:activity prov:id="ex:a2">
<prov:startTime>2011-11-17T10:00:00</prov:startTime>
<prov:endTime>2011-11-17T17:00:00</prov:endTime>
@@ -1301,9 +1296,9 @@
<prov:agent prov:ref="ex:Bob" />
<prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
- </prov:bundle>
+ </prov:bundleContent>
- <prov:bundle prov:id="tool:analysis01">
+ <prov:bundleContent prov:id="tool:analysis01">
<prov:agent prov:id="tool:Bob-2011-11-16">
<ex:perfrating>good</ex:perfrating>
</prov:agent>
@@ -1323,7 +1318,7 @@
<prov:generalEntity prov:ref="ex:Bob" />
<prov:bundle prov:ref="ex:run2" />
</prov:mentionOf></b>
- </prov:bundle>
+ </prov:bundleContent>
</prov:document></pre></div>
</section>
@@ -1375,6 +1370,10 @@
</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></ul>
</section>
--- a/links/releases/WD-prov-links-20130312/diff.html Wed Feb 27 01:53:19 2013 -0700
+++ b/links/releases/WD-prov-links-20130312/diff.html Wed Feb 27 10:13:34 2013 +0000
@@ -931,8 +931,9 @@
<h2><span class="secno">1. </span>Introduction</h2>
<p>
-<a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/">Provenance</a>
-is a record that describes the people, institutions, entities, and
+<span class="delete">Provenance</span><span class="delete">
+is</span><span class="insert">The PROV data model [</span><cite><a class="bibref" href="#bib-PROV-DM"><span class="insert">PROV-DM</span></a></cite><span class="insert">] defines </span><a href="http://www.w3.org/TR/2013/PR-prov-dm-20130312/"><span class="insert">provenance</span></a><span class="insert">
+as</span> 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 [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>], [<cite><a class="bibref" href="#bib-PROV-DM">PROV-DM</a></cite>],
[<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
@@ -941,11 +942,13 @@
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/2013/PR-prov-dm-20130312/#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/PR-prov-o-20130312/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>] and <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/#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 illustrated by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/#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/PR-prov-dm-20130312/#concept-bundle">Bundle</a>: defined as a set of provenance <span class="delete">descriptions,</span><span class="insert">descriptions;</span> it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2013/PR-prov-o-20130312/#Bundle">Bundle</a> [<cite><a class="bibref" href="#bib-PROV-O">PROV-O</a></cite>] and <a href="http://www.w3.org/TR/2013/WD-prov-xml-20130312/#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 <span class="delete">illustrated</span><span class="insert">formalized</span> by [<cite><a class="bibref" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] which determines their <a href="http://www.w3.org/TR/2013/PR-prov-constraints-20130312/#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><span class="insert">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. </span></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>
<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.
@@ -955,7 +958,7 @@
<section id="prov-namespace">
<h3><span class="secno"><span class="insert">1.1 </span></span><span class="insert">PROV Namespace</span></h3>
-<p><span class="insert">The PROV namespace is </span><span class="name"><span class="insert">http://www.w3.org/ns/prov#</span></span><span class="insert">.</span></p>
+<p><span class="insert">The PROV namespace URI is </span><span class="name"><span class="insert">http://www.w3.org/ns/prov#</span></span><span class="insert"> and prefix </span><span class="name"><span class="insert">prov</span></span><span class="insert">.</span></p>
<p><span class="insert"> All the concepts, reserved names, classes, properties, attributes introduced in this specification belong to the PROV namespace.</span></p>
</section>
@@ -993,7 +996,7 @@
<p>
<a href="#figure-component5">Figure 1</a> depicts
-the relation MentionOf (<a href="#concept-mention" class="internalDFN"><span class="delete">mention</span><span class="insert">Mention</span></a>) as a ternary relation.
+the relation MentionOf <span class="delete">(</span><span class="insert">(concept </span><a href="#concept-mention" class="internalDFN"><span class="delete">mention</span><span class="insert">Mention</span></a>) as a ternary relation.
</p>
@@ -1005,7 +1008,7 @@
</div>
-<p>Thus, Mention is a relation between two entities with regard to a bundle.
+<p>Thus, <span class="delete">Mention is </span>a <span class="delete">relation between</span><span class="insert">mention relates</span> two entities with regard to a bundle.
It is a special case of specialization.</p>
@@ -1064,15 +1067,15 @@
<p>
-Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle. The entity <span class="name">e1</span> may described im multiple other bundle <span class="name">b<sub>i</sub></span>.
-From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name">mentionOf(e2,e1,b)</span> for a given <span class="name">b</span>, since it is unknown which <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of <span class="name">e2</span>. Hence, <span class="name">mentionOf</span> has to be asserted. </p>
+Let us consider a bundle and the expression <span class="name">specializationOf(e2,e1)</span> occuring in this bundle. The entity <span class="name">e1</span> may described <span class="delete">im</span><span class="insert">in</span> multiple other bundle <span class="name">b<sub>i</sub></span>.
+From <span class="name">specializationOf(e2,e1)</span>, one cannot infer <span class="name"><span class="delete">mentionOf(e2,e1,b)</span><span class="insert">prov:mentionOf(e2,e1,b)</span></span> for a given <span class="name">b</span>, since it is unknown which <span class="name">b<sub>i</sub></span>'s descriptions were used to computed additional aspects of <span class="name">e2</span>. Hence, <span class="name"><span class="delete">mentionOf</span><span class="insert">prov:mentionOf</span></span> has to be asserted. </p>
<p><a href="#mention-constraints" class="section-ref"><span>Section 5.</span></a> presents constraints applicable to <a href="#concept-mention" class="internalDFN">Mention</a>, and in particular, the fact that an entity can be a <a href="#mention.specificEntity">specific entity</a> of a <a href="#concept-mention" class="internalDFN">Mention</a> at most once.</p>
<div class="anexample" id="anexample-mention-rating"><div class="anexampleTitle">Example 1<sup><a class="internalDFN" href="#anexample-mention-rating"><span class="diamond"> ◊</span></a></sup></div>
<p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents. To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
-<p>As an illustration, we consider that two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
+<p>As an illustration, we consider <span class="delete">that </span>two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span><span class="insert"> that</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
<pre class="codeexample">bundle ex:run1
activity(ex:a1, 2011-11-16T16:00:00, 2011-11-16T17:00:00) //duration: 1hour
@@ -1149,7 +1152,7 @@
<section id="mention-ontology">
<h2><span class="secno">3. </span>Ontological Definition of Mention</h2>
-<p>The ternary relation <a href="#dfn-mentionof" class="internalDFN">mentionOf</a> is encoded as two properties:
+<p>The ternary relation <span class="delete">mentionOf</span><a title="mentionOf" href="#dfn-mentionof" class="internalDFN"><span class="insert">prov:mentionOf</span></a> is encoded as two properties:
<a href="#mentionOf">prov:mentionOf</a> and
<a href="#asInBundle">prov:asInBundle</a>, defined as follows.</p>
@@ -1195,11 +1198,13 @@
</ul>
</dd>
- <dt>PROV-DM term</dt>
- <dd>
- <a href="#term-mention" title="prov-dm">mention</a> </dd>
+ <span class="delete">PROV-DM term</span>
+
+ <span class="delete">mention</span>
- </dl>
+
+
+ </dl>
</div>
</div>
@@ -1233,18 +1238,22 @@
</ul>
</dd>
- <dt>PROV-DM term</dt>
- <dd>
- <a href="#term-mention" title="prov-dm">mention</a> </dd>
+ <span class="delete">PROV-DM term</span>
+
+ <span class="delete">mention</span>
- </dl>
+
+
+ </dl>
</div>
</div>
<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.</p>
+<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.<span class="insert"> For this, we use teh TRIG notation to express bundles
+</span><span class="name"><span class="insert">:run2</span></span><span class="insert"> and
+</span><span class="name"><span class="insert">tool:analysis01</span></span><span class="insert">.</span></p>
<pre property="prov:value" resource="http://dvcs.w3.org/hg/prov/raw-file/tip/examples/eg-24-prov-o-html-examples/rdf/create/rdf/property_mentionOf.ttl" data-rel="prov:wasQuotedFrom">@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@@ -1263,21 +1272,29 @@
.
}
-tool:analysis_01 {
+<span class="delete">tool:analysis_01</span><span class="insert">tool:analysis01</span> {
tool:bob-2011-11-17
a prov:Agent;
prov:mentionOf :bob;
prov:asInBundle :run2;
perf:rating perf:very-slow;
- .
+ .<span class="delete">
}
-# This is inferred from prov:mentionOf
-tool:bob-2011-11-17 prov:specializationOf :bob .
+</span>
-# This is inferred from prov:specializationOf
-tool:bob-2011-11-17 prov:alternateOf :bob .
-</pre>
+ # 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 .
+<span class="insert">}
+
+</span></pre>
</div>
</section>
@@ -1306,7 +1323,7 @@
xmlns:perf="http://example.com/ns/perf#"
xmlns:tool="http://example.com/ns/tool#">
- <prov:bundle prov:id="ex:run1">
+ <span class="delete"><prov:bundle</span><span class="insert"><prov:bundleContent</span> prov:id="ex:run1">
<prov:activity prov:id="ex:a1">
<prov:startTime>2011-11-16T16:00:00</prov:startTime>
<prov:endTime>2011-11-16T17:00:00</prov:endTime>
@@ -1317,9 +1334,9 @@
<prov:agent prov:ref="ex:Bob" />
<prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
- </prov:bundle>
+ <span class="delete"></prov:bundle></span><span class="insert"></prov:bundleContent></span>
- <prov:bundle prov:id="ex:run2">
+ <span class="delete"><prov:bundle</span><span class="insert"><prov:bundleContent</span> prov:id="ex:run2">
<prov:activity prov:id="ex:a2">
<prov:startTime>2011-11-17T10:00:00</prov:startTime>
<prov:endTime>2011-11-17T17:00:00</prov:endTime>
@@ -1330,9 +1347,9 @@
<prov:agent prov:ref="ex:Bob" />
<prov:role xsi:type="xsd:QName">controller</prov:role>
</prov:wasAssociatedWith>
- </prov:bundle>
+ <span class="delete"></prov:bundle></span><span class="insert"></prov:bundleContent></span>
- <prov:bundle prov:id="tool:analysis01">
+ <span class="delete"><prov:bundle</span><span class="insert"><prov:bundleContent</span> prov:id="tool:analysis01">
<prov:agent prov:id="tool:Bob-2011-11-16">
<ex:perfrating>good</ex:perfrating>
</prov:agent>
@@ -1352,7 +1369,7 @@
<prov:generalEntity prov:ref="ex:Bob" />
<prov:bundle prov:ref="ex:run2" />
</prov:mentionOf></b>
- </prov:bundle>
+ <span class="delete"></prov:bundle></span><span class="insert"></prov:bundleContent></span>
</prov:document></pre></div>
</section>
@@ -1408,6 +1425,10 @@
</span></li><li><span class="insert"> Updated affiliations.
</span></li><li><span class="insert"> Added namespace and convention sections.
</span></li><li><span class="insert"> Updated 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 xml example with new syntax of bundles.
</span></li></ul>
</section>