--- a/model/ProvenanceModel.html Wed Oct 05 21:35:43 2011 +0100
+++ b/model/ProvenanceModel.html Wed Oct 05 21:38:44 2011 +0100
@@ -1164,7 +1164,7 @@
<span class='conditional'>if</span> <span class="name">wasDerivedFrom(e2,e1)</span> and <span class="name">wasGeneratedBy(e2,pe,q2)</span> hold, <span class='conditional'>then</span> there exists a qualifier <span class="name">q1</span>,
such that <span class="name">used(pe,e1,r1)</span> also holds.
</div>
-This inference is justified by the fact that the characterized thing represented by entity expression identified by <span class="name">e2</span> is generated by at most one activity in a given account (see <a href="#generation-unicity">generation-unicity</a>). Hence, this process execution expression is also the one referred to in the use expression of <span class="name">e1</span>.
+<p>This inference is justified by the fact that the characterized thing represented by entity expression identified by <span class="name">e2</span> is generated by at most one activity in a given account (see <a href="#generation-unicity">generation-unicity</a>). Hence, this process execution expression is also the one referred to in the use expression of <span class="name">e1</span>.
</p>
@@ -1330,7 +1330,7 @@
An entity expression represents, by means of attribute-value pairs, a thing and its situation in the world, which remain constant over a characterization interval.
As soon as the thing's situation changes, this marks the end of the characterization interval for the entity expression representing it. The thing's novel situation is represented by an attribute with a new value, or an entirely different set of attribute-value pairs, embodied in another entity expression, with a new characterization interval. Thus, if we overlap the timelines (or, more generally, the sequences of value-changing events) for the two characterised things, we can hope to establish correspondences amongst the entity expressions that represent them at various points along that events line. The figure below illustrates this intuition.</p>
-<img src="complement-of.png"/>
+<img src="complement-of.png" alt="illustration complementOf"/>
<p>
Relation <em>complement-of</em> between two entity expressions is intended to capture these correspondences, as follows. Suppose entity expressions A and B share a set P of properties, and each of them has other properties in addition to P. If the values assigned to each property in P are <em>compatible</em> between A and B, then we say that <em>A is-complement-of B</em>, and <em>B is-complement-of A</em>, in a symmetrical fashion. In the particular case where the set P of properties of B is a strict superset of A's properties, then we say that <em>B is-complement-of A</em>, but in this case the opposite does not hold. In this case, the relation is not symmetric. (as a special case, A and B may not share any attributes at all, and yet the asserters may still stipulate that they are representing the same thing "Royal Society". The symmetric relation may hold trivially in this case).</p>
@@ -1361,7 +1361,6 @@
<p>An instance of a complementarity expression is written <span class="name">wasComplementOf(e2,e1)</span>, where <span class="name">e1</span> and <span class="name">e2</span> are two identifiers denoting entity expressions.</p>
-<p>
<pre class="example">
entity(rs,[created="1870"])
@@ -1383,7 +1382,7 @@
wasComplementOf(rs_l1, rs)
wasComplementOf(rs_l2, rs)
</pre>
-</p>
+
<div class='constraint' id='wasComplementOf-necessary-cond'>
An assertion "wasComplementOf(B,A)" holds over the temporal intersection of A and B, <span class='conditional'>only if</span>:
@@ -1525,7 +1524,7 @@
<div class='pending'>Suggested definition for process ordering. This is <a href="http://www.w3.org/2011/prov/track/issues/50">ISSUE-50</a>.</div>
-</p>
+
<section id="expression-Revision">
@@ -1550,13 +1549,13 @@
-<p>An instance of a revision expression, noted <span class="name">wasRevisionOf(e2,e1,ag)</span> in PROV-ASN:
+<p>An instance of a revision expression, noted <span class="name">wasRevisionOf(e2,e1,ag)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">e2</span> identifying an entity that represents a newer version of a thing;
<li> contains an identifier <span class="name">e1</span> identifying an entity that represents an older version of a thing;
<li> MAY refer to a responsible agent with identifier <span class="name">ag</span>.
</ul>
-</p>
+
<p>A revision expression can only be asserted, since it needs to include a reference to an agent who represents someone in the real world who bears responsibility for declaring a variant of a thing. However, it needs to satisfy the following constraint, linking the two entity expressions by a derivation, and stating them to be a complement of a third entity expression.</p>
@@ -1579,11 +1578,11 @@
</p>
<p>
-The following revision assertion
+The following revision assertion</p>
<pre class="example">
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>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>
@@ -1624,7 +1623,6 @@
<p>A thing's participation in an activity can be by direct use or direct control. But also, if a thing and situation are characterized in two complementary manners (and are represented by two entity expressions related by <span class="name">isComplementOf</span>), if one of them participates in an activity, so does the other. The following captures the definition of participation.</p>
<div class='constraint' id='participation'>
-<a name="PIL:0014">
Given two identifiers <span class="name">pe</span> and <span class="name">e</span>, respectively identifying a process execution expression and an entity expression, the expression <span class="name">hadParticipant(pe,e)</span> holds <span class='conditional'>if and only if</span>:
<ul>
<li> <span class="name">used(pe,e)</span> holds, or</li>
@@ -1632,8 +1630,6 @@
<li> <span class="name">wasComplementOf(e1,e)</span> holds for some entity expression identified by <span class="name">e1</span>, and
<span class="name">hadParticipant(pe,e1)</span> holds some process execution expression identified by <span class="name">pe</span>.</li>
</ul>
-</a> [<a
-href="../ontology/ProvenanceFormalModel.html#PROV:0014">PROV:0014</a>]
</div>
@@ -1668,10 +1664,10 @@
<span class="nonterminal">identifier</span> <span class="nonterminal">identifier</span> <span class="nonterminal">qualifier</span>
</div>
-<p>The interpretation of annotations is application-specific. See Section <a href="#expression-annotation">Annotation</a> for a discussion of the difference between attributes and annotations</a>.
+<p>The interpretation of annotations is application-specific. See Section <a href="#expression-annotation">Annotation</a> for a discussion of the difference between attributes and annotations. </p>
<p>
-The following expressions
+The following expressions</p>
<pre class="example">
entity(e1,[type="document"])
entity(e2,[type="document"])
@@ -1679,7 +1675,7 @@
hasAnnotation(e1,ann1)
hasAnnotation(e2,ann1)
</pre>
-assert the existence of two documents in the world (attribute-value pair: <span class="name">type="document"</span>) represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and annotate these expressions with an annotation indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>.
+<p>assert the existence of two documents in the world (attribute-value pair: <span class="name">type="document"</span>) represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and annotate these expressions with an annotation indicating that the icon (an application specific way of rendering provenance) is <span class="name">doc.png</span>.
</p>