--- a/model/ProvenanceModel.html Mon Dec 05 12:10:13 2011 +0000
+++ b/model/ProvenanceModel.html Mon Dec 05 12:50:53 2011 +0000
@@ -1913,22 +1913,11 @@
-<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">identifier</span>
-<span class="name">,</span>
-<span class="nonterminal">identifier</span>
-<span class="name">)</span>
-</div>
+<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">
-<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>
-
+<p>The following example illustrates the entity "Royal Society"and its perspectives at various points in time.</p>
<pre class="codeexample">
entity(rs,[ex:created=1870])
@@ -1953,6 +1942,7 @@
</div>
+
<div class='constraint' id='wasComplementOf-necessary-cond'>
An assertion "wasComplementOf(B,A)" holds over the temporal intersection of A and B, <span class='conditional'>only if</span>:
<ol>
@@ -1961,13 +1951,72 @@
</li></ol>
</div>
-<p>The complementariy relation is not transitive. Let us consider identifiers <span class="name">e1</span>, <span class="name">e2</span>, and <span class="name">e3</span> identifying three entity records such that
+<p>The complementarity relation is not transitive. Let us consider identifiers <span class="name">e1</span>, <span class="name">e2</span>, and <span class="name">e3</span> identifying three entity records such that
<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>
-<div class='note'>We will allow wasComplementOf to be asserted between entities identified by qualified identifiers. This will allow us to express wasComplementOf between entities asserted in separate accounts (potentially, with the same identifiers).
+<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="optional"><span class="name">,</span>
+<span class="nonterminal">attribute-values</span>
+</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="optional"><span class="name">,</span>
+<span class="nonterminal">attribute-values</span>
+</span>
+<span class="name">)</span>
</div>
+
+<p>In order to allow for complementarity records linking entity records occurring in different accounts, each entity record identifier can be accompanied by an account identifier. In particular, this variant of the complementarity record allows for the linking of entity records identifier that are the same, but asserted in different accounts.
+</p>
+
+</p>
+
+<div class="anexample">
+<p>In the following example, the same description of the Royal Society is structured according to two different accounts. In the second account, we find a complementarity record linking <span class="name">rs_m1</span> in account <span class="name">ex:acc2</span> to
+<span class="name">rs</span> in account <span class="name">ex:acc1</span>.
+<pre class="codeexample">
+account(ex:acc1,
+ http://example.org/asserter1,
+
+ ...
+ entity(rs,[ex:created=1870])
+ ...
+ )
+
+
+account(ex:acc2,
+ http://example.org/asserter2,
+
+ ...
+ entity(rs_m1,[ex:membership=250, ex:year=1900])
+ ...
+ wasComplementOf(rs_m1, ex:acc2, rs, ex:acc1)
+
+)
+</pre>
+</div>
+
+
+
<div class='note'>It is suggested that the name 'wasComplementOf' does not capture the meaning of this relation adequately. No concrete suggestion has been made so far.
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>
@@ -2358,10 +2407,6 @@
</div>
-<div class='note'>We are going to introduce a notion of "qualified identifier", which allows us to refer to a provenance record in the scope of a given account. Given that accounts may be nested, a qualified identifier will be prefixed by a sequence of account identifiers, and then followed by an identifier, local to the innermost account.
-</div>
-
-
</section>
<section id="record-literal">