--- a/model/ProvenanceModel.html	Tue Sep 06 01:24:40 2011 +0100
+++ b/model/ProvenanceModel.html	Tue Sep 06 10:12:39 2011 +0100
@@ -664,7 +664,7 @@
 <p>If <b>e2</b> is derived from <b>e1</b>, then 
 this means that the thing represented by <b>e1</b> has an influence on the thing represented by <b>e2</b>, which is captured by a dependency between their attribute values; it also implies temporal ordering. These are specified as follows:</p>
 
-<div class='constraint' id='derivation-attributes'><a name="PIL:0007">Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
+<div class='constraint' id='derivation-attributes'><a name="PIL:0007">Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
 or <b>wasDerivedFrom(e2,e1)</b> holds, <span class='conditional'>if and only if</span>:
  the values of some attributes
 of <b>e2</b> are partly or fully determined by the values of some
@@ -675,8 +675,8 @@
 
 
 
-<div class='constraint' id='derivation-use-generation-ordering'><a name="PIL:0008">Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, if the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
-or <b>wasDerivedFrom(e2,e1)</b> holds, then
+<div class='constraint' id='derivation-use-generation-ordering'><a name="PIL:0008">Given a process execution <b>pe</b>, entities <b>e1</b> and <b>e2</b>, roles <b>r1</b> and <b>r2</b>, <span class='conditional'>if</span> the assertion <b>wasDerivedFrom(e2,e1,pe,r2,r1)</b>
+or <b>wasDerivedFrom(e2,e1)</b> holds, <span class='conditional'>then</span>
 the use
 of characterized thing denoted by <b>e1</b> precedes the generation of
 the characterized thing denoted by <b>e2</b>.</a> [<a href="../ontology/ProvenanceFormalModel.html#PIL:0008">PIL:0008</a>]
@@ -1040,25 +1040,52 @@
 <h3>Ordering of Process Executions</h3>
 </section>
 
-<p>Various relationships of temporal nature exist between process executions.
-<dfn id="ControlOrdering">Control ordering</dfn> means that the end of
+
+<p>PIDM allows two forms of temporal relationships between process executions to be expressed.
+<dfn id="InformationOrdering">Information flow ordering</dfn> states that a characterized thing was generated by a process execution before it was used by another process execution.
+<dfn id="ControlOrdering">Control ordering</dfn> states that the end of
 a process execution precedes the start of another process execution,
 by a same agent.
-<dfn id="InformationOrdering">Information flow</dfn> means that a characterized thing was generated by a process execution before it was used by another process execution.
 </p>
 
-<p>An assertion isScheduledAfter:
+
+<p>
+An instance of a <b>wasInformedBy</b> construct, written as 
+<b>wasInformedBy(pe2,pe1)</b> in the Provenance Abstract Syntax Notation: 
 <ul>
-<li> refers to a process execution;
-<li> refers to a process execution.
+<li> refers to a process execution <b>pe2</b>;
+<li> refers to a process execution <b>pe1</b>
 </ul>
-</p>
+and expresses information flow ordering between <b>pe2</b> and <b>pe1</b>.
+The meaning of the <b>wasInformedBy</b> construct is specified as follows.
 
-<p>An assertion isInformedBy:
+<div class='constraint' id='wasInformedBy'>Given two process executions denoted by <b>pe1</b> and <b>pe2</b>, 
+ the construct <b>wasInformedBy(pe2,pe1)</b>
+holds, <span class='conditional'>if and only if</span>
+ there is an entity denoted by <b>e</b> and roles <b>r1</b> and <b>r2</b>,
+such that <b>wasGeneratedBy(e,pe1,r1)</b> and <b>used(pe2,e,r2)</b> hold.
+</div>
+
+
+
+<p>
+An instance of an <b>wasScheduledAfter</b> construct, written as 
+<b>wasScheduledAfter(pe2,pe1)</b> in the Provenance Abstract Syntax Notation: 
 <ul>
-<li> refers to a process execution;
-<li> refers to a process execution.
+<li> refers to a process execution <b>pe2</b>;
+<li> refers to a process execution <b>pe1</b>,
 </ul>
+and expresses control ordering between <b>pe2</b> and <b>pe1</b>.
+The meaning of the <b>wasScheduledAfter</b> construct is as follows.
+
+<div class='constraint' id='wasScheduledAfter'>Given two process executions denoted by <b>pe1</b> and <b>pe2</b>, 
+ the construct <b>wasScheduledAfter(pe2,pe1)</b>
+holds, <span class='conditional'>if and only if</span>
+ there are two entities denoted by <b>e1</b> and <b>e2</b> and roles <b>r1</b> and <b>r2</b>,
+such that <b>wasControlledBy(pe1,e1,r1)</b> and <b>wasControlledBy(pe2,e2,r2)</b> and <b>wasDerivedFrom(e2,e1)</b>.
+</div>
+
+
 
 <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>
 </p>