--- a/model/ProvenanceModel.html Fri Sep 16 10:25:24 2011 +0100
+++ b/model/ProvenanceModel.html Fri Sep 16 12:21:10 2011 +0100
@@ -1550,7 +1550,7 @@
<p>
The following revision assertion
<pre class="example">
-wasRevisionBy(e3,e2,a4)
+wasRevisionOf(e3,e2,a4)
</pre>
states that the document represented by entity expression identified by <span class="name">e3</span> is declared to be revision of document represented by entity expression identified by <span class="name">e2</span> by agent representy by entity expression denoted by <span class="name">a4</span>.
</p>
@@ -1882,32 +1882,36 @@
<p>Use, generation, and control expressions MUST contain a qualifier. A qualifier's sequence of name-value pairs MAY be empty. </p>
-<div class='note'>LUC TO ADAPT to QUALIFIER</div>
-
+<p>The interpretation of a qualifier is specific to the process execution expression it occurs in, which means that a same qualifier may appear in two different process execution expressions with different interpretations.
+From this specification's viewpoint, a qualifier's interpretation is out of
+scope.</p>
<p>
-A use (resp. generation, control) expression does not contain an identifier.
+By definition, a use (resp. generation, control) expression does not contain an identifier.
If one wants to annotate a use (resp. generation, control) expression, this expression MUST be identifiable from its constituents, i.e. its source's identifier, its destination's identifier, and its qualifier.</p>
-<p> To be able to annotate, use (resp. generation, control) expressions that refer to a given process execution identifier,
+<p> To be able to annotate use (resp. generation, control) expressions that refer to a given process execution identifier,
any qualifier occuring in use expressions (resp. generation, control) with this identifier and a given entity expression identifier MUST be unique.</p>
-
-
-If one wants to annotate a use (resp. generation) edge expression or if one wants express a pe-linked-derivationExpression referring to this entity and process execution expressions, the qualifier occuring in this use assertion must be unique among the qualifiers qualifiying use expressions for this process execution.
-
-
-The set of all use (resp. generation, control) expressions that refer to a given process execution execution MUST contain at most one occurrence of a given role. The rationale for this requirement is that when provenance is used to replay execution, roles are used to determine which values must be associated with which input (resp. output, control channel) of a process execution.</p>
-
-<div class='resolved'>Decide the level of requirements: MUST/SHOULD and justify. This is <a href="http://www.w3.org/2011/prov/track/issues/40">ISSUE-40</a> and <a href="http://www.w3.org/2011/prov/track/issues/41">ISSUE-41</a>. MUST is confirmed. </div>
-
-
-<p>The interpretation of a role is specific to the process execution it relates
-to, which means that a same role may appear in relation to two different process executions with different interpretations.
-From this specification's viewpoint, a role's interpretation is out of
-scope.</p>
+<div class='note'>It may seem strange that we do not require use expressions to have an identifier. Mandating the presence of identifiers in use expressions would facilitate their annotation. However, this would make it difficult for use expressions to be encoded as properties in OWL2.
+</div>
+
+<p>Qualifiers are used in determining the exact source and destination of a <span class="nonterminal">pe-linked-derivationExpression</span>. Hence,
+if one wants to express a <span class="nonterminal">pe-linked-derivationExpression</span> referring to an entity expression and a process execution expression,
+<ul>
+<li>the useQualifier MUST be unique among the qualifiers occuring in use expressions for this process execution expression;
+<li>the generationQualifier MUST be unique among the qualifiers occuring in generation expressions for this process execution expression.
+</ul>
+</p>
+
+
+
+<div class='resolved'>Decide the level of requirements: MUST/SHOULD and justify. This is <a href="http://www.w3.org/2011/prov/track/issues/40">ISSUE-40</a> and <a href="http://www.w3.org/2011/prov/track/issues/41">ISSUE-41</a>. The circumstances in which the requirement is of type must MUST are now made explicit. </div>
+
+
+
</section>