--- a/links/prov-links.html Mon Nov 26 13:43:32 2012 +0000
+++ b/links/prov-links.html Tue Nov 27 11:43:03 2012 +0000
@@ -628,83 +628,11 @@
berjon.biblio[k] = extraReferences[k];
};
var extraReferences = {
- "CLOCK":
- "Lamport, L. "+
- "<a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\"><cite>Time, clocks, and the ordering of events in a distributed system</cite></a>."+
- "Communications of the ACM 21 (7): 558–565. 1978. "+
- "URL: <a href=\"http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf\">http://research.microsoft.com/users/lamport/pubs/time-clocks.pdf</a> " +
- "DOI: doi:10.1145/359545.359563.",
- "CSP":
- "Hoare, C. A. R. "+
- "<a href=\"http://www.usingcsp.com/cspbook.pdf\"><cite>Communicating Sequential Processes</cite></a>."+
- "Prentice-Hall. 1985"+
- "URL: <a href=\"http://www.usingcsp.com/cspbook.pdf\">http://www.usingcsp.com/cspbook.pdf</a>",
- "Logic":
- "W. E. Johnson "+
- "<a href=\"http://www.ditext.com/johnson/intro-3.html\"><cite>Logic: Part III</cite></a>."+
- "1924. "+
- "URL: <a href=\"http://www.ditext.com/johnson/intro-3.html\">http://www.ditext.com/johnson/intro-3.html</a>",
- "PROV-SEM":
- "James Cheney "+
- "<a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\"><cite>Formal Semantics Strawman</cite></a>. "+
- "2011, Work in progress. "+
- "URL: <a href=\"http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman\">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>",
-
- "PROV-PRIMER":
- "Yolanda Gil and Simon Miles (eds.) Khalid Belhajjame, Helena Deus, Daniel Garijo, Graham Klyne, Paolo Missier, Stian Soiland-Reyes, and Stephan Zednik "+
- "<a href=\"http://www.w3.org/TR/prov-primer/\"><cite>Prov Model Primer</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-primer/\">http://www.w3.org/TR/prov-primer/</a>",
-
- "PROV-O":
- "Timothy Lebo, Satya Sahoo and Deborah McGuinness (eds.) Khalid Belhajjame, James Cheney, David Corsar, Daniel Garijo, Stian Soiland-Reyes, and Stephan Zednik "+
- "<a href=\"http://www.w3.org/TR/prov-o/\"><cite>Provenance Formal Model</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-o/\">http://www.w3.org/TR/prov-o/</a>",
-
-
- "PROV-CONSTRAINTS":
- "James Cheney, Paolo Missier, and Luc Moreau (eds.) "+
- "<a href=\"http://www.w3.org/TR/prov-constraints/\"><cite>Constraints of the PROV Data Model</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-constraints/\">http://www.w3.org/TR/prov-constraints/</a>",
-
- "PROV-N":
- "Luc Moreau and Paolo Missier (eds.) James Cheney, Stian Soiland-Reyes "+
- "<a href=\"http://www.w3.org/TR/prov-n/\"><cite>PROV-N: The Provenance Notation</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-n/\">http://www.w3.org/TR/prov-n/</a>",
-
- "PROV-AQ":
- "Graham Klyne and Paul Groth (eds.) Luc Moreau, Olaf Hartig, Yogesh Simmhan, James Meyers, Timothy Lebo, Khalid Belhajjame, and Simon Miles "+
- "<a href=\"http://www.w3.org/TR/prov-aq/\"><cite>Provenance Access and Query</cite></a>. "+
- "2012, Working Draft. "+
- "URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
-
- "UML":
- "Object Management Group "+
- "<a href=\"http://www.omg.org/spec/UML/2.0/Superstructure/PDF/\"><cite>Unified Modeling Language: Superstructure</cite></a>. "+
- "version 2.0, 2005 "+
- "URL: <a href=\"http://www.omg.org/spec/UML/2.0/Superstructure/PDF/\">http://www.omg.org/spec/UML/2.0/Superstructure/PDF/</a>",
-
- "RDF-CONCEPTS11":
- "Richard Cyganiak and David Wood (eds.) " +
- "RDF 1.1 Concepts and Abstract Syntax "+
- "<a href=\"http://www.w3.org/TR/rdf11-concepts/\"><cite>RDF 1.1 Concepts and Abstract Syntax</cite></a>. "+
- "URL: <a href=\"http://www.w3.org/TR/rdf11-concepts/\">http://www.w3.org/TR/rdf11-concepts/</a>",
-
- "Mappings":
- "Satya Sahoo and Paul Groth and Olaf Hartig and Simon Miles and Sam Coppens and James Myers and Yolanda Gil and Luc Moreau and Jun Zhao and Michael Panzer and Daniel Garijo "+
- "<a href=\"http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings\"><cite>Provenance Vocabulary Mappings</cite></a>. "+
- "August 2010 "+
- "URL: <a href=\"http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings\">http://www.w3.org/2005/Incubator/prov/wiki/Provenance_Vocabulary_Mappings</a>",
-
-
};
var respecConfig = {
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
+ specStatus: "ED", //FPWD-NOTE
// the specification's short name, as in http://www.w3.org/TR/short-name/
shortName: "prov-links",
@@ -782,11 +710,17 @@
Provenance is information about entities, activities, and people
involved in producing a piece of data or thing, which can be used to
form assessments about its quality, reliability or trustworthiness.
-Bundles, defined as sets of provenance descriptions, are a mechanism by
-which provenance of provenance can be expressed.</p>
+<a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/#dfn-bundle">Bundles</a>,
+defined in [[!PROV-DM]] as sets of provenance descriptions, were
+introduced in PROV as the mechanism by which provenance of provenance
+can be expressed. Bundles, whose validity is established
+independently of each other [[!PROV-CONSTRAINTS]], are essentially
+independent of each other, acting as islands of provenance
+descriptions.
+</p>
<p>
-In applications where provenance is created by multiple parties over time, it is useful for provenance descriptions created by one party to link to provenance descriptions created by another party. To address this requirement, this document introduces a relation allowing an entity description to be linked to another entity description occurring in another bundle.
+In applications where provenance is created by multiple parties over time, it is useful for provenance descriptions created by one party to link to provenance descriptions created by another party. Such a mechanism would allow the "stitching" of provenance descriptions together. Given that provenance descriptions are expected to be contained in bundles, this would require a capability to link entity descriptions across bundles. To address this requirement, this document introduces a relation <a>Mention</a> allowing an entity description to be linked to another entity description occurring in another bundle.
</p>
<p>The <a href="http://www.w3.org/TR/2012/WD-prov-overview-20121211/">PROV Document Overview</a> describes the overall state of PROV, and should be read before other PROV documents.</p>
@@ -806,7 +740,7 @@
<li> <a href="http://www.w3.org/TR/2012/CR-prov-constraints-20121211/">PROV-CONSTRAINTS</a> (Candidate Recommendation), a set of constraints applying to the PROV data model [[!PROV-CONSTRAINTS]];</li>
<li> <a href="http://www.w3.org/TR/2012/WD-prov-aq-20120619/">PROV-AQ</a> (To be published as Note), the mechanisms for accessing and querying provenance [[PROV-AQ]]; </li>
<li> <a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211/">PROV-XML</a> (To be published as Note), an XML schema for the PROV data model [[PROV-XML]];</li>
-<li> <a href="http://www.w3.org/TR/2012/WD-prov-link-20121211/">PROV-LINK</a> (To be published as Note), introduces a mechanism to link across bundles (this document).</li>
+<li> <a href="http://www.w3.org/TR/2012/WD-prov-links-20121211/">PROV-LINKS</a> (To be published as Note), introduces a mechanism to link across bundles (this document).</li>
</ul>
<h4>How to read the PROV Family of Documentation</h4>
@@ -841,10 +775,10 @@
represented in various representations, and interchanged between systems across the Web.
</p>
-<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it. To support this, provenance should be trusted, and therefore, provenance of provenance is itself a critical aspect of an information infrastructure such as the Web. To this end, PROV introduces the concept of <a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/#concept-bundle">Bundle</a>: defined as a set of provenance descriptions, it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2012/CR-prov-o-20121211/#Bundle">Bundle</a> [[!PROV-O]] and <a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211/#term-Bundle">Bundle</a> [[PROV-XML]]). With bundles, blobs of provenance descriptions can be given names and can themselves be regarded as entities, whose provenance can in turn be described using PROV. </p>
+<p>The provenance of information is crucial in deciding whether information is to be trusted, how it should be integrated with other diverse information sources, and how to give credit to its originators when reusing it. To support this, provenance itself should be trusted, and therefore, provenance of provenance is itself a critical aspect of an information infrastructure such as the Web. To this end, PROV introduces the concept of <a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/#concept-bundle">Bundle</a>: defined as a set of provenance descriptions, it is a mechanism by which provenance of provenance can be expressed (see also <a href="http://www.w3.org/TR/2012/CR-prov-o-20121211/#Bundle">Bundle</a> [[!PROV-O]] and <a href="http://www.w3.org/TR/2012/WD-prov-xml-20121211/#term-Bundle">Bundle</a> [[PROV-XML]]). With bundles, blobs of provenance descriptions can be given names and can themselves be regarded as entities, whose provenance can in turn be described using PROV. These blobs of provenance descriptions are independent of each other, as illustrated by [[!PROV-CONSTRAINTS]] which determines their <a href="http://www.w3.org/TR/2012/CR-prov-constraints-20121211/#bundle-constraints">validity</a> by examining them in isolation of each other. </p>
-<p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party creates some data and its provenance, whereas another party consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by another producer. For the consumer, it is not suitable to repeat the provenance created by the producer, and augment it according to their need. Instead, a consumer wants to <em>refer</em> to the description as created by the producer <em>in situ</em>, i.e. in its bundle, and <em>specialize it</em>, allowing the consumer to add their own view on this entity.</p>
+<p>In a distributed environment, it is common to encounter applications that involve multiple parties: it is a common situation that some party creates some data and its provenance, whereas another party consumes the data and its provenance. In such a situation, the consumer, when it in turn generates provenance, often wants to augment the descriptions of entities generated by another producer. For the consumer, it is not suitable to repeat the provenance created by the producer, and augment it according to their need. Instead, a consumer wants to <em>refer</em> to the description as created by the producer <em>in situ</em>, i.e. in its bundle, and <em>specialize it</em>, allowing the consumer to add their own view on this entity. Such a capability would allow parties to "stitch together" provenance descriptions that would otherwise be disconnected.</p>
<p>This document introduces a new concept <a>Mention</a> allowing an entity to be described as the specialization of another entity, itself described in another bundle. The document provides not only a conceptual definition of <a>Mention</a>, but also the corresponding ontological, schema, and notational definitions, for the various representations of PROV. It also includes constraints that apply to this construct specifically. It is our aim to promote inter-operability by defining <a>Mention</a> conceptually and in the representations of PROV.</p>
@@ -852,7 +786,7 @@
</div>
</section>
-<section id="mention-dm">
+<section id="term-mention">
<h2>Conceptual Definition of Mention</h2>
@@ -862,9 +796,9 @@
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.
-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 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>
+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>.
-Thus, the mentionOf relation cannot be inferred from knowing that <span class="name">e2</span> is a specialization of <span class="name">e1</span> that appears in bundle <span class="name">b</span>.</p>
+</p>
<p>
@@ -881,7 +815,7 @@
</div>
-<p>Thus, the following notion is a relation between two entities with regard to a bundle.
+<p>Thus, Mention is a relation between two entities with regard to a bundle.
It is a special case of specialization.</p>
@@ -912,7 +846,7 @@
</ul>
</div>
-<p>A mention is not, as defined here, an influence, and therefore does not have an id and attributes.
+<p>Like <a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/#dfn-specialization">specialization</a>, a mention is not, as defined here, an <a href="http://www.w3.org/TR/2012/CR-prov-dm-20121211/#dfn-influence">influence</a>, and therefore does not have an id and attributes.
Its grammar, in the provenance notation, is written as follows.</p>
<table class="grammar">
@@ -939,6 +873,12 @@
</div>
+<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>
+
+<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>
@@ -955,7 +895,7 @@
wasAssociatedWith(ex:a2, ex:Bob, [prov:role="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.
+<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>
<pre class="codeexample">
bundle tool:analysis01
@@ -969,6 +909,8 @@
</div>
+
+
<div class="anexample" id="aexample-mention-viz">
<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
<pre class="codeexample">
@@ -998,6 +940,8 @@
<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming visualisation-specific attributes, types or values.</p>
+<p>This example is typical of a common situation in distributed environments, where the consumer and producer of provenance are different.</p>
+
<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualisation tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
</p>
@@ -1065,7 +1009,7 @@
<dt>PROV-DM term</dt>
<dd>
- <a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/Overview.html#term-mention" title="prov-dm">mention</a> </dd>
+ <a href="#term-mention" title="prov-dm">mention</a> </dd>
</dl>
</div>
@@ -1103,7 +1047,7 @@
<dt>PROV-DM term</dt>
<dd>
- <a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/Overview.html#term-mention" title="prov-dm">mention</a> </dd>
+ <a href="#term-mention" title="prov-dm">mention</a> </dd>
</dl>
</div>