--- a/model/ProvenanceModel.html Mon Nov 21 16:51:20 2011 +0000
+++ b/model/ProvenanceModel.html Mon Nov 21 17:03:37 2011 +0000
@@ -850,10 +850,10 @@
<p>identified by identifier <span class="name">id</span>, states the existence of an activity with recipe link <span class="name">add-crime-in-london</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> (declared in some namespace with prefix <span class="name">app</span>). The attribute <span class="name">host</span> is application specific, but MUST hold for the duration of activity. The attribute <span class="name">type</span> is a reserved attribute of PROV-DM, allowing for subtyping to be expressed.</p>
</div>
-<p>The mere existence of an activity assertion entails some event ordering in the world, since the start event precedes the end event. This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
+<p>The mere existence of an activity assertion entails some event ordering in the world, since the start event <a>precedes</a> the end event. This is expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>
<div class='interpretation' id='start-precedes-end'> From an activity record, one can infer that the
-start event precedes the end event of the represented activity.</div>
+start event <a>precedes</a> the end event of the represented activity.</div>
<p>An activity record is not an entity record.
Indeed, an entity record represents an entity that exists in full at
@@ -1072,8 +1072,8 @@
<p>The assertion of a generation event implies ordering of events in the world.</p>
-<div class='interpretation' id='generation-activity-ordering'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,pe,attrs)</span> or <span class="name">wasGeneratedBy(x,pe,attrs,t)</span>, <span class='conditional'>then</span> generation of the entity denoted by <span class="name">x</span> precedes the end
-of <span class="name">pe</span> and follows the beginning of <span class="name">pe</span>.
+<div class='interpretation' id='generation-activity-ordering'><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,pe,attrs)</span> or <span class="name">wasGeneratedBy(x,pe,attrs,t)</span>, <span class='conditional'>then</span> generation of the entity denoted by <span class="name">x</span> <a>precedes</a> the end
+of <span class="name">pe</span> and <a>follows</a> the beginning of <span class="name">pe</span>.
</div>
@@ -1157,15 +1157,18 @@
+<div class='interpretation' id='usage-generation-ordering'>The generation of an entity always <a>precedes</a> its use.
+</div>
<div class='interpretation' id='usage-activity-ordering'>Given an activity record identified by <span class="name">pe</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(pe,e,attrs)</span> or <span class="name">used(pe,e,attrs,t)</span> holds, <span class='conditional'>then</span>
- the usage of the entity represented by entity record identified by <span class="name">e</span> precedes the end of activity represented by record identified by <span class="name">pe</span> and follows its beginning. Furthermore, the generation of the entity denoted by entity record identified by <span class="name">e</span> always precedes
-its use.
+ the usage of the entity represented by entity record identified by <span class="name">e</span> <a>precedes</a> the end of activity represented by record identified by <span class="name">pe</span> and <a>follows</a> its beginning.
</div>
+
+
<div class='issue'>Should we define a taxonomy of use? This is <a href="http://www.w3.org/2011/prov/track/issues/23">ISSUE-23</a>.</div>
</section>
@@ -1556,7 +1559,7 @@
<div class='interpretation' id='derivation-use-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)</span>
or <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span>
the use
-of entity denoted by <span class="name">e1</span> precedes the generation of
+of entity denoted by <span class="name">e1</span> <a>precedes</a> the generation of
the entity denoted by <span class="name">e2</span>.
</div>
@@ -1565,7 +1568,7 @@
<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">wasBasedOn(e2,e1)</span>
holds, <span class='conditional'>then</span> the
-generation event of the entity represented by the entity record denoted by <span class="name">e1</span> precedes the generation event of
+generation event of the entity represented by the entity record denoted by <span class="name">e1</span> <a>precedes</a> the generation event of
the entity represented by the entity record denoted by <span class="name">e2</span>.
</div>
@@ -1602,12 +1605,12 @@
<p>
Note that inferring derivation from usage and generation does not hold
in general. Indeed, when a generation <span class="name">wasGeneratedBy(g, e2, a, attrs2)</span>
-precedes <span class="name">used(u, a, e1, attrs1)</span>, for
+<a>precedes</a> <span class="name">used(u, a, e1, attrs1)</span>, for
some <span class="name">e1</span>, <span class="name">e2</span>, <span class="name">attrs1</span>, <span class="name">attrs2</span>, and <span class="name">a</span>, one
cannot infer derivation <span class="name">wasDerivedFrom(e2, e1, a, g, u)</span>
or <span class="name">wasDerivedFrom(e2,e1)</span> since
of <span class="name">e2</span> cannot possibly be determined by
-of <span class="name">e1</span>, given the creation of <span class="name">e2</span> precedes the use
+of <span class="name">e1</span>, given the creation of <span class="name">e2</span> <a>precedes</a> the use
of <span class="name">e1</span>.
</p>
@@ -2440,7 +2443,7 @@
An <dfn id="InformationFlowOrdering">information flow ordering record</dfn> is a representation that an entity was generated by an activity, before it was used by another activity.
A <dfn id="ControlOrdering">control ordering record</dfn> is a representation that the end of
-an activity precedes the start of another activity.
+an activity <a>precedes</a> the start of another activity.
</p>
<p>In PROV-ASN, an activity ordering record's text matches the <span class="nonterminal">activityOrderingRecord</span> production of the grammar defined in this specification document.
@@ -2501,7 +2504,7 @@
|
----- a3
</pre>
-<p>The end in activity record identified by <span class="name">a3</span> precedes the start in activity record identified by <span class="name">a1</span>, while interval for activity record <span class="name">a2</span> overlaps with each interval for <span class="name">a1</span> and <span class="name">a3</span>, allowing information to flow (<span class="name">e1</span> and <span class="name">e2</span>, respectively).</p>
+<p>The end in activity record identified by <span class="name">a3</span> <a>precedes</a> the start in activity record identified by <span class="name">a1</span>, while interval for activity record <span class="name">a2</span> overlaps with each interval for <span class="name">a1</span> and <span class="name">a3</span>, allowing information to flow (<span class="name">e1</span> and <span class="name">e2</span>, respectively).</p>
@@ -2509,7 +2512,7 @@
<div class="issue">
Temporal constraints to be make explicit. This is <a href="http://www.w3.org/2011/prov/track/issues/156">ISSUE-156</a>.
-The temporal constraint follows immediately from the fact that generation always precedes use of a given entity. Note that this constraint is currently not written in the document.
+The temporal constraint follows immediately from the fact that generation always <a>precedes</a> use of a given entity. See usage-generatio-ordering.
</div>