--- a/model/prov-dm-constraints.html Fri Mar 30 08:14:07 2012 +0100
+++ b/model/prov-dm-constraints.html Fri Mar 30 08:52:09 2012 +0100
@@ -547,16 +547,11 @@
<h2>PROV-DM Definitional Constraints and Inferences</h2>
-<p>In this section, we revisit elements and relations of PROV-DM, and examine and examine the constraints associated with their definitions. </p>
+<p>In this section, we revisit the types and relations of PROV-DM, and examine the constraints associated with their definitions. </p>
-<div class='note'>
-Proposing to remove the subsections in this section, since some have no constraints.
-</div>
-
-
- <section id="term-element">
-<h3>Element</h3>
+ <section id="component1">
+<h3>Component 1: Entities and Activities</h3>
<section id="term-Entity">
@@ -564,26 +559,27 @@
<p>
-An <dfn>entity</dfn> is a thing in the world one wants to provide provenance for and whose situation in the world is represented by some attribute-value pairs; an entity's attribute-value pairs remain unchanged during an entity's characterization interval,
+An <dfn>entity</dfn> is a thing one wants to provide provenance for and whose situation in the world is represented by some attribute-value pairs. An entity's attribute-value pairs are specified when the entity description is created and remain unchanged. An entity's attribute-value pairs are expected to represent the entity's situation and (partial) state during an entity's characterization interval,
i.e. a continuous interval between two <a title="event">instantaneous events</a> in the world, namely its <a title="entity generation event">generation event</a> and its <a title="entity destruction event">destruction event</a>.</p>
+<p>If an entity's situation changes in the world, this may result in its description being invalid, because one or more attribute-value pairs no longer hold. In that case, from the PROV viewpoint, there exists a new entity, which needs to be given a distinct identifier, and associated with the attribute-value pairs that reflect its new situation in the world.</p>
+
+
Further considerations:
<ul>
-<li>In order to describe something over several intervals, it is required to create multiple entities (either by direct
-assertion or by inference), each with its own identifier (so as to allow potential dependencies between the various entity records).
-
-
+<li>In order to describe something over several intervals, it is required to create multiple entities, each with its own identifier. This allow potential dependencies between the various entities to be expressed.
</li>
<li>There is no assumption that the set of attributes is complete and that the attributes are independent or orthogonal of each other.</li>
<li>A characterization interval may collapse into a single instant.</li>
+</ul>
-
-</ul>
-
+<div class="interpretation-forward">
+For the interpretation of an activity, see <a href="#generation-precedes-invalidation">generation-precedes-invalidation</a>.
+</div>
<div class='issue'>The characterization interval of an entity record is currently implicit. Making it explicit would allow us to define alternateOf and specializationOf more precisely.
@@ -602,9 +598,9 @@
-<p>An activity is anything that involves entities. An activity is delimited by its <a title="activity start event">start</a> and its <a title="activity end event">end</a> events; hence, it occurs over
+<p>An activity is delimited by its <a title="activity start event">start</a> and its <a title="activity end event">end</a> events; hence, it occurs over
an interval delimited by two <a title="event">instantaneous events</a>. However, an activity need not mention time information, nor duration, because they may not be known.
-An activity's attribute-value pairs remain unchanged during an activity's interval, i.e. an interval between two instantaneous events in the world, namely its <a title="activity start event">start</a> event and its <a title="activity end event">end</a> event.
+An attribute-value pairs for an activity remain unchanged. They represent's the activity's situation during the activity's interval, i.e. an interval between two instantaneous events in the world, namely its <a title="activity start event">start</a> event and its <a title="activity end event">end</a> event.
</p>
<div class="interpretation-forward">
@@ -617,33 +613,16 @@
Indeed, an entity exists in full at
any point in its lifetime, persists during this
interval, and preserves the characteristics that makes it
-identifiable. In contrast, an activity is something that happens,
-unfolds or develops through time, but is typically not identifiable by
+identifiable. In contrast, an activity is something that occurs, happens,
+unfolds, or develops through time, but is typically not identifiable by
the characteristics it exhibits at any point during its duration.
This distinction is similar to the distinction between
'continuant' and 'occurrent' in logic [[Logic]].</li>
</ul>
-</section>
-
- <section id="term-note">
-
-<h4>Note</h4>
-
-<p>Attribute-value pairs occurring in notes are application specific. Thus, their interpretation is outside the scope of this document, and they are not subject to any of the constraints listed in this document. </p>
-
-
- </section>
-
-</section>
-
-
-<section id="term-relation">
-<h3>PROV-DM Relations</h3>
-
-
+</section>
<section id="term-Generation">
<h4>Generation</h4>
@@ -707,183 +686,16 @@
</section>
-
-
-
-
-
-<section id="term-ActivityAssociation">
-<h4>Activity Association</h4>
-
-<div class="interpretation-forward">
-For the interpretation of an activity association, see <a href="#wasAssociatedWith-ordering">wasAssociatedWith-ordering</a>.
-</div>
-
-
-
-</section>
-
-
-
-
-
-
-
-<section id="Derivation-Relation">
-<h4>Derivation</h4>
-
-<p>A derivation is more informative if it contains a reference to an activity, generation, and usage. Hence, the following implication
-holds.</p>
-<div class='inference' id='derivation-implication'>
-Given two entities denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the assertion <span class="name">wasDerivedFrom(e2,
-e1, a, g2, u1, attrs)</span>
- holds for some generation <span class="name">g2</span>, usage <span class="name">u1</span>, and set of attribute-value pairs <span class="name">attrs</span>, then <span
-class="name">wasDerivedFrom(e2,e1, attrs)</span> also holds.<br>
- </div>
-
-<div class="interpretation-forward">
-For the interpretation of a derivation, 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>
-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>
-<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 derived from
- <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>
-
-
-<p></p>
-<div class="structural-forward">
-See <a href="#derivation-use">derivation-use</a> for a structural constraint on derivations.
-</div>
-
-
-
-
-
-
-
-</section>
-
-
-<section id="term-alternate-specialization">
-
-<h4>Alternate and Specializations</h4>
-
-<p>Nothing to add here</p>
-
- <div class="note">
-In order to further convey the intended meaning, the following properties are associated to these two relations.
-
- <ul>
- <li><span class="name">specializationOf(e2,e1)</span> is <strong>transitive</strong>: <span class="name">specializationOf(e3,e2)</span> and <span
-class="name">specializationOf(e2,e1)</span> implies <span class="name">specializationOf(e3,e1)</span>.
-
- <li><span class="name">specializationOf(e2,e1)</span> is <strong>anti-symmetric</strong>: <span class="name">specializationOf(e2,e1)</span> implies that <span
-class="name">specializationOf(e1,e2)</span> does not hold.
- <li><span class="name">alternateOf(e2,e1)</span> is <strong>symmetric</strong>: <span class="name">alternateOf(e2,e1)</span> implies <span class="name">alternateOf(e1,e2)</span>.
- </ul>
-
-There are proposals to make alternateOf a transitive property. This is still under discussion and the default is for alternateOf <strong>not</strong> to be transitive, and this is what the current text reflects.</div>
+<section id="term-Start">
+<h3>Start</h3>
+</section>
+<section id="term-End">
+<h3>End</h3>
+</section>
-<div class='issue'>A discussion on alternative definition of these relations has not reached a satisfactory conclusion yet. This is <a
-href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a>. Also <a href="http://www.w3.org/2011/prov/track/issues/96">ISSUE-96</a>.</div>
-
-
-</section>
-
-
-
-
-
-
-
-
-
-
-</section>
-
-
-
-
- <section id="common-relations">
-<h2>PROV-DM Common Relations</h2>
-
-<p>This section contains constraints associated with PROV-DM common relations.</p>
-
-
-
-
-
-<section id="term-traceability">
-<h3>Traceability</h3>
-
-
-<p>Traceability can be inferred from existing descriptions, or can be asserted stating that a dependency path exists without its individual steps being expressed. This is captured
-by the following inference and constraint, respectively.
-
-<div class='inference' id='traceability-inference'>
-Given two identifiers <span class="name">e2</span> and <span class="name">e1</span> for entities,
-the following statements hold:
-
-<ol>
-<li><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1,a,g2,u1)</span> holds, for some <span class="name">a</span>, <span class="name">g2</span>, <span
-class="name">u1</span>, <span class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also holds.</li>
-<li><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also
-holds.</li>
-<li><span class='conditional'>If</span> <span class="name">wasGeneratedBy(e2,a,gAttr) and wasAssociatedWith(a,e1)</span> hold, for some <span class="name">a</span> and <span
-class="name">gAttr</span>, <span class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also holds.</li>
-<li><span class='conditional'>If</span> <span class="name">wasGeneratedBy(e2,a,gAttr)</span>, <span class="name">wasAssociatedWith(a,e)</span> and <span
-class="name">actedOnBehalfOf(e,e1)</span> hold, for some <span class="name">a</span>, <span class="name">e</span>, and <span class="name">gAttr</span>, <span
-class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also holds.</li>
-<li><span class='conditional'>If</span> <span class="name">wasGeneratedBy(e2,a,gAttr) and wasStartedBy(a,e1,sAttr)</span> hold, for some <span class="name">a</span>, <span
-class="name">e</span>, and <span class="name">gAttr</span>, and <span class="name">sAttr</span>, <span class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also
-holds.</li>
-<li><span class='conditional'>If</span> <span class="name">tracedTo(e2,e)</span> and <span class="name">tracedTo(e,e1)</span> hold for some <span class="name">e</span>, <span
-class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also holds.</li>
-</ol>
-</div>
-
-<p>We note that the inference rule <a href="#traceability-inference">traceability-inference</a> does not allow us to infer attributes, which are application specific. </p>
-
-<div class='constraint' id='traceability-assertion'>
-<span class='conditional'>If</span> <span class="name">tracedTo(r2,r1,attrs)</span> holds for two identifiers <span class="name">r2</span> and <span class="name">r1</span>
-identifying entities, and attribute-value pairs <span class="name">attrs</span>,
- <span class='conditional'>then</span> there exist
-<span class="name">e<sup>0</sup></span>, <span class="name">e<sup>1</sup></span>, ..., <span class="name">e<sup>n</sup></span> for <span class="name">n≥1</span>, with <span
-class="name">e<sup>0</sup></span>=<span class="name">r2</span> and <span class="name">e<sup>n</sup></span>=<span class="name">r1</span>, and
-for any i such that <span class="name">0≤i≤n-1</span>, at least of the following statements holds:
-<ul>
-<li> <span class="name">wasDerivedFrom(e<sup>i</sup>,e<sup>i+1</sup>,a,g2,u1)</span> holds, for some <span class="name">a</span>, <span class="name">g2</span>, <span class="name">u1</span>,
-or</li>
-<li> <span class="name">wasDerivedFrom(e<sup>i</sup>,e<sup>i+1</sup>)</span> holds, or</li>
-<li> <span class="name">wasBasedOn(e<sup>i</sup>,e<sup>i+1</sup>)</span> holds, or</li>
-<li> <span class="name">wasGeneratedBy(e<sup>i</sup>,a,gAttr) and wasAssociatedWith(a,e<sup>i+1</sup>)</span> hold, for some <span class="name">a</span> and <span
-class="name">gAttr</span>, or</li>
-<li> <span class="name">wasGeneratedBy(e<sup>i</sup>,a,gAttr)</span>, <span class="name">wasAssociatedWith(a,e)</span> and <span class="name">actedOnBehalfOf(e,e<sup>i+1</sup>)</span> hold,
-for some <span class="name">a</span>, <span class="name">e</span> and <span class="name">gAttr</span>, or</li>
-<li> <span class="name">wasGeneratedBy(e<sup>i</sup>,a,gAttr) and wasStartedBy(a,e<sup>i+1</sup>,sAttr)</span> hold, for some <span class="name">a</span>, <span class="name">e</span>, and
-<span class="name">gAttr</span>, and <span class="name">sAttr</span>.</li>
-</ul>
-</div>
-
-<p>We note that the previous constraint is not really an inference <em>rule</em>, since there is nothing that we can actually infer. Instead, this constraint should simply be seen as part
-of the definition of the traceability relation. </p>
-
-
-</section>
-
-<section id="term-OrderingOfActivities">
-<h3>Activity Ordering</h3>
+<section id="term-Communication">
+<h3>Communication</h3>
@@ -948,6 +760,116 @@
</section>
+<section id="term-StartByActivity">
+<h3>Start by Activity</h3>
+</section>
+
+ </section>
+
+
+
+ <section id="component2">
+<h3>Component 2: Agents and Responsibility</h3>
+
+
+<section id="term-Agent">
+<h3>Agent</h3>
+</section>
+
+<section id="recod-attribution">
+<h3>Attribution</h3>
+
+
+<div class='inference' id='attribution-implication'>
+<span class='conditional'>If</span>
+<span class="name">wasAttributedTo(e,ag)</span> holds for some identifiers
+<span class="name">e</span> and <span class="name">ag</span>,
+<span class='conditional'>then</span>, there exists an activity with some identifier <span class="name">a</span> such that the following statements hold:
+<pre>
+activity(a,t1,t2,attr1)
+wasGenerateBy(e,a)
+wasAssociatedWith(a,ag,attr2)
+</pre>
+for some sets of attribute-value pairs <span class="name">attr1</span> and <span class="name">attr2</span>, time <span class="name">t1</span>, and <span class="name">t2</span>.
+</div>
+
+</section>
+
+
+
+
+<section id="term-Association">
+<h4>Association</h4>
+
+<div class="interpretation-forward">
+For the interpretation of an activity association, see <a href="#wasAssociatedWith-ordering">wasAssociatedWith-ordering</a>.
+</div>
+
+
+
+</section>
+
+<section id="term-Responsibility">
+<h3>Responsibility</h3>
+</section>
+
+
+</section>
+
+
+
+
+
+ <section id="component3">
+<h3>Component 3: Derivations</h3>
+
+
+
+
+<section id="Derivation-Relation">
+<h4>Derivation</h4>
+
+<p>A derivation is more informative if it contains a reference to an activity, generation, and usage. Hence, the following implication
+holds.</p>
+<div class='inference' id='derivation-implication'>
+Given two entities denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the assertion <span class="name">wasDerivedFrom(e2,
+e1, a, g2, u1, attrs)</span>
+ holds for some generation <span class="name">g2</span>, usage <span class="name">u1</span>, and set of attribute-value pairs <span class="name">attrs</span>, then <span
+class="name">wasDerivedFrom(e2,e1, attrs)</span> also holds.<br>
+ </div>
+
+<div class="interpretation-forward">
+For the interpretation of a derivation, 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>
+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>
+<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 derived from
+ <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>
+
+
+<p></p>
+<div class="structural-forward">
+See <a href="#derivation-use">derivation-use</a> for a structural constraint on derivations.
+</div>
+
+
+
+
+
+
+
+</section>
+
<section id="term-Revision">
<h3>Revision</h3>
@@ -977,27 +899,6 @@
</section>
-
-<section id="recod-attribution">
-<h3>Attribution</h3>
-
-
-<div class='inference' id='attribution-implication'>
-<span class='conditional'>If</span>
-<span class="name">wasAttributedTo(e,ag)</span> holds for some identifiers
-<span class="name">e</span> and <span class="name">ag</span>,
-<span class='conditional'>then</span>, there exists an activity with some identifier <span class="name">a</span> such that the following statements hold:
-<pre>
-activity(a,t1,t2,attr1)
-wasGenerateBy(e,a)
-wasAssociatedWith(a,ag,attr2)
-</pre>
-for some sets of attribute-value pairs <span class="name">attr1</span> and <span class="name">attr2</span>, time <span class="name">t1</span>, and <span class="name">t2</span>.
-</div>
-
-</section>
-
-
<section id="term-quotation">
<h3>Quotation</h3>
@@ -1026,6 +927,105 @@
</section>
+<section id="term-traceability">
+<h3>Traceability</h3>
+
+
+<p>Traceability can be inferred from existing descriptions, or can be asserted stating that a dependency path exists without its individual steps being expressed. This is captured
+by the following inference and constraint, respectively.
+
+<div class='inference' id='traceability-inference'>
+Given two identifiers <span class="name">e2</span> and <span class="name">e1</span> for entities,
+the following statements hold:
+
+<ol>
+<li><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1,a,g2,u1)</span> holds, for some <span class="name">a</span>, <span class="name">g2</span>, <span
+class="name">u1</span>, <span class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also holds.</li>
+<li><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also
+holds.</li>
+<li><span class='conditional'>If</span> <span class="name">wasGeneratedBy(e2,a,gAttr) and wasAssociatedWith(a,e1)</span> hold, for some <span class="name">a</span> and <span
+class="name">gAttr</span>, <span class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also holds.</li>
+<li><span class='conditional'>If</span> <span class="name">wasGeneratedBy(e2,a,gAttr)</span>, <span class="name">wasAssociatedWith(a,e)</span> and <span
+class="name">actedOnBehalfOf(e,e1)</span> hold, for some <span class="name">a</span>, <span class="name">e</span>, and <span class="name">gAttr</span>, <span
+class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also holds.</li>
+<li><span class='conditional'>If</span> <span class="name">wasGeneratedBy(e2,a,gAttr) and wasStartedBy(a,e1,sAttr)</span> hold, for some <span class="name">a</span>, <span
+class="name">e</span>, and <span class="name">gAttr</span>, and <span class="name">sAttr</span>, <span class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also
+holds.</li>
+<li><span class='conditional'>If</span> <span class="name">tracedTo(e2,e)</span> and <span class="name">tracedTo(e,e1)</span> hold for some <span class="name">e</span>, <span
+class='conditional'>then</span> <span class="name">tracedTo(e2,e1)</span> also holds.</li>
+</ol>
+</div>
+
+<p>We note that the inference rule <a href="#traceability-inference">traceability-inference</a> does not allow us to infer attributes, which are application specific. </p>
+
+<div class='constraint' id='traceability-assertion'>
+<span class='conditional'>If</span> <span class="name">tracedTo(r2,r1,attrs)</span> holds for two identifiers <span class="name">r2</span> and <span class="name">r1</span>
+identifying entities, and attribute-value pairs <span class="name">attrs</span>,
+ <span class='conditional'>then</span> there exist
+<span class="name">e<sup>0</sup></span>, <span class="name">e<sup>1</sup></span>, ..., <span class="name">e<sup>n</sup></span> for <span class="name">n≥1</span>, with <span
+class="name">e<sup>0</sup></span>=<span class="name">r2</span> and <span class="name">e<sup>n</sup></span>=<span class="name">r1</span>, and
+for any i such that <span class="name">0≤i≤n-1</span>, at least of the following statements holds:
+<ul>
+<li> <span class="name">wasDerivedFrom(e<sup>i</sup>,e<sup>i+1</sup>,a,g2,u1)</span> holds, for some <span class="name">a</span>, <span class="name">g2</span>, <span class="name">u1</span>,
+or</li>
+<li> <span class="name">wasDerivedFrom(e<sup>i</sup>,e<sup>i+1</sup>)</span> holds, or</li>
+<li> <span class="name">wasBasedOn(e<sup>i</sup>,e<sup>i+1</sup>)</span> holds, or</li>
+<li> <span class="name">wasGeneratedBy(e<sup>i</sup>,a,gAttr) and wasAssociatedWith(a,e<sup>i+1</sup>)</span> hold, for some <span class="name">a</span> and <span
+class="name">gAttr</span>, or</li>
+<li> <span class="name">wasGeneratedBy(e<sup>i</sup>,a,gAttr)</span>, <span class="name">wasAssociatedWith(a,e)</span> and <span class="name">actedOnBehalfOf(e,e<sup>i+1</sup>)</span> hold,
+for some <span class="name">a</span>, <span class="name">e</span> and <span class="name">gAttr</span>, or</li>
+<li> <span class="name">wasGeneratedBy(e<sup>i</sup>,a,gAttr) and wasStartedBy(a,e<sup>i+1</sup>,sAttr)</span> hold, for some <span class="name">a</span>, <span class="name">e</span>, and
+<span class="name">gAttr</span>, and <span class="name">sAttr</span>.</li>
+</ul>
+</div>
+
+<p>We note that the previous constraint is not really an inference <em>rule</em>, since there is nothing that we can actually infer. Instead, this constraint should simply be seen as part
+of the definition of the traceability relation. </p>
+
+
+</section>
+
+</section>
+
+<section id="component4">
+<h3>Component 4: Alternate Entities</h3>
+
+
+<section id="term-Specialization">
+<h3>Specialization</h3>
+</section>
+
+<section id="term-Alternate">
+<h3>Alternate</h3>
+</section>
+
+
+ <div class="note">
+In order to further convey the intended meaning, the following properties are associated to these two relations.
+
+ <ul>
+ <li><span class="name">specializationOf(e2,e1)</span> is <strong>transitive</strong>: <span class="name">specializationOf(e3,e2)</span> and <span
+class="name">specializationOf(e2,e1)</span> implies <span class="name">specializationOf(e3,e1)</span>.
+
+ <li><span class="name">specializationOf(e2,e1)</span> is <strong>anti-symmetric</strong>: <span class="name">specializationOf(e2,e1)</span> implies that <span
+class="name">specializationOf(e1,e2)</span> does not hold.
+ <li><span class="name">alternateOf(e2,e1)</span> is <strong>symmetric</strong>: <span class="name">alternateOf(e2,e1)</span> implies <span class="name">alternateOf(e1,e2)</span>.
+ </ul>
+
+There are proposals to make alternateOf a transitive property. This is still under discussion and the default is for alternateOf <strong>not</strong> to be transitive, and this is what the current text reflects.</div>
+
+
+<div class='issue'>A discussion on alternative definition of these relations has not reached a satisfactory conclusion yet. This is <a
+href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a>. Also <a href="http://www.w3.org/2011/prov/track/issues/96">ISSUE-96</a>.</div>
+
+
+
+
+</section>
+
+
+
+
<section id="term-Collection">
<h3>Collections</h3>
@@ -1034,11 +1034,28 @@
</section>
- </section>
+
+
+ <section id="component6">
+<h3>Component 6: Annotations</h3>
+
+
+ <section id="term-note">
+
+<h4>Note</h4>
+
+<p>Attribute-value pairs occurring in notes are application specific. Thus, their interpretation is outside the scope of this document, and they are not subject to any of the constraints listed in this document. </p>
+
+
+
+ </section>
+
+
</section>
+</section>
<section id="account-constraints">
<h3>PROV-DM Account Constraints</h3>
@@ -1152,6 +1169,13 @@
</div>
+<div class="note">THis is new</div>
+
+<div class='interpretation' id='generation-precedes-invalidation'>For any entity, the following ordering constraint holds: the <a title="entity generation event">generation</a> of an entity always
+<a>precedes</a> any of its <a title="entity destruction event">destruction</a>.
+</div>
+
+
<p>The mere existence of an activity 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
illustrated by Subfigure <a href="#constraint-summary">constraint-summary</a> (a) and expressed by constraint <a href="#start-precedes-end">start-precedes-end</a>.</p>