--- a/model/ProvenanceModel.html Wed Oct 05 16:42:44 2011 -0400
+++ b/model/ProvenanceModel.html Wed Oct 05 16:43:06 2011 -0400
@@ -887,12 +887,12 @@
<p>
-The following generation assertions
+The following generation assertions</p>
<pre class="example">
wasGeneratedBy(e1,pe1,qualifier(port="p1", order=1),t1)
wasGeneratedBy(e2,pe1,qualifier(port="p1", order=2),t2)
</pre>
-state the existence of two events in the world (with respective times <span class="name">t1</span> and <span class="name">t2</span>), at which new characterized things, represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, are created by an activity, itself represented by a process execution expression identified by <span class="name">pe1</span>.
+<p>state the existence of two events in the world (with respective times <span class="name">t1</span> and <span class="name">t2</span>), at which new characterized things, represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, are created by an activity, itself represented by a process execution expression identified by <span class="name">pe1</span>.
The first one is available as the first value on port p1, whereas the other is the second value on port p1. The semantics of <span class="name">port</span> and <span class="name">order</span> in these expressions are application specific.
</p>
@@ -970,12 +970,12 @@
</ul>
-<p>The following use assertions
+<p>The following use assertions</p>
<pre class="example">
used(pe1,e1,qualifier(parameter="p1"),t1)
used(pe1,e2,qualifier(parameter="p2"),t2)
</pre>
-state that the activity, represented by the process execution expression identified by <span class="name">pe1</span>, consumed two characterized things, represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, at times <span class="name">t1</span> and <span class="name">t2</span>, respectively; the first one was found as the value of parameter <span class="name">p1</span>, whereas the second was found as value of parameter <span class="name">p2</span>. The semantics of <span class="name">parameter</span> in these expressions is application specific.</p>
+<p>state that the activity, represented by the process execution expression identified by <span class="name">pe1</span>, consumed two characterized things, represented by entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, at times <span class="name">t1</span> and <span class="name">t2</span>, respectively; the first one was found as the value of parameter <span class="name">p1</span>, whereas the second was found as value of parameter <span class="name">p2</span>. The semantics of <span class="name">parameter</span> in these expressions is application specific.</p>
<p>A reference to a given entity expression MAY appear in multiple use expressions that share
@@ -1079,20 +1079,20 @@
-<p>For convenience, PROV-DM allows for a compact, process-execution linked derivation assertion, written <span class="name">wasDerivedFrom(e2,e1)</span> in PROV-ASN, which:
+<p>For convenience, PROV-DM allows for a compact, process-execution linked derivation assertion, written <span class="name">wasDerivedFrom(e2,e1)</span> in PROV-ASN, which:</p>
<ul>
<li> refers to an entity expression identified by <span class="name">e2</span>, which is a representation of the generated characterized thing;
<li> refers to an entity expression identified by <span class="name">e1</span>, which is a represenation of the used characterized thing.
</ul>
-</p>
-
-
-<p>The following derivation assertions
+
+
+
+<p>The following derivation assertions</p>
<pre class="example">
wasDerivedFrom(e5,e3,pe4,qualifier(channel=out),qualifier(channel=in))
wasDerivedFrom(e3,e2)
</pre>
-</p>
+<p>
state the existence of process-linked derivations;
the first expresses that the activity represented by the process execution <span class="name">pe4</span>, by
using the thing represented by <span class="name">e3</span> obtained on the <span class="name">in</span> channel
@@ -1107,9 +1107,9 @@
</p>
<div class="constraint" id='derivation-events'>
-<a name="PIL:0010"><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1,pe,r2,r1)</span> holds, <span class='conditional'>then</span>
+<span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1,pe,r2,r1)</span> holds, <span class='conditional'>then</span>
<span class="name">wasGeneratedBy(e2,pe,r2)</span> and <span class="name">used(pe,e1,r1)</span> also
- hold. </a> [<a href="../ontology/ProvenanceFormalModel.html#PROV:0010">PROV:0010</a>]
+ hold.
</div>
@@ -1140,7 +1140,7 @@
or <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span>
the use
of characterized thing denoted by <span class="name">e1</span> precedes the generation of
-the characterized thing denoted by <span class="name">e2</span>.</a>
+the characterized thing denoted by <span class="name">e2</span>.
</div>
@@ -1158,14 +1158,13 @@
</p>
-<p>A further inference is permitted from the compact version of derivation expression:
+<p>A further inference is permitted from the compact version of derivation expression: </p>
<div class='constraint' id='derivation-use'>
-<a name="PIL:0011">Given a process execution expression identified by <span class="name">pe</span>, entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and qualifier <span class="name">q2</span>,
+<p>Given a process execution expression identified by <span class="name">pe</span>, entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and qualifier <span class="name">q2</span>,
<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.</a>
- [<a href="../ontology/ProvenanceFormalModel.html#PROV:0011">PROV:0011</a>]
+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>
@@ -1296,20 +1295,20 @@
</div>
-<p>An instance of a control expression, noted <span class="name">wasControlledBy(pe,ag,q)</span> in PROV-ASN :
+<p>An instance of a control expression, noted <span class="name">wasControlledBy(pe,ag,q)</span> in PROV-ASN:</p>
<ul>
<li> contains an identifier <span class="name">pe</span> denoting a process execution expression, representing the controlled activity;
<li> refers to an agent expression or an entity expression identified by <span class="name">ag</span>, representing the controlling characterized thing;
<li> contains a qualifier <span class="name">q</span>, qualifying the involvement of the thing in the activity.
</ul>
-</p>
+
<p>
-The following control assertion
+The following control assertion</p>
<pre class="example">
wasControlledBy(pe3,a4,[role=author])
</pre>
-states that the activity, represented by the process execution expression denoted by <span class="name">pe3</span> saw the involvement of a characterized thing, represented by entity expression denoted by <span class="name">a4</span> in the capacity of author. This specification defines the qualifier name <span class="name">role</span> (see Section <a href="#expression-qualifier">Qualifier</a>) to denote the function of a characterized thing with respect to an activity.
+<p>states that the activity, represented by the process execution expression denoted by <span class="name">pe3</span> saw the involvement of a characterized thing, represented by entity expression denoted by <span class="name">a4</span> in the capacity of author. This specification defines the qualifier name <span class="name">role</span> (see Section <a href="#expression-qualifier">Qualifier</a>) to denote the function of a characterized thing with respect to an activity.
</p>
</section>
@@ -1331,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>
@@ -1362,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"])
@@ -1384,15 +1382,14 @@
wasComplementOf(rs_l1, rs)
wasComplementOf(rs_l2, rs)
</pre>
-</p>
+
<div class='constraint' id='wasComplementOf-necessary-cond'>
- <a name="PIL:0013">An assertion "wasComplementOf(B,A)" holds over the temporal intersection of A and B, <span class='conditional'>only if</span>:
+An assertion "wasComplementOf(B,A)" holds over the temporal intersection of A and B, <span class='conditional'>only if</span>:
<ol>
-<li> if a mapping can be established from an attribute X of entity expression identified by B to an attribute Y of entity expression identified by A, then the values of A and B must be consistent with that mapping</em>;</li>
+<li> if a mapping can be established from an attribute X of entity expression identified by B to an attribute Y of entity expression identified by A, then the values of A and B must be consistent with that mapping;</li>
<li>entity expression identified by B has some attribute that entity expression identified by A does not have.
-</li></ol></a>
- [<a href="../ontology/ProvenanceFormalModel.html#PROV:0013">PROV:0013</a>]
+</li></ol>
</div>
<p>The complementariy relation is not transitive. Let us consider identifiers <span class="name">e1</span>, <span class="name">e2</span>, and <span class="name">e3</span> identifying three entity expressions such that
@@ -1485,18 +1482,18 @@
|
----- pe3
</pre>
-The end in process execution expression identified by <span class="name">pe3</span> precedes the start in process execution expression identified by <span class="name">pe1</span>, while interval for process execution expression <span class="name">pe2</span> overlaps with each interval for <span class="name">pe1</span> and <span class="name">pe3</span>, allowing information to flow (<span class="name">e1</span> and <span class="name">e2</span>, respectively).</p>
+<p>The end in process execution expression identified by <span class="name">pe3</span> precedes the start in process execution expression identified by <span class="name">pe1</span>, while interval for process execution expression <span class="name">pe2</span> overlaps with each interval for <span class="name">pe1</span> and <span class="name">pe3</span>, allowing information to flow (<span class="name">e1</span> and <span class="name">e2</span>, respectively).</p>
<p>
An instance of a control ordering expression, written as
-<span class="name">wasScheduledAfter(pe2,pe1)</span> in PROV-ASN:
+<span class="name">wasScheduledAfter(pe2,pe1)</span> in PROV-ASN: </p>
<ul>
<li> refers to a process execution expression identified by <span class="name">pe2</span>;
<li> refers to a process execution expression identified by <span class="name">pe1</span>,
</ul>
-and states control ordering between <span class="name">pe2</span> and <span class="name">pe1</span>, specified as follows.
+<p>and states control ordering between <span class="name">pe2</span> and <span class="name">pe1</span>, specified as follows.</p>
<div class='constraint' id='wasScheduledAfter'>Given two process execution expressions identified by <span class="name">pe1</span> and <span class="name">pe2</span>,
the expression <span class="name">wasScheduledAfter(pe2,pe1)</span>
@@ -1504,10 +1501,10 @@
there are two entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>,
such that <span class="name">wasControlledBy(pe1,e1,qualifier(role="end"))</span> and <span class="name">wasControlledBy(pe2,e2,qualifier(role="start"))</span> and <span class="name">wasDerivedFrom(e2,e1)</span>.
</div>
-This definition assumes that the activities represented by process execution expressions identified by <span class="name">pe1</span> and <span class="name">pe2</span> are controlled by some agents (with identifiers <span class="name">e1</span> and <span class="name">e2</span>), where the first agent terminates (control qualifier <span class="name">qualifier(role="end")</span>) the first activity, and the second agents initiates (control qualifier <span class="name">qualifier(role="start")</span>) the second activity. The second agent being "derived" from the first enforces temporal ordering.
+<p>This definition assumes that the activities represented by process execution expressions identified by <span class="name">pe1</span> and <span class="name">pe2</span> are controlled by some agents (with identifiers <span class="name">e1</span> and <span class="name">e2</span>), where the first agent terminates (control qualifier <span class="name">qualifier(role="end")</span>) the first activity, and the second agents initiates (control qualifier <span class="name">qualifier(role="start")</span>) the second activity. The second agent being "derived" from the first enforces temporal ordering. </p>
<p>
-In the following assertions, we find two process execution expressions, identified by <span class="name">pe1</span> and <span class="name">pe2</span>, representing two activities, which took place on two separate hosts.
+In the following assertions, we find two process execution expressions, identified by <span class="name">pe1</span> and <span class="name">pe2</span>, representing two activities, which took place on two separate hosts.</p>
<pre class="example">
processExecution(pe1,long-workflow,t1,t2,[host="server1.example.com"])
processExecution(pe2,long-workflow,t3,t4,[host="server2.example.com"])
@@ -1518,7 +1515,7 @@
wasDerivedFrom(e2,e1)
wasScheduledAfter(pe2,pe1)
</pre>
-The one identified by <span class="name">pe2</span> is said to be
+<p>The one identified by <span class="name">pe2</span> is said to be
scheduled after the one identified by <span class="name">pe1</span>
because the scheduler terminated the activity (represented by process
execution identified by <span class="name">pe1</span>) to relocate it
@@ -1527,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">
@@ -1552,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>
@@ -1581,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>
@@ -1626,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>
@@ -1634,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>
@@ -1670,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"])
@@ -1681,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>