--- a/model/ProvenanceModel.html Thu Nov 24 23:10:38 2011 +0000
+++ b/model/ProvenanceModel.html Thu Nov 24 23:26:48 2011 +0000
@@ -777,6 +777,13 @@
<p>This section contains the normative specification of PROV-DM core, the core of the PROV data model.</p>
+<div class="note">
+In a next iteration of this document, it is proposed to reorganize
+section 5 as follows. First, the presentation of the data model
+alone. Second, its temporal interpretation. Third, the constraints and
+inferences associated with well-formed accounts.
+</div>
+
<section id="PROV-DM-record">
<h3>Record</h3>
@@ -1115,7 +1122,7 @@
<div class="table">
<table border="1" align="center">
<tr><td></td><td>Entity</td><td>Activity</td><td>Agent</td><td>Note</td></tr>
-<tr><td>Entity</td><td>wasDerivedFrom<br>wasBasedOn<br>wasComplementOf</td><td>wasGeneratedBy</td><td>-</td><td>hasAnnotation</td></tr>
+<tr><td>Entity</td><td>wasDerivedFrom<br>wasComplementOf</td><td>wasGeneratedBy</td><td>-</td><td>hasAnnotation</td></tr>
<tr><td>Activity</td><td>used</td><td>-</td><td>wasStartedBy<br>wasEndedBy<br>wasAssociatedWith</td><td>hasAnnotation</td></tr>
<tr><td>Agent</td><td>-</td><td>-</td><td>actedOnBehalfOf<br>wasComplementOf</td><td>hasAnnotation</td></tr>
<tr><td>Note</td><td>-</td><td>-</td><td>-</td><td>hasAnnotation</td></tr>
@@ -1168,7 +1175,7 @@
<p>
-A generation record's id is OPTIONAL. It MUST be used when annotating generation records (see Section <a href="#record-annotation">Annotation Record</a>) or when defining derivations (see <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a>).
+A generation record's id is OPTIONAL. It MUST be used when annotating generation records (see Section <a href="#record-annotation">Annotation Record</a>) or when defining precise-1 derivations (see <a href="#Derivation-Relation">Derivation Record</a>).
</p>
@@ -1264,13 +1271,15 @@
-<p>A reference to a given entity record MAY appear in multiple usage records that share
- a given activity record identifier. If one wants to annotate a usage record or if one wants to express a <a href="#pe-linked-derivationRecord"><span class='nonterminal'>pe-linked-derivationRecord</span></a> referring to this entity and activity records, the attributes occuring in this usage assertion MUST be unique among the attributes of other usage records for this activity
+<p>
+A usage record's id is OPTIONAL. It MUST be present when annotating usage records (see Section <a href="#record-annotation">Annotation Record</a>) or when defining precise-1 derivations (see <a href="#Derivation-Relation">Derivation Record</a>).</p>
+
+<p>
+A reference to a given entity record MAY appear in multiple usage records that share
+ a given activity record identifier.
</p>
-<div class='note'>TODO: The two previous paragraphs can be merged. The unicity property on attributes is not required, since we have introduced an identity. Needs reformulating.</div>
-
@@ -1796,6 +1805,9 @@
<h4>Complementarity Record</h4>
+<div class="note">While the working group recognizes the importance of the complementarity record concept, its name and its exact semantics are still being discussed.
+</div>
+
<p>A <dfn id="complementOf">complementarity record</dfn> is a relationship between two entities stated to have compatible characterization over some continuous interval between two events.</p>