--- a/model/ProvenanceModel.html Thu Sep 22 21:31:02 2011 -0400
+++ b/model/ProvenanceModel.html Fri Sep 23 12:33:05 2011 +0100
@@ -125,8 +125,6 @@
formal semantics.
</p>
-<div class='resolved'>The name of the data model still has to be decided by the WG. Current placeholder name is PIDM. This is <a href="http://www.w3.org/2011/prov/track/issues/31">ISSUE-31</a></div>
-
</section>
<section>
@@ -336,8 +334,6 @@
Attributes, qualifiers, and annotation are the main <strong>extensibility points</strong> in the model: individual interest groups are expected to extend PROV-DM by introducing new sets of attributes, qualifiers, and annotations as needed to address applications-specific provenance modelling requirements.
-<div class='note'>Note: time is not explicit in the figure.</div>
-
<div class='pending'>Conceptual model needs a high level overview <a href="http://www.w3.org/2011/prov/track/issues/86">ISSUE-86</a>.</div>
</section>
@@ -744,7 +740,7 @@
<div class='constraint' id='start-precedes-end'><a name="PIL:0001"> From a process execution expression, one can infer that the
start event precedes the end event of the represented activity.</a> [<a
-href="../ontology/ProvenanceFormalModel.html#PIL:0001">PIL:0001</a>] </div>
+href="../ontology/ProvenanceFormalModel.html#PROV:0001">PROV:0001</a>] </div>
<p>A process execution expression is not an entity expression.
Indeed, an entity expression represents a thing that exists in full at
@@ -938,14 +934,14 @@
entity expressions used by <span class="name">pe</span>.
Only some (possibly none) of the attributes values may be determined
since, in an open world, not all used entity expressions may have been
-asserted.</a> [<a href="../ontology/ProvenanceFormalModel.html#PIL:0002">PIL:0002</a>]
+asserted.</a> [<a href="../ontology/ProvenanceFormalModel.html#PROV:0002">PROV:0002</a>]
</div>
The assertion of a generation event implies ordering of events in the world.
<div class='constraint' id='generation-pe-ordering'><a name="PIL:0003"><span class='conditional'>If</span> an assertion <span class="name">wasGeneratedBy(x,pe,r)</span> or <span class="name">wasGeneratedBy(x,pe,r,t)</span>, <span class='conditional'>then</span> generation of the thing denoted by <span class="name">x</span> precedes the end
-of <span class="name">pe</span> and follows the beginning of <span class="name">pe</span>.</a> [<a href="../ontology/ProvenanceFormalModel.html#PIL:0003">PIL:0003</a>]
+of <span class="name">pe</span> and follows the beginning of <span class="name">pe</span>.</a> [<a href="../ontology/ProvenanceFormalModel.html#PROV:0003">PROV:0003</a>]
</div>
@@ -1017,7 +1013,7 @@
assertion <span class="name">used(pe,e,q)</span> or <span class="name">used(pe,e,q,t)</span> holds,
<span class='conditional'>then</span> the existence of an attribute-value pair in the entity expression identified by <span class="name">e</span> is a
pre-condition for the termination of the activity represented by the process execution expression identified by <span class="name">pe</span></a>
-[<a href="../ontology/ProvenanceFormalModel.html#PIL:0005">PIL:0005</a>]</div>
+[<a href="../ontology/ProvenanceFormalModel.html#PROV:0005">PROV:0005</a>]</div>
@@ -1026,7 +1022,7 @@
the use of the thing represented by entity expression identified by <span class="name">e</span> precedes the end
time contained in the process execution expression identified by <span class="name">pe</span> and follows its beginning. Furthermore, the generation of the thing denoted by entity expression identified by <span class="name">e</span> always precedes
its use.</a>
-[<a href="../ontology/ProvenanceFormalModel.html#PIL:0006">PIL:0006</a>] </div>
+[<a href="../ontology/ProvenanceFormalModel.html#PROV:0006">PROV:0006</a>] </div>
<div class='issue'>Should we define a taxonomy of use? This is <a href="http://www.w3.org/2011/prov/track/issues/23">ISSUE-23</a>.</div>
@@ -1135,7 +1131,7 @@
<div class="constraint" id='derivation-events'>
<a name="PIL:0010"><span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1,pe,r2,r1)</span> holds, <span class='conditional'>then</span>
<span class="name">wasGeneratedBy(e2,pe,r2)</span> and <span class="name">used(pe,e1,r1)</span> also
- hold. </a> [<a href="../ontology/ProvenanceFormalModel.html#PIL:0010">PIL:0010</a>]
+ hold. </a> [<a href="../ontology/ProvenanceFormalModel.html#PROV:0010">PROV:0010</a>]
</div>
@@ -1148,7 +1144,7 @@
<a name="PIL:0009">
<span class='conditional'>If</span> <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span> there exists a process execution expression identified by <span class="name">pe</span>, and qualifiers <span class="name">q1</span>,<span class="name">q2</span>,
such that:
- <span class="name">wasGeneratedBy(e2,pe,q2)</span> and <span class="name">used(pe,e1,q1)</span>. [<a href="../ontology/ProvenanceFormalModel.html#PIL:0009">PIL:0009</a>]
+ <span class="name">wasGeneratedBy(e2,pe,q2)</span> and <span class="name">used(pe,e1,q1)</span>. [<a href="../ontology/ProvenanceFormalModel.html#PROV:0009">PROV:0009</a>]
</div></p>
@@ -1161,7 +1157,7 @@
the values of some attributes of the entity expression identified by
<span class="name">e2</span> are partly or fully determined by the values of some
attributes of the entity expression identified by <span class="name">e1</span>.</a> [<a
- href="../ontology/ProvenanceFormalModel.html#PIL:0007">PIL:0007</a>] </div>
+ href="../ontology/ProvenanceFormalModel.html#PROV:0007">PROV:0007</a>] </div>
<div class='note'>Should this dependency of attributes be made explicit as argument of the derivation expression? By making it explicit, we would allow someone to verify the validity of the derivation expression.<br/>
Khalid's note: I was thinking of adding derivation-qualifier to wasDerivedFrom(e2,e1),
@@ -1177,7 +1173,7 @@
or <span class="name">wasDerivedFrom(e2,e1)</span> holds, <span class='conditional'>then</span>
the use
of characterized thing denoted by <span class="name">e1</span> precedes the generation of
-the characterized thing denoted by <span class="name">e2</span>.</a> [<a href="../ontology/ProvenanceFormalModel.html#PIL:0008">PIL:0008</a>]
+the characterized thing denoted by <span class="name">e2</span>.</a> [<a href="../ontology/ProvenanceFormalModel.html#PROV:0008">PROV:0008</a>]
</div>
@@ -1200,7 +1196,7 @@
<a name="PIL:0011">Given a process execution expression identified by <span class="name">pe</span>, entity expressions identified by <span class="name">e1</span> and <span class="name">e2</span>, and qualifier <span class="name">q2</span>,
<span class='conditional'>if</span> <span class="name">wasDerivedFrom(e2,e1)</span> and <span class="name">wasGeneratedBy(e2,pe,q2)</span> hold, <span class='conditional'>then</span> there exists a qualifier <span class="name">q1</span>,
such that <span class="name">used(pe,e1,r1)</span> also holds.</a>
- [<a href="../ontology/ProvenanceFormalModel.html#PIL:0011">PIL:0011</a>]
+ [<a href="../ontology/ProvenanceFormalModel.html#PROV:0011">PROV:0011</a>]
</div>
This inference is justified by the fact that the characterized thing represented by entity expression identified by <span class="name">e2</span> is generated by at most one activity in a given account (see <a href="#generation-unicity">generation-unicity</a>). Hence, this process execution expression is also the one referred to in the use expression of <span class="name">e1</span>.
</p>
@@ -1240,7 +1236,7 @@
holds, <span class='conditional'>then</span> the
generation event of the characterized thing represented by the entity expression denoted by <span class="name">e1</span> precedes the generation event of
the characterized thing represented by the entity expression denoted by <span class="name">e2</span>.</a>
- [<a href="../ontology/ProvenanceFormalModel.html#PIL:0012">PIL:0012</a>]
+ [<a href="../ontology/ProvenanceFormalModel.html#PROV:0012">PROV:0012</a>]
</div>
<p>Note that temporal ordering is between generations of <span class="name">e1</span>
@@ -1436,7 +1432,7 @@
<li> if a mapping can be established from an attribute X of entity expression identified by B to an attribute Y of entity expression identified by A, then the values of A and B must be consistent with that mapping</em>;</li>
<li>entity expression identified by B has some attribute that entity expression identified by A does not have.
</li></ol></a>
- [<a href="../ontology/ProvenanceFormalModel.html#PIL:0013">PIL:0013</a>]
+ [<a href="../ontology/ProvenanceFormalModel.html#PROV:0013">PROV:0013</a>]
</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 expressions such that
@@ -1510,6 +1506,21 @@
such that <span class="name">wasGeneratedBy(e,pe1,q1)</span> and <span class="name">used(pe2,e,q2)</span> hold.
</div>
+<p>The relationship <span class="name">wasInformedBy</span> is not transitive. Indeed, consider the expressions <span class="name">wasInformedBy(pe2,pe1)</span> and <span class="name">wasInformedBy(pe3,pe2)</span>, the expression
+<span class="name">wasInformedBy(pe3,pe1)</span>, may not necessarily hold, as illustrated by the following event line.
+<pre>
+ ------ pe1
+ |
+ e1
+ |
+ ------- pe2
+ |
+ e2
+ |
+ ----- pe3
+</pre>
+The end in process execution expression identified by <span class="name">pe3</span> precedes the start in process execution expression identified by <span class="name">pe1</span>, while interval for process execution expression <span class="name">pe2</span> overlaps with each interval for <span class="name">pe1</span> and <span class="name">pe3</span>, allowing information to flow (<span class="name">e1</span> and <span class="name">e2</span>, respectively).</p>
+
<p>
@@ -1659,7 +1670,7 @@
<span class="name">hadParticipant(pe,e1)</span> holds some process execution expression identified by <span class="name">pe</span>.</li>
</ul>
</a> [<a
-href="../ontology/ProvenanceFormalModel.html#PIL:0014">PIL:0014</a>]
+href="../ontology/ProvenanceFormalModel.html#PROV:0014">PROV:0014</a>]
</div>
@@ -2277,6 +2288,8 @@
<div class='issue'>There are a number of commonly used provenance relations in particular for the web that are not in the model. For practical use and uptake, it would be good to have definitions of these in the provenance model. These concepts should be defined in terms of the already existing "core" concepts. This is <a href="http://www.w3.org/2011/prov/track/issues/44">ISSUE-44</a>.</div>
+<div class='note'>This section needs editing. It needs to be aligned the terminology of previous sections and it needs to adopt the same presentation style. </div>
+
<section>
<h3>Quotation</h3>