--- a/model/ProvenanceModel.html Thu Dec 08 22:39:12 2011 +0000
+++ b/model/ProvenanceModel.html Thu Dec 08 23:01:47 2011 +0000
@@ -71,7 +71,7 @@
// if your specification has a subtitle that goes below the main
// formal title, define it here
- // subtitle : "Initial draft for internal discussion",
+ subtitle : "Initial draft (WD3) for internal discussion",
// if you wish the publication date to be other than today, set this
// publishDate: "2011-10-18",
@@ -1028,10 +1028,16 @@
<p>identified by identifier <span class="name">a1</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">ex</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>
+<div class="interpretation-forward">
+For the interpretation of an activity record, see <a href="#start-precedes-end">start-precedes-end</a>.
+</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>An activity record is not an entity record.
Indeed, an entity record represents an entity that exists in full at
@@ -1246,15 +1252,19 @@
</div>
-
+<div class="interpretation-forward">
+For the interpretation of a generation record, see <a href="#generation-activity-ordering">generation-activity-ordering</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>A given entity record can be referred to in a single generation record in the scope of a given <a href="#record-Account">account</a>.
The rationale for this constraint is as follows.
@@ -1340,22 +1350,11 @@
</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 class="interpretation-forward">
+For the interpretation of a usage record, see <a href="#usage-generation-ordering">usage-generation-ordering</a> and <a href="#usage-activity-ordering">usage-activity-ordering</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>
-
-
-
-
-<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>
</section>
@@ -2570,6 +2569,38 @@
</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>
@@ -3271,50 +3302,9 @@
<section class="appendix">
- <h2>Changes Since First Public Working Draft</h2>
+ <h2>Changes Since Second Public Working Draft</h2>
<ul>
-<li>12/08/11: Explained non-transitivity of wasInformedBy. </li>
-<li>12/05/11: Made attributes optional, and used non-terminal optional-attribute-values. </li>
-<li>12/05/11: Changed syntax of recordContainer to be more user friendly, and removed list of account ids, since redundant. </li>
-<li>12/05/11: Changed syntax of namespace declaration to be more user friendly. </li>
-<li>12/05/11: Simplified Typed literals, now allows for intLiteral, and datatype adjusted to be qualified name. </li>
-<li>11/29/11: Introduced typed identifiers to make grammar clearer. </li>
-<li>11/29/11: Added section 2.4 on grammar notation. </li>
-<li>11/28/11: Changed grammar notation. </li>
-<li>11/25/11: Updated examples of section 8. </li>
-<li>11/25/11: Definition of namespace. Clarification about interpretation of IRI occurrences. </li>
-<li>11/25/11: Definition of attribute and identifier. </li>
-<li>11/24/11: Added figure of Common Relations in Section 6. </li>
-<li>11/24/11: Updated text preceding graphical illustration, removed appendix A. </li>
-<li>11/24/11: Fix on traceability record. </li>
-<li>11/24/11: Revisited Derivation record, with a single name for derivation. </li>
-<li>11/23/11: Defined attribute, identifier, and namespace declaration. </li>
-<li>11/23/11: Consolidation of event in section 2.1.2 and linking to definitions from the rest of document. </li>
-<li>11/21/11: Added wasStartedBy between activities.</li>
-<li>11/21/11: Added wasInformedBy-ordering constraint.</li>
-<li>11/17/11: Added Traceability Record.</li>
-<li>11/17/11: Rewrote the whole section on Derivation Record.</li>
-<li>11/17/11: Updated wasDerivedFrom to refer to generation/usage record ids.</li>
-<li>11/17/11: Simplified hasAnnotation mechanism, now requiring to-be-annotated record to had id.</li>
-<li>11/17/11: Renamed annotation into note.</li>
-<li>11/17/11: Introduced wasStartedBy, wasEndedBy, and actedOnBehalfOf.</li>
-<li>11/16/11: New version of agent/wasAssociatedWith.</li>
-<li>11/16/11: Introduced class anexample.</li>
-<li>11/16/11: Changed presentation of entity and activity.</li>
-<li>11/16/11: Updated examples for usage and generation record.</li>
-<li>11/16/11: Renamed use record into usage record.</li>
-<li>11/16/11: Removed constraint generation-affects-attributes.</li>
-<li>11/16/11: Removed constraint use-attributes.</li>
-<li>11/16/11: Introduced optional identity for use and generation record.</li>
-<li>11/11/11: Swapped sections 6 and 7.</li>
-<li>11/11/11: Use attribute-value pairs uniformly, instead of qualifiers and name-value pairs.</li>
-<li>11/08/11: Renamed 'provenance container' into 'record container'.</li>
-<li>11/07/11: Addressed ISSUE-143 (qualifiers as a set of name value pairs).</li>
-<li>11/07/11: Added a section on Literals (ISSUE-142).</li>
-<li>11/07/11: Aligned terminology 'activity' and 'process execution record'.</li>
-<li>11/07/11: Renamed 'xxx Expression' into 'xxx Record' to avoid the language connotation.</li>
-<li>11/07/11: Defined entity as identifiable characterized thing, and updated text accordingly.</li>
-<li>10/08/11: Made explicit the term expression wherever was appropriate, including section titles.</li>
+<li>12/08/11: Restructuring of Constraints. </li>
</ul>
</section>