--- a/model/ProvenanceModel.html	Mon Jan 23 15:03:06 2012 +0000
+++ b/model/ProvenanceModel.html	Wed Jan 25 17:48:44 2012 +0100
@@ -3546,7 +3546,7 @@
 
 This representation of a collection's evolution makes no assumption regarding the underlying data structure used to store and manage collections. In particular, no assumptions are needed regarding the mutability of a data structure that is subject to updates.   In fact, the state of a collection (i.e., the set of key-value pairs it contains) at a given point in a sequence of operations is never stated explicitly. Rather, it can be obtained by querying the chain of derivation assertions involving insertions and removals. Entity type <span class="name">prov:type="emptyCollection"</span> can be used in this context as it marks the start of a sequence of collection operations.
 
-<p>A number of observations follow from this.
+<p>Observations:
 
 <ul>
 
@@ -3582,7 +3582,14 @@
 <span class="name">CollectionAfterInsertion(c, c1, k1, v1)</span><br/>
 <span class="name">CollectionAfterInsertion(c, c2, k2, v2)</span><br/>
 
-one can infer: <span class="name">c1==c2, k1==k2, v1==v</span>.<p/>
+one can infer: <span class="name">c1==c2, k1==k2, v1==v2</span>, because one cannot have two different derivations for the same final collection state.<p/>
+
+<li>The following set of insertions:<br/>
+
+<span class="name">CollectionAfterInsertion(c1, c, k, v1)</span><br/>
+<span class="name">CollectionAfterInsertion(c1, c, k, v2)</span><br/>
+
+entails  <span class="name">v1==v2</span>.<p/>
 
 
 <li> The state of a collection is only known to the extent that a chain of derivations starting from an empty collection can be found. It is understood that a set of assertions regarding a collection's evolution may be incomplete, and therefore so is the reconstructed state obtained by querying those assertions. In general, all assertions reflect the asserter's partial knowledge of a sequence of data transformation events. In the particular case of collection evolution, in which the asserter  <em>knows</em> that some of the state changes may have been missed, then the more generic <span class="name">wasDerivedFrom</span> relation should be used to signal that some updates may have occurred, which cannot be precisely asserted as insertions or removals. The following two examples illustrate this.