--- a/model/ProvenanceModel.html	Thu Jan 19 15:22:24 2012 +0000
+++ b/model/ProvenanceModel.html	Thu Jan 19 15:28:45 2012 +0000
@@ -3793,6 +3793,7 @@
 </div>
 
 
+
 <p>Further constraints appear in Figure <a href="#constraint-summary2">constraint-summary2</a> and are discussed below.</p>
 
 <div style="text-align: center;">
@@ -3816,6 +3817,22 @@
 </div>
 
 
+<p>An activity that was associated with an agent must have some overlap with the agent. The agent may be generated, or may only become associated with the activity, after its start: so, the agent is required to exist before the activity end. Likewise, the agent may be destructed, or may terminate its association with the activity, before the activity end: hence, the agent destruction is required to happen after the activity start.
+This is
+illustrated by Subfigure <a href="#constraint-summary2">constraint-summary2</a> (b) and  expressed by constraint <a href="#wasAssociatedWith-ordering">wasAssociatedWith-ordering</a>.</p>
+</p>
+
+<div class='interpretation' id='wasAssociatedWith-ordering'>
+Given an activity denoted by <span class="name">a</span> and an agent denoted by   <span class="name">ag</span>, <span class='conditional'>if</span> the record <span
+class="name">wasAssociatedWith(a,ag)</span>
+ holds, <span class='conditional'>then</span> the following ordering constraints hold: the
+<a title="activity start event">start</a> event of the activity  denoted by <span class="name">a</span>
+precedes the destruction event of 
+the agent denoted by <span class="name">ag</span>, and 
+ the <a title="entity generation event">generation event</a> for agent denoted by <span class="name">ag</span>
+<a>precedes</a> the activity <a title="activity end event">end</a> event.
+</div>
+
 
 <div class="issue">
 For completeness, we should define ordering constraint for wasAssociatedWith and actedOnBehalfOf.