--- a/ontology/ProvenanceFormalModel.html Fri Nov 18 15:48:46 2011 -0500
+++ b/ontology/ProvenanceFormalModel.html Sun Nov 20 14:49:04 2011 -0500
@@ -240,22 +240,22 @@
</section> <!-- Classes -->
- <section id = "processexecution">
- <h4>ProcessExecution</h4>
+ <section id = "activity">
+ <h4>Activity</h4>
<div><b>Class Description</b></div>
- <p>ProcessExecution is defined to be "an identifiable activity, which performs a piece of work." [[PROV-DM]]</p>
+ <p>Activity is defined to be "an identifiable activity, which performs a piece of work." [[PROV-DM]]</p>
<div><b>OWL syntax</b></div>
- <pre>prov:ProcessExecution rdfs:subClassOf owl:Thing.</pre>
+ <pre>prov:Activity rdfs:subClassOf owl:Thing.</pre>
<div><b>Example</b></div>
- <p> Example instances of the class ProcessExecution (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 ProcessExecution 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 pe2 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:type rdf:resource="http://www.w3.org/ns/prov-o/ProcessExecution"/>
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Activity"/>
</rdf:Description>
</pre>
</div>
- <div class='note'> pe2 is an instance of class <code>:Emailing</code>, which is defined to be sub-class of class <code>prov:ProcessExecution</code> in the CrimeFile ontology. Hence, using standard RDFS entailment allows us to infer that pe2 is also an instance of <code>prov:ProcessExecution</code>.
+ <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>
</section>
@@ -289,7 +289,7 @@
<div><b>OWL syntax</b></div>
<pre>time:TemporalEntity rdfs:subClassOf owl:Thing.</pre>
<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 ProcessExecution pe2. The instances of TemporalEntity are linked to instances of Entity or ProcessExecution classes by the <a href="#hadtemporalvalue">hadTemporalValue</a> property that is described later in this document. </p>
+ <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>
<div class="exampleOuter">
@@ -356,7 +356,7 @@
<section id="qualifiedinvolvement">
<h4>QualifiedInvolvement</h4>
<div><b>Class Description</b></div>
- <p>The QualifiedInvolvement class represents an n-ary property to capture qualifying information related to the use of Entity by ProcessExecution.</p>
+ <p>The QualifiedInvolvement class represents an n-ary property to capture qualifying information related to the use of Entity by Activity.</p>
<div><b>OWL syntax</b></div>
<pre>prov:QualifiedInvolvement rdfs:subClassOf owl:Thing.</pre>
@@ -381,7 +381,7 @@
<section id="participation">
<h4>Participation</h4>
<div><b>Class Description</b></div>
- <p>The Participation class represents an n-ary property to capture qualifying information related to the participation of Entity in ProcessExecution.</p>
+ <p>The Participation class represents an n-ary property to capture qualifying information related to the participation of Entity in Activity.</p>
<div><b>OWL syntax</b></div>
<pre>prov:Participation rdfs:subClassOf prov:QualifiedInvolvement.</pre>
<div><b>Example</b></div>
@@ -399,7 +399,7 @@
<section id="control">
<h4>Control</h4>
<div><b>Class Description</b></div>
- <p>The Control class represents an n-ary property to capture qualifying information related to the control of ProcessExecution by Agent.</p>
+ <p>The Control class represents an n-ary property to capture qualifying information related to the control of Activity by Agent.</p>
<div><b>OWL syntax</b></div>
<pre>prov:Control rdfs:subClassOf prov:QualifiedInvolvement.</pre>
<div><b>Example</b></div>
@@ -417,7 +417,7 @@
<section id="generation">
<h4>Generation</h4>
<div><b>Class Description</b></div>
- <p>The Generation class represents an n-ary property to capture qualifying information related to the generation of Entity by ProcessExecution.</p>
+ <p>The Generation class represents an n-ary property to capture qualifying information related to the generation of Entity by Activity.</p>
<div><b>OWL syntax</b></div>
<pre>prov:Generation rdfs:subClassOf prov:QualifiedInvolvement.</pre>
<div><b>Example</b></div>
@@ -436,7 +436,7 @@
<section id="recipe">
<h4>Recipe</h4>
<div><b>Class Description</b></div>
- <p>Recipe represents the specification of a <a href="#processexecution">ProcessExecution</a>. PROV ontology does not define the different types of recipes that can be created by provenance applications in different domains.</p>
+ <p>Recipe represents the specification of a <a href="#activity">Activity</a>. PROV ontology does not define the different types of recipes that can be created by provenance applications in different domains.</p>
<div><b>OWL syntax</b></div>
<pre>prov:Recipe rdfs:subClassOf owl:Thing.</pre>
<div><b>Example</b></div>
@@ -444,7 +444,7 @@
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crimeFile#news_editing">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/ProcessExection"/>
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Activity"/>
<prov:hadRecipe rdf:resource="http://www.example.com/crimeFile#NewsReportEditingProtocol"/>
</rdf:Description>
</pre>
@@ -454,7 +454,7 @@
<section id ="role">
<h4>Role</h4>
<div><b>Class Description</b></div>
- <p>Role class models additional information about Entity or ProcessExecution class with respect to the QualifiedInvolvement class [[PROV-DM]]</p>
+ <p>Role class models additional information about Entity or Activity class with respect to the QualifiedInvolvement class [[PROV-DM]]</p>
<div><b>OWL syntax</b></div>
<pre>prov:Role rdfs:subClassOf owl:Thing.</pre>
<div><b>Example</b></div>
@@ -467,7 +467,7 @@
</rdf:Description>
</pre>
</div>
- <div class='note'> It is not clear how two roles can be modeled using the QualifiedInvolvement class-based approach, where an Entity plays a role of "author", while the ProcessExecution plays the role of "save" (from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a>).
+ <div class='note'> It is not clear how two roles can be modeled using the QualifiedInvolvement class-based approach, where an Entity plays a role of "author", while the Activity plays the role of "save" (from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a>).
</div>
</section>
@@ -500,10 +500,10 @@
<section id="wasgeneratedby">
<h4>wasGeneratedBy</h4>
- <p>The wasGeneratedBy property links the Entity class with the ProcessExecution class.</p>
- <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
+ <p>The wasGeneratedBy property links the Entity class with the Activity class.</p>
+ <p><i>Note: No arity constraints are assumed between Entity and Activity</i></p>
<img src="diagram-history/khalidDiagrams/wasGeneratedBy.png"
- style="height: 3em" alt="wasGeneratedBy links Entity to ProcessExecution" />
+ style="height: 3em" alt="wasGeneratedBy links Entity to Activity" />
<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>
@@ -513,7 +513,7 @@
<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:type rdf:resource="http://www.w3.org/ns/prov-o/ProcessExecution"/>
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Activity"/>
</rdf:Description>
<prov:wasGeneratedBy>
</rdf:Description>
@@ -564,7 +564,7 @@
<section id="waseventuallyderivedfrom">
<h4>wasEventuallyDerivedFrom</h4>
- <p>This object property is used to link two instances of Entity class that "...are not directly used and generated respectively" by a single instance of ProcessExecution class [[PROV-DM]].
+ <p>This object property is used to link two instances of Entity class that "...are not directly used and generated respectively" by a single instance of Activity class [[PROV-DM]].
</p>
<img src="diagram-history/khalidDiagrams/wasEventuallyDerivedFrom.png"
style="height: 3em" alt="wasEventuallyDerivedFrom links Entity to Entity" />
@@ -604,10 +604,10 @@
<section id="used">
<h4>used</h4>
- <p>The used property links the ProcessExecution class to the Entity class, where the Entity instance is "consumed" by a ProcessExecution instance.</p>
- <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
+ <p>The used property links the Activity class to the Entity class, where the Entity instance is "consumed" by a Activity instance.</p>
+ <p><i>Note: No arity constraints are assumed between Entity and Activity</i></p>
<img src="diagram-history/khalidDiagrams/used.png"
- style="height: 3em" alt="used links ProcessExecution to Entity" />
+ style="height: 3em" alt="used links Activity to Entity" />
<div><b>Example</b></div>
<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">
@@ -622,10 +622,10 @@
<section id="hadparticipant">
<h4>hadParticipant</h4>
- <p>The hadPariticipant property links Entity class to ProcessExecution class, where Entity used or wasGeneratedBy ProcessExecution.</p>
- <p><i>Note: No arity constraints are assumed between Entity and ProcessExecution</i></p>
+ <p>The hadPariticipant property links Entity class to Activity class, where Entity used or wasGeneratedBy Activity.</p>
+ <p><i>Note: No arity constraints are assumed between Entity and Activity</i></p>
<img src="diagram-history/khalidDiagrams/hadParticipant.png"
- style="height: 3em" alt="hadParticipant links ProcessExecution to Entity" />
+ style="height: 3em" alt="hadParticipant links Activity to Entity" />
<div><b>Example</b></div>
<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">
@@ -636,7 +636,7 @@
</pre>
</div>
<div class='pending'>Suggested definition for participation. This is <a href="http://www.w3.org/2011/prov/track/issues/49">ISSUE-49</a>.</div>
- <div class='note'> The current definition of hasParticipant does not account for involvement of an Entity in ProcessExecution where it was neither "used" or "generated". For example, a witness in a criminal activity.
+ <div class='note'> The current definition of hasParticipant does not account for involvement of an Entity in Activity where it was neither "used" or "generated". For example, a witness in a criminal activity.
</div>
</section>
@@ -655,11 +655,11 @@
<section id="wascontrolledby">
<h4>wasControlledBy</h4>
- <p>The wasControlledBy property links ProcessExecution class to Agent class, where control represents the involvement of the Agent in modifying the characteristics of the instance of the ProcessExecution class"[[PROV-DM]].</p>
+ <p>The wasControlledBy property links Activity class to Agent class, where control represents the involvement of the Agent in modifying the characteristics of the instance of the Activity class"[[PROV-DM]].</p>
<img src="diagram-history/khalidDiagrams/wasControlledBy.png"
- style="height: 3em" alt="wasControlledBy links ProcessExecution to Agent" />
+ style="height: 3em" alt="wasControlledBy links Activity to Agent" />
<div><b>Example</b></div>
- <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> (ProcessExecution) <i>wasControlledBy Bob</i>. The RDF/XML syntax for asserting this is given below.
+ <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">
@@ -677,12 +677,12 @@
<section id="hadrecipe">
<h4>hadRecipe</h4>
- <p>This property links the ProcessExecution class to the Recipe class, which describes the execution characteristics of the instance of the ProcessExecution class. The recipe might or might not have been followed exactly by the ProcessExecution.
+ <p>This property links the Activity class to the Recipe class, which describes the execution characteristics of the instance of the Activity class. The recipe might or might not have been followed exactly by the Activity.
</p>
<img src="diagram-history/khalidDiagrams/hadRecipe.png"
- style="height: 3em" alt="hadRecipe links ProcessExecution to Agent" />
+ style="height: 3em" alt="hadRecipe links Activity to Agent" />
<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 ProcessExecution 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 pe1 (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">
@@ -696,10 +696,10 @@
<section id="wasinformedby">
<h4>wasInformedBy</h4>
- <p> This object property links two instances of the ProcessExecution classes. It is used to express the information that a given process execution used an entity that was generated by another process execution.
+ <p> This object property links two instances of the Activity classes. It is used to express the information that a given process execution used an entity that was generated by another process execution.
</p>
<img src="diagram-history/khalidDiagrams/wasInformedBy.png"
- style="height: 3em" alt="wasInformedBy links ProcessExecution to ProcessExecution" />
+ style="height: 3em" alt="wasInformedBy links Activity to Activity" />
<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>
<div class="exampleOuter">
@@ -716,10 +716,10 @@
<section id="wascheduledafter">
<h4>wasScheduledAfter</h4>
<p>
- This property links two instances of ProcessExecution class to specify the order of their executions. Specifically, it is used to specify that a given process execution starts after the end of another process execution.
+ This property links two instances of Activity class to specify the order of their executions. Specifically, it is used to specify that a given process execution starts after the end of another process execution.
</p>
<img src="diagram-history/khalidDiagrams/wasScheduledAfter.png"
- style="height: 3em" alt="wasScheduledAfter links ProcessExecution to ProcessExecution" />
+ style="height: 3em" alt="wasScheduledAfter links Activity to Activity" />
<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>
<div class="exampleOuter">
@@ -736,12 +736,12 @@
<section id="hadtemporalvalue">
<h4>hadTemporalValue</h4>
- <p> This object property links an instance of <code>ProcessExecution</code> or <code>Entity</code> with an <code>time:TemporalEntity</code> from [[!OWL-TIME]], thereby allowing association of time value with instances of the two classes and their subclasses.
+ <p> This object property links an instance of <code>Activity</code> or <code>Entity</code> with an <code>time:TemporalEntity</code> from [[!OWL-TIME]], thereby allowing association of time value with instances of the two classes and their subclasses.
</p>
<img src="diagram-history/khalidDiagrams/hadTemporalValue.png"
- style="height: 3em" alt="hadTemporalValue links ProcessExecution or Entity to time:TemporalValue" />
+ style="height: 3em" alt="hadTemporalValue links Activity or Entity to time:TemporalValue" />
<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 ProcessExecution 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 pe3 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">
@@ -751,11 +751,11 @@
</div>
<section id="startedat">
<h4>startedAt</h4>
- <p> This object property defines the time when <code>ProcessExecution</code> started. The time is specified as an <code>time:Instant</code> [[!OWL-TIME]].
+ <p> This object property defines the time when <code>Activity</code> started. The time is specified as an <code>time:Instant</code> [[!OWL-TIME]].
</p>
- <img src="diagram-history/khalidDiagrams/startedAt.png" style="height: 3em" alt="startedAt links ProcessExecution to Instant"/>
+ <img src="diagram-history/khalidDiagrams/startedAt.png" style="height: 3em" alt="startedAt links Activity to Instant"/>
<div><b>Example</b></div>
- <p> Example of startedAt property is that a pe1 (instance of ProcessExecution 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 pe1 (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">
@@ -770,11 +770,11 @@
</section>
<section id="endedat">
<h4>endedAt</h4>
- <p> This object property defines the time when a <code>ProcessExecution</code> ended. The time is specified as an <code>time:Instant</code> [[!OWL-TIME]].
+ <p> This object property defines the time when a <code>Activity</code> ended. The time is specified as an <code>time:Instant</code> [[!OWL-TIME]].
</p>
- <img src="diagram-history/khalidDiagrams/endedAt.png" style="height: 3em" alt="endedAt links ProcessExecution to Instant"/>
+ <img src="diagram-history/khalidDiagrams/endedAt.png" style="height: 3em" alt="endedAt links Activity to Instant"/>
<div><b>Example</b></div>
- <p> Example of endedAt property is that a pe1 (instance of ProcessExecution 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 pe1 (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">
@@ -789,7 +789,7 @@
</section>
<section id="wasGeneratedat">
<h4>wasGeneratedAt</h4>
- <p> This object property defines the time when a <code>Entity</code> was generated by ProcessExecution.
+ <p> This object property defines the time when a <code>Entity</code> was generated by Activity.
</p>
<img src="diagram-history/khalidDiagrams/wasGeneratedAt.png" style="height: 3em" alt="wasGeneratedAt links Entity to Instant"/>
<div><b>Example</b></div>
@@ -873,9 +873,9 @@
<section id="hadqualifiedusage">
<h4>hadQualifiedUsage</h4>
- <p>The hadQualifiedUsage property links the ProcessExecution class with the Usage class.</p>
+ <p>The hadQualifiedUsage property links the Activity class with the Usage class.</p>
<img src="diagram-history/khalidDiagrams/hadQualifiedUsage.png"
- style="height: 3em" alt="hadQualifiedUsage links ProcessExecution to Usage" />
+ style="height: 3em" alt="hadQualifiedUsage links Activity to Usage" />
<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>
<div class="exampleOuter">
@@ -889,9 +889,9 @@
<section id="hadqualifiedparticipation">
<h4>hadQualifiedParticipation</h4>
- <p>The hadQualifiedParticipation property links the ProcessExecution class with the Participation class.</p>
+ <p>The hadQualifiedParticipation property links the Activity class with the Participation class.</p>
<img src="diagram-history/khalidDiagrams/hadQualifiedParticipation.png"
- style="height: 3em" alt="hadQualifiedParticipation links ProcessExecution to Participation" />
+ style="height: 3em" alt="hadQualifiedParticipation links Activity to Participation" />
<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>
<div class="exampleOuter">
@@ -905,9 +905,9 @@
<section id="hadqualifiedcontrol">
<h4>hadQualifiedControl</h4>
- <p>The hadQualifiedControl property links the ProcessExecution class with the Control class.</p>
+ <p>The hadQualifiedControl property links the Activity class with the Control class.</p>
<img src="diagram-history/khalidDiagrams/hadQualifiedControl.png"
- style="height: 3em" alt="hadQualifiedControl links ProcessExecution to Control" />
+ style="height: 3em" alt="hadQualifiedControl links Activity to Control" />
<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>
<div class="exampleOuter">
@@ -921,9 +921,9 @@
<section id="hadqualifiedgeneration">
<h4>hadQualifiedGeneration</h4>
- <p>The hadQualifiedGeneration property links the ProcessExecution class with the Generation class.</p>
+ <p>The hadQualifiedGeneration property links the Activity class with the Generation class.</p>
<img src="diagram-history/khalidDiagrams/hadQualifiedGeneration.png"
- style="height: 3em" alt="hadQualifiedGeneration links ProcessExecution to Generation" />
+ style="height: 3em" alt="hadQualifiedGeneration links Activity to Generation" />
<div><b>Example</b></div>
<p> Example of hadQualifiedGeneration property from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario"> provenance scenario </a> <i> e1 hadQualifiedGeneration g1</i>, where the hadRole describes the generation of e1 by "save". The RDF/XML syntax for asserting this is given below.</p>
<div class="exampleOuter">
@@ -1093,7 +1093,7 @@
<p>The example scenario can be encoded as a <a href = "http://www.w3.org/TR/rdf-primer/"> Resource Description Framework (RDF)</a>. For example,</p>
<ul>
<li>specialization of <a href="#agent">Agent</a> to define a class called Journalist, which has individuals such as alice, bob, and edith </li>
- <li><a href="#processexecution">ProcessExecution</a>, e.g. FileCreation, FileAppending, and FileEditing </li>
+ <li><a href="#activity">Activity</a>, e.g. FileCreation, FileAppending, and FileEditing </li>
<li>specialization of <a href="#entity">Entity</a> to define a class called CrimeFile, which has individuals such as e1, e2, and e3 </li>
</ul>
<p>Example given below describes the provenance of <a href="#entity">Entity</a> e2 using RDF/XML syntax</p>
@@ -1111,7 +1111,7 @@
<rdf:type rdf:resource="http://www.example.com/crime#CrimeFile"/>
<prov:wasGeneratedBy>
<rdf:Description rdf:about="http://www.example.com/crimeFile#pe1">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/ProcessExecution"/>
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Activity"/>
<rdf:type rdf:resource="http://www.example.com/crime#FileAppending"/>
<prov:wasControlledBy>
<rdf:Description rdf:about="http://www.example.com/crimeFile#Bob">
@@ -1149,7 +1149,7 @@
was a lot of crime in London last month.</cf:hasFileContent>
</rdf:Description>
<rdf:Description rdf:about="http://www.example.com/crimeFile#pe2">
- <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/ProcessExecution"/>
+ <rdf:type rdf:resource="http://www.w3.org/ns/prov-o/Activity"/>
<prov:used rdf:resource="http://www.example.com/crimeFile#e2"/>
</rdf:Description>
</rdf:RDF>
@@ -1186,29 +1186,29 @@
<p>The classes cf:FileCreation, cf:FileEditing,
cf:FileAppending, cf:Emailing, cf:SpellChecking are
specialization of the PROV ontology <a
- href="#processexecution">ProcessExecution</a> and model the
+ href="#activity">Activity</a> and model the
different activities in the <a
href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance
scenario</a>. The following RDF/XML code illustrates the
- specialization of the <a href="#processexecution">prov:ProcessExecution</a> to define class cf:FileCreation (other classes can be similarly defined by using the subClassOf property).</p>
+ specialization of the <a href="#activity">prov:Activity</a> to define class cf:FileCreation (other classes can be similarly defined by using the subClassOf property).</p>
<div class="exampleOuter">
<pre class="example">
<rdf:Description rdf:about="http://www.example.com/crime#FileCreation">
- <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov-o/ProcessExecution"/>
+ <rdfs:subClassOf rdf:resource="http://www.w3.org/ns/prov-o/Activity"/>
</rdf:Description>
</pre>
</div>
<p>The following diagram illustrates the above class specializations: </p>
<!--
- <img src="http://www.w3.org/2011/prov/wiki/images/5/5d/AlternativeSchema.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:Emailing, cf:Journalist) extend the classes in the PROV Ontology (Entity, Agent, ProcessExecution)."/>
- <a href="https://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.pdf"><img src="https://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:Emailing, cf:Journalist) extend the classes in the PROV Ontology (Entity, Agent, ProcessExecution)."/></a>
+ <img src="http://www.w3.org/2011/prov/wiki/images/5/5d/AlternativeSchema.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:Emailing, cf:Journalist) extend the classes in the PROV Ontology (Entity, Agent, Activity)."/>
+ <a href="https://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.pdf"><img src="https://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.classes.png" alt="New classes (cf:SpellChecking, cf:FileEditing, cf:FileCreation, cf:FileAppending, cf:Emailing, cf:Journalist) extend the classes in the PROV Ontology (Entity, Agent, Activity)."/></a>
<img src="examples/ontology-extensions/crime-file/diagrams/2011-10-13-ssoiland/crime.owl.png "
style="min-width: 45em; width: 55em; max-width: 95%"
- alt="New classes (:SpellChecking, :FileEditing, :FileCreation, :FileAppending, :Emailing, :Journalist) extend the classes in the PROV Ontology (prov:Entity, prov:Agent, prov:ProcessExecution). "/>
+ alt="New classes (:SpellChecking, :FileEditing, :FileCreation, :FileAppending, :Emailing, :Journalist) extend the classes in the PROV Ontology (prov:Entity, prov:Agent, prov:Activity). "/>
-->
<img src="examples/ontology-extensions/crime-file/diagrams/2011-10-13-ssoiland/crime.owl.classes.png "
style="min-width: 35em; width: 45em; max-width: 95%"
- alt="New classes (:SpellChecking, :FileEditing, :FileCreation, :FileAppending, :Emailing, :Journalist) extend the classes in the PROV Ontology (prov:Entity, prov:Agent, prov:ProcessExecution). "/>
+ alt="New classes (:SpellChecking, :FileEditing, :FileCreation, :FileAppending, :Emailing, :Journalist) extend the classes in the PROV Ontology (prov:Entity, prov:Agent, prov:Activity). "/>
<br>
<em>Example extension of PROV ontology in order to describe the crime file scenario</em>
</section>
@@ -1231,12 +1231,12 @@
<!--
<a href="https://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.pdf">
<img src="https://dvcs.w3.org/hg/prov/raw-file/631b9ae346a0/ontology/examples/ontology-extensions/crime-file/diagrams/2011-10-04-tlebo/crime.owl.properties.png"
- alt="ext:FileCreation, ext:FileAppending, ext:FileEditing, ext:Emailing, extSpellChecking extend prov:ProcessExecution; ext:Journalist extends prov:Agent; ext:CrimeFile extends prov:Entity; ext:hadFilePath extends prov:hadLocation and has range prov:Location."/>
+ alt="ext:FileCreation, ext:FileAppending, ext:FileEditing, ext:Emailing, extSpellChecking extend prov:Activity; ext:Journalist extends prov:Agent; ext:CrimeFile extends prov:Entity; ext:hadFilePath extends prov:hadLocation and has range prov:Location."/>
</a>
-->
<img src="examples/ontology-extensions/crime-file/diagrams/2011-10-13-ssoiland/crime.owl.properties.png "
style="min-width: 30em; width: 40em; max-width: 95%"
- alt="ext:FileCreation, ext:FileAppending, ext:FileEditing, ext:Emailing, extSpellChecking extend prov:ProcessExecution; ext:Journalist extends prov:Agent; ext:CrimeFile extends prov:Entity; ext:hadFilePath extends prov:hadLocation and has range prov:Location."/>
+ alt="ext:FileCreation, ext:FileAppending, ext:FileEditing, ext:Emailing, extSpellChecking extend prov:Activity; ext:Journalist extends prov:Agent; ext:CrimeFile extends prov:Entity; ext:hadFilePath extends prov:hadLocation and has range prov:Location."/>
<br>
<em>Example extension of PROV ontology in order to describe the crime file scenario</em>
</section>
@@ -1276,7 +1276,7 @@
style="width: 60%; min-width: 20em; max-width: 40em"
alt="New classes wf:WorkFlowEngine, wf:Process,
wf:ValueAtPort, wf:FileValue, and wf:Value extend prov:Agent,
- prov:ProcessExecution. New properties wf:wasLaunchedBy, wf:ranInWorkflowEngine, wf:wasSubProcessExecutionOf, wf:wasReadFrom, wf:sawValue extend prov:wasControlledBy, prov:wasDerivedFrom." />
+ prov:Activity. New properties wf:wasLaunchedBy, wf:ranInWorkflowEngine, wf:wasSubActivityOf, wf:wasReadFrom, wf:sawValue extend prov:wasControlledBy, prov:wasDerivedFrom." />
<br>
<em>Example extension of PROV ontology in order to describe
workflow provenance. This OWL ontology can be downloaded as
@@ -1297,7 +1297,7 @@
<dl>
<dt>wf:Process</dt>
<dd>
- A subclass of <i>prov:ProcessExecution</i> to
+ A subclass of <i>prov:Activity</i> to
signify an execution of a process which
<i>wf:wasDefinedBy</i> a
a <i>wf:ProcessDefinition</i>, e.g. a workflow or a
@@ -1379,7 +1379,7 @@
wf:ProcessDefinition in the specified
<i>wf:WorkflowEngine</i>.
</dd>
- <dt>wf:wasSubProcessExecutionOf</dt>
+ <dt>wf:wasSubActivityOf</dt>
<dd>
This subproperty of <i>prov:wasControlledBy</i> links a
<i>wf:Process</i> to another <i>prov:Process</i>, indicating
@@ -1619,7 +1619,7 @@
<Process rdf:about="#constant">
<wasDefinedBy rdf:resource="http://www.example.com/workflow1#String_Constant"/>
- <wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
+ <wasSubActivityOf rdf:resource="#workflowRun"/>
<prov:startedAt>
<time:Instant rdf:about="#t0">
<time:inDateTimeXSD>2011-10-21T09:20:15Z</time:inDateTimeXSD>
@@ -1642,7 +1642,7 @@
<Process rdf:about="#combine">
<wasDefinedBy rdf:resource="http://www.example.com/workflow1#cat"/>
- <wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
+ <wasSubActivityOf rdf:resource="#workflowRun"/>
<prov:startedAt rdf:parseType="Resource">
<time:inDateTimeXSD>2011-10-21T09:20:20Z</time:inDateTimeXSD>
</prov:startedAt>
@@ -1680,7 +1680,7 @@
</Process>
<Process rdf:about="#shasum">
<wasDefinedBy rdf:resource="http://www.example.com/workflow1#shasum"/>
- <wasSubProcessExecutionOf rdf:resource="#workflowRun"/>
+ <wasSubActivityOf rdf:resource="#workflowRun"/>
<prov:startedAt rdf:parseType="Resource">
<time:inDateTimeXSD>2011-10-21T09:20:30Z</time:inDateTimeXSD>
</prov:startedAt>
@@ -1791,36 +1791,36 @@
<section id = "entailments-supported-by-the-provenance-model">
<h3>Provenance-specific Entailments Supported by PROV Ontology</h3>
<p>The PROV-DM [[PROV-DM]] introduces a set of specific constraints applicable to PROV ontology. The following is a list of constraints that will be supported by the PROV ontology and any provenance application that uses the PROV ontology.</p>
- <section id="provenance-constraint-on-processexecution">
- <h4>Provenance constraint on ProcessExecution</h4>
- <p>The PROV-DM describes a constraint on ordering of time (or event) associated with a <a href="#processexecution">ProcessExecution.</a> </p>
+ <section id="provenance-constraint-on-activity">
+ <h4>Provenance constraint on Activity</h4>
+ <p>The PROV-DM describes a constraint on ordering of time (or event) associated with a <a href="#activity">Activity.</a> </p>
<div class='issue'>"From a process execution expression, one can infer that the start event precedes the end event of the represented activity." This is <a href="http://www.w3.org/2011/prov/track/issues/121">ISSUE-121</a></div>
</section>
<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 ProcessExecution that generated the Entity.</p>
+ <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>
</section>
<section id="provenance-constraint-on-wasgeneratedby-generation-pe-ordering">
<h4>Provenance constraint on wasGeneratedBy (generation-pe-ordering)</h4>
- <p>The second constraint on wasGeneratedBy associates an ordering of events associated with the generation of an Entity instance and the start, end time or event of the PE instance.</p>
- <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ <p>The second constraint on wasGeneratedBy associates an ordering of events associated with the generation of an Entity instance and the start, end time or event of theActivityinstance.</p>
+ <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> with the <a href="#entity">Entity</a> instance and <a href="#activity">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
</div>
</section>
<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 one PE instance can be associated to an Entity instance by the property wasGeneratedBy.</p>
+ <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>
</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 ProcessExecution instance by relation Used.
+ <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>
</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 ProcessExecution 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 pe by Used relation) to be "used" before pe 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>
</section>
@@ -1832,9 +1832,9 @@
</section>
<section id ="provenance-constraint-on-derivation-use-generation-ordering">
<h4>Provenance constraint on wasDerivedFrom (derivation-use-generation-ordering)</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), then the for time instant t1 associated with a PE instance that "used" is less than the time instant t2 associated with "generation" of e2.
+ <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), then the for time instant t1 associated with aActivityinstance that "used" is less than the time instant t2 associated with "generation" of e2.
</p>
- <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> with the <a href="#entity">Entity</a> instance and <a href="#activity">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
</div>
</section>
<section id ="provenance-constraint-on-derivation-events">
@@ -1846,7 +1846,7 @@
</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 some PE instance 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, pe) 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>
@@ -1862,7 +1862,7 @@
<h4>Provenance constraint on wasEventuallyDerivedFrom (derivation-generation-generation-ordering)</h4>
<p>The PROV-DM describes a constraint that if wasEventuallyDerivedFrom property is asserted between two Entity instances e1 and e2, then generation of e1 occurred before generation of e2.
</p>
- <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> (or event) with the <a href="#entity">Entity</a> instance and <a href="#processexecution">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
+ <div class='note'> Without an explicit association of <a href="#time">TemporalEntity</a> (or event) with the <a href="#entity">Entity</a> instance and <a href="#activity">PE</a> instance, it is not possible to state or enforce this constraint in the PROV ontology schema and the corresponding RDF dataset.
</div>
</section>
<section id ="provenance-constraint-on-derivation-linked-independent">
@@ -1881,7 +1881,7 @@
</section>
<section id ="provenance-constraint-on-hasParticipant-participant">
<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 ProcessExecution if the two instances are linked by "used" of "wasControlledBy" or "wasComplementOf".
+ <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:
*used(pe,e) holds, or