--- a/model/ProvenanceModel.html	Fri Dec 09 07:58:45 2011 +0000
+++ b/model/ProvenanceModel.html	Fri Dec 09 08:03:30 2011 +0000
@@ -2522,6 +2522,16 @@
 <section id="record-RecipeLink">
 <h3>Recipe Link</h3>
 
+<div class="note">
+At the teleconference of 12/08/2012, the WG decided that the word Plan
+should be used, instead of recipe.  Given that a plan can change, it
+is useful to track its provenance. So a Plan is a kind of entity.
+Furthermore, a new relationship between activity and Plan is going to
+be introduced. This relationship is a specialization of
+wasAssociatedWith. By entailment, this makes a Plan an agent, since
+associated with an activity.
+</div>
+
 
 <p>A <dfn id="dfn-RecipeLink">recipe link</dfn> is an association between an activity record and a process specification that underpins the represented activity. Such IRI has no specific interpretation in the context of PROV-DM.
 </p>
@@ -2539,11 +2549,6 @@
 Process specifications, as referred to by recipe links, are out of scope of this specification.
 </p>
 
-<div class="note">
-By defining a recipe link as an IRI whose interpretation is out of
-scope of PROV-DM, we don't allow it to refer to an entity (in an
-inter-operable manner). Is this what we intend?
-</div>
 
 <div class='issue'> Simplify the references to recipe link. This is <a href="http://www.w3.org/2011/prov/track/issues/131">ISSUE-131</a></div>