--- a/model/ProvenanceModel.html Mon Dec 12 23:55:57 2011 +0000
+++ b/model/ProvenanceModel.html Tue Dec 13 10:42:45 2011 +0000
@@ -995,7 +995,7 @@
<p> An activity record, written <span class="name">activity(id, rl, st, et, [ attr1=val1, ...])</span> in PROV-ASN, contains:</p>
<ul>
<li><em>id</em>: an identifier <span class="name">id</span> identifying an activity; the identifier of the activity record is defined to be the same as the identifier of the activity;</li>
-<li><em>recipeLink</em>: an OPTIONAL <a href="#record-RecipeLink">recipe link</a> <span class="name">rl</span>, which consists of a domain specific specification of the activity;</li>
+<!--<li><em>recipeLink</em>: an OPTIONAL <a href="#record-RecipeLink">recipe link</a> <span class="name">rl</span>, which consists of a domain specific specification of the activity;</li>-->
<li><em>startTime</em>: an OPTIONAL time <span class="name">st</span> indicating the start of the activity;</li>
<li><em>endTime</em>: an OPTIONAL time <span class="name">et</span> indicating the end of the activity;</li>
<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs <span class="name">[ attr1=val1, ...]</span>, representing other attributes of this activity that hold for its whole duration.</li>
@@ -1011,8 +1011,10 @@
<span class="name">(</span>
<span class="nonterminal">identifier</span>
<span class="optional"><span class="name">,</span>
+<!--
<span class="nonterminal">recipeLink</span> </span>
<span class="name">,</span>
+-->
<span class="optional"><span class="nonterminal">time</span></span>
<span class="name">,</span>
<span class="optional"><span class="nonterminal">time</span></span>
@@ -1073,8 +1075,14 @@
<li><span class="name">Organization</span>: agents of type Organization are social institutions such as companies, societies etc. (This type is equivalent to a "foaf:organization" [[FOAF]])</li>
<li><span class="name">SoftwareAgent</span>: a software agent is a piece of software. </li>
</ul>
+<p>Furthermore, section <a href="#record-planLink">Plan Link Record</a>, introduces the idea of <em>plans</em> being associated with activities:</p>
+<ul>
+<li><span class="name">Plan</span>: agents of type <a >plan</a> are entities that represent a set of
+actions or steps intended to achieve some goal.</li>
+</ul>
<p>These types are mutually exclusive, though they do not cover all kinds of agent. </p>
+
<p>An agent record, noted <span class="name">agent(id, [ attr1=val1, ...])</span> in PROV-ASN, contains:</p>
<ul>
<li><em>id</em>: an identifier <span class="name">id</span> identifying an agent; the identifier of the agent record is defined to be the same as the identifier of the agent;</li>
@@ -1184,7 +1192,7 @@
<caption>PROV-DM Core Relation Summary</caption>
<tr><td></td><td>Entity</td><td>Activity</td><td>Agent</td><td>Note</td></tr>
<tr><td>Entity</td><td><a title="derivation record">wasDerivedFrom</a><br><a title="complementarity record">wasComplementOf</a></td><td><a title="generation record">wasGeneratedBy</a></td><td>-</td><td><a title="annotation record">hasAnnotation</a></td></tr>
-<tr><td>Activity</td><td><a title="usage record">used</a></td><td>-</td><td><a title="start record">wasStartedBy</a><br><a title="end record">wasEndedBy</a><br><a title="activity association record">wasAssociatedWith</a></td><td><a title="annotation record">hasAnnotation</a></td></tr>
+<tr><td>Activity</td><td><a title="usage record">used</a></td><td>-</td><td><a title="start record">wasStartedBy</a><br><a title="end record">wasEndedBy</a><br><a title="activity association record">wasAssociatedWith</a><br><a title="plan link record">hadPlan</a></td><td><a title="annotation record">hasAnnotation</a></td></tr>
<tr><td>Agent</td><td>-</td><td>-</td><td><a title="responsibility record">actedOnBehalfOf</a></td><td><a title="annotation record">hasAnnotation</a></td></tr>
<tr><td>Note</td><td>-</td><td>-</td><td>-</td><td><a title="annotation record">hasAnnotation</a></td></tr>
</table>
@@ -1486,12 +1494,72 @@
was started and ended by an agent, represented by record denoted by <span class="name">ah</span>, in "manual" mode, an application specific characterization of these relations.
</p>
</div>
-</section>
+
<div class="note">Temporal constraints for these relations remain to be
written. The temporal constraints should ensure that the agent started
its existence before the effect it may have on the activity. </div>
-
+</section>
+
+
+<section id="record-planLink">
+<h4>Plan Link Record</h4>
+
+<p>In the context of PROV-DM, a <dfn>plan</dfn> should be understood as a set of
+actions or steps intended to achieve some goal. PROV-DM is not
+prescriptive about the nature of plans, their representation, the
+actions and steps they consist of, and their intended goals. Hence,
+for the purpose of this specification, a plan can be a workflow for a
+scientific experiment, a recipe for a cooking activity, or a list of
+instructions for a micro-processor execution. While PROV-DM does not
+specify the representations of plans, it allows for activities to be
+associated with plans. Furthermore, since plans may evolve over time,
+it may become necessary to track their provenance, and hence, plans are
+entities. An activity MAY be associated with multiple plans. This
+allows for descriptions of activities initially associated with a
+plan, which was changed, on the fly, as the activity progresses. Plans
+can be successfully executed or they can fail. We expect applications
+to exploit PROV-DM <a href="#extensibility-section">extensibility
+mechanisms</a> to capture the rich nature of plans and associations
+between activities and plans.</p>
+
+
+<p>A
+<dfn>plan link record</dfn> is a representation of an association
+between an activity and a plan. It is a specialization of
+an <a>activity association record</a>. Hence, a plan is also a PROV-DM
+agent, by virtue of being associated with an activity (cf. constraint <a href="#association-agent">association-agent</a>).</p>
+
+
+
+
+<p>A plan link record, written <span class="name">hadPlan(id,a,e,attrs)</span> in PROV-ASN, contains:</p>
+<ul>
+<li><em>id</em>: an OPTIONAL identifier <span class="name">id</span> identifying the plan link record;</li>
+<li><em>activity</em>: an identifier <span class="name">a</span> denoting an activity record;
+<li><em>e</em>: an identifier <span class="name">e</span> for an entity, representing a plan;
+<li><em>attributes</em>: an OPTIONAL set of attribute-value pairs <span class="name">attrs</span>, describing modalities of this relation.
+</ul>
+
+
+<div class='grammar'>
+<span class="nonterminal">planLink</span> ::=
+<span class="name">hadPlan</span>
+<span class="name">(</span>
+<span class="optional"> <span class="nonterminal">identifier</span>,</span>
+<span class="nonterminal">aIdentifier</span>,
+<span class="nonterminal">eIdentifier</span>
+<span class="nonterminal">optional-attribute-values</span>
+<span class="name">)</span>
+</div>
+
+
+<div class="note">
+Need an example. Can we introduce an example of plan in the File example?
+Maybe: email file hadPlan "Communication Strategy"?
+</div>
+
+</section>
<!--
@@ -2520,6 +2588,7 @@
</section>
+<!--
<section id="record-RecipeLink">
<h3>Recipe Link</h3>
@@ -2555,7 +2624,7 @@
</section>
-
+-->
@@ -3029,7 +3098,7 @@
<span class="name">e</span> and <span class="name">ag</span>,
<span class='conditional'>then</span> there exists an activity identified by <span class="name">pe</span> such that the following statements hold:
<pre>
-activity(pe,recipe,t1,t2,attr1)
+activity(pe,t1,t2,attr1)
wasGenerateBy(e,pe)
wasAssociatedWith(pe,ag,attr2)
</pre>
@@ -3435,6 +3504,7 @@
<section class="appendix">
<h2>Changes Since Second Public Working Draft</h2>
<ul>
+<li>12/13/11: Introduced hadPlan as a specialization of wasAssociatedWith. </li>
<li>12/12/11: Section 7 on interpretation. </li>
<li>12/08/11: Restructuring of Constraints. </li>
</ul>