--- a/model/prov-constraints.html	Thu Jul 19 09:52:44 2012 +0100
+++ b/model/prov-constraints.html	Thu Jul 19 10:12:29 2012 +0100
@@ -449,7 +449,7 @@
 relating the activities, entities and agents involved.
 </p>
 
-<p><a href="#equivalence">Section 6</a> defines the notions of 
+<p><a href="#equivalence">Section 6</a> defines the notions
 of <a>validity</a>, <a>equivalence</a> and <a>normalization</a>.
 </p>
 
@@ -512,8 +512,8 @@
 specialization and alternate can be used to link such entities.</p>
 
 <p>Besides entities, a variety of other PROV objects have
-attributes, including activity, generation, usage, start, end,
-communication, attribution, association, responsibility, and
+attributes, including activity, generation, usage, invalidation, start, end,
+communication, attribution, association, delegation, and
 derivation. Each object has an associated duration interval (which may
 be a single time point), and attribute-value pairs for a given object
 are expected to be descriptions that hold for the object's duration.
@@ -549,13 +549,13 @@
 
 <p>An <a>activity</a> is delimited by its <a title="activity start event">start</a> and its <a title="activity end event">end</a> events; hence, it occurs over
 an interval delimited by two <a title="instantaneous event">instantaneous
-events</a>. However, an activity record need not mention start or end time information, because they may not be known.
+events</a>. However, an activity statement need not mention start or end time information, because they may not be known.
 An activity's attribute-value pairs are expected to describe the activity's situation during its interval, i.e. an interval between two instantaneous events, namely its <a title="activity start event">start</a> event and its <a title="activity end event">end</a> event.
 </p>
 
 
 
-<p>An activity is not necessarily an entity.  Indeed, an entity exists in full at
+<p>An activity is not an entity.  Indeed, an entity exists in full at
 any point in its lifetime, persists during this interval, and
 preserves the characteristics that makes it identifiable.  In
 contrast, an activity is something that occurs, happens, unfolds, or
@@ -572,7 +572,7 @@
 <p> Although time is important for provenance, provenance can be used
 in many different contexts within individual systems and across the
 Web. Different systems may use different clocks which may not be
-precisely synchronized, so when provenance records are combined by
+precisely synchronized, so when provenance statements are combined by
 different systems, we may not be able to align the times involved to a
 single global timeline.  Hence, PROV is designed to minimize
 assumptions about time.  Instead, PROV talks about (identified)
@@ -582,7 +582,7 @@
   id="dfn-event">instantaneous event</dfn>s (or just <a
   title="instantaneous event">event</a>s), that mark
 transitions in the world.  Events include generation, usage, or
-invalidation of entities, as well as starting or ending of activities.  This
+invalidation of entities, as well as start or end of activities.  This
 notion of event is not first-class in the data model, but it is useful
 for explaining its other concepts and its semantics [[PROV-SEM]].
 Thus, events help justify  <i>inferences</i> on provenance as well as
@@ -1102,9 +1102,9 @@
 
 <div class="remark">
   <p>The converse inference does not hold.  Informally, from <span
-class="name">wasDerivedFrom(e2,e1)</span> and <span
-class="name">used(a,e1,-)</span>, one cannot derive <span
-class="name">wasGeneratedBy(e2,a,-)</span> because identifier <span
+class="name">wasDerivedFrom(id;e2,e1,-,-,-,attrs)</span> and <span
+class="name">used(use;a,e1,_t1,attrs1)</span>, one cannot derive <span
+class="name">wasGeneratedBy(gen;e2,a,_t2,attrs2)</span> because entity <span
 class="name">e1</span> may be used by many activities, whereas at most
 one activity could generate the entity <span class="name">e2</span>.
 Even if <span class="name">e2</span> is used by some activity that
@@ -1264,6 +1264,10 @@
   <li>
     <span class="conditional">IF</span> <span class="name">wasDerivedFrom(id; e2, e1, a, g2, u1, attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; e2, e1, attrs)</span>.
   </li>
+
+  <li>
+    <span class="conditional">IF</span> <span class="name">wasDerivedFrom(id; e2, e1, -, -, -, attrs)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; e2, e1, attrs)</span>.
+  </li>
   <li>
     <span class="conditional">IF</span> <span class="name">wasAttributedTo(id;e,ag,attr)</span> <span class="conditional">THEN</span> <span class="name">wasInfluencedBy(id; e, ag, attrs)</span>.
   </li>