--- a/model/ProvenanceModel.html Tue Nov 29 16:00:46 2011 +0000
+++ b/model/ProvenanceModel.html Tue Nov 29 20:28:22 2011 +0000
@@ -541,7 +541,7 @@
</li>
<li>
-<span class="name">abc</span>: matches a literal string inside the single quotes.
+<span class="name">abc</span>: matches the literal string inside the single quotes.
</li>
@@ -1616,6 +1616,10 @@
<p>In PROV-DM, a <dfn id="dfn-Derivation">derivation record</dfn> is a representation that some entity is transformed from, created from, or affected by another entity in the world. </p>
+
+<p>Examples of derivation include the transformation of a canvas into a painting, the transportation of a person from London to New-York, the transformation of a relational table into a linked data set, and the melting of ice into water.</p>
+
+
<p>According to <a href="#conceptualization">Section Conceptualization</a>, for an entity to be transformed from, created from, or affected by another in some way, there must be some underpinning activities performing the necessary actions resulting in such a derivation.
However, asserters may not assert or have knowledge of these activities and associated details: they may not assert or know their number, they may not assert or know their identity, they may not assert or know the attributes characterizing how the relevant entities are used or generated. To accommodate the varying circumstances of the various asserters, PROV-DM allows more or less precise records of derivation to be asserted. Hence, PROV-DM uses the terms <em>precise</em> and <em>imprecise</em> to characterize the different kinds of derivation record. We note that the derivation itself is exact (i.e., deterministic, non-probabilistic), but it is its description, expressed in a derivation record, that may be imprecise. </p>
@@ -1638,8 +1642,8 @@
<table border="1" align="center">
<tr><td colspan=2 rowspan=2></td><td colspan=2>precision axis</td></tr>
<tr><td>precise</td><td>imprecise</td></tr>
-<tr><td rowspan=2>activity<br>axis</td><td>one activity</td><td>precise-1 derivation</td><td>imprecise-1 derivation</td></tr>
-<tr><td>n activities</td><td>---</td><td>imprecise-n derivation</td></tr>
+<tr><td rowspan=2>activity<br>axis</td><td>one activity</td><td><a>precise-1 derivation record</a></td><td><a>imprecise-1 derivation record</a></td></tr>
+<tr><td>n activities</td><td>---</td><td><a>imprecise-n derivation record</a></td></tr>
<caption>PROV-DM Derivation Type Summary</caption>
</table>
</div>
@@ -1650,12 +1654,12 @@
<li> The asserter does not know how many activities are involved in the derivation, and other details, whether known or unknown, are also not asserted. We call this an imprecise-n derivation record.</li>
</ul>
-<p> We note that the fourth theoretical case of a precise derivation, where the number of activities is not known cannot occur. </p>
+<p> We note that the fourth theoretical case of a precise derivation, where the number of activities is not known or asserted cannot occur. </p>
<p>The three kinds of derivation records are successively introduced. To minimize the number of relation types in PROV-DM, we introduce a PROV-DM reserved attribute <span class="name">steps</span>, which allows us to distinguish the various derivation types. </p>
-<p>A precise-1 derivation record, written <span class="name">wasDerivedFrom(id, e2, e1, a, g2, u1, attr)</span> in PROV-ASN, contains:</p>
+<p>A <dfn>precise-1 derivation record</dfn>, written <span class="name">wasDerivedFrom(id, e2, e1, a, g2, u1, attrs)</span> in PROV-ASN, contains:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier <span class="name">id</span> identifying the derivation record;</li>
<li><em>generatedEntity</em>: the identifier <span class="name">e2</span> of an entity record, which is a representation of the generated entity;</li>
@@ -1668,24 +1672,24 @@
<p>It is OPTIONAL to include the attribute <span class="name">prov:steps</span> in a precise-1 derivation since the record already refers to the one and only one activity underpinning the derivation.</p>
-<p>An imprecise-1 derivation record, written <span class="name">wasDerivedFrom(id, e2,e1, attrs)</span> in PROV-ASN, contains:</p>
+<p>An <dfn>imprecise-1 derivation record</dfn>, written <span class="name">wasDerivedFrom(id, e2,e1, attrs)</span> in PROV-ASN, contains:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier <span class="name">id</span> identifying the derivation record;</li>
<li><em>generatedEntity</em>: the identifier <span class="name">e2</span> of an entity record, which is a representation of the generated entity;</li>
<li><em>usedEntity</em>: the identifier <span class="name">e1</span> of an entity record, which is a representation of the used entity.</li>
<li><em>attributes</em>: a set of attribute-value pairs <span class="name">attrs</span> that describe the modalities of this derivation; it MUST include the attribute-value pair <span class="name">prov:steps="1"</span>.</li>
</ul>
-<p>It is MANDATORY to include the attribute <span class="name">prov:steps</span> in an imprecise-1 derivation since it is the mechanism used to distinguish it from an imprecise-n derivation record.</p>
-
-
-<p>An imprecise-n derivation record, written <span class="name">wasDerivedFrom(id, e2, e1, attrs)</span> in PROV-ASN, contains:</p>
+<p>An imprecise-1 derivation MUST include the attribute <span class="name">prov:steps</span>, since it is the only means to distinguish this record from an imprecise-n derivation record.</p>
+
+
+<p>An <dfn>imprecise-n derivation record</dfn>, written <span class="name">wasDerivedFrom(id, e2, e1, attrs)</span> in PROV-ASN, contains:</p>
<ul>
<li><em>id</em>: an OPTIONAL identifier <span class="name">id</span> identifying the derivation record;</li>
<li><em>generatedEntity</em>: the identifier <span class="name">e2</span> of an entity record, which is a representation of the generated entity;</li>
<li><em>usedEntity</em>: the identifier <span class="name">e1</span> of an entity record, which is a representation of the used entity.</li>
<li><em>attributes</em>: a set of attribute-value pairs <span class="name">attrs</span> that describe the modalities of this derivation; it optionally includes the attribute-value pair <span class="name">prov:steps="n"</span>.</li>
</ul>
-<p>It is OPTIONAL to include the attribute <span class="name">prov:steps</span>. It defaults to <span class="name">prov:steps="n"</span>.</p>
+<p>It is OPTIONAL to include the attribute <span class="name">prov:steps</span> in an imprecise-n derivation record. It defaults to <span class="name">prov:steps="n"</span>.</p>
<p>None of the three kinds of derivation is defined to be transitive. Domain-specific specializations of these derivations may be defined in such a way that the transitivity property holds.</p>
@@ -1699,41 +1703,43 @@
| <span class="nonterminal">imprecise-1-derivationRecord</span>
| <span class="nonterminal">imprecise-n-derivationRecord</span><br/>
<br/>
-<span class="nonterminal">precise-1-derivationRecord</span>:=
+<span class="nonterminal">precise-1-derivationRecord</span> :=
<span class="name">wasDerivedFrom</span>
<span class="name">(</span>
-<span class="nonterminal">identifier</span>
-<span class="name">,</span>
-<span class="nonterminal">identifier</span>
+<span class="optional"> <span class="nonterminal">identifier</span>,</span>
+<span class="nonterminal">eIdentifier</span>
<span class="name">,</span>
-<span class="nonterminal">identifier</span>
+<span class="nonterminal">eIdentifier</span>
<span class="name">,</span>
-<span class="nonterminal">generationIdentifier</span>
+<span class="nonterminal">aIdentifier</span>
<span class="name">,</span>
-<span class="nonterminal">usageIdentifier</span>,
+<span class="nonterminal">gIdentifier</span>
+<span class="name">,</span>
+<span class="nonterminal">uIdentifier</span>
+<span class="name">,</span>
<span class="nonterminal">attribute-values</span>
<span class="name">)</span><br/>
<span class="nonterminal">imprecise-1-derivationRecord</span>:=
<span class="name">wasDerivedFrom</span>
<span class="name">(</span>
-<span class="nonterminal">identifier</span>
+<span class="optional"> <span class="nonterminal">identifier</span>,</span>
+<span class="nonterminal">eIdentifier</span>
<span class="name">,</span>
-<span class="nonterminal">identifier</span>,
+<span class="nonterminal">eIdentifier</span>
+<span class="name">,</span>
<span class="nonterminal">attribute-values</span>
<span class="name">)</span>
<br/>
<span class="nonterminal">imprecise-n-derivationRecord</span>:=
<span class="name">wasDerivedFrom</span>
<span class="name">(</span>
-<span class="nonterminal">identifier</span>
+<span class="optional"> <span class="nonterminal">identifier</span>,</span>
+<span class="nonterminal">eIdentifier</span>
<span class="name">,</span>
-<span class="nonterminal">identifier</span>,
+<span class="nonterminal">eIdentifier</span>
+<span class="name">,</span>
<span class="nonterminal">attribute-values</span>
<span class="name">)</span>
-<br/>
-<br/>
-<span class="nonterminal">generationIdentifier</span>:= <span class="nonterminal">identifier</span><br/>
-<span class="nonterminal">usageIdentifier</span>:= <span class="nonterminal">identifier</span>
</div>
<div class="note">
The grammar should make it clear that attribute <span class="name">prov:steps="1"</span> is required for imprecise-1-derivationRecord.<br/>
@@ -1763,7 +1769,7 @@
</div>
-<p>An precise-1 derivation record is a richer than an imprecise-1 derivation record, itself, being more informative that an imprecise-n derivation record. Hence, the following implications hold.</p>
+<p>An precise-1 derivation record is richer than an imprecise-1 derivation record, itself, being more informative that an imprecise-n derivation record. Hence, the following implications hold.</p>
<div class='constraint' id='derivation-implications'>
Given two entity records denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the assertion <span class="name">wasDerivedFrom(e2, e1, a, g2, u1, attrs)</span>
holds for some generation record identified by <span class="name">g2</span>, and usage record identified by <span class="name">u1</span>, then <span class="name">wasDerivedFrom(e2,e1,[prov:steps="1"] ∪ attrs)</span> also holds.<br>
@@ -1782,6 +1788,7 @@
<div class='interpretation' id='derivation-usage-generation-ordering'>Given an activity record identified by <span class="name">a</span>, entity records identified by <span class="name">e1</span> and <span class="name">e2</span>, generation record identified by <span class="name">g2</span>, and usage record identified by <span class="name">u1</span>, <span class='conditional'>if</span> the record <span class="name">wasDerivedFrom(e2,e1,a,g2,u1,attrs)</span>
or <span class="name">wasDerivedFrom(e2,e1,[prov:steps="1"] ∪ attrs)</span> holds, <span class='conditional'>then</span>
+the following temporal constraint holds:
the <a title="entity usage event">usage</a>
of entity denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation</a> of
the entity denoted by <span class="name">e2</span>.
@@ -1791,16 +1798,16 @@
<div class='interpretation' id='derivation-generation-generation-ordering'>
Given two entity records denoted by <span class="name">e1</span> and <span class="name">e2</span>, <span class='conditional'>if</span> the record <span class="name">wasDerivedFrom(e2,e1,[prov:steps="n"] ∪ attrs)</span>
- holds, <span class='conditional'>then</span> the
-<a title="entity generation event">generation event</a> of the entity represented by the entity record denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation event</a> of
-the entity represented by the entity record denoted by <span class="name">e2</span>.
+ holds, <span class='conditional'>then</span> the following temporal constraint holds:
+the <a title="entity generation event">generation event</a> of the entity denoted by <span class="name">e1</span> <a>precedes</a> the <a title="entity generation event">generation event</a> of
+the entity denoted by <span class="name">e2</span>.
</div>
<p>Note that temporal ordering is between generations of <span class="name">e1</span>
and <span class="name">e2</span>, as opposed to precise-1 derivation,
which implies temporal ordering between the usage of <span class="name">e1</span> and
generation of <span class="name">e2</span>. Indeed, in the case of
-wasBasedOn, nothing is known about the usage of <span class="name">e1</span>,
+imprecise-n derivation, nothing is known about the usage of <span class="name">e1</span>,
since there is no associated activity.</p>
@@ -1839,7 +1846,7 @@
</p>
<div class="note">The following property holds for account where
-generation-unicity applies. Maybe move it to separate section with all
+generation-unicity applies. Move it to separate section with all
related material. </div>
<p>A further inference is permitted from the imprecise-1 derivation record: </p>
@@ -1853,7 +1860,7 @@
-<p>We note that the "symmetric" inference, does not hold.
+<p>We note that the converse inference, does not hold.
From <span class="name">wasDerivedFrom(e2,e1)</span> and <span class="name">used(pe,e1)</span>, one cannot
derive <span class="name">wasGeneratedBy(e2,pe,attrs2)</span> because identifier <span class="name">e1</span> may occur in usage records referring to
many activity records, but they may not be referred to in generation records containing identifier <span class="name">e2</span>.</p>
@@ -2340,6 +2347,8 @@
<span class="nonterminal">eIdentifier</span> := <span class="nonterminal">identifier</span> <em>(for an entity)</em><br/>
<span class="nonterminal">aIdentifier</span> := <span class="nonterminal">identifier</span> <em>(for an activity)</em><br/>
<span class="nonterminal">agIdentifier</span> := <span class="nonterminal">identifier</span> <em>(for an agent)</em>
+<span class="nonterminal">gIdentifier</span>:= <span class="nonterminal">identifier</span> <em>(for a generation record)</em><br/>
+<span class="nonterminal">uIdentifier</span>:= <span class="nonterminal">identifier</span> <em>(for a usage record)</em>
</div>