Added hadRecipe ISSUE-102
authorStian Soiland-Reyes <soiland-reyes@cs.manchester.ac.uk>
Wed, 28 Sep 2011 15:34:06 +0100
changeset 399 16935344d7c5
parent 397 9bb9bcddb036
child 400 8ec4363177ce
Added hadRecipe ISSUE-102
ontology/ProvenanceFormalModel.html
ontology/ProvenanceOntology.owl
--- a/ontology/ProvenanceFormalModel.html	Wed Sep 28 10:34:15 2011 +0100
+++ b/ontology/ProvenanceFormalModel.html	Wed Sep 28 15:34:06 2011 +0100
@@ -380,8 +380,22 @@
 		  <h4>preceded</h4>
 	      <p>preceded links two instances of ProcessExecution, where "Ordering of processes execution (in provenance) needs to be modeled as a property linking process entities in specific order along a particular dimension (temporal or control flow)"</p>
 		  <img src="http://www.w3.org/2011/prov/wiki/images/e/e5/Preceeded.png" />
-		  <div class='issue'>update picture above to show inverse property 'preceded'</div>
 	    </section>
+        <section>
+          <h4>hadRecipe</h4>
+          <p>The ProcessExecution activity performed was described by
+          the given recipe resource. Describing process specifications,
+          as referred to by recipe links, are out of scope of this
+          specification. A recipe can be anything from a cooking recipe
+          or textual document to a programmatic script or workflow
+          definition. It is not a requirement that the process execution
+          "went according to the plan", this property merely asserts that
+          the execution was attempting to follow the given recipe.
+          </p>
+          <img
+          src="http://www.w3.org/2011/prov/wiki/images/2/22/HadRecipe.png"
+          style="height: 4em" />
+        </section>
 	  </section>
 	  <section> 
 	  	<h3>Datatype Properties</h3>
@@ -582,14 +596,16 @@
             <dl>
                 <dt>wf:wasDefinedBy</dt>
                 <dd>
-                   This sub-property of <i>prov:recipe</i> (not yet
-                   defined in PROV ontology) links a
+                   This sub-property of <i>prov:recipe</i> 
+                   links a
                    <i>wf:Process</i> to the defining
                    <i>wf:ProcessDefinition</i>. Thus, if there are
                    multiple executions of the same workflow definition,
                    each of the separate <i>wf:Process</i>es will link to
                    the same definition.  
-                  <div class='issue'>Need prov:recipe in ontology -Stian</div>
+                  <div class='issue'>Need prov:recipe in ontology
+                  -Stian. This is <a
+                  href="http://www.w3.org/2011/prov/track/issues/102">ISSUE-102</a></div>
                   
                 </dd>
                 <dt>wf:ranInWorkflowEngine</dt>
@@ -648,7 +664,9 @@
                     entity to to have the same attributes, but in
                     addition the <i>wf:seenAtPort</i> property is fixed.
                   <div class='issue'>Should be subproperty of
-                  not-yet-existing prov:assumedBy -Stian</div>
+                  not-yet-existing prov:assumedBy or similar -Stian -
+                  part of <a
+                  href="http://www.w3.org/2011/prov/track/issues/103">ISSUE-103</a></div>
                  </dd>
 
                  <dt>wf:wasSeenAtPort</dt>
--- a/ontology/ProvenanceOntology.owl	Wed Sep 28 10:34:15 2011 +0100
+++ b/ontology/ProvenanceOntology.owl	Wed Sep 28 15:34:06 2011 +0100
@@ -147,6 +147,19 @@
         <rdfs:range rdf:resource="#ProcessExecution"/>
     </owl:ObjectProperty>
     
+    <owl:ObjectProperty rdf:about="#hadRecipe">
+        <rdf:type rdf:resource="&owl;AsymmetricProperty"/>
+        <!-- functional? <rdf:type rdf:resource="&owl;FunctionalProperty"/> -->
+        <rdf:type rdf:resource="&owl;IrreflexiveProperty"/>
+        <rdfs:label xml:lang="en"
+            >had recipe</rdfs:label>
+        <rdfs:comment xml:lang="en"
+            >The ProcessExecution activity performed was described by
+            the given recipe resource. Process specifications, as
+            referred to by recipe links, are out of scope of this
+            specification</rdfs:comment>
+        <rdfs:domain rdf:resource="#ProcessExecution"/>
+    </owl:ObjectProperty>
 
 
     <!-- 
@@ -184,6 +197,7 @@
     <owl:Class rdf:about="#Location">
         <rdfs:subClassOf rdf:resource="#Entity"/>
     </owl:Class>
+