prep for fpwd
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Wed, 05 Oct 2011 23:05:57 +0100
changeset 537 a55f4df1a107
parent 536 78028c935235
child 538 aa3ecb190b53
prep for fpwd
model/ProvenanceModel.html
--- a/model/ProvenanceModel.html	Wed Oct 05 22:59:51 2011 +0100
+++ b/model/ProvenanceModel.html	Wed Oct 05 23:05:57 2011 +0100
@@ -717,9 +717,9 @@
 <p>
 The following process execution assertion</p>
 <pre class="example">
-processExecution(pe1,add-crime-in-london,t+1,t+1+epsilon,[host="server.example.com"])
+processExecution(pe1,add-crime-in-london,t+1,t+1+epsilon,[host="server.example.org"])
 </pre>
-<p>identified by identifier <span class="name">id</span>, states the existence of an activity with recipe link <span class="name">add-crime-in-london</span>, start time <span class="name">t+1</span>, and end time <span class="name">t+1+epsilon</span>, running on host <span class="name">server.example.com</span>.  The attribute <span class="name">host</span> is application specific, but MUST hold for the duration of activity.
+<p>identified by identifier <span class="name">id</span>, states the existence of an activity with recipe link <span class="name">add-crime-in-london</span>, start time <span class="name">t+1</span>, and end time <span class="name">t+1+epsilon</span>, running on host <span class="name">server.example.org</span>.  The attribute <span class="name">host</span> is application specific, but MUST hold for the duration of activity.
 </p>
 
 <p>The mere existence of a process execution assertion entails some event ordering in the world, since the start event precedes the end event.  This is expressed by constraint <a href="'#start-precedes-end'">start-precedes-end</a>.</p>
@@ -1508,8 +1508,8 @@
 <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.</p>
 <pre class="example">
-processExecution(pe1,long-workflow,t1,t2,[host="server1.example.com"])
-processExecution(pe2,long-workflow,t3,t4,[host="server2.example.com"])
+processExecution(pe1,long-workflow,t1,t2,[host="server1.example.org"])
+processExecution(pe2,long-workflow,t3,t4,[host="server2.example.org"])
 entity(e1,[type="scheduler",state=1])
 entity(e2,[type="scheduler",state=2])
 wasControlledBy(pe1,e1,qualifier(role="end"))
@@ -1859,7 +1859,7 @@
 <p>
 The following container </p>
 <pre class="example">
-container([x http://example.org],[acc1,acc2]
+container([x http://example.org/], [acc1,acc2]
           account(acc1,http://example.org/asserter1,...)
           account(acc2,http://example.org/asserter1,...))
 </pre>