--- a/model/ProvenanceModel.html	Thu Dec 15 15:20:38 2011 +0000
+++ b/model/ProvenanceModel.html	Thu Dec 15 17:54:23 2011 +0000
@@ -1966,12 +1966,60 @@
 
 <div class="note">This section is currently under revision and in flux</div>
 
-<p>A <dfn id="view">view record</dfn> is used to establish a relationship between two entity records, which asserts that the two records provide a different characterization of the same entity.  One example is an entity record <span class="name">e1</span> describing "Bob, the holder of facebook account ABC", and another entity record <span class="name">e2</span> describing "Bob, the holder of twitter account XYZ". 
-
-In this case it may be desirable to assert that these two entity records indeed provide  a different characterization of the same entity. Relation
-<span class="name">ViewOf(e2,e1)</span>, where  <span class="name">e1</span>,  <span class="name">e2</span> are the two entity records involved,  is introduced to convey this meaning. </br>
-
-As we know from [entity record], each of the two entity records involved in the relation is valid within a certain events interval. The relation <span class="name">ViewOf(e2,e1)</span> itself is only meaningful if those two intervals overlap, and then only for the extent of such overlap. If the entity records are valid in disjoint intervals, the <span class="name">ViewOf</span> assertion is meaningless by definition.<br/>
+<p>A <dfn id="view">view record</dfn> is used to establish a relationship between two entity records, which asserts that the two records provide a different characterization of the same entity.  Consider for example three entity records:
+<ul>
+
+  <li><span class="name">e1</span> describing "Bob, the holder of facebook account ABC",
+  
+  <li><span class="name">e2</span> describing "Bob, the holder of twitter account XYZ",
+
+  <li><span class="name">e3</span> describing "Bob, the person".
+</ul>
+
+One may make several assertions to establish that these entity records refer to the same entity "Bob", either in different contexts, or at different levels of abstraction. For example:
+
+<ol>
+  <li> <span class="name">e1</span> provides a more concrete characterization of Bob than <span class="name">e2</span> does
+
+  <li>  <span class="name">e1</span> and  <span class="name">e2</span> provide two different characterizations of the same entity.
+</ol>
+
+Two relations are introduced to express these assertions:
+
+<ul>
+
+  <li> B is a view of A, written <span class="name">ViewOf(B,A)</span> captures the intent of assertion (1);
+  <li> B is a [foobar] of A, written <span class="name">foobar(B,A)</span> captures the intent of assertion (2).
+  
+  </ul>
+
+In order to further convey the intended meaning, the following properties are associated to these two relations.
+
+  <ul>
+    <li><span class="name">ViewOf(B,A)</span> is <strong>transitive</strong>:    <span class="name">ViewOf(C,B)</span> and  <span class="name">ViewOf(B,A)</span> implies  <span class="name">ViewOf(C,A)</span>.
+
+    <li><span class="name">ViewOf(B,A)</span> is <strong>anti-symmetric</strong>:   <span class="name">ViewOf(B,A)</span> implies that  <span class="name">ViewOf(A,B)</span>  does not hold.
+  </ul>
+
+  
+  <ul>
+    <li><span class="name">foobar(B,A)</span> is <strong>transitive</strong>:    <span class="name">foobar(C,B)</span> and  <span class="name">foobar(B,A)</span> implies  <span class="name">foobar(C,A)</span>.
+
+    <li><span class="name">foobar(B,A)</span> is <strong>symmetric</strong>:   <span class="name">foobar(B,A)</span> implies  <span class="name">foobar(A,B)</span>.
+  </ul>
+
+<h5>Case of entities with known limited validity</h5>
+
+As we know from [entity record], entity records may only be valid within certain events interval. Let  <span class="name">val(e)</span> denote the validity interval of  <span class="name">e</span>.
+
+  When these intervals are known, relations <span class="name">ViewOf(e2,e1)</span> and <span class="name">foobar(e2,e1)</span> can only be asserted if
+<span class="name">val(e1)</span> is a sub-interval of  <span class="name">val(e2)</span>. This condition ensures transitivity.
+
+  
+<!--     
+
+
+  The relation <span class="name">ViewOf(e2,e1)</span> itself is only meaningful if those two intervals overlap, and then only for the extent of such overlap. If the entity records are valid in disjoint intervals, the <span class="name">ViewOf</span> assertion is meaningless by definition.<br/>
 Note that, as a particular case, the validity interval of <span class="name">e1</span> may be <em>contained</em> within the validity interval of <span class="name">e1</span>.<p/>
 
 With these assumptions, the  <span class="name">ViewOf</span> relation enjoys two properties:
@@ -2037,6 +2085,7 @@
 <span class="name">)</span>
 </div>
 
+-->
 
 <!--