--- a/model/ProvenanceModel.html Wed Jan 18 09:41:24 2012 +0000
+++ b/model/ProvenanceModel.html Wed Jan 18 09:42:06 2012 +0000
@@ -2029,7 +2029,7 @@
<div class="note">This section is currently under revision and in flux</div>
-The purpose of the record types defined in this section is to establish a relationship between two entitues, which asserts that they provide a different characterization of the same thing. Consider for example three entities:
+The purpose of the record types defined in this section is to establish a relationship between two entities, which asserts that they provide a different characterization of the same thing. Consider for example three entities:
<ul>
<li><span class="name">e1</span> denoting "Bob, the holder of facebook account ABC",
@@ -2044,59 +2044,53 @@
<ol>
<li> Entity denoted by <span class="name">e1</span> provides a <em>more concrete</em> characterization of Bob than <span class="name">e3</span> does;
<li> Entity denoted by <span class="name">e2</span> provides a <em>more concrete</em> characterization of Bob than <span class="name">e3</span> does;
- <li> The entities denoted by <span class="name">e1</span> and <span class="name">e2</span> provide two different characterizations of the same thing.
+ <li> The entities denoted by <span class="name">e1</span> and <span class="name">e2</span> provide two different characterizations of the same thing, i.e., Bob.
</ol>
Two relations are introduced to express these assertions:
<ul>
- <li> B is a <em>specialization</em> of A, written <span class="name">specializationOf(B,A)</span> captures the intent of assertion (1) and (2);
- <li> B is an <em>alternative characterization</em> of A, written <span class="name">alternateOf(B,A)</span> captures the intent of assertion (3).
+ <li> e2 is a <em>specialization</em> of e1, written <span class="name">specializationOf(e2,e1)</span> captures the intent of assertion (1) and (2);
+ <li> e2 is an <em>alternative characterization</em> of e1, written <span class="name">alternateOf(e2,e1)</span> captures the intent of assertion (3).
</ul>
In order to further convey the intended meaning, the following properties are associated to these two relations.
<ul>
- <li><span class="name">specializationOf(B,A)</span> is <strong>transitive</strong>: <span class="name">specializationOf(C,B)</span> and <span class="name">specializationOf(B,A)</span> implies <span class="name">specializationOf(C,A)</span>.
-
- <li><span class="name">specializationOf(B,A)</span> is <strong>anti-symmetric</strong>: <span class="name">specializationOf(B,A)</span> implies that <span class="name">specializationOf(A,B)</span> does not hold.
- <li><span class="name">alternateOf(B,A)</span> is <strong>symmetric</strong>: <span class="name">alternateOf(B,A)</span> implies <span class="name">alternateOf(A,B)</span>.
+ <li><span class="name">specializationOf(e2,e1)</span> is <strong>transitive</strong>: <span class="name">specializationOf(e3,e2)</span> and <span class="name">specializationOf(e2,e1)</span> implies <span class="name">specializationOf(e3,e1)</span>.
+
+ <li><span class="name">specializationOf(e2,e1)</span> is <strong>anti-symmetric</strong>: <span class="name">specializationOf(e2,e1)</span> implies that <span class="name">specializationOf(e1,e2)</span> does not hold.
+ <li><span class="name">alternateOf(e2,e1)</span> is <strong>symmetric</strong>: <span class="name">alternateOf(e2,e1)</span> implies <span class="name">alternateOf(e1,e2)</span>.
</ul>
-<div class="note">
-Paolo, TODO: similarly to other records, one needs to provide a standalone definition for these records, and also enumerate their components.
-</div>
-
-<p>A <dfn id="dfn-Alternate">alternate record</dfn> ...</p>
-
-<p>A <dfn id="dfn-Specialization">specialization record</dfn> ...</p>
-
-<!--
- <h5>Case of entities with known limited validity</h5>
-
-As we know from [entity record], entity records may only be valid within certain event's interval. Let <span class="name">char(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
-the validity interval of <span class="name">e1</span> is a sub-interval of that of <span class="name">e2</span>. This condition ensures transitivity.
-
- -->
+<p>A <dfn id="dfn-Alternate">alternate record</dfn>, written alternateOf(alt1, alt2, attrs) in PROV-ASN, has the following constituents:</p>
+
+<ul>
+<li><em>first alternate</em>: an identifier <span class="name">alt1</span> of the first of the two entities</li>
+<li><em>second alternate</em>: an identifier <span class="name">alt2</span> of the second of the two entities</li>
+<li><em>attrs</em>: an OPTIONAL set <span class="name">attrs</span> of attribute-value pairs to further describe this record.</li>
+</ul>
+
+
+<p>A <dfn id="dfn-Specialization">specialization record</dfn> written specializationOf(sub, super, attrs) in PROV-ASN, has the following constituents:</p>
+
+<ul>
+<li><em>specialised entity</em>: an identifier <span class="name">sub</span> of the specialised entity</li>
+<li><em>general entity</em>: an identifier <span class="name">super</span> of the entity that is being specialised</li>
+<li><em>attrs</em>: an OPTIONAL set <span class="name">attrs</span> of attribute-value pairs to further describe this record.</li>
+</ul>
+</p>
+
+
<p>
An entity record identifier can optionally be accompanied by an account identifier. When this is the case, it becomes possible to use the <span class="name">alternateOf</span> relation to link two entity record identifiers that are appear in different accounts. (In particular, the entity identifiers in two different account are allowed to be the same.). When account identifiers are not available, then the linking of entity records through <span class="name">alternateOf</span> can only take place within the scope of a single account.
</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, an alternate record's text matches the <span class="nonterminal">alternateRecord</span>production of the grammar defined in this specification document.</p>
+
+<p>In PROV-ASN, an alternate record's text matches the <span class="nonterminal">alternateRecord</span> production of the grammar defined in this specification document.</p>
<div class='grammar'>
<span class="nonterminal">alternateRecord</span> ::=
@@ -2160,6 +2154,11 @@
+<<<<<<< local
+<!--
+<section>
+<h4>Transitive Derivation Record</h4>
+=======
<!--
<div style="text-align: center;">
@@ -2207,20 +2206,49 @@
<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>
+>>>>>>> other
<p>
+<<<<<<< local
+If <span class="name">wasDerivedFrom(e2,e1)</span> holds because attribute <span class="name">a2.1</span> of <span class="name">e2</span> is determined by attribute <span class="name">a1.1</span> of <span class="name">e1</span>,
+and if <span class="name">wasDerivedFrom(e3,e2)</span> holds because attribute <span class="name">a3.1</span>of <span class="name">e3</span> is determined by attribute <span class="name">a2.2</span> of <span class="name">e1</span>, it is not necessarily the case that an attribute of <span class="name">e3</span> is determined by an attribute of <span class="name">e1</span>; so, an asserter may not be able to assert <span class="name">wasDerivedFrom(e3,e1)</span>, since it would fail to satisfy constraint <a href="#derivation-attributes">derivation-attributes</a>. Hence, the constraint on attributes as expressed in <a href="#derivation-attributes">derivation-attributes</a> invalidates transitivity in the general case.
+=======
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.
+>>>>>>> other
</p>
-
+<<<<<<< local
+<p>However, there is sense that <span class="name">e3</span> still depends on <span class="name">e1</span>, since <span class="name">e3</span> could not be generated without <span class="name">e1</span> existing. Hence, we introduce a weaker notion of derivation record, which is transitive.</p>
+=======
+>>>>>>> other
+
+<<<<<<< local
+A transitive derivation record, written <span class="name">dependedOn(e2, e1)</span> in PROV-ASN:
+<ul>
+<li> contains an identifier <span class="name">e2</span>, denoting an entity record, which represents the entity that is the result of the derivation;
+<li> contains an identifier <span class="name">e1</span>, denoting an entity record, which represents the entity that the derivation relies upon.
+</ul>
+<p>The record <span class="name">dependedOn</span> can only be inferred; in other words, it cannot be asserted. It is
+transitive by definition and relies on the previously defined derivation assertions for its
+base case.</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,
-
+>>>>>>> other
+
+<<<<<<< local
+<div class='constraint' id='transitive-derivation'>
+<ul>
+<li><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> or <span class="name">wasDerivedFrom(e2,e1,pe,attrs2,attrs1)</span> holds, <span class='conditional'>then</span> <span class="name">dependedOn(e2,e1)</span> holds.</li>
+<li><span class='conditional'>If</span> <span class="name">wasEventuallyDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> <span class="name">dependedOn(e2,e1)</span> holds.</li>
+<li><span class='conditional'>If</span> <span class="name">dependedOn(e3,e2)</span> and <span class="name">dependedOn(e2,e1)</span> hold, <span class='conditional'>then</span> <span class="name">dependedOn(e3,e1)</span> holds.</li>
+</ul>
+=======
...
entity(rs,[ex:created=1870])
...
@@ -2237,12 +2265,20 @@
)
</pre>
+>>>>>>> other
</div>
-
+<<<<<<< local
+</section>
+=======
+
+>>>>>>> other
-->
-
-
+<<<<<<< local
+=======
+
+
+>>>>>>> other