--- a/ontology/ProvenanceFormalModel.html Fri Nov 25 15:23:21 2011 +0000
+++ b/ontology/ProvenanceFormalModel.html Sun Nov 27 16:04:15 2011 -0500
@@ -107,6 +107,9 @@
{ name: "Stian Soiland-Reyes",
url:"http://soiland-reyes.com/stian/",
company: "University of Manchester, UK" },
+ { name: "Stephan Zednick",
+ url:"http://tw.rpi.edu/web/person/StephanZednik",
+ company: "Rensselaer Polytechnic Institute, USA" },
],
// name of the WG
@@ -276,16 +279,16 @@
<pre>prov:Activity rdfs:subClassOf owl:Thing.</pre>
<div class="anexample">
<div><b>Example</b></div>
- <p> Example instances of the class Activity (from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a>) are "file creation" (<i>pe0</i>) and "file editing" (<i>pe2</i>) . The RDF/XML syntax for asserting that pe2 is an instance of Activity is given below.
+ <p> Example instances of the class Activity (from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a>) are "file creation" (<i>pe0</i>) and "file editing" (<i>pe2</i>) . The RDF/XML syntax for asserting that act2 is an instance of Activity is given below.
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe2">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act2">
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Activity"/>
</rdf:Description>
</pre>
</div>
</div>
- <div class='note'> pe2 is an instance of class <code>:Emailing</code>, which is defined to be sub-class of class <code>prov:Activity</code> in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that pe2 is also an instance of <code>prov:Activity</code>.
+ <div class='note'> act2 is an instance of class <code>:Emailing</code>, which is defined to be sub-class of class <code>prov:Activity</code> in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that act2 is also an instance of <code>prov:Activity</code>.
</div>
</section>
@@ -322,12 +325,12 @@
<pre>time:TemporalEntity rdfs:subClassOf owl:Thing.</pre>
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of instances of class TemporalEntity from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. t+1 is associated with the instance of Activity pe2. The instances of TemporalEntity are linked to instances of Entity or Activity classes by the <a href="#hadtemporalvalue">hadTemporalValue</a> property that is described later in this document. </p>
- <p>The RDF/XML syntax for this asserting that t+1 is an instance of class TemporalEntity and t+1 is associated with pe2 is given below.
+ <p> Example of instances of class TemporalEntity from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> are <i>t</i> and <i>t+1</i>. t+1 is associated with the instance of Activity act2. The instances of TemporalEntity are linked to instances of Entity or Activity classes by the <a href="#hadtemporalvalue">hadTemporalValue</a> property that is described later in this document. </p>
+ <p>The RDF/XML syntax for this asserting that t+1 is an instance of class TemporalEntity and t+1 is associated with act2 is given below.
</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe2">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act2">
<prov:hadTemporalValue rdf:about="http://www.example.com/crimeFile#t+1">
<rdf:type rdf:resource="http://www.w3.org/2006/time#TemporalEntity"/>
</prov:hadTemporalValue>
@@ -508,7 +511,7 @@
<pre>prov:Role rdfs:subClassOf owl:Thing.</pre>
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of instances of class Role from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> are <i>author (for Alice)</i> and <i>save (for pe1)</i>. The RDF/XML syntax for asserting that Alice played a role of author in the usage u1 (instance of class Usage) of file e1 in the activity of adding content.
+ <p> Example of instances of class Role from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> are <i>author (for Alice)</i> and <i>save (for act1)</i>. The RDF/XML syntax for asserting that Alice played a role of author in the usage u1 (instance of class Usage) of file e1 in the activity of adding content.
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crimeFile#u1">
@@ -564,14 +567,14 @@
style="height: 3em" alt="wasGeneratedBy links Entity to Activity" />
<div class="anexample">
<div><b>Example</b></div>
- <p>Example of wasGeneratedBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy pe0</i>. The RDF/XML syntax for asserting this information is given below.
+ <p>Example of wasGeneratedBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>e1 wasGeneratedBy act0</i>. The RDF/XML syntax for asserting this information is given below.
</p>
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crimeFile#e1">
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Entity"/>
<prov:wasGeneratedBy>
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe0">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act0">
<rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Activity"/>
</rdf:Description>
<prov:wasGeneratedBy>
@@ -681,7 +684,7 @@
<p> Example of used property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe2 used e2</i>. The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe2">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act2">
<prov:used rdf:resource="http://www.example.com/crimeFile#e2"/>
</rdf:Description>
</pre>
@@ -701,7 +704,7 @@
<p> Example of hadParticipant property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe2 hadParticipant e2</i>. The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe2">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act2">
<prov:hadParticipant rdf:resource="http://www.example.com/crimeFile#e2"/>
</rdf:Description>
</pre>
@@ -735,7 +738,7 @@
<p> Example of wasControlledBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>FileAppending</i> (Activity) <i>wasControlledBy Bob</i>. The RDF/XML syntax for asserting this is given below.
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act1">
<prov:wasControlledBy>
<rdf:Description rdf:about="http://www.example.com/crimeFile#Bob">
<rdf:type rdf:resource="http://www.example.com/crime#Journalist"/>
@@ -757,10 +760,10 @@
style="height: 3em" alt="hadRecipe links Activity to Agent" />
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of hadRecipe property in the (extended)<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is that pe1 (instance of Activity class) followed some file appending instructions (instructions1). The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of hadRecipe property in the (extended)<a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is that act1 (instance of Activity class) followed some file appending instructions (instructions1). The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act1">
<prov:hadRecipe rdf:resource="http://www.example.com/crimeFile#instructions1"/>
</rdf:Description>
</pre>
@@ -778,11 +781,11 @@
style="height: 3em" alt="wasInformedBy links Activity to Activity" />
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of wasInformedBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe4 wasInformedBy pe3</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of wasInformedBy property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe4 wasInformedBy act3</i>. The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe4">
- <prov:wasInformedBy rdf:resource="http://www.example.com/crimeFile#pe3"/>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act4">
+ <prov:wasInformedBy rdf:resource="http://www.example.com/crimeFile#act3"/>
</rdf:Description>
</pre>
</div>
@@ -800,11 +803,11 @@
style="height: 3em" alt="wasScheduledAfter links Activity to Activity" />
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of wasScheduledAfter property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe4 wasScheduledAfter pe3</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of wasScheduledAfter property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> is <i>pe4 wasScheduledAfter act3</i>. The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe4">
- <prov:wasScheduledAfter rdf:resource="http://www.example.com/crimeFile#pe3"/>
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act4">
+ <prov:wasScheduledAfter rdf:resource="http://www.example.com/crimeFile#act3"/>
</rdf:Description>
</pre>
</div>
@@ -822,10 +825,10 @@
style="height: 3em" alt="hadTemporalValue links Activity or Entity to time:TemporalValue" />
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of hadTemporalValue property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a> is <i>t+3</i> time value is associated with the pe3 Activity instanc</i>. The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of hadTemporalValue property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a> is <i>t+3</i> time value is associated with the act3 Activity instanc</i>. The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe3">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act3">
<prov:hasTemporalValue rdf:resource="http://www.example.com/crimeFile#t+3"/>
</rdf:Description>
</pre>
@@ -840,10 +843,10 @@
<img src="diagram-history/khalidDiagrams/startedAt.png" style="height: 3em" alt="startedAt links Activity to Instant"/>
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of startedAt property is that a pe1 (instance of Activity class) is "2011-10-20T17:14:12Z". The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of startedAt property is that a act1 (instance of Activity class) is "2011-10-20T17:14:12Z". The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act1">
<prov:startedAt rdf:about="http://www.example.com/crimeFile#t1>
<rdf:type rdf:resource=""http://www.w3.org/2006/time#Instant"/>
<time:inXSDDateTime>2011-10-20T17:14:12Z</time:inXSDDateTime>
@@ -861,10 +864,10 @@
<img src="diagram-history/khalidDiagrams/endedAt.png" style="height: 3em" alt="endedAt links Activity to Instant"/>
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of endedAt property is that a pe1 (instance of Activity class) is "2011-10-20T20:14:12Z". The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of endedAt property is that a act1 (instance of Activity class) is "2011-10-20T20:14:12Z". The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act1">
<prov:endedAt rdf:about="http://www.example.com/crimeFile#t2>
<rdf:type rdf:resource=""http://www.w3.org/2006/time#Instant"/>
<time:inXSDDateTime>2011-10-20T20:14:12Z</time:inXSDDateTime>
@@ -975,10 +978,10 @@
style="height: 3em" alt="hadQualifiedUsage links Activity to Usage" />
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of hadQualifiedUsage property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> pe1 hadQualifiedUsage u1</i>, where the hadRole describes the usage of e1 as a "load". The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of hadQualifiedUsage property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> act1 hadQualifiedUsage u1</i>, where the hadRole describes the usage of e1 as a "load". The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act1">
<prov:hadQualifiedUsage rdf:resource="http://www.example.com/Usage#u1"/>
</rdf:Description>
</pre>
@@ -993,10 +996,10 @@
style="height: 3em" alt="hadQualifiedParticipation links Activity to Participation" />
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of hadQualifiedParticipation property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> pe1 hadQualifiedParticipation p1</i>, where the hadRole describes the participation of Alice as an "author" in pe1. The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of hadQualifiedParticipation property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> act1 hadQualifiedParticipation p1</i>, where the hadRole describes the participation of Alice as an "author" in act1. The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act1">
<prov:hadQualifiedParticipation rdf:resource="http://www.example.com/crimeFile#p1"/>
</rdf:Description>
</pre>
@@ -1011,10 +1014,10 @@
style="height: 3em" alt="hadQualifiedControl links Activity to Control" />
<div class="anexample">
<div><b>Example</b></div>
- <p> Example of hadQualifiedControl property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> pe0 hadQualifiedControl c1</i>, where the hadRole describes the control of pe0 by Alice as "creator". The RDF/XML syntax for asserting this is given below.</p>
+ <p> Example of hadQualifiedControl property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> act0 hadQualifiedControl c1</i>, where the hadRole describes the control of act0 by Alice as "creator". The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
<pre class="example">
- <rdf:Description rdf:about="http://www.example.com/crimeFile#pe0">
+ <rdf:Description rdf:about="http://www.example.com/crimeFile#act0">
<prov:hadQualifiedControl rdf:resource="http://www.example.com/crimeFile#c1"/>
</rdf:Description>
</pre>
@@ -1147,7 +1150,7 @@
</td><td style="border-style: solid; border-width: 0 1px 1px 0">No
</td><td style="border-style: solid; border-width: 0 1px 1px 0">Yes
</td></tr></table>
- <div class='note'>Some of the properties may be subject to discussion. In particular, regarding the object properties <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>used</i>, we did not specify whether they are transitive or not. One may argue that given that an agent can be a process execution, a process execution, e.g., <i>pe1</i>, can be controlled by an agent <i>pe2</i>, which happens to be a process execution that is controlled by an agent <i>ag</i>, and that, therefore, <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument can be applied to <i>wasGeneratedBy</i> and <i>used</i>. That said, we are not convinced that these properties should be declared as transitive. In fact, we are more inclined towards specifying that they are not.</div>
+ <div class='note'>Some of the properties may be subject to discussion. In particular, regarding the object properties <i>wasControlledBy</i>, <i>wasGeneratedBy</i> and <i>used</i>, we did not specify whether they are transitive or not. One may argue that given that an agent can be a process execution, a process execution, e.g., <i>pe1</i>, can be controlled by an agent <i>pe2</i>, which happens to be a process execution that is controlled by an agent <i>ag</i>, and that, therefore, <i>ag</i> (indirectly) controls <i>pe1</i>. The same argument can be applied to <i>wasGeneratedBy</i> and <i>used</i>. That said, we are not convinced that these properties should be declared as transitive. In fact, we are more inclined towards specifying that they are not.</div>
</section>
<section id="annotation-properties">
@@ -1194,16 +1197,19 @@
</section>
<section class='informative' id="specializing-provenance-ontology-for-domain-specific-provenance-applications">
- <h2>Specializing Provenance Ontology for Domain-specific Provenance Applications</h2>
- <p>The PROV Ontology is conceived as a reference ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The PROV Ontology classes and properties can be specialized using the following two RDFS properties:</p>
+ <h2>Specializing the PROV Ontology for Domain-specific Provenance Applications</h2>
+ <p>The PROV Ontology does not include all the provenance terms that are required by different application to model provenance information. For example, the classes and properties to model provenance information in the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a>, such as "Journalist" or "FileEditing", are not part of the PROV ontology. This is a deliberate design choice for PROV ontology, since modeling provenance terms for a variety of domain applications in a single ontology is impractical. Hence, the PROV Ontology is conceived as an ontology that can be extended by various domain-specific applications to model the required set of provenance terms. The PROV Ontology classes and properties can be specialized using the following two RDFS properties:</p>
<ul>
- <li>rdfs:subClassOf: The property rdfs:subClassOf is an instance of rdf:Property that is used to state that all the instances of one class are instances of another [[!RDF-SCHEMA]]</li>
- <li>rdfs:subPropertyOf: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property" [[!RDF-SCHEMA]]</li>
+ <li><i>rdfs:subClassOf</i>: The property rdfs:subClassOf is an instance of rdf:Property that is used to state that all the instances of one class are instances of another [[!RDF-SCHEMA]]</li>
+ <li><i>rdfs:subPropertyOf</i>: "A rdfs:subPropertyOf axiom defines that the property is a subproperty of some other property" [[!RDF-SCHEMA]]</li>
</ul>
- <p>The [[PROV-BestPractices]] document illustrates this
- specialisation mechanism by defining two PROV-O extensions
- for domain-specific examples.</p>
-
+ <p>A new provenance ontology can be created to model the classes and properties required by an application to represent its domain-specific provenance terms. The new provenance ontology, for the given application, is also expected to include all the PROV Ontology classes and properties, which will facilitate provenance exchange through a common set of terms.</p>
+ <p>The following are a few example classes from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario</a> that are created by specializing PROV Ontology classes:
+ <ul>
+ <li>The <a href="#agent">Agent</a> class can be specialized to define a class called Journalist, which has individuals such as alice, bob, and edith </li>
+ <li>Similarly, the <a href="#activity">Activity</a> class can be specialized to define classes called FileCreation, FileAppending, and FileEditing </li>
+ </ul>
+ The [[PROV-BestPractices]] document describes in detail the approach used to model provenance information in two domain-specific examples by specializing the PROV Ontology.</p>
</section>
<section id="formal-semantics-of-the-prov-ontology">
<h2>Formal Semantics of the PROV Ontology</h2>
@@ -1296,7 +1302,7 @@
<section id="provenance-constraint-on-wasgeneratedby-generation-affects-attributes">
<h4>Provenance constraint on wasGeneratedBy (generation-affects-attributes)</h4>
<p>The PROV-DM describes a constraint on wasGeneratedBy that associates the values of attributes of an Entity with the Activity that generated the Entity.</p>
- <div class='issue'>"Given a process execution pe, entity e, role r, and optional time t, if the assertion wasGeneratedBy(e,pe,r) or wasGeneratedBy(e,pe,r,t) holds, the values of some of e's attributes are determined by the activity denoted by pe and the entities used by pe. Only some (possibly none) of the attributes values may be determined since, in an open world, not all used entities may have been asserted." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122 </a> and <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
+ <div class='issue'>"Given a process execution act, entity e, role r, and optional time t, if the assertion wasGeneratedBy(e,pe,r) or wasGeneratedBy(e,pe,r,t) holds, the values of some of e's attributes are determined by the activity denoted by act and the entities used by act. Only some (possibly none) of the attributes values may be determined since, in an open world, not all used entities may have been asserted." This is <a href="http://www.w3.org/2011/prov/track/issues/122">ISSUE-122 </a> and <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
</section>
<section id="provenance-constraint-on-wasgeneratedby-generation-pe-ordering">
<h4>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</h4>
@@ -1307,25 +1313,25 @@
<section id="provenance-constraint-on-wasgeneratedby-generation-unicity">
<h4>Provenance constraint on wasGeneratedBy (generation-unicity)</h4>
<p>The PROV-DM describes a constraint on wasGeneratedBy that asserts that given an account, only oneActivityinstance can be associated to an Entity instance by the property wasGeneratedBy.</p>
- <div class='issue'>"Given an entity expression denoted by e, two process execution expressions denoted by pe1 and pe2, and two qualifiers q1 and q2, if the expressions wasGeneratedBy(e,pe1,q1) and wasGeneratedBy(e,pe2,q2) exist in the scope of a given account, then pe1=pe2 and q1=q2." This is <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
+ <div class='issue'>"Given an entity expression denoted by e, two process execution expressions denoted by act1 and act2, and two qualifiers q1 and q2, if the expressions wasGeneratedBy(e,pe1,q1) and wasGeneratedBy(e,pe2,q2) exist in the scope of a given account, then act1=act2 and q1=q2." This is <a href="http://www.w3.org/2011/prov/track/issues/105">ISSUE-105</a></div>
</section>
<section id ="provenance-constraint-on-used-use-attributes">
<h4>Provenance constraint on Used (use-attributes)</h4>
<p>A constraint is defined for the Used relation in PROV-DM, that makes it necessary for an attribute-value to be true for an Entity instance linked to a Activity instance by relation Used.
</p>
- <div class='issue'>"Given a process execution expression identified by pe, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the existence of an attribute-value pair in the entity expression identified by e is a pre-condition for the termination of the activity represented by the process execution expression identified by pe." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
+ <div class='issue'>"Given a process execution expression identified by act, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the existence of an attribute-value pair in the entity expression identified by e is a pre-condition for the termination of the activity represented by the process execution expression identified by act." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
</section>
<section id ="provenance-constraint-on-used-pe-ordering">
<h4>Provenance constraint on Used (use-pe-ordering)</h4>
- <p>The PROV-DM describes a constraint for Used relation, which makes it necessary for an Entity instance e (linked to a Activity instance pe by Used relation) to be "used" before pe terminates and also the "generation" of e precedes "use" of e.
+ <p>The PROV-DM describes a constraint for Used relation, which makes it necessary for an Entity instance e (linked to a Activity instance act by Used relation) to be "used" before act terminates and also the "generation" of e precedes "use" of e.
</p>
- <div class='issue'>"Given a process execution expression identified by pe, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the use of the thing represented by entity expression identified by e precedes the end time contained in the process execution expression identified by pe and follows its beginning. Furthermore, the generation of the thing denoted by entity expression identified by e always precedes its use." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
+ <div class='issue'>"Given a process execution expression identified by act, an entity expression identified by e, a qualifier q, and optional time t, if assertion used(pe,e,q) or used(pe,e,q,t) holds, then the use of the thing represented by entity expression identified by e precedes the end time contained in the process execution expression identified by act and follows its beginning. Furthermore, the generation of the thing denoted by entity expression identified by e always precedes its use." This is <a href="http://www.w3.org/2011/prov/track/issues/124">ISSUE-124</a></div>
</section>
<section id ="provenance-constraint-on-derivation-attributes">
<h4>Provenance constraint on wasDerivedFrom (derivation-attributes)</h4>
<p>The PROV-DM describes a constraint for asserting wasDerivedFrom property between two Entity instances if some attributes of an Entity instance are partially or fully determined by attributes values of the other Entity instance.
</p>
- <div class='issue'>"Given a process execution expression denoted by pe, entity expressions denoted by e1 and e2, qualifiers q1 and q2, the assertion wasDerivedFrom(e2,e1,pe,q2,q1) or wasDerivedFrom(e2,e1) holds if and only if the values of some attributes of the entity expression identified by e2 are partly or fully determined by the values of some attributes of the entity expression identified by e1." This is <a href="http://www.w3.org/2011/prov/track/issues/125">ISSUE-125</a></div>
+ <div class='issue'>"Given a process execution expression denoted by act, entity expressions denoted by e1 and e2, qualifiers q1 and q2, the assertion wasDerivedFrom(e2,e1,pe,q2,q1) or wasDerivedFrom(e2,e1) holds if and only if the values of some attributes of the entity expression identified by e2 are partly or fully determined by the values of some attributes of the entity expression identified by e1." This is <a href="http://www.w3.org/2011/prov/track/issues/125">ISSUE-125</a></div>
</section>
<section id ="provenance-constraint-on-derivation-use-generation-ordering">
<h4>Provenance constraint on wasDerivedFrom (derivation-use-generation-ordering)</h4>
@@ -1336,21 +1342,21 @@
</section>
<section id ="provenance-constraint-on-derivation-events">
<h4>Provenance constraint on wasDerivedFrom (derivation-events)</h4>
- <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, that is wasDerivedFrom (e2, e1, pe), then wasGeneratedBy(e2, pe) and used(pe, e1) can also be asserted.
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, that is wasDerivedFrom (e2, e1, act), then wasGeneratedBy(e2, act) and used(pe, e1) can also be asserted.
</p>
- <div class='note'> Since the above constraint defined in PROV-DM does not define how pe is linked to the derivation of e2 from e1, this constraint can be supported in the "opposite" direction in PROV-O. In other words, given e2 was generated at time instant t2 by pe and pe used e1 at time instant t1 and t1 is less than t2, then we can assert that wasDerivedFrom(e2, e1).
+ <div class='note'> Since the above constraint defined in PROV-DM does not define how act is linked to the derivation of e2 from e1, this constraint can be supported in the "opposite" direction in PROV-O. In other words, given e2 was generated at time instant t2 by act and act used e1 at time instant t1 and t1 is less than t2, then we can assert that wasDerivedFrom(e2, e1).
</div>
</section>
<section id ="provenance-constraint-on-derivation-process-execution">
<h4>Provenance constraint on wasDerivedFrom (derivation-events)</h4>
- <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, then there exists someActivityinstance such that wasGeneratedBy(e2, pe) and used(pe, e1) can also be asserted.
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, then there exists someActivityinstance such that wasGeneratedBy(e2, act) and used(pe, e1) can also be asserted.
</p>
<div class='note'> This constraint is a re-statement of the generic Semantic Web "open-world assumption". Hence, it is not mapped to PROV ontology.
</div>
</section>
<section id ="provenance-constraint-on-derivation-use">
<h4>Provenance constraint on wasDerivedFrom (derivation-use)</h4>
- <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, and wasGeneratedBy(e2, pe) is also asserted then Used(pe, e1) can also be asserted.
+ <p>The PROV-DM describes a constraint that if wasDerivedFrom property is asserted between two Entity instances e1 and e2, and wasGeneratedBy(e2, act) is also asserted then Used(pe, e1) can also be asserted.
</p>
<div class='note'> This will be asserted as a rule.
</div>
@@ -1380,10 +1386,10 @@
<h4>Provenance constraint on hadParticipant (participant)</h4>
<p>The PROV-DM describes a constraint that hadParticipant property holds between an instance of Entity and instance of Activity if the two instances are linked by "used" of "wasControlledBy" or "wasComplementOf".
</p>
- <div class='issue'> "Given two identifiers pe and e, respectively identifying a process execution expression and an entity expression, the expression hadParticipant(pe,e) holds if and only if:
+ <div class='issue'> "Given two identifiers act and e, respectively identifying a process execution expression and an entity expression, the expression hadParticipant(pe,e) holds if and only if:
*used(pe,e) holds, or
*wasControlledBy(pe,e) holds, or
- *wasComplementOf(e1,e) holds for some entity expression identified by e1, and hadParticipant(pe,e1) holds some process execution expression identified by pe." This is <a href="http://www.w3.org/2011/prov/track/issues/127">ISSUE-127</a>
+ *wasComplementOf(e1,e) holds for some entity expression identified by e1, and hadParticipant(pe,e1) holds some process execution expression identified by act." This is <a href="http://www.w3.org/2011/prov/track/issues/127">ISSUE-127</a>
</div>
</section>
</section>