--- a/model/ProvenanceModel.html Fri Dec 09 09:24:48 2011 +0000
+++ b/model/ProvenanceModel.html Wed Dec 14 00:09:57 2011 +0000
@@ -1883,15 +1883,72 @@
<section id="record-complement-of">
-<h4>Complementarity Record</h4>
-
-<div class="note">While the working group recognizes the importance of the complementarity record concept, its name and its exact semantics are still being discussed.
+<h4>View Record</h4>
+
+<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.<br/>
+
+Two versions of this relation are considered.
+<ul>
+
+ <li>The <span class="name">strictViewOf(e2,e1)</span> relation captures the intuition that <span class="name">e2</span> and <span class="name">e1</span> denote the same entity, but <span class="name">e2</span> provides a <em>more specific</em> characterization of the entity than <span class="name">e1</span> does. One example is an entity record <span class="name">e1</span> describing "Bob as a person", and another entity record <span class="name">e2</span> describing "Bob, the holder of twitter account XYZ". Following this interpretation, relation <span class="name">strictViewOf()</span> is both <strong>transitive</strong> and <strong>anti-symmetric</strong>:
+
+ <ul>
+ <li>if <span class="name">strictViewOf(e3,e2)</span> and <span class="name">strictViewOf(e2,e1)</span> hold then it follows that <span class="name">strictViewOf(e3,e1)</span> holds.
+
+ <li>if <span class="name">strictViewOf(e2,e1)</span> then it follows that <span class="name">strictViewOf(e1,e2)</span> does not hold.
+ </ul>
+
+ <li>The <span class="name">ViewOf(e2,e1)</span> relation captures the intuition that <span class="name">e2</span> and <span class="name">e1</span> provide a different characterization of the same entity, but there is no indication that one is more specific than the other. 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". Following this interpretation, relation <span class="name">strictViewOf()</span> is <strong>transitive</strong> and <strong>symmetric</strong>:
+
+ <ul>
+ <li>if <span class="name">ViewOf(e3,e2)</span> and <span class="name">ViewOf(e2,e1)</span> hold then it follows that <span class="name">ViewOf(e3,e1)</span> holds.
+
+ <li>if <span class="name">ViewOf(e2,e1)</span> then it follows that <span class="name">ViewOf(e1,e2)</span> also holds.
+ </ul>
+
+</ul>
+
+The definition of entity record includes a specification of the characterization interval within which the record is valid. In both versions, the two relations <span class="name">e2</span> are only valid within the intersection of the characterization intervals of the two participating entity records. <p/>
+
+
+<p>A strict view record is written <span class="name">strictView(e2,e1)</span>, where <span class="name">e1</span> and <span class="name">e2</span> are two identifiers denoting entity records.</p>
+
+<p>A view record is written <span class="name">View(e2,e1)</span>, where <span class="name">e1</span> and <span class="name">e2</span> are two identifiers denoting entity records.</p>
+
+
+<div class="anexample">
+
+ <div class="note">RS example to be replaced once we reach consensus on the definition</div>
</div>
+
+<p>In PROV-ASN, a view (resp. strictView) record's text matches the <span class="nonterminal">viewRecord</span> (resp. <span class="nonterminal">strictViewRecord</span>) production of the grammar defined in this specification document.</p>
+
+<div class='grammar'>
+<span class="nonterminal">viewRecord</span> ::=
+<span class="name">viewOf</span>
+<span class="name">(</span>
+<span class="nonterminal">eIdentifier</span>
+<span class="name">,</span>
+<span class="nonterminal">eIdentifier</span>
+<span class="nonterminal">optional-attribute-values</span>
+<span class="name">)</span> <br/>
+|
+<span class="name">strictViewOf</span>
+<span class="name">(</span>
+<span class="nonterminal">eIdentifier</span>
+<span class="name">,</span>
+<span class="nonterminal">eIdentifier</span>
+<span class="nonterminal">optional-attribute-values</span>
+<span class="name">)</span> <br/>
+</div>
+
+
+<!--
+
<p>A <dfn id="complementOf">complementarity record</dfn> is a relationship between two entities stated to have compatible characterization over some continuous interval between two events.</p>
-<!-- PAOLO, which event do you refer to? <a>event</a>?? -->
<p>
@@ -1913,13 +1970,7 @@
<p>It is important to note that the relation holds only for the characterization intervals of the entity expessions involved As soon as one attribute changes value in one of them, new correspondences need to be found amongst the new entities. Thus, the relation has a validity span that can be expressed in terms of the event lines of the entity.</p>
-<!--
-The "IVP of" relationship is designed to represent pairs of entities that correspond to each other. By their own nature, an entity remains valid only as long as all of its attributes do not change their value. It follows that the correspondence "B IVP of A" is only valid within the time interval during which such invariance attribute holds for both A and B. When any of the attribute values change in either A or B, those entities are replaced by new ones, and a new correspondence may be established. Thus, "IVP of" is defined relative to the intersection of the temporal intervals for which A and B are valid.
--->
-
-
-
-<p>A complementarity record is written <span class="name">wasComplementOf(e2,e1)</span>, where <span class="name">e1</span> and <span class="name">e2</span> are two identifiers denoting entity records.</p>
+
<div class="anexample">
@@ -1961,31 +2012,6 @@
<span class="name">wasComplementOf(e3,e2)</span> and <span class="name">wasComplementOf(e2,e1)</span> hold. The record <span class="name">wasComplementOf(e3,e1)</span> may not hold because the characterization intervals of the denoted entity records may not overlap.</p>
-<p>In PROV-ASN, a complementarity record's text matches the <span class="nonterminal">complementarityRecord</span> production of the grammar defined in this specification document.</p>
-
-<div class='grammar'>
-<span class="nonterminal">complementarityRecord</span> ::=
-<span class="name">wasComplementOf</span>
-<span class="name">(</span>
-<span class="nonterminal">eIdentifier</span>
-<span class="name">,</span>
-<span class="nonterminal">eIdentifier</span>
-<span class="nonterminal">optional-attribute-values</span>
-<span class="name">)</span> <br/>
-|
-<span class="name">wasComplementOf</span>
-<span class="name">(</span>
-<span class="nonterminal">eIdentifier</span>
-<span class="name">,</span>
-<span class="nonterminal">accIdentifier</span>
-<span class="name">,</span>
-<span class="nonterminal">eIdentifier</span>
-<span class="name">,</span>
-<span class="nonterminal">accIdentifier</span>
-<span class="nonterminal">optional-attribute-values</span>
-<span class="name">)</span>
-</div>
-
<p>
An entity record identifier can optionally be accompanied by an account identifier. When this is the case, it becomes possible to link two entity record identifiers that are appear in different accounts. (In particular, the entity record identifiers in two different account are allowed to be the same.). When account identifiers are not available, then the linking of entity records through complementarity can only take place within the scope of a single account.
@@ -2023,7 +2049,7 @@
Furthermore, there is a suggestion that an alternative relation that is transitive may also be useful.
This is raised in the following <a href="http://lists.w3.org/Archives/Public/public-prov-wg/2011Sep/0315.html">email</a>.</div>
-
+-->
<div class='issue'>A discussion on alternative definition of wasComplementOf has not reached a satisfactory conclusion yet. This is <a href="http://www.w3.org/2011/prov/track/issues/29">ISSUE-29</a></div>