--- a/model/prov-constraints.html Fri Jun 01 14:47:40 2012 +0100
+++ b/model/prov-constraints.html Fri Jun 01 14:59:26 2012 +0100
@@ -466,9 +466,9 @@
<tr><td><a><b>Type or Relation Name</b></a></td><td><b>Definitions, Constraints, Inferences</b></td><td><b>Component</b></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
-<tr class="component1-color"><td class="essential"><a>Entity</a></td><td><a class="rule-text" href="#entity-unique"><span>TBD</span></a><br><a class="rule-text" href="#unique-generation-time"><span>TBD</span></a><br><a class="rule-text" href="#unique-invalidation-time"><span>TBD</span></a></td><td rowspan="8"><a href="#component1">Component 1: Entities/Activities</a></td></tr>
-<tr class="component1-color"><td class="essential"><a>Activity</a></td><td><a class="rule-text" href="#activity-unique"><span>TBD</span></a><br><a class="rule-text" href="#unique-startTime"><span>TBD</span></a><br><a class="rule-text" href="#unique-endTime"><span>TBD</span></a><br><a class="rule-text" href="#usage-within-activity"><span>TBD</span></a><br><a class="rule-text" href="#generation-within-activity"><span>TBD</span></a></td></tr>
-<tr class="component1-color"><td class="essential"><a>Generation</a></td><td><a class="rule-text" href="#generation-uniqueness"><span>TBD</span></a><br><a class="rule-text" href="#unique-generation-time"><span>TBD</span></a><br><a class="rule-text" href="#generation-within-activity"><span>TBD</span></a> </td></tr>
+<tr class="component1-color"><td class="essential"><a>Entity</a></td><td><a class="rule-text" href="#unique-entity"><span>TBD</span></a><br><a class="rule-text" href="#unique-generation-time"><span>TBD</span></a><br><a class="rule-text" href="#unique-invalidation-time"><span>TBD</span></a></td><td rowspan="8"><a href="#component1">Component 1: Entities/Activities</a></td></tr>
+<tr class="component1-color"><td class="essential"><a>Activity</a></td><td><a class="rule-text" href="#unique-activity"><span>TBD</span></a><br><a class="rule-text" href="#unique-startTime"><span>TBD</span></a><br><a class="rule-text" href="#unique-endTime"><span>TBD</span></a><br><a class="rule-text" href="#usage-within-activity"><span>TBD</span></a><br><a class="rule-text" href="#generation-within-activity"><span>TBD</span></a></td></tr>
+<tr class="component1-color"><td class="essential"><a>Generation</a></td><td><a class="rule-text" href="#unique-generation"><span>TBD</span></a><br><a class="rule-text" href="#unique-generation-time"><span>TBD</span></a><br><a class="rule-text" href="#generation-within-activity"><span>TBD</span></a> </td></tr>
<tr class="component1-color"><td class="essential"><a>Usage</a></td><td><a class="rule-text" href="#usage-within-activity"><span>TBD</span></a> </td></tr>
<tr class="component1-color"><td class="essential"><a>Communication</a></td><td><a class="rule-text" href="#wasInformedBy-definition"><span>TBD</span></a> </td></tr>
<tr class="component1-color"><td><a>Start</a></td><td><a class="rule-text" href="#wasStartedBy-definition"><span>TBD</span><br></a><a class="rule-text" href="#unique-startTime"><span>TBD</span></a><br> <a class="rule-text" href="#start-precedes-end"><span>TBD</span></a></td></tr>
@@ -481,11 +481,11 @@
<tr class="component2-color"><td class="provType"><a>Revision</a></td><td></td></tr>
<tr class="component2-color"><td class="provType"><a>Quotation</a></td><td></td></tr>
<tr class="component2-color"><td class="provType"><a>Original Source</a></td><td></td></tr>
-<tr class="component2-color"><td><a>Trace</a></td><td><a class="rule-text" href="#trace-inference"><span>TBD</span></a></td></tr>
+<tr class="component2-color"><td><a>Trace</a></td><td><a class="rule-text" href="#inference-trace"><span>TBD</span></a></td></tr>
<tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
<tr class="component3-color" style="border-collapse: collapse; "><td class="essential"><a>Agent</a></td><td> </td><td rowspan="8"><a href="#component3">Component 3: Agents/Responsibility</a></td></tr>
-<tr class="component3-color"><td class="essential"><a>Attribution</a></td><td><a class="rule-text" href="#attribution-implication"><span>TBD</span></a> </td></tr>
+<tr class="component3-color"><td class="essential"><a>Attribution</a></td><td><a class="rule-text" href="#inference-attribution"><span>TBD</span></a> </td></tr>
<tr class="component3-color"><td class="essential"><a>Association</a></td><td> </td></tr>
<tr class="component3-color"><td class="essential"><a>Delegation</a></td><td> </td></tr>
<tr class="component3-color"><td class="provType"><a>Plan</a></td><td> </td>
@@ -672,7 +672,7 @@
class='conditional'>THEN</span> <span class="name">used(-;a,e1,-)</span> also holds.
</div>
<p>This inference is justified by the fact that the entity denoted by <span class="name">e2</span> is generated by at most one activity in a given account
-(see <a class="rule-text" href="#generation-uniqueness"><span>TBD</span></a>). Hence, this activity is also the one referred to by the usage of <span class="name">e1</span>.
+(see <a class="rule-text" href="#unique-generation"><span>TBD</span></a>). Hence, this activity is also the one referred to by the usage of <span class="name">e1</span>.
</p>
<div class="note">
@@ -759,13 +759,13 @@
<section >
<h3>Component 3: Agents</h3>
-<p id='attribution-implication_text'> Attribution identifies an agent as responsible for an entity. An
+<p id='inference-attribution_text'> Attribution identifies an agent as responsible for an entity. An
agent can only be responsible for an entity if it was associated with
an activity that generated the entity. If the activity, generation
and association events are not explicit in the instance, they can
be inferred.</p>
-<div class='inference' id='attribution-implication'>
+<div class='inference' id='inference-attribution'>
<p>
<span class='conditional'>IF</span>
<span class="name">wasAttributedTo(-;e,ag)</span> holds for some identifiers
@@ -793,12 +793,12 @@
<hr>
-<p id='trace-inference_text'>A trace allows an entity to be transitively linked to another entity it is derived from, to an agent it is attributed to, or another agent having some responsibility, or a trigger of an activity that generated it.</p>
+<p id='inference-trace_text'>A trace allows an entity to be transitively linked to another entity it is derived from, to an agent it is attributed to, or another agent having some responsibility, or a trigger of an activity that generated it.</p>
<p>A trace can be inferred from existing statements, or can be asserted stating that a dependency path exists without its individual steps being expressed. This is captured
by the following inferences:
-<div class='inference' id='trace-inference'>
+<div class='inference' id='inference-trace'>
<p>
Given two identifiers <span class="name">e2</span> and <span class="name">e1</span> for entities,
the following statements hold:</p>
@@ -829,7 +829,7 @@
</div>
<p>We note that <a class="rule-text"
-href="#trace-inference"><span>TBD</span></a> does not
+href="#inference-trace"><span>TBD</span></a> does not
allow us to infer anything about the attributes of the related
entities, agents or events.
</p>
@@ -1195,16 +1195,16 @@
<p>
<hr>
- <p id='entity-unique_text'> We assume that the various identified objects of PROV-DM have
+ <p id='unique-entity_text'> We assume that the various identified objects of PROV-DM have
unique statements describing them within a PROV instance.
</p>
- <div class='constraint' id='entity-unique'>
+ <div class='constraint' id='unique-entity'>
<p>Given an entity identifier <span class="name">e</span>, there is at
most one expression
<span class="name">entity(e,attrs)</span>, where <span
class="name">attrs</span> is some set of attribute-values.</p>
</div>
- <div class='constraint' id='activity-unique'>
+ <div class='constraint' id='unique-activity'>
<p>Given an activity identifier <span class="name">a</span>, there is
at most one expression
<span class="name">activity(a,t1,t2,attrs)</span>, where <span
@@ -1222,7 +1222,7 @@
<hr>
-<div id='generation-uniqueness_text'>
+<div id='unique-generation_text'>
<p>We assume that an entity has exactly one generation and
invalidation event (either or both may, however, be left implicit).
So, PROV-DM allows for two distinct <a>generations</a> <span class="name">g1</span> and <span class="name">g2</span> referencing the same entity provided they occur
@@ -1234,7 +1234,7 @@
</div>
-<div class='constraint' id='generation-uniqueness'>
+<div class='constraint' id='unique-generation'>
<p>
Given an entity denoted by <span class="name">e</span>, two activities denoted by <span class="name">a1</span> and <span
class="name">a2</span>, two time instants <span class="name">t1</span> and <span
@@ -1257,7 +1257,7 @@
<p id='unique-generation-time_text'>A generation can be used to indicate a generation time without having to specify the involved activity. A generation time is unique, as specified by the following constraint.<p>
<div class="note">
-Seems redundant given generation-uniqueness
+Seems redundant given unique-generation
</div>
<div class='constraint' id='unique-generation-time'>
<p>Given an entity denoted by <span class="name">e</span> and
@@ -2071,10 +2071,10 @@
<p>Two different statements about the same entity cannot co-exist in a PROV instance
- as formalized in <a class="rule-text" href="#entity-unique"><span>entity-unique</span></a>.</p>
+ as formalized in <a class="rule-text" href="#unique-entity"><span>unique-entity</span></a>.</p>
<!-- Moved to uniqueness constraints section
-<div class='constraint' id='entity-unique'>
+<div class='constraint' id='unique-entity'>
<p>Given an entity identifier <span class="name">e</span>, there is at most one statement
<span class="name">entity(e,attrs)</span> occurring in a given
account, where <span class="name">attrs</span> is some set of
@@ -2088,7 +2088,7 @@
<p>In some cases, there may be a requirement for two different
- statements concerning the same entity to be included in the same provenance instance. To satisfy the constraint <a class="rule-text" href="#entity-unique"><span>entity-unique</span></a>, we can adopt a different identifier for one of them, and relate the two statements with the <span class="name">alternateOf</span> relation. </p>
+ statements concerning the same entity to be included in the same provenance instance. To satisfy the constraint <a class="rule-text" href="#unique-entity"><span>unique-entity</span></a>, we can adopt a different identifier for one of them, and relate the two statements with the <span class="name">alternateOf</span> relation. </p>
<div class="anexample" id="merge-with-rename">
<p>We now reconsider the same two statements of a same entity, but we change the identifier for one of them:</p>
@@ -2107,11 +2107,11 @@
<p> Taking the union of two accounts is another account,
formed by the union of the statements they respectively contain. We note that the resulting union may or may not invalidate some constraints:
<ul>
-<li> Two entity statements with the same identifier but different sets of attributes exist in each original PROV instance may invalidate <a class="rule-text" href="#entity-unique"><span>entity-unique</span></a> in the union, unless some form of statement merging or renaming (as per <a href="#merge-with-rename">Example</a>) occurs.
+<li> Two entity statements with the same identifier but different sets of attributes exist in each original PROV instance may invalidate <a class="rule-text" href="#unique-entity"><span>unique-entity</span></a> in the union, unless some form of statement merging or renaming (as per <a href="#merge-with-rename">Example</a>) occurs.
<li> Structurally well-formed
accounts are not
closed under union because the
-constraint <a class="rule-text" href="#generation-uniqueness"><span>TBD</span></a> may no
+constraint <a class="rule-text" href="#unique-generation"><span>TBD</span></a> may no
longer be satisfied in the resulting union. </li>
</ul>
<p>How to reconcile such accounts is beyond the scope of this specification.</p>