--- a/model/ProvenanceModel.html	Mon Nov 21 15:01:42 2011 -0500
+++ b/model/ProvenanceModel.html	Mon Nov 21 22:03:36 2011 +0000
@@ -1470,7 +1470,7 @@
 <li><em>usedEntity</em>: the identifier <span class="name">e1</span> of  an entity record, which is a representation of the used entity.</li>
 </ul>
 
-<p>None of the three kinds of derivation is defined to be transitive. Domain-specific specializations of these derivatiosn may be defined in such a way that the transitivity property holds.</p>
+<p>None of the three kinds of derivation is defined to be transitive. Domain-specific specializations of these derivations may be defined in such a way that the transitivity property holds.</p>
 
 <div class="note">
 Give counter-example of transitivity? maybe?
@@ -2491,6 +2491,14 @@
 such that <span class="name">wasGeneratedBy(e,a1,attrs1)</span> and <span class="name">used(a2,e,attrs2)</span> hold.
 </div>
 
+<div class='interpretation' id='wasInformedBy-ordering'>
+Given two activity records denoted by <span class="name">a1</span> and <span class="name">a2</span>, <span class='conditional'>if</span> the record <span class="name">wasInformedBy(a2,a1)</span>
+ holds, <span class='conditional'>then</span> the
+start event of the activity record denoted by <span class="name">a1</span> <a>precedes</a> the end event of
+the activity record denoted by <span class="name">a2</span>.
+</div>
+
+
 <p>The relationship <span class="name">wasInformedBy</span> is not transitive. Indeed, consider the records <span class="name">wasInformedBy(a2,a1)</span> and <span class="name">wasInformedBy(a3,a2)</span>, the record
 <span class="name">wasInformedBy(a3,a1)</span>, may not necessarily hold, as illustrated by the following event line. 
 <pre>
@@ -2508,15 +2516,6 @@
 
 
 
-
-<div class="issue">
-Temporal constraints to be make explicit. This is  <a href="http://www.w3.org/2011/prov/track/issues/156">ISSUE-156</a>.
-
-The temporal constraint follows immediately from the fact that generation always <a>precedes</a> use of a given entity. See usage-generatio-ordering.
-
-</div>
-
-
 <div class="note">
 The relation wasScheduledAfter is to be simplified using wasStartedBy/wasEndedBy.
 </div>
@@ -2906,6 +2905,7 @@
 <section class="appendix"> 
       <h2>Changes Since Previous Version</h2> 
 <ul>
+<li>11/21/11: Added wasInformedBy-ordering.</li>
 <li>11/17/11: Added Traceability  Record.</li>
 <li>11/17/11: Rewrote the whole section on Derivation Record.</li>
 <li>11/17/11: Updated wasDerivedFrom to refer to generation/usage record ids.</li>