--- a/model/ProvenanceModel.html	Mon Nov 21 16:09:42 2011 +0000
+++ b/model/ProvenanceModel.html	Mon Nov 21 16:46:28 2011 +0000
@@ -2481,7 +2481,7 @@
 </ul>
 and states information flow ordering between the activities represented by these records, specified as follows.
 
-<div class='constraint' id='wasInformedBy'>Given two activity records identified by <span class="name">a1</span> and <span class="name">a2</span>, 
+<div class='constraint' id='wasInformedBy Definition'>Given two activity records identified by <span class="name">a1</span> and <span class="name">a2</span>, 
  the record <span class="name">wasInformedBy(a2,a1)</span>
 holds, <span class='conditional'>if and only if</span>
  there is an entity record identified by <span class="name">e</span> and sets of attribute-value pairs <span class="name">attrs1</span> and <span class="name">attrs2</span>,
@@ -2504,8 +2504,13 @@
 <p>The end in activity record identified by <span class="name">a3</span> precedes the start in activity record identified by <span class="name">a1</span>, while interval for activity record <span class="name">a2</span> overlaps with each interval for <span class="name">a1</span> and <span class="name">a3</span>, allowing information to flow (<span class="name">e1</span> and <span class="name">e2</span>, respectively).</p>
 
 
+
+
 <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 precedes use of a given entity. Note that this constraint is currently not written in the document.
+
 </div>