example of wasScheduledAfter with pe relocation
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Thu, 15 Sep 2011 22:15:30 +0100
changeset 290 35c543bd8d7e
parent 289 9c3688c8cc7e
child 291 2807ccf4ae37
example of wasScheduledAfter with pe relocation
model/ProvenanceModel.html
--- a/model/ProvenanceModel.html	Thu Sep 15 14:54:34 2011 +0100
+++ b/model/ProvenanceModel.html	Thu Sep 15 22:15:30 2011 +0100
@@ -588,7 +588,7 @@
 
 <p>An instance of an entity expression, noted <span class="name">entity(id, [ attr1= val1, ...])</span> in PROV-ASN:
 <ul>
-<li> contains an identifier <span class="name">id</span> denoting a characterized thing;</li>
+<li> contains an identifier <span class="name">id</span> identifying a characterized thing;</li>
 <li> contains a set of attribute-value pairs <span class="name">[ attr1= val1, ...]</span>, representing this characterized thing's situation in the world.</li>
 </ul>
 </p>
@@ -1465,11 +1465,29 @@
  there are two entity expressions denoted by <span class="name">e1</span> and <span class="name">e2</span>,
 such that <span class="name">wasControlledBy(pe1,e1,[role="end"])</span> and <span class="name">wasControlledBy(pe2,e2,[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, represented by expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, where the first agent terminates (control qualifier <span class="name">[role="end"]</span>) the first activity, and the second initiates (control qualifier <span class="name">[role="start"]</span>) the second.  The second agent being "derived" from the first enforces  temporal ordering. 
-
-
-
-<div class='issue'>Suggested definition for process ordering. This is <a href="http://www.w3.org/2011/prov/track/issues/50">ISSUE-50</a>.</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, represented by expressions identified by <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 initiates (control qualifier <span class="name">qualifier([role="start"])</span>) the second.  The second agent being "derived" from the first enforces  temporal ordering. 
+
+<p>
+In the following assertions, we find two process execution expressions, identified by <span class="name">pe1</span> and <span class="name">pe2</span>, denoting two activities, which took place on two separate hosts.
+<pre class="example">
+processExecution(pe1,long-workflow,t1,t2,[host="server1.example.com"])
+processExecution(pe2,long-workflow,t3,t4,[host="server2.example.com"])
+entity(e1,[type="scheduler",state=1])
+entity(e2,[type="scheduler",state=2])
+wasControlledBy(pe1,e1,qualifier([role="end"]))
+wasControlledBy(pe2,e2,qualifier([role="start"]))
+wasDerivedFrom(e2,e1)
+wasScheduledAfter(pe2,pe1)
+</pre>
+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
+to the new host.
+</p>
+
+
+<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>