--- a/model/diff.html Mon Oct 22 18:46:59 2012 +0200
+++ b/model/diff.html Mon Oct 22 18:48:07 2012 +0200
@@ -1026,7 +1026,7 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><link href="./extra-dm.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8"></head>
- <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">PROV-DM: The PROV Data Model</h1><h2 id="subtitle"><a href="diff.html"><span class="insert">Changes</span></a><span class="insert"> since LC release</span></h2><h2 id="w3c-editor-s-draft-11-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">11 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+ <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">PROV-DM: The PROV Data Model</h1><h2 id="subtitle"><a href="diff.html"><span class="insert">Changes</span></a><span class="insert"> since LC release</span></h2><h2 id="w3c-editor-s-draft-22-october-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">22 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
<dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University</dd>
<dt><span class="delete">Contributors:</span><span class="insert">Authors:</span></dt><dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester</dd>
<dd><span>Reza B'Far</span>, Oracle Corporation</dd>
@@ -1653,9 +1653,15 @@
<p><a class="section-ref" href="#core-structures"><span>Section 2.1</span></a> shows that seven concepts are mapped to binary relations in the core of PROV. However, some advanced uses of these concepts cannot be captured by a binary relation, but require relations to be expanded to n-ary relations.</p>
+
+
+<p><span class="insert">Indeed, binary relations are actually shorthands that can be 'opened up' by applications and filled in with further application details. For example, derivation is a very high level relationship between two entities: an application may decide to 'open up' that relationship in an expanded relation that describes how an entity was derived from another by virtue of listing the generation, usage, and activity involved in the 'WasDerivedFrom' relationship. Applications are free to decide which level of granularity they want describe, and PROV gives them the way to do that.</span></p>
+
+
+
<p>To illustrate expanded relations, we consider the concept of
association, described
-in <a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a>. Agents may adopt <em>plans</em>, i.e. sets of actions or steps, to achieve their
+in <a class="section-ref" href="#section-agents-attribution-association-delegation"><span>Section 2.1.3</span></a>. Agents may <span class="delete">adopt</span><span class="insert">rely on</span> <em>plans</em>, i.e. sets of actions or steps, to achieve their
goals in the context of an activity.
Hence, an expanded form of
association relation allows for a plan to be specified. Plan is defined by subtyping and
@@ -1829,19 +1835,21 @@
<div class="anexample" id="anexample-prov-n"><div class="anexampleTitle">Example <span class="delete">15</span><span class="insert">16</span><sup><a class="internalDFN" href="#anexample-prov-n"><span class="diamond"> ◊</span></a></sup></div>
<p>
An activity with identifier <span class="name">a1</span> and an attribute <span class="name">type</span> with value <span class="name">createFile</span>.
-</p><pre class="codeexample">activity(a1, [prov:type="createFile"])
+</p><pre class="codeexample">activity(a1, <span class="delete">[prov:type="createFile"])</span><span class="insert">[ prov:type="createFile" ])</span>
</pre>
Two entities with identifiers <span class="name">e1</span> and <span class="name">e2</span>.
<pre class="codeexample">entity(e1)
entity(e2)
</pre>
The activity <span class="name">a1</span> used <span class="name">e1</span>, and <span class="name">e2</span> was generated by <span class="name">a1</span>.
-<pre class="codeexample">used(a1,e1)
-wasGeneratedBy(e2,a1)
+<pre class="codeexample"><span class="delete">used(a1,e1)
+wasGeneratedBy(e2,a1)</span><span class="insert">used(a1, e1)
+wasGeneratedBy(e2, a1)</span>
</pre>
The same descriptions, but with an explicit identifier <span class="name">u1</span> for the usage, and the syntactic marker '<span class="name">-</span>' to mark the absence of identifier in the generation. Both are followed by '<span class="name">;</span>'.
-<pre class="codeexample">used(u1;a1,e1)
-wasGeneratedBy(-;e2,a1)
+<pre class="codeexample"><span class="delete">used(u1;a1,e1)
+wasGeneratedBy(-;e2,a1)</span><span class="insert">used(u1; a1, e1)
+wasGeneratedBy(-; e2, a1)</span>
</pre>
</div>
@@ -1897,11 +1905,11 @@
</li>
<li>There was an editing activity.
-<pre>activity(ex:edit1,[prov:type="edit"])
+<pre><span class="delete">activity(ex:edit1,[prov:type="edit"])</span><span class="insert">activity(ex:edit1, [ prov:type="edit" ])</span>
</pre>
</li>
-<li>The document was generated by the editing activity: this was a <a title="concept-generation">Generation</a>.
+<li>The document was generated by the editing activity: this was a <a title="concept-generation">Generation</a>.<span class="insert"> Its time is not specified, hence, the marker '-'.</span>
<pre>wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
</pre>
</li>
@@ -1913,7 +1921,7 @@
</pre>
</li>
-<li>Agents were assigned various responsibilities in the editing activity: contributor and editor.
+<li>Agents were assigned various responsibilities in the editing activity: contributor and editor.<span class="insert"> The plan the agent relied upon is not specified, hence, the marker '-'.</span>
<pre>wasAssociatedWith(ex:edit1, ex:Paolo, -, [ prov:role="editor" ])
wasAssociatedWith(ex:edit1, ex:Simon, -, [ prov:role="contributor" ])
</pre>
@@ -1983,11 +1991,11 @@
</pre>
</li>
<li>There was a publication activity.
-<pre>activity(ex:act2,[prov:type="publish"])
+<pre><span class="delete">activity(ex:act2,[prov:type="publish"])</span><span class="insert">activity(ex:act2, [ prov:type="publish" ])</span>
</pre>
</li>
-<li>The document was generated by the publication activity: this was a <a title="concept-Generation">Generation</a>.
+<li>The document was generated by the publication activity: this was a <a title="concept-Generation">Generation</a>.<span class="insert"> Its time is not specified, hence, the marker '-'.</span>
<pre>wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2, -)
</pre>
</li>
@@ -1998,7 +2006,7 @@
</pre>
</li>
-<li>The activity required a publication request: this was a <a title="concept-Usage">Usage</a>.
+<li>The activity required a publication request: this was a <a title="concept-Usage">Usage</a>.<span class="insert"> Its time is not specified, hence, the marker '-'.</span>
<pre>used(ex:act2, email:2011Dec/0111, -)
</pre>
</li>
@@ -2053,10 +2061,10 @@
<p>To express their respective provenance, these bundles must be seen as entities, and all PROV constructs are now available to express their provenance. In the example below, <span class="name">ex:author-view</span> is attributed to the agent <span class="name">ex:Simon</span>, whereas <span class="name">ex:process-view</span> to <span class="name">w3:Consortium</span>.
-</p><pre class="codeexample">entity(ex:author-view, [prov:type='prov:Bundle' ])
+</p><pre class="codeexample">entity(ex:author-view, <span class="delete">[prov:type='prov:Bundle'</span><span class="insert">[ prov:type='prov:Bundle'</span> ])
wasAttributedTo(ex:author-view, ex:Simon)
-entity(ex:process-view, [prov:type='prov:Bundle' ])
+entity(ex:process-view, <span class="delete">[prov:type='prov:Bundle'</span><span class="insert">[ prov:type='prov:Bundle'</span> ])
wasAttributedTo(ex:process-view, w3:Consortium)
</pre>
@@ -2276,7 +2284,7 @@
<div class="anexample" id="anexample-activity"><div class="anexampleTitle">Example <span class="delete">17</span><span class="insert">18</span><sup><a class="internalDFN" href="#anexample-activity"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following expression</p>
-<pre class="codeexample">activity(a1,2011-11-16T16:05:00,2011-11-16T16:06:00,
+<pre class="codeexample"><span class="delete">activity(a1,2011-11-16T16:05:00,2011-11-16T16:06:00,</span><span class="insert">activity(a1, 2011-11-16T16:05:00, 2011-11-16T16:06:00,</span>
[ ex:host="server.example.org", prov:type='ex:edit' ])
</pre>
<p>states the existence of an activity with identifier <span class="name">a1</span>, start time <span class="name">2011-11-16T16:05:00</span>, and end time <span class="name">2011-11-16T16:06:00</span>, running on host <span class="name">server.example.org</span>, and of type <span class="name">edit</span>. The attribute <span class="name">host</span> is application specific (declared in some namespace with prefix <span class="name">ex</span>). The attribute <span class="name">type</span> is a reserved attribute of PROV-DM, allowing for sub-typing to be expressed (see <a href="#term-attribute-type">Section 5.7.4.4</a>).</p>
@@ -2299,6 +2307,9 @@
<div class="glossary-ref"> <dfn id="concept-generation" class="internalDFN">Generation</dfn><sup><a class="internalDFN" href="#concept-generation"><span class="diamond"> ◊</span></a></sup> is the completion of production of a new entity by an activity. This entity did not exist before generation and becomes available for usage after this generation. </div>
+<p><span class="insert">Given that a generation is the completion of production of an entity,
+it is instantaneous.</span></p>
+
<p>
</p><div class="attributes" id="attributes-generation"><dfn title="wasGeneratedBy" id="dfn-wasgeneratedby" class="internalDFN">Generation</dfn><sup><a class="internalDFN" href="#dfn-wasgeneratedby"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id; e, a, t, attrs)</span> in PROV-N,</span> has:
<ul>
@@ -2346,6 +2357,11 @@
<p><span class="glossary-ref"> <dfn id="concept-usage" class="internalDFN">Usage</dfn><sup><a class="internalDFN" href="#concept-usage"><span class="diamond"> ◊</span></a></sup> is the beginning of utilizing an entity by an activity. Before usage, the activity had not begun to utilize this entity and could not have been affected by the entity. </span> (Note: This definition is formulated for a given usage; it is permitted for an activity to have used a same entity multiple times.)</p>
+
+
+<p><span class="insert">Given that a usage is the beginning of utilizing an entity, it is
+instantaneous.</span></p>
+
<p></p><div class="attributes" id="attributes-usage"><dfn title="used" id="dfn-used" class="internalDFN">Usage</dfn><sup><a class="internalDFN" href="#dfn-used"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">used(id; a, e, t, attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class="attribute" id="usage.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier for a usage;</li>
@@ -2420,6 +2436,11 @@
<div class="glossary-ref"> <dfn id="concept-start" class="internalDFN">Start</dfn><sup><a class="internalDFN" href="#concept-start"><span class="diamond"> ◊</span></a></sup> is when an activity is deemed to have started. The activity did not exist before its start. Any usage or generation involving an activity follows the activity's start. A start may refer to an entity, known as <dfn id="concept-start-trigger" class="internalDFN">trigger</dfn><sup><a class="internalDFN" href="#concept-start-trigger"><span class="diamond"> ◊</span></a></sup>, that set off the activity, or to an activity, known as <dfn id="concept-start-starter" class="internalDFN">starter</dfn><sup><a class="internalDFN" href="#concept-start-starter"><span class="diamond"> ◊</span></a></sup>, that generated the trigger. </div>
+
+
+<p><span class="insert">Given that a start is when an activity is deemed to have started, it
+is instantaneous.</span></p>
+
<p></p><div class="attributes" id="attributes-start">An activity <dfn title="wasStartedBy" id="dfn-wasstartedby" class="internalDFN">start</dfn><sup><a class="internalDFN" href="#dfn-wasstartedby"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasStartedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class="attribute" id="start.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier for the activity start;</li>
@@ -2495,6 +2516,11 @@
<div class="glossary-ref"> <dfn id="concept-end" class="internalDFN">End</dfn><sup><a class="internalDFN" href="#concept-end"><span class="diamond"> ◊</span></a></sup> is when an activity is deemed to have ended. The activity no longer exists after its end. Any usage, generation, or invalidation involving an activity precedes the activity's end. An end may refer to an entity, known as <dfn id="concept-end-trigger" class="internalDFN">trigger</dfn><sup><a class="internalDFN" href="#concept-end-trigger"><span class="diamond"> ◊</span></a></sup>, that terminated the activity, or to an activity, known as <dfn id="concept-end-ender" class="internalDFN">ender</dfn><sup><a class="internalDFN" href="#concept-end-ender"><span class="diamond"> ◊</span></a></sup> that generated the trigger. </div>
+
+
+<p><span class="insert">Given that an end is when an activity is deemed to have ended, it is
+instantaneous.</span></p>
+
<p></p><div class="attributes" id="attributes-end">An activity <dfn title="wasEndedBy" id="dfn-wasendedby" class="internalDFN">end</dfn><sup><a class="internalDFN" href="#dfn-wasendedby"><span class="diamond"> ◊</span></a></sup><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
<ul>
<li><span class="attribute" id="end.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier for the activity end;</li>
@@ -2527,6 +2553,11 @@
+
+
+<p><span class="insert">Given that an invalidation is the start of destruction, cessation, or
+expiry, it is instantaneous.</span></p>
+
<p>
Entities have a duration. Generation marks the beginning of an entity, whereas invalidation marks its end.
An entity's lifetime can end for different reasons:</p>
@@ -2956,7 +2987,7 @@
<li><span class="attribute" id="association.id">id</span>: an <em class="rfc2119" title="optional">optional</em> identifier for the association between an activity and an agent;</li>
<li><span class="attribute" id="association.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity;</li>
<li><span class="attribute" id="association.agent">agent</span>: an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">ag</span>) for the agent associated with the activity;</li>
-<li><span class="attribute" id="association.plan">plan</span>: an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">pl</span>) for the plan adopted by the agent in the context of this activity;
+<li><span class="attribute" id="association.plan">plan</span>: an <em class="rfc2119" title="optional">optional</em> identifier (<span class="name">pl</span>) for the plan<span class="delete"> adopted by </span> the agent<span class="insert"> relied on</span> in the context of this activity;
</li><li><span class="attribute" id="association.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set (<span class="name">attrs</span>) of attribute-value pairs representing additional information about this association of this activity with this agent.</li>
</ul></div>
@@ -3185,7 +3216,7 @@
<p>
-A bundle description is of the form <span class="pnExpression">entity(id,[prov:type='prov:Bundle', attr1=val1, ...])</span>
+A bundle description is of the form <span class="pnExpression"><span class="delete">entity(id,[prov:type='prov:Bundle',</span><span class="insert">entity(id, [ prov:type='prov:Bundle',</span> attr1=val1, <span class="delete">...])</span><span class="insert">...] )</span></span>
where <span class="name">id</span> is an identifier denoting a bundle,
a type <span>prov:Bundle</span> and
an <em class="rfc2119" title="optional">optional</em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this bundle.
@@ -3230,7 +3261,7 @@
<p>The first bundle contains the descriptions corresponding to Bob observing the creation of <span class="name">ex:report1</span>. Its provenance can be described as follows.</p>
<pre class="codeexample">
-entity(bob:bundle1, [prov:type='prov:Bundle'])
+entity(bob:bundle1, <span class="delete">[prov:type='prov:Bundle'])</span><span class="insert">[ prov:type='prov:Bundle' ])</span>
wasGeneratedBy(bob:bundle1, -, 2012-05-24T10:30:00)
wasAttributedTo(bob:bundle1, ex:Bob)
</pre>
@@ -3270,6 +3301,9 @@
+
+
+
</div>
@@ -3382,7 +3416,7 @@
Considering again the two versions of the technical report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft). They are alternate of each other.
</p><pre class="codeexample">entity(tr:WD-prov-dm-20111018)
entity(tr:WD-prov-dm-20111215)
-alternateOf(tr:WD-prov-dm-20111018,tr:WD-prov-dm-20111215)
+<span class="delete">alternateOf(tr:WD-prov-dm-20111018,tr:WD-prov-dm-20111215)</span><span class="insert">alternateOf(tr:WD-prov-dm-20111018, tr:WD-prov-dm-20111215)</span>
</pre>
<p>They are both specialization of the page <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>.</p>
</div>
@@ -3470,10 +3504,10 @@
<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
</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)
- entity(ex:report2, [prov:type="report", ex:version=2])
- wasGeneratedBy(ex:g2; ex:report2,-,2012-05-25T11:00:01)
+ entity(ex:report1, <span class="delete">[prov:type="report", ex:version=1])</span><span class="insert">[ prov:type="report", ex:version=1 ])</span>
+ wasGeneratedBy(ex:g1; <span class="delete">ex:report1,-,2012-05-24T10:00:01)</span><span class="insert">ex:report1, -, 2012-05-24T10:00:01)</span>
+ entity(ex:report2, <span class="delete">[prov:type="report", ex:version=2])</span><span class="insert">[ prov:type="report", ex:version=2 ])</span>
+ wasGeneratedBy(ex:g2; <span class="delete">ex:report2,-,2012-05-25T11:00:01)</span><span class="insert">ex:report2, -, 2012-05-25T11:00:01)</span>
wasDerivedFrom(ex:report2, ex:report1)
endBundle
entity(obs:bundle1, [ prov:type='prov:Bundle' ])
@@ -3485,10 +3519,10 @@
entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
wasAttributedTo(tool:bundle2, viz:Visualizer)
- entity(tool:report1, [viz:color="orange"])
+ entity(tool:report1, <span class="delete">[viz:color="orange"])</span><span class="insert">[ viz:color="orange" ])</span>
mentionOf(tool:report1, ex:report1, obs:bundle1)
- entity(tool:report2, [viz:color="blue"])
+ entity(tool:report2, <span class="delete">[viz:color="blue"])</span><span class="insert">[ viz:color="blue" ])</span>
mentionOf(tool:report2, ex:report2, obs:bundle1)
endBundle
</pre>
@@ -3513,6 +3547,10 @@
+
+
+
+
</div>
<div id="component6" class="section">
@@ -3555,8 +3593,8 @@
<p><span class="insert">PROV defines no collection-specific attributes.</span></p>
<div class="anexample" id="example_48"><div class="anexampleTitle">Example <span class="delete">47</span><span class="insert">48</span><sup><a class="internalDFN" href="#example_48"><span class="diamond"> ◊</span></a></sup></div>
-<pre class="codeexample">entity(c0, [prov:type='prov:EmptyCollection' ]) // c0 is an empty collection
-entity(c1, [prov:type='prov:Collection' ]) // c1 is a collection, with unknown content
+<pre class="codeexample">entity(c0, <span class="delete">[prov:type='prov:EmptyCollection'</span><span class="insert">[ prov:type='prov:EmptyCollection'</span> ]) // c0 is an empty collection
+entity(c1, <span class="delete">[prov:type='prov:Collection'</span><span class="insert">[ prov:type='prov:Collection'</span> ]) // c1 is a collection, with unknown content
</pre>
</div>
@@ -3758,13 +3796,13 @@
<div id="term-attribute-value" class="section">
<h5><span class="secno">5.7.2.5 </span>prov:value</h5>
-<p><span class="glossary-ref"> The attribute <dfn id="concept-value-attribute" title="value-attribute" class="internalDFN"><span class="name">prov:value</span></dfn><sup><a class="internalDFN" href="#concept-value-attribute"><span class="diamond"> ◊</span></a></sup> provides a <a href="#concept-value" class="internalDFN">Value</a> for an entity. </span></p>
+<p><span class="glossary-ref"> The attribute <dfn id="concept-value-attribute" title="value-attribute" class="internalDFN"><span class="name">prov:value</span></dfn><sup><a class="internalDFN" href="#concept-value-attribute"><span class="diamond"> ◊</span></a></sup> provides a <span class="insert">value that is a direct representation of an entity as a PROV-DM </span><a title="value" href="#concept-value" class="internalDFN">Value</a><span class="delete"> for an entity.</span><span class="insert">.</span> </span></p>
<p>The attribute <span class="name">prov:value</span> is an <em class="rfc2119" title="optional">optional</em> attribute of entity. The value associated with the attribute <span class="name">prov:value</span> <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>. The attribute <span class="name">prov:value</span> <em class="rfc2119" title="may">may</em> occur at most once in a set of attribute-value pairs.</p>
-<div class="anexample" id="example_54"><div class="anexampleTitle">Example <span class="delete">53</span><span class="insert">54</span><sup><a class="internalDFN" href="#example_54"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-value1"><div class="anexampleTitle">Example <span class="delete">53</span><span class="insert">54</span><sup><a class="internalDFN" href="#anexample-value1"><span class="diamond"> ◊</span></a></sup></div>
<p>The following example illustrates the provenance of the number <span class="name">4</span> obtained by an activity that computed the length of an input string <span class="name">"abcd"</span>.
The input and the output are expressed as entities <span class="name">ex:in</span> and <span class="name">ex:out</span>, respectively. They each have a <span class="name">prov:value</span> attribute associated with the corresponding value.
</p>
@@ -3777,6 +3815,26 @@
</pre>
</div>
+<p><span class="insert">
+Two different entities </span><em class="rfc2119" title="may"><span class="insert">may</span></em><span class="insert"> have the same value for the attribute
+prov:value. For instance,
+when two entities, with the same prov:value, are generated by two
+different activities, as illustrated
+by the following example.</span></p>
+
+<div class="anexample" id="anexample-value2"><div class="anexampleTitle"><span class="insert">Example 55</span><sup><a class="internalDFN" href="#anexample-value2"><span class="diamond"><span class="insert"> ◊</span></span></a></sup></div>
+<p><a href="#anexample-value1" class="anexample-ref"><span><span class="insert">Example 54</span></span></a><span class="insert"> illustrates an entity with a given value
+ </span><span class="name"><span class="insert">4</span></span><span class="insert">. This examples shows that another entity with the same value may be computed differently (by an addition).
+</span></p>
+<pre class="codeexample"><span class="insert">entity(ex:in1, [ prov:value=3 ])
+entity(ex:in2, [ prov:value=1 ])
+entity(ex:out2, [ prov:value=4 ]) // ex:out2 also has value 4
+activity(ex:add1, [ prov:type="addition" ])
+used(ex:add1, ex:in1)
+used(ex:add1, ex:in2)
+wasGeneratedBy(ex:out2, ex:add1)
+</span></pre>
+</div>
</div>
@@ -3784,6 +3842,10 @@
+
+
+
+
</div>
<div id="term-value" class="section">
@@ -3826,7 +3888,7 @@
-<div class="anexample" id="anexample-value"><div class="anexampleTitle">Example <span class="delete">54</span><span class="insert">55</span><sup><a class="internalDFN" href="#anexample-value"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-value"><div class="anexampleTitle">Example <span class="delete">54</span><span class="insert">56</span><sup><a class="internalDFN" href="#anexample-value"><span class="diamond"> ◊</span></a></sup></div>
<p>
The following examples respectively are the string "abc", the integer number 1, and the IRI "http://example.org/foo".
</p><pre class="codeexample"> "abc"
@@ -3848,7 +3910,7 @@
<p>We note that PROV-DM <dfn title="time" id="dfn-time" class="internalDFN">time instants</dfn><sup><a class="internalDFN" href="#dfn-time"><span class="diamond"> ◊</span></a></sup> are defined according to xsd:dateTime [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p>
-<div class="anexample" id="anexample-time"><div class="anexampleTitle">Example <span class="delete">55</span><span class="insert">56</span><sup><a class="internalDFN" href="#anexample-time"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-time"><div class="anexampleTitle">Example <span class="delete">55</span><span class="insert">57</span><sup><a class="internalDFN" href="#anexample-time"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, the generation time of entity <span class="name">e1</span> is expressed according to
<a href="http://www.w3.org/TR/xmlschema11-2/#dateTime">xsd:dateTime</a> [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p>
@@ -3912,7 +3974,7 @@
<li>Sub-types and sub-relations can be expressed by means of the reserved attribute
<a href="#term-attribute-type"><span class="name">prov:type</span></a>.
-<div class="anexample" id="anexample-sub-relation"><div class="anexampleTitle">Example <span class="delete">56</span><span class="insert">57</span><sup><a class="internalDFN" href="#anexample-sub-relation"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-sub-relation"><div class="anexampleTitle">Example <span class="delete">56</span><span class="insert">58</span><sup><a class="internalDFN" href="#anexample-sub-relation"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, <span class="name">e2</span> is a translation of <span class="name">e1</span>,
expressed as a sub-type of derivation.
@@ -3921,7 +3983,7 @@
</pre>
</div>
-<div class="anexample" id="anexample-sub-type"><div class="anexampleTitle">Example <span class="delete">57</span><span class="insert">58</span><sup><a class="internalDFN" href="#anexample-sub-type"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-sub-type"><div class="anexampleTitle">Example <span class="delete">57</span><span class="insert">59</span><sup><a class="internalDFN" href="#anexample-sub-type"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, <span class="name">e</span> is described as a Car, a type of entity.
</p><pre class="codeexample">
@@ -3937,7 +3999,7 @@
<li>Application and domain specific roles can be expressed by means of the reserved attribute
<a href="#term-attribute-role"><span class="name">prov:role</span></a>.
-<div class="anexample" id="anexample-usage-with-role"><div class="anexampleTitle">Example <span class="delete">58</span><span class="insert">59</span><sup><a class="internalDFN" href="#anexample-usage-with-role"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-usage-with-role"><div class="anexampleTitle">Example <span class="delete">58</span><span class="insert">60</span><sup><a class="internalDFN" href="#anexample-usage-with-role"><span class="diamond"> ◊</span></a></sup></div>
<p>
In the following example, two computers <span class="name">ex:laptop4</span> and <span class="name">ex:desktop9</span> are used in different roles in a work activity.
</p><pre class="codeexample">
@@ -4241,6 +4303,10 @@
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/519"><span class="insert">ISSUE-519</span></a><span class="insert">, </span><a href="http://www.w3.org/2011/prov/track/issues/523"><span class="insert">ISSUE-523</span></a><span class="insert">, </span><a href="http://www.w3.org/2011/prov/track/issues/524"><span class="insert">ISSUE-524</span></a><span class="insert">, </span><a href="http://www.w3.org/2011/prov/track/issues/529"><span class="insert">ISSUE-529</span></a><span class="insert">: changed UML diagram of figure 8 by removing explicit inheritance from influence for usage, start, end, generation, invalidation, communication, derivation, attribution, association, and delegation. Instead, introduced correspondance table 7. Furthermore, in response to these issues, it was made clear that PROV defines no attribute specific to subtypes such as SoftwareAgent, ..., Plan, Revision, Bundle, Collection.
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/495"><span class="insert">ISSUE-495</span></a><span class="insert">: made explicit which section, figure, table was informative or normative.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/521"><span class="insert">ISSUE-521</span></a><span class="insert">: now states that "an agent relied on a plan" instead of "an agent adopted a plan".
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/499"><span class="insert">ISSUE-499</span></a><span class="insert">: Made explicit that generation/usage/invalidation/start/end are implicit.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/449"><span class="insert">ISSUE-449</span></a><span class="insert">: Clarified definition of prov:value attribute and added an example.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/495"><span class="insert">ISSUE-495</span></a><span class="insert">: added paragraph about 'relations opening up'. Clarified the role of '-' in example. Fixed dates in biblio. Fixed space issue in prov-n examples
</span></li></ul>
</div>
@@ -4327,11 +4393,11 @@
</dd><dt id="bib-XMLSCHEMA11-2">[XMLSCHEMA11-2]</dt><dd>Henry S. Thompson; et al. <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes.</cite></a> 5 April 2012. W3C Recommendation URL: <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/">http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/</a>
</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno"><span class="delete">C.2</span><span class="insert">D.2</span> </span>Informative references</h3><dl class="bibliography"><dt id="bib-Logic">[Logic]</dt><dd>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>
</dd><dt id="bib-Mappings">[Mappings]</dt><dd>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>
-</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>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>. 2011, Working Draft. URL: <a href="http://www.w3.org/TR/prov-aq/">http://www.w3.org/TR/prov-aq/</a>
-</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>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>. 2011, Working Draft. URL: <a href="http://www.w3.org/TR/prov-constraints/">http://www.w3.org/TR/prov-constraints/</a>
-</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>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>. 2011, Working Draft. URL: <a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a>
-</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>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>. 2011, Working Draft. URL: <a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a>
-</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>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>. 2011, Working Draft. URL: <a href="http://www.w3.org/TR/prov-primer/">http://www.w3.org/TR/prov-primer/</a>
+</dd><dt id="bib-PROV-AQ">[PROV-AQ]</dt><dd>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>. <span class="delete">2011,</span><span class="insert">2012,</span> Working Draft. URL: <a href="http://www.w3.org/TR/prov-aq/">http://www.w3.org/TR/prov-aq/</a>
+</dd><dt id="bib-PROV-CONSTRAINTS">[PROV-CONSTRAINTS]</dt><dd>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>. <span class="delete">2011,</span><span class="insert">2012,</span> Working Draft. URL: <a href="http://www.w3.org/TR/prov-constraints/">http://www.w3.org/TR/prov-constraints/</a>
+</dd><dt id="bib-PROV-N">[PROV-N]</dt><dd>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>. <span class="delete">2011,</span><span class="insert">2012,</span> Working Draft. URL: <a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a>
+</dd><dt id="bib-PROV-O">[PROV-O]</dt><dd>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>. <span class="delete">2011,</span><span class="insert">2012,</span> Working Draft. URL: <a href="http://www.w3.org/TR/prov-o/">http://www.w3.org/TR/prov-o/</a>
+</dd><dt id="bib-PROV-PRIMER">[PROV-PRIMER]</dt><dd>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>. <span class="delete">2011,</span><span class="insert">2012,</span> Working Draft. URL: <a href="http://www.w3.org/TR/prov-primer/">http://www.w3.org/TR/prov-primer/</a>
</dd><dt id="bib-RDF-CONCEPTS11">[RDF-CONCEPTS11]</dt><dd>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>
</dd></dl></div></div></body></html>
--- a/model/prov-dm.html Mon Oct 22 18:46:59 2012 +0200
+++ b/model/prov-dm.html Mon Oct 22 18:48:07 2012 +0200
@@ -325,32 +325,32 @@
"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>. "+
- "2011, Working Draft. "+
+ "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>. "+
- "2011, Working Draft. "+
+ "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>. "+
- "2011, Working Draft. "+
+ "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>. "+
- "2011, Working Draft. "+
+ "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>. "+
- "2011, Working Draft. "+
+ "2012, Working Draft. "+
"URL: <a href=\"http://www.w3.org/TR/prov-aq/\">http://www.w3.org/TR/prov-aq/</a>",
"UML":
@@ -1103,6 +1103,9 @@
<p><a class="section-ref" href="#core-structures"><span>TBD</span></a> shows that seven concepts are mapped to binary relations in the core of PROV. However, some advanced uses of these concepts cannot be captured by a binary relation, but require relations to be expanded to n-ary relations.</p>
+<p>Indeed, binary relations are actually shorthands that can be 'opened up' by applications and filled in with further application details. For example, derivation is a very high level relationship between two entities: an application may decide to 'open up' that relationship in an expanded relation that describes how an entity was derived from another by virtue of listing the generation, usage, and activity involved in the 'WasDerivedFrom' relationship. Applications are free to decide which level of granularity they want describe, and PROV gives them the way to do that.</p>
+
+
<p>To illustrate expanded relations, we consider the concept of
association, described
@@ -1281,7 +1284,7 @@
<p>
An activity with identifier <span class="name">a1</span> and an attribute <span class="name">type</span> with value <span class="name">createFile</span>.
<pre class="codeexample" >
-activity(a1, [prov:type="createFile"])
+activity(a1, [ prov:type="createFile" ])
</pre>
Two entities with identifiers <span class="name">e1</span> and <span class="name">e2</span>.
<pre class="codeexample" >
@@ -1290,13 +1293,13 @@
</pre>
The activity <span class="name">a1</span> used <span class="name">e1</span>, and <span class="name">e2</span> was generated by <span class="name">a1</span>.
<pre class="codeexample" >
-used(a1,e1)
-wasGeneratedBy(e2,a1)
+used(a1, e1)
+wasGeneratedBy(e2, a1)
</pre>
The same descriptions, but with an explicit identifier <span class="name">u1</span> for the usage, and the syntactic marker '<span class="name">-</span>' to mark the absence of identifier in the generation. Both are followed by '<span class="name">;</span>'.
<pre class="codeexample" >
-used(u1;a1,e1)
-wasGeneratedBy(-;e2,a1)
+used(u1; a1, e1)
+wasGeneratedBy(-; e2, a1)
</pre>
</div>
@@ -1354,11 +1357,11 @@
<li>There was an editing activity.
<pre>
-activity(ex:edit1,[prov:type="edit"])
+activity(ex:edit1, [ prov:type="edit" ])
</pre>
</li>
-<li>The document was generated by the editing activity: this was a <a title="concept-generation">Generation</a>.
+<li>The document was generated by the editing activity: this was a <a title="concept-generation">Generation</a>. Its time is not specified, hence, the marker '-'.
<pre>
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:edit1, -)
</pre>
@@ -1372,7 +1375,7 @@
</pre>
</li>
-<li>Agents were assigned various responsibilities in the editing activity: contributor and editor.
+<li>Agents were assigned various responsibilities in the editing activity: contributor and editor. The plan the agent relied upon is not specified, hence, the marker '-'.
<pre>
wasAssociatedWith(ex:edit1, ex:Paolo, -, [ prov:role="editor" ])
wasAssociatedWith(ex:edit1, ex:Simon, -, [ prov:role="contributor" ])
@@ -1445,11 +1448,11 @@
</li>
<li>There was a publication activity.
<pre>
-activity(ex:act2,[prov:type="publish"])
+activity(ex:act2, [ prov:type="publish" ])
</pre>
</li>
-<li>The document was generated by the publication activity: this was a <a title="concept-Generation">Generation</a>.
+<li>The document was generated by the publication activity: this was a <a title="concept-Generation">Generation</a>. Its time is not specified, hence, the marker '-'.
<pre>
wasGeneratedBy(tr:WD-prov-dm-20111215, ex:act2, -)
</pre>
@@ -1462,7 +1465,7 @@
</pre>
</li>
-<li>The activity required a publication request: this was a <a title="concept-Usage">Usage</a>.
+<li>The activity required a publication request: this was a <a title="concept-Usage">Usage</a>. Its time is not specified, hence, the marker '-'.
<pre>
used(ex:act2, email:2011Dec/0111, -)
</pre>
@@ -1522,10 +1525,10 @@
<p>To express their respective provenance, these bundles must be seen as entities, and all PROV constructs are now available to express their provenance. In the example below, <span class="name">ex:author-view</span> is attributed to the agent <span class="name">ex:Simon</span>, whereas <span class="name">ex:process-view</span> to <span class="name">w3:Consortium</span>.
<pre class="codeexample">
-entity(ex:author-view, [prov:type='prov:Bundle' ])
+entity(ex:author-view, [ prov:type='prov:Bundle' ])
wasAttributedTo(ex:author-view, ex:Simon)
-entity(ex:process-view, [prov:type='prov:Bundle' ])
+entity(ex:process-view, [ prov:type='prov:Bundle' ])
wasAttributedTo(ex:process-view, w3:Consortium)
</pre>
@@ -1755,7 +1758,7 @@
<p>
The following expression</p>
<pre class="codeexample">
-activity(a1,2011-11-16T16:05:00,2011-11-16T16:06:00,
+activity(a1, 2011-11-16T16:05:00, 2011-11-16T16:06:00,
[ ex:host="server.example.org", prov:type='ex:edit' ])
</pre>
<p>states the existence of an activity with identifier <span class="name">a1</span>, start time <span class="name">2011-11-16T16:05:00</span>, and end time <span
@@ -1780,6 +1783,9 @@
<div class="glossary-ref" data-ref="glossary-generation"></div>
+<p>Given that a generation is the completion of production of an entity,
+it is instantaneous.</p>
+
<p>
<div class="attributes" id="attributes-generation"><dfn title="wasGeneratedBy">Generation</dfn><span class="withPn">, written <span class="pnExpression">wasGeneratedBy(id; e, a, t, attrs)</span> in PROV-N,</span> has:
<ul>
@@ -1829,6 +1835,8 @@
<p><span class="glossary-ref" data-ref="glossary-usage"></span> (Note: This definition is formulated for a given usage; it is permitted for an activity to have used a same entity multiple times.)</p>
+<p>Given that a usage is the beginning of utilizing an entity, it is
+instantaneous.</p>
<p><div class="attributes" id="attributes-usage"><dfn title="used">Usage</dfn><span class="withPn">, written <span class="pnExpression">used(id; a, e, t, attrs)</span> in PROV-N,</span> has:
<ul>
@@ -1907,6 +1915,8 @@
<div class="glossary-ref" data-ref="glossary-start"></div>
+<p>Given that a start is when an activity is deemed to have started, it
+is instantaneous.</p>
<p><div class="attributes" id="attributes-start">An activity <dfn title="wasStartedBy">start</dfn><span class="withPn">, written <span class="pnExpression">wasStartedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
<ul>
@@ -1988,6 +1998,8 @@
<div class="glossary-ref" data-ref="glossary-end"></div>
+<p>Given that an end is when an activity is deemed to have ended, it is
+instantaneous.</p>
<p><div class="attributes" id="attributes-end">An activity <dfn title="wasEndedBy">end</dfn><span class="withAsn">, written <span class="pnExpression">wasEndedBy(id; a2, e, a1, t, attrs)</span> in PROV-N,</span> has:
<ul>
@@ -2020,7 +2032,8 @@
<div class="glossary-ref" data-ref="glossary-invalidation"></div>
-
+<p>Given that an invalidation is the start of destruction, cessation, or
+expiry, it is instantaneous.</p>
<p>
Entities have a duration. Generation marks the beginning of an entity, whereas invalidation marks its end.
@@ -2705,7 +2718,7 @@
<p>
-A bundle description is of the form <span class="pnExpression">entity(id,[prov:type='prov:Bundle', attr1=val1, ...])</span>
+A bundle description is of the form <span class="pnExpression">entity(id, [ prov:type='prov:Bundle', attr1=val1, ...] )</span>
where <span class='name'>id</span> is an identifier denoting a bundle,
a type <span>prov:Bundle</span> and
an OPTIONAL set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this bundle.
@@ -2750,7 +2763,7 @@
<p>The first bundle contains the descriptions corresponding to Bob observing the creation of <span class="name">ex:report1</span>. Its provenance can be described as follows.</p>
<pre class="codeexample">
-entity(bob:bundle1, [prov:type='prov:Bundle'])
+entity(bob:bundle1, [ prov:type='prov:Bundle' ])
wasGeneratedBy(bob:bundle1, -, 2012-05-24T10:30:00)
wasAttributedTo(bob:bundle1, ex:Bob)
</pre>
@@ -2904,7 +2917,7 @@
<pre class="codeexample">
entity(tr:WD-prov-dm-20111018)
entity(tr:WD-prov-dm-20111215)
-alternateOf(tr:WD-prov-dm-20111018,tr:WD-prov-dm-20111215)
+alternateOf(tr:WD-prov-dm-20111018, tr:WD-prov-dm-20111215)
</pre>
<p>They are both specialization of the page <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>.</p>
</div>
@@ -2994,10 +3007,10 @@
<p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
<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)
- entity(ex:report2, [prov:type="report", ex:version=2])
- wasGeneratedBy(ex:g2; ex:report2,-,2012-05-25T11:00:01)
+ entity(ex:report1, [ prov:type="report", ex:version=1 ])
+ wasGeneratedBy(ex:g1; 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)
wasDerivedFrom(ex:report2, ex:report1)
endBundle
entity(obs:bundle1, [ prov:type='prov:Bundle' ])
@@ -3009,10 +3022,10 @@
entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
wasAttributedTo(tool:bundle2, viz:Visualizer)
- entity(tool:report1, [viz:color="orange"])
+ entity(tool:report1, [ viz:color="orange" ])
mentionOf(tool:report1, ex:report1, obs:bundle1)
- entity(tool:report2, [viz:color="blue"])
+ entity(tool:report2, [ viz:color="blue" ])
mentionOf(tool:report2, ex:report2, obs:bundle1)
endBundle
</pre>
@@ -3075,8 +3088,8 @@
<div class="anexample">
<pre class="codeexample">
-entity(c0, [prov:type='prov:EmptyCollection' ]) // c0 is an empty collection
-entity(c1, [prov:type='prov:Collection' ]) // c1 is a collection, with unknown content
+entity(c0, [ prov:type='prov:EmptyCollection' ]) // c0 is an empty collection
+entity(c1, [ prov:type='prov:Collection' ]) // c1 is a collection, with unknown content
</pre>
</div>
@@ -3292,7 +3305,7 @@
<p>The attribute <span class="name">prov:value</span> is an OPTIONAL attribute of entity. The value associated with the attribute <span class="name">prov:value</span> MUST be a PROV-DM <a title="value">Value</a>. The attribute <span class="name">prov:value</span> MAY occur at most once in a set of attribute-value pairs.</p>
-<div class="anexample">
+<div class="anexample" id="anexample-value1">
<p>The following example illustrates the provenance of the number <span class="name">4</span> obtained by an activity that computed the length of an input string <span class="name">"abcd"</span>.
The input and the output are expressed as entities <span class="name">ex:in</span> and <span class="name">ex:out</span>, respectively. They each have a <span class="name">prov:value</span> attribute associated with the corresponding value.
</p>
@@ -3306,6 +3319,28 @@
</pre>
</div>
+<p>
+Two different entities MAY have the same value for the attribute
+prov:value. For instance,
+when two entities, with the same prov:value, are generated by two
+different activities, as illustrated
+by the following example.</p>
+
+<div class="anexample" id="anexample-value2">
+<p><a href="#anexample-value1" class="anexample-ref"><span>Example REF</span></a> illustrates an entity with a given value
+ <span class="name">4</span>. This examples shows that another entity with the same value may be computed differently (by an addition).
+</p>
+<pre class="codeexample">
+entity(ex:in1, [ prov:value=3 ])
+entity(ex:in2, [ prov:value=1 ])
+entity(ex:out2, [ prov:value=4 ]) // ex:out2 also has value 4
+activity(ex:add1, [ prov:type="addition" ])
+used(ex:add1, ex:in1)
+used(ex:add1, ex:in2)
+wasGeneratedBy(ex:out2, ex:add1)
+</pre>
+</div>
+
</section>
@@ -3851,6 +3886,9 @@
<li> <a href="http://www.w3.org/2011/prov/track/issues/519">ISSUE-519</a>, <a href="http://www.w3.org/2011/prov/track/issues/523">ISSUE-523</a>, <a href="http://www.w3.org/2011/prov/track/issues/524">ISSUE-524</a>, <a href="http://www.w3.org/2011/prov/track/issues/529">ISSUE-529</a>: changed UML diagram of figure 8 by removing explicit inheritance from influence for usage, start, end, generation, invalidation, communication, derivation, attribution, association, and delegation. Instead, introduced correspondance table 7. Furthermore, in response to these issues, it was made clear that PROV defines no attribute specific to subtypes such as SoftwareAgent, ..., Plan, Revision, Bundle, Collection.
<li> <a href="http://www.w3.org/2011/prov/track/issues/495">ISSUE-495</a>: made explicit which section, figure, table was informative or normative.
<li> <a href="http://www.w3.org/2011/prov/track/issues/521">ISSUE-521</a>: now states that "an agent relied on a plan" instead of "an agent adopted a plan".
+<li> <a href="http://www.w3.org/2011/prov/track/issues/499">ISSUE-499</a>: Made explicit that generation/usage/invalidation/start/end are implicit.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/449">ISSUE-449</a>: Clarified definition of prov:value attribute and added an example.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/495">ISSUE-495</a>: added paragraph about 'relations opening up'. Clarified the role of '-' in example. Fixed dates in biblio. Fixed space issue in prov-n examples
</ul>
</section>