--- a/ontology/ProvenanceFormalModel.html Tue Jan 17 12:07:20 2012 +0000
+++ b/ontology/ProvenanceFormalModel.html Tue Jan 17 12:57:27 2012 +0000
@@ -520,21 +520,55 @@
</section>
</section>
- <section id="recipe">
- <h4>Recipe</h4>
+ <section id="plan">
+ <h4>Plan</h4>
<div><b>Class Description</b></div>
- <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>
+ <p>A <em>Plan</em> is a special kind of <a href="#entity">Entity</a>
+ which represents the rules or specification that guided
+ an <a href="#agent">Agent</a>'s association with an <a
+ href="#activity">Activity</a>. The plan is linked to the <a
+ href="#Control">Association</a> using <a
+ href="#adoptedplan">prov:adoptedPlan</a>. The
+ PROV ontology does not put any restrictions on the plan
+ beyond it being a characterised <em>entity</em> (e.g. it
+ must have been generated before the end of the agent's
+ association of the activity).
+ </p>
+ <p>
+ A plan can can be anything from
+ a cooking recipe or a film script to a formal specification
+ or programmatic source code. Note that it is also not a
+ requirement that the agent's involvement with the activity
+ went according to the plan.
+ </p>
+ <div class="note">
+ This text assumes <em>Control</em> and friends has been
+ renamed to <em>Association</em> to match PROV-DM
+ <em>wasAssociatedWith()</em>.
+ </div>
+ <div><b>OWL syntax</b></div>
+ <pre>prov:Plan rdfs:subClassOf prov:Entity.</pre>
<div class="anexample">
<div><b>Example</b></div>
- <p>An example of recipe from the <a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">provenance scenario </a>may be the editing protocol followed by the journalists to edit a news report.
+ <p>An example of a plan from the <a
+ href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">file
+ scenario</a> is the <em>editing protocol</em> followed by the
+ journalist Edith.
<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/Activity"/>
- <prov:hadRecipe rdf:resource="http://www.example.com/crimeFile#NewsReportEditingProtocol"/>
- </rdf:Description>
+ <prov:Activity rdf:about="http://www.example.com/crimeFile#news_editing">
+ <prov:wasAssociatedWith>
+ <prov:Agent rdf:about="http://www.example.com/crimeFile#Edith">
+ </prov:wasAssociatedWith>
+ <prov:hadQualifiedAssociation>
+ <prov:Association>
+ <prov:hadQualifiedEntity rdf:resource="http://www.example.com/crimeFile#Edith" />
+ <strong><prov:adoptedPlan>
+ <prov:Plan rdf:about="http://www.example.com/crimeFile#NewsReportEditingProtocol" />
+ <prov:adoptedPlan></strong>
+ </prov:Association>
+ </prov:wasAssociatedWith>
+ </rdf:Description>
</pre>
</div>
</div>
@@ -795,23 +829,55 @@
- <section id="hadrecipe">
- <h4>hadRecipe</h4>
- <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.
+ <section id="adoptedplan">
+ <h4>adoptedPlan</h4>
+ <p>This property links the a <a href="#plan">Plan</a> with an
+ <a href="#control">Association</a>, specifying that the
+ associated <a href="#Agent">Agent</a> <em>adopted the
+ plan</em> in its
+ involvement with the activity. The plan might or might not
+ have been followed exactly, but was in some
+ way informing the activity. Note that
+ <code>prov:adoptedPlan</code> is distinct from specifying <a
+ href="#role">hadRole</a> in
+ the <code>prov:Association</code>, which could specify which role the agent
+ assumed when adopting the plan.
</p>
+ <div class="note">
+ This text assumes <em>Control</em> and friends has been
+ renamed to <em>Association</em> to match PROV-DM
+ <em>wasAssociatedWith()</em>.
+ </div>
<img src="diagrams/hadRecipe.png"
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 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#act1">
- <prov:hadRecipe rdf:resource="http://www.example.com/crimeFile#instructions1"/>
- </rdf:Description>
- </pre>
- </div>
- </div>
+ <pre>prov:Plan rdfs:subClassOf prov:Entity.</pre>
+
+ <div class="anexample">
+ <div><b>Example</b></div>
+ <p>An example of <code>prov:adoptedPlan</code> from the <a
+ href="http://www.w3.org/TR/2011/WD-prov-dm-20111018/#a-file-scenario">file
+ scenario</a> is the <em>editing protocol</em> followed by the
+ journalist Edith.
+ <div class="exampleOuter">
+ <pre class="example">
+ <prov:Activity rdf:about="http://www.example.com/crimeFile#news_editing">
+ <prov:wasAssociatedWith>
+ <prov:Agent rdf:about="http://www.example.com/crimeFile#Edith">
+ </prov:wasAssociatedWith>
+ <prov:hadQualifiedAssociation>
+ <prov:Association>
+ <prov:hadQualifiedEntity rdf:resource="http://www.example.com/crimeFile#Edith" />
+ <strong><prov:adoptedPlan>
+ <prov:Plan rdf:about="http://www.example.com/crimeFile#NewsReportEditingProtocol" />
+ <prov:adoptedPlan></strong>
+ </prov:Association>
+ </prov:wasAssociatedWith>
+ </rdf:Description>
+ </pre>
+ </div>
+ </div>
</section>