--- a/model/ProvenanceModel.html Wed Oct 05 21:30:44 2011 +0100
+++ b/model/ProvenanceModel.html Wed Oct 05 21:35:43 2011 +0100
@@ -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,12 +1158,11 @@
</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>
@@ -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>
@@ -1387,12 +1386,11 @@
</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 +1483,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 +1502,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 +1516,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