--- a/model/ProvenanceModel.html Thu Dec 08 23:06:15 2011 +0000
+++ b/model/ProvenanceModel.html Fri Dec 09 07:49:42 2011 +0000
@@ -1781,8 +1781,11 @@
holds, then <span class="name">wasDerivedFrom(e2,e1,attrs)</span> also holds.<br>
</div>
-
-
+<div class="interpretation-forward">
+For the interpretation of a derivation record, see <a href="#derivation-usage-generation-ordering">derivation-usage-generation-ordering</a> and <a href="#derivation-generation-generation-ordering">derivation-generation-generation-ordering</a>
+</div>
+
+<!--
<p>
<p>If a derivation record holds for <span class="name">e2</span> and <span class="name">e1</span>, then
this means that the entity represented by entity record identified by <span class="name">e1</span> has an influence on the entity represented entity record identified by <span class="name">e2</span>,
@@ -1813,7 +1816,7 @@
imprecise-n derivation, nothing is known about the usage of <span class="name">e1</span>,
since there is no associated activity.</p>
-
+-->
<p>The imprecise-1 derivation has the same meaning as the precise-1
@@ -2569,38 +2572,6 @@
</section>
- <section id="interpretation">
-<h2>PROV-DM Interpretation</h2>
-
-<div class="note">
-Work in progress: we are consolidating here all interpretation constraints. Need to recap some of the overview material about events. </div>
-
-<p>The mere existence of an activity assertion entails some <a>event</a> ordering in the world, since an <a>activity start event</a> always <a>precedes</a> the corresponding <a>activity end event</a>. This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
-
-<div class='interpretation' id='start-precedes-end'> The following temporal constraint holds for any activity record: the
-<a title="activity start event">start event</a> <a>precedes</a> the <a title="activity end event">end event</a>.</div>
-
-<p>The assertion of a generation record implies ordering of <a title="event">events</a> in the world.</p>
-
-<div class='interpretation' id='generation-activity-ordering'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,a,attrs)</span> or <span class="name">wasGeneratedBy(x,a,attrs,t)</span> holds, <span class='conditional'>then</span> the following temporal constraint also holds: the <a title="entity generation event">generation</a> of the entity denoted by <span class="name">x</span> <a>precedes</a> the <a title="activity end event">end</a>
-of <span class="name">a</span> and <a>follows</a> the <a title="activity start event">start</a> of <span class="name">a</span>.
-</div>
-
-<p>The assertion of a usage record implies ordering of <a title="event">events</a> in the world.</p>
-
-<div class='interpretation' id='usage-generation-ordering'>For any entity, the following temporal constraint holds: the <a title="entity generation event">generation</a> of an entity always <a>precedes</a> any of its <a title="entity usage event">usages</a>.
-</div>
-
-
-<div class='interpretation' id='usage-activity-ordering'>Given an activity record identified by <span class="name">a</span>, an entity record identified by <span class="name">e</span>, a set of attribute-value pairs <span class="name">attrs</span>, and optional time <span class="name">t</span>, <span class='conditional'>if</span>
- assertion <span class="name">used(a,e,attrs)</span> or <span class="name">used(a,e,attrs,t)</span> holds, <span class='conditional'>then</span> the following temporal constraint holds:
- the <a title="entity usage event">usage</a> of the entity represented by entity record identified by <span class="name">e</span> <a>precedes</a> the <a title="activity end event">end</a> of activity represented by record identified by <span class="name">a</span> and <a>follows</a> its <a title="activity start event">start</a>.
-</div>
-
-
-
-
-</section>
<section id="common-relations">
<h2>PROV-DM Common Relations</h2>
@@ -2858,13 +2829,19 @@
such that <span class="name">wasGeneratedBy(e,a1,attrs1)</span> and <span class="name">used(a2,e,attrs2)</span> hold.
</div>
+
+<div class="interpretation-forward">
+For the interpretation of an information flow ordering record, see <a href="#wasInformedBy-ordering">wasInformedBy-ordering</a>.
+</div>
+
+<!--
<div class='interpretation' id='wasInformedBy-ordering'>
Given two activity records denoted by <span class="name">a1</span> and <span class="name">a2</span>, <span class='conditional'>if</span> the record <span class="name">wasInformedBy(a2,a1)</span>
holds, <span class='conditional'>then</span> the following temporal constraint holds:
the <a title="activity start event">start event</a> of the activity record denoted by <span class="name">a1</span> <a>precedes</a> the <a title="activity end event">end event</a> of
the activity record denoted by <span class="name">a2</span>.
</div>
-
+-->
<p>The relationship <span class="name">wasInformedBy</span> is not transitive. Indeed, consider the following records.</p>
<pre class="codeexample">
@@ -2879,13 +2856,9 @@
<img src="informedByNonTransitive.png" alt="non transitivity of wasInformedBy" />
</div>
-<div class="note">
-The relation wasScheduledAfter was dropped, and replaced by a simplier relation wasStartedBy(a2,a1). It is intentional that the name wasStartedBy is overloaded.
-</div>
-
<p>
A control ordering record, written as
-<span class="name">wasStartedBy(a2,a1)</span> in PROV-ASN, contains: </p>
+<span class="name">wasStartedBy(a2,a1, attrs)</span> in PROV-ASN, contains: </p>
<ul>
<li><em>id</em>: an OPTIONAL identifier <span class="name">id</span>;</li>
<li><em>started</em>: refers to an activity record identified by <span class="name">a2</span>, representing the started activity;
@@ -2923,13 +2896,19 @@
</pre>
</div>
+
+<div class="interpretation-forward">
+For the interpretation of a control flow ordering record, see <a href="#wasStartedBy-ordering">wasStartedBy-ordering</a>.
+</div>
+
+<!--
<div class='interpretation' id='wasStartedBy-ordering'>
Given two activity records denoted by <span class="name">a1</span> and <span class="name">a2</span>, <span class='conditional'>if</span> the record <span class="name">wasStartedBy(a2,a1)</span>
holds, <span class='conditional'>then</span> the following temporal constraint holds: the
<a title="activity start event">start</a> event of the activity record denoted by <span class="name">a1</span> <a>precedes</a> the <a title="activity start event">start event</a> of
the activity record denoted by <span class="name">a2</span>.
</div>
-
+-->
<div class='pending'>Suggested definition for process ordering. This is <a href="http://www.w3.org/2011/prov/track/issues/50">ISSUE-50</a>.</div>
@@ -3092,7 +3071,7 @@
<div class='constraint' id='quotation-implication'>
<span class='conditional'>If</span>
-<span class="name">wasQuotedFrom(e2,e1,ag2,ag1)</span> holds for some identifiers
+<span class="name">wasQuotedFrom(e2,e1,ag2,ag1,attrs)</span> holds for some identifiers
<span class="name">e2</span>, <span class="name">e1</span>, <span class="name">ag2</span>, <span class="name">ag1</span>,
<span class='conditional'>then</span> the following records hold:
<pre>
@@ -3175,6 +3154,82 @@
</section>
</section>
+ <section id="interpretation">
+<h2>PROV-DM Interpretation</h2>
+
+<div class="note">
+Work in progress: we are consolidating here all interpretation constraints. Need to recap some of the overview material about events. </div>
+
+<p>The mere existence of an activity assertion entails some <a>event</a> ordering in the world, since an <a>activity start event</a> always <a>precedes</a> the corresponding <a>activity end event</a>. This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
+
+<div class='interpretation' id='start-precedes-end'> The following temporal constraint holds for any activity record: the
+<a title="activity start event">start event</a> <a>precedes</a> the <a title="activity end event">end event</a>.</div>
+
+<p>The assertion of a generation record implies ordering of <a title="event">events</a> in the world.</p>
+
+<div class='interpretation' id='generation-activity-ordering'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,a,attrs)</span> or <span class="name">wasGeneratedBy(x,a,attrs,t)</span> holds, <span class='conditional'>then</span> the following temporal constraint also holds: the <a title="entity generation event">generation</a> of the entity denoted by <span class="name">x</span> <a>precedes</a> the <a title="activity end event">end</a>
+of <span class="name">a</span> and <a>follows</a> the <a title="activity start event">start</a> of <span class="name">a</span>.
+</div>
+
+<p>The assertion of a usage record implies ordering of <a title="event">events</a> in the world.</p>
+
+<div class='interpretation' id='usage-generation-ordering'>For any entity, the following temporal constraint holds: the <a title="entity generation event">generation</a> of an entity always <a>precedes</a> any of its <a title="entity usage event">usages</a>.
+</div>
+
+
+<div class='interpretation' id='usage-activity-ordering'>Given an activity record identified by <span class="name">a</span>, an entity record identified by <span class="name">e</span>, a set of attribute-value pairs <span class="name">attrs</span>, and optional time <span class="name">t</span>, <span class='conditional'>if</span>
+ assertion <span class="name">used(a,e,attrs)</span> or <span class="name">used(a,e,attrs,t)</span> holds, <span class='conditional'>then</span> the following temporal constraint holds:
+ the <a title="entity usage event">usage</a> of the entity represented by entity record identified by <span class="name">e</span> <a>precedes</a> the <a title="activity end event">end</a> of activity represented by record identified by <span class="name">a</span> and <a>follows</a> its <a title="activity start event">start</a>.
+</div>
+
+
+<p>
+<p>If a derivation record holds for <span class="name">e2</span> and <span class="name">e1</span>, then
+this means that the entity represented by entity record identified by <span class="name">e1</span> has an influence on the entity represented entity record identified by <span class="name">e2</span>,
+ which at the minimum implies temporal ordering, specified as follows.
+First, we consider one-activity derivations.</p>
+
+<div class='interpretation' id='derivation-usage-generation-ordering'>Given an activity record identified by <span class="name">a</span>, entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, generation record identified by <span class="name">g2</span>, and usage record identified by <span class="name">u1</span>, <span class='conditional'>if</span> the record <span class="name">wasDerivedFrom(e2,e1,a,g2,u1,attrs)</span>
+or <span class="name">wasDerivedFrom(e2,e1,[prov:steps="1"] ∪ attrs)</span> holds, <span class='conditional'>then</span>
+the following temporal constraint holds:
+the <a title="entity usage event">usage</a>
+of entity denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation</a> of
+the entity denoted by <span class="name">e2</span>.
+</div>
+
+<p>Then, imprecise-n derivations.</p>
+
+<div class='interpretation' id='derivation-generation-generation-ordering'>
+Given two entity records denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the record <span class="name">wasDerivedFrom(e2,e1,[prov:steps="n"] ∪ attrs)</span>
+ holds, <span class='conditional'>then</span> the following temporal constraint holds:
+the <a title="entity generation event">generation event</a> of the entity denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation event</a> of
+the entity denoted by <span class="name">e2</span>.
+ </div>
+
+<p>Note that temporal ordering is between generations of <span class="name">e1</span>
+and <span class="name">e2</span>, as opposed to precise-1 derivation,
+which implies temporal ordering between the usage of <span class="name">e1</span> and
+generation of <span class="name">e2</span>. Indeed, in the case of
+imprecise-n derivation, nothing is known about the usage of <span class="name">e1</span>,
+since there is no associated activity.</p>
+
+<div class='interpretation' id='wasInformedBy-ordering'>
+Given two activity records denoted by <span class="name">a1</span> and <span class="name">a2</span>, <span class='conditional'>if</span> the record <span class="name">wasInformedBy(a2,a1)</span>
+ holds, <span class='conditional'>then</span> the following temporal constraint holds:
+the <a title="activity start event">start event</a> of the activity record denoted by <span class="name">a1</span> <a>precedes</a> the <a title="activity end event">end event</a> of
+the activity record denoted by <span class="name">a2</span>.
+</div>
+
+<div class='interpretation' id='wasStartedBy-ordering'>
+Given two activity records denoted by <span class="name">a1</span> and <span class="name">a2</span>, <span class='conditional'>if</span> the record <span class="name">wasStartedBy(a2,a1)</span>
+ holds, <span class='conditional'>then</span> the following temporal constraint holds: the
+<a title="activity start event">start</a> event of the activity record denoted by <span class="name">a1</span> <a>precedes</a> the <a title="activity start event">start event</a> of
+the activity record denoted by <span class="name">a2</span>.
+</div>
+
+
+</section>
+
<section id="extensibility-section">
<h2>PROV-DM Extensibility Points</h2>