Mercurial > hg > prov / changeset
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset
changed intro and restaged
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Thu, 22 Nov 2012 21:30:39 +0000
changeset 4936 beac6b568c21
parent 4935 567c1318c375
child 4937 a1c32174d82e
changed intro and restaged
model/diff-c.html
model/diff-n.html
model/diff.html
model/prov-constraints.html
model/prov-dm.html
model/prov-n.html
model/releases/CR-prov-constraints-20121211/Overview.html
model/releases/CR-prov-constraints-20121211/diff-c.html
model/releases/CR-prov-dm-20121211/Overview.html
model/releases/CR-prov-dm-20121211/diff.html
model/releases/CR-prov-n-20121211/Overview.html
model/releases/CR-prov-n-20121211/diff-n.html 
--- a/model/diff-c.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/diff-c.html	Thu Nov 22 21:30:39 2012 +0000
@@ -1721,11 +1721,12 @@
 <li>Readers seeking to implement other PROV serializations
 should focus on PROV-DM and PROV-CONSTRAINTS.  PROV-O and PROV-N offer examples of mapping to RDF and text, respectively.</li>
 </ul>
-
-
-
-
-        <p>
+<h4 id="please-comment-by-january-31-2013"><span class="insert">Please Comment By January 31, 2013</span></h4>
+
+<span class="insert">The PROV Working Group seeks to gather experience from </span><a href="http://www.w3.org/2011/prov/wiki/ProvImplementations"><span class="insert">implementations</span></a><span class="insert"> in order to increase confidence in the specifications and meet specific </span><a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria"><span class="insert">exit criteria</span></a><span class="insert">. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request </span><a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR"><span class="insert">Proposed Recommendation</span></a><span class="insert"> status.
+
+
+        </span><p>
           This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a <span class="delete">Last Call Working Draft. </span><span class="insert">Candidate Recommendation.
           
             </span>This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. 
@@ -5248,7 +5249,7 @@
 <span class="name">'agent' ∈ typeOf(ag)</span>.
 </li><li>
 <span class="conditional">IF</span> 
-   <span class="name">activity(a,attrs)</span>  
+   <span class="name"><span class="delete">activity(a,attrs)</span><span class="insert">activity(a,t1,t2,attrs)</span></span>  
 <span class="conditional">THEN</span> 
 <span class="name">'activity' ∈ typeOf(a)</span>.
 
@@ -5399,9 +5400,9 @@
 </li><li>
 
 <span class="conditional">IF</span> 
-   <span class="name"><span class="delete">hadMember(c,e)</span>  
-<span class="delete">THEN</span> 
-<span class="delete">'prov:Collection' ∈ typeOf(c)</span><span class="delete"> AND
+   <span class="name"><span class="delete">hadMember(c,e)</span><span class="insert">entity(c,[prov:type='prov:EmptyCollection'])</span></span>  
+<span class="conditional">THEN</span> 
+<span class="name"><span class="delete">'prov:Collection' ∈ typeOf(c)</span><span class="delete"> AND
 </span><span class="delete">'entity' ∈ typeOf(c)</span><span class="delete"> AND
 </span><span class="delete">'entity' ∈ typeOf(e)</span><span class="delete">.
 
@@ -5409,10 +5410,10 @@
 </span>
 
 <span class="delete">IF</span> 
-   entity(c,[prov:type='prov:EmptyCollection'])</span>  
-<span class="conditional">THEN</span> 
-<span class="name">'entity' ∈ typeOf(c)</span>  AND
-<span class="name">'prov:Collection' ∈ typeOf(c)</span>AND
+   <span class="delete">entity(c,[prov:type='prov:EmptyCollection'])</span>  
+<span class="delete">THEN</span> 
+'entity' ∈ typeOf(c)</span>  AND
+<span class="name">'prov:Collection' ∈ typeOf(c)</span> AND
 <span class="name">'prov:EmptyCollection' ∈ typeOf(c)</span>.
 
 </li></ol>
@@ -5542,7 +5543,7 @@
 <span class="name">actedOnBehalfOf</span>}, the following
   impossibility constraint holds:</p>
 
-<p>    <span class="conditional">IF</span> <span class="name">p(id,a<sub>1</sub>,...,a<sub>n</sub>)</span> and
+<p>    <span class="conditional">IF</span> <span class="name">p(id,a<sub>1</sub>,...,a<sub><span class="delete">n</span><span class="insert">m</span></sub>)</span> and
   <span class="name">r(id; b<sub>1</sub>,...,b<sub>n</sub>)</span> <span class="conditional">THEN INVALID</span>.
   </p>
   </div>
--- a/model/diff-n.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/diff-n.html	Thu Nov 22 21:30:39 2012 +0000
@@ -1,4 +1,3 @@
-
 <!DOCTYPE html>
 <html lang="en" dir="ltr">
 <head><style type="text/css"><!--
@@ -1724,7 +1723,12 @@
 </ul>
 
 
-        <p>
+<h4 id="please-comment-by-january-31-2013"><span class="insert">Please Comment By January 31, 2013</span></h4><span class="insert">
+
+The PROV Working Group seeks to gather experience from </span><a href="http://www.w3.org/2011/prov/wiki/ProvImplementations"><span class="insert">implementations</span></a><span class="insert"> in order to increase confidence in the specifications and meet specific </span><a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria"><span class="insert">exit criteria</span></a><span class="insert">. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request </span><a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR"><span class="insert">Proposed Recommendation</span></a><span class="insert"> status.
+
+
+        </span><p>
           This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a <span class="delete">Last Call Working Draft. </span><span class="insert">Candidate Recommendation.
           
             </span>This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. 
@@ -3974,7 +3978,7 @@
     <p>The Internet Media Type / MIME Type for PROV-N is "text/provenance-notation".</p> 
     <p>It is recommended that PROV-N files have the extension ".provn" (all lowercase) on all platforms.</p> 
     <p>It is recommended that PROV-N files stored on Macintosh HFS file systems be given a file type of "TEXT".</p> 
-    <p><span class="delete">This</span><span class="insert">The</span> information that follows <span class="delete">is being </span><span class="insert">has been </span><a href="TBD">submitted to the IESG</a> for review, approval, and registration with IANA.</p> 
+    <p><span class="delete">This</span><span class="insert">The</span> information that follows <span class="delete">is being </span><span class="insert">has been </span><a href="https://lists.w3.org/Archives/Member/w3c-archive/2012Nov/0317.html">submitted to the IESG</a> for review, approval, and registration with IANA.</p> 
     <dl> 
       <dt>Type name:</dt> 
       <dd>text</dd> 
--- a/model/diff.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/diff.html	Thu Nov 22 21:30:39 2012 +0000
@@ -1660,9 +1660,6 @@
       <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</span></a></dd>
     
     
-      <dt><span class="insert">Test suite:</span></dt>
-      <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html</span></a></dd>
-    
     
       <dt><span class="insert">Implementation report:</span></dt>
       <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html</span></a></dd>
@@ -1798,7 +1795,13 @@
 </ul>
 
 
-        <p>
+<h4 id="please-comment-by-january-31-2013"><span class="insert">Please Comment By January 31, 2013</span></h4><span class="insert">
+
+The PROV Working Group seeks to gather experience from </span><a href="http://www.w3.org/2011/prov/wiki/ProvImplementations"><span class="insert">implementations</span></a><span class="insert"> in order to increase confidence in the specifications and meet specific </span><a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria"><span class="insert">exit criteria</span></a><span class="insert">. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request </span><a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR"><span class="insert">Proposed Recommendation</span></a><span class="insert"> status.
+
+
+
+        </span><p>
           This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a <span class="delete">Last Call Working Draft. </span><span class="insert">Candidate Recommendation.
           
             </span>This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. 
@@ -1918,7 +1921,7 @@
 </li><li> component 2: derivations of entities from others;
 </li><li> component 3: agents bearing responsibility for entities that were generated and activities that happened;
 </li><li> component 4: bundles, a mechanism to support provenance of provenance;
-</li><li> component 5: properties to link entities that refer to a same thing;
+</li><li> component 5: properties to link entities that refer to <span class="delete">a</span><span class="insert">the</span> same thing;
 </li><li> component 6: collections forming a logical structure for its members.
 </li></ul>
 
@@ -2208,7 +2211,7 @@
 This is answered by
 considering that a single artifact may
 correspond to several entities; in this case, a car in Boston may be a
-different entity from a car in Cambridge.  
+different entity from the same car in Cambridge.  
 Thus, among other things,
 an entity "car in Boston" would be used, and a new entity "car in
 Cambridge" would be generated by this activity of driving.  The
@@ -2410,7 +2413,7 @@
 <p>Subtyping can be applied to core types. For example, a software agent is special kind of agent, defined as follows.</p>
 
 <span class="glossary-ref">
-   A <span class="dfn">software agent</span>  is running software. </span>
+   A <span class="dfn"><span class="delete">software agent</span><span class="insert">SoftwareAgent</span></span>  is running software. </span>
 
 
 <p>Subtyping can also be applied to  core relations. For example, a revision is a special kind of derivation, defined as follows.</p>
@@ -2533,7 +2536,7 @@
 <h4><span class="secno">2.2.3 </span>Collections</h4>
 
 <p>
-<span class="glossary-ref">   A <span class="dfn">collection</span> is an entity that provides a structure to some <span class="delete">constituents, which are</span><span class="insert">constituents that must</span> themselves<span class="insert"> be</span> entities. These constituents are said to be <span class="dfn">member of</span> the collections.  </span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>. 
+<span class="glossary-ref">   A <span class="dfn">collection</span> is an entity that provides a structure to some <span class="delete">constituents, which are</span><span class="insert">constituents that must</span> themselves<span class="insert"> be</span> entities. These constituents are said to be <span class="dfn">member<span class="delete"> of</span></span><span class="insert"> of</span> the collections.  </span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>. 
 Using Collections, one can express the provenance of the collection itself in addition to that of the members.  </p>
 
 <div class="anexample conceptexample" id="collection-example"><div class="anexampleTitle">Example <span class="delete">14</span><span class="insert">15</span><sup><a class="internalDFN" href="#collection-example"><span class="diamond"> ◊</span></a></sup></div>
@@ -2565,7 +2568,7 @@
 <tbody><tr><td style="border-width: 0px; "></td><td>Component</td><td>Core <br>Structures</td><td>Overview</td><td>Specification</td><td>Description</td></tr> 
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 <tr><td style="	padding: 8px;">1</td><td style="text-align: left;">Entities and Activities</td><td>✔</td><td><a href="#section-entity-activity">2.1.1</a></td><td><a href="#component1">5.1</a></td><td style="text-align: left;">about entities and activities, and their interrelations</td></tr> 
-<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component3">5.2</a></td><td style="text-align: left;">about derivations and its subtypes</td></tr> 
+<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component3">5.2</a></td><td style="text-align: left;">about <span class="delete">derivations</span><span class="insert">derivation</span> and its subtypes</td></tr> 
 <tr><td>3</td><td style="text-align: left;">Agent and Responsibility</td><td>✔</td><td><a href="#section-agents-attribution-association-delegation">2.1.3</a></td><td><a href="#component2">5.3</a></td><td style="text-align: left;">about agents and concepts ascribing responsibility to them</td></tr> 
 <tr><td>4</td><td style="text-align: left;">Bundles</td><td></td><td><a href="#section-provenance-of-provnance">2.2.2</a></td><td><a href="#component4">5.4</a></td><td style="text-align: left;">about bundles, a mechanism to support provenance of provenance</td></tr> 
 <tr><td>5</td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><a href="#component5">5.5</a></td><td style="text-align: left;">about relations linking entities referring the same thing</td></tr> 
@@ -2732,7 +2735,7 @@
 </p>
 
 <p>
-We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined <span class="delete">URIs</span><span class="insert">IRIs</span> (some of which refer archived email messages, available to <abbr title="World Wide Web Consortium">W3C</abbr> Members).</p>
+We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined <span class="delete">URIs</span><span class="insert">IRIs</span> (some of which refer <span class="insert">to </span>archived email messages, available to <abbr title="World Wide Web Consortium">W3C</abbr> Members).</p>
 
 <ul>
 <li> Two versions of a document were involved: <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft);</li>
@@ -2786,9 +2789,10 @@
 </pre>
 </li>
 
-<li>The activity was associated with the Consortium agent, and proceeded according to its publication policy: this is an <a title="concept-activityAssociation">Activity Association</a>.
+<li>The activity was associated with the Consortium agent, and proceeded according to its publication policy: this is an <span class="delete">Activity </span><a title="concept-association">Association</a>.
 <pre>wasAssociatedWith(ex:act2, w3:Consortium, process:rec-advance)
-</pre>
+</pre><span class="insert">
+This relation is illustrated in </span><a href="#prov-a-document2-top" class="fig-ref"><span class="insert">Figure 3</span></a><span class="insert"> with a multi-edge labelled </span><span class="name"><span class="insert">wasAssociatedWith</span></span><span class="insert"> pointing to an agent and entity (representing a plan).</span>
 </li>
 </ul>
 
@@ -3267,7 +3271,7 @@
 
 <div class="anexample" id="anexample-start3"><div class="anexampleTitle">Example <span class="delete">24</span><span class="insert">25</span><sup><a class="internalDFN" href="#anexample-start3"><span class="diamond"> ◊</span></a></sup></div>
 <p>
-In this example, filling fuel was started as a consequence of
+In this example, filling <span class="insert">the </span>fuel<span class="insert"> tank</span> was started as a consequence of
 observing low fuel. The trigger entity is unspecified, it could
 for instance have been the low fuel warning light, the fuel tank
 indicator needle position, or the engine not running properly.
@@ -3348,7 +3352,7 @@
 </li></ul>
 <p>In the first two cases, the entity has physically disappeared after its termination: there is no more soup, or painting.  In the <span class="delete">last three cases,</span><span class="insert">third case,</span> there may be an "offer voucher" that still exists, but it is no longer valid; likewise, on April 4th, the BBC news site still exists but it is not the same entity as BBC news Web site on April 3rd; or the<span class="insert"> 
 green</span> traffic light <span class="insert">(an entity with a fixed aspect green light) </span>became <span class="insert">the
-</span>red <span class="delete">and therefore is regarded as</span><span class="insert">traffic light (anohter entity with</span> a <span class="delete">different entity to the green light.</span><span class="insert">fixed aspect red light).</span>
+</span>red <span class="delete">and therefore is regarded as</span><span class="insert">traffic light (another entity with</span> a <span class="delete">different entity to the green light.</span><span class="insert">fixed aspect red light).</span>
 </p>
 
 
@@ -3698,7 +3702,7 @@
 There are three types of agents that are common across most anticipated domains of use; it is acknowledged that these types do not cover all kinds of agent. </p>
 <ul>
 <li><span class="name">SoftwareAgent</span>
-<div class="glossary-ref">   A <dfn id="concept-software-agent" title="software-agent" class="internalDFN">software agent</dfn><sup><a class="internalDFN" href="#concept-software-agent"><span class="diamond"> ◊</span></a></sup>  is running software. </div>
+<div class="glossary-ref">   A <dfn id="concept-software-agent" title="software-agent" class="internalDFN"><span class="delete">software agent</span><span class="insert">SoftwareAgent</span></dfn><sup><a class="internalDFN" href="#concept-software-agent"><span class="diamond"> ◊</span></a></sup>  is running software. </div>
 
 <p></p></li>
 
@@ -3768,13 +3772,13 @@
 <section id="term-Association">
 <h4><span class="secno">5.3.3 </span>Association</h4>
 
-<div class="glossary-ref">   An activity <dfn id="concept-activityAssociation" class="internalDFN">association</dfn><sup><a class="internalDFN" href="#concept-activityAssociation"><span class="diamond"> ◊</span></a></sup> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </div>
+<div class="glossary-ref">   An activity <dfn id="concept-association" class="internalDFN">association</dfn><sup><a class="internalDFN" href="#concept-association"><span class="diamond"> ◊</span></a></sup> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </div>
 
 <p></p>
 <div class="glossary-ref">   A <dfn id="concept-plan" class="internalDFN">plan</dfn><sup><a class="internalDFN" href="#concept-plan"><span class="diamond"> ◊</span></a></sup> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals.  </div>
 
 
-<p></p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith" id="dfn-wasassociatedwith" class="internalDFN">activity association</dfn><sup><a class="internalDFN" href="#dfn-wasassociatedwith"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id; a, ag, pl, attrs)</span> in PROV-N,</span> has:
+<p></p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith" id="dfn-wasassociatedwith" class="internalDFN"><span class="delete">activity </span>association</dfn><sup><a class="internalDFN" href="#dfn-wasassociatedwith"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id; a, ag, pl, attrs)</span> in PROV-N,</span> has:
 <ul>
 <li><span class="attribute" id="association.id">id</span>:  an <em class="rfc2119" title="optional">optional</em> identifier for the association between an activity and an agent;</li> 
 <li><span class="attribute" id="association.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity;</li>
@@ -3879,9 +3883,9 @@
 on  <span class="name">o1</span> that signifies some form of influence of <span class="name">o1</span> on <span class="name">o2</span>.</p>
 
 
-<p>
-</p><div class="attributes" id="attributes-influence">
-A <dfn title="wasInfluencedBy" id="dfn-wasinfluencedby" class="internalDFN">Influence</dfn><sup><a class="internalDFN" href="#dfn-wasinfluencedby"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">wasInfluencedBy(id; o2, o1, attrs)</span> in PROV-N,</span> has:
+<p><span class="delete">A</span>
+</p><div class="attributes" id="attributes-influence"><span class="insert">
+An</span> <dfn title="wasInfluencedBy" id="dfn-wasinfluencedby" class="internalDFN">Influence</dfn><sup><a class="internalDFN" href="#dfn-wasinfluencedby"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">wasInfluencedBy(id; o2, o1, attrs)</span> in PROV-N,</span> has:
 <ul>
 <li><span class="attribute" id="influence.id">id</span>:  an <em class="rfc2119" title="optional">optional</em> identifier identifying the relation;</li> 
 <li><span class="attribute" id="influence.influencee">influencee</span>:  an identifier (<span class="name">o2</span>) for an entity, activity, or agent;
@@ -3890,14 +3894,14 @@
 </ul></div>
 
 <p>
-<a href="#concept-usage" class="internalDFN">Usage</a>, <a>start</a>, <a>end</a>, <a>generation</a>, <a>invalidation</a>, <a>communication</a>, <a href="#concept-derivation" class="internalDFN">derivation</a>, <a>attribution</a>, <a href="#concept-activityAssociation" class="internalDFN">association</a>, and <a>delegation</a> are <span class="delete">particular cases of  influence.</span><span class="insert">also </span><a><span class="insert">influence</span></a><span class="insert">.</span> It is <em class="rfc2119" title="recommended">recommended</em> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a href="#concept-influence" class="internalDFN">Influence</a> relation may be useful to express queries over provenance information.
+<span class="insert">A </span><a href="#concept-usage" class="internalDFN">Usage</a>, <a>start</a>, <a>end</a>, <a>generation</a>, <a>invalidation</a>, <a>communication</a>, <a href="#concept-derivation" class="internalDFN">derivation</a>, <a>attribution</a>, <a href="#concept-association" class="internalDFN">association</a>, and <a>delegation</a> <span class="delete">are particular cases of  influence.</span><span class="insert">is also an </span><a><span class="insert">influence</span></a><span class="insert">.</span> It is <em class="rfc2119" title="recommended">recommended</em> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a href="#concept-influence" class="internalDFN">Influence</a> relation may be useful to express queries over provenance information.
 </p>
 
 
 <div id="mapping-relations-to-influence-table_text" style="text-align: left;"><span class="insert">
 The following table establishes the correspondence between 
 the attributes </span><a class="attribute" href="#influence.influencee"><span class="insert">influencee</span></a><span class="insert"> and </span><a class="attribute" href="#influence.influencer"><span class="insert">influencer</span></a><span class="insert">, and attributes of
-</span><a><span class="insert">usage</span></a><span class="insert">, </span><a><span class="insert">start</span></a><span class="insert">, </span><a><span class="insert">end</span></a><span class="insert">, </span><a><span class="insert">generation</span></a><span class="insert">, </span><a><span class="insert">invalidation</span></a><span class="insert">, </span><a><span class="insert">communication</span></a><span class="insert">, </span><a href="#concept-derivation" class="internalDFN"><span class="insert">derivation</span></a><span class="insert">, </span><a><span class="insert">attribution</span></a><span class="insert">, </span><a href="#concept-activityAssociation" class="internalDFN"><span class="insert">association</span></a><span class="insert">, and </span><a><span class="insert">delegation</span></a><span class="insert">.</span>
+</span><a><span class="insert">usage</span></a><span class="insert">, </span><a><span class="insert">start</span></a><span class="insert">, </span><a><span class="insert">end</span></a><span class="insert">, </span><a><span class="insert">generation</span></a><span class="insert">, </span><a><span class="insert">invalidation</span></a><span class="insert">, </span><a><span class="insert">communication</span></a><span class="insert">, </span><a href="#concept-derivation" class="internalDFN"><span class="insert">derivation</span></a><span class="insert">, </span><a><span class="insert">attribution</span></a><span class="insert">, </span><a href="#concept-association" class="internalDFN"><span class="insert">association</span></a><span class="insert">, and </span><a><span class="insert">delegation</span></a><span class="insert">.</span>
 
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <caption id="mapping-relations-to-influence-table"><span><span class="insert">Table 7</span><sup><a class="internalDFN" href="#mapping-relations-to-influence-table"><span class="diamond"><span class="insert"> ◊:</span></span></a></sup> </span><span class="insert">Mapping Relations to Influence</span></caption> 
@@ -4156,7 +4160,7 @@
 
 
 
-<p><span class="insert">Specialization is not  defined as Influence, and therefore does not have an id and attributes.</span></p>
+<p><span class="insert">A specialization is not, as  defined here, also an influence, and therefore does not have an id and attributes.</span></p>
 
 
 
@@ -4199,7 +4203,7 @@
 </ul>
 </div>
 
-<p><span class="insert">Alternate is not  defined as Influence, and therefore does not have an id and attributes.</span></p>  
+<p><span class="insert">An alternate is not, as  defined  here, also an influence, and therefore does not have an id and attributes.</span></p>  
 
 <p><span class="insert">
 Note that </span><a title="alternateOf" href="#dfn-alternateof" class="internalDFN"><span class="insert">alternateOf</span></a><span class="insert"> is a necessarily very general
@@ -4230,7 +4234,7 @@
 
 <div class="anexample" id="anexample-alternate2"><div class="anexampleTitle">Example <span class="delete">44</span><span class="insert">45</span><sup><a class="internalDFN" href="#anexample-alternate2"><span class="diamond"> ◊</span></a></sup></div>
 <p>
-Considering again the two versions of the technical report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft). They are alternate of each other.
+Considering again the two versions of the technical report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft). They are <span class="delete">alternate</span><span class="insert">alternates</span> of each other.
 </p><pre class="codeexample">entity(tr:WD-prov-dm-20111018)
 entity(tr:WD-prov-dm-20111215)
 <span class="delete">alternateOf(tr:WD-prov-dm-20111018,tr:WD-prov-dm-20111215)</span><span class="insert">alternateOf(tr:WD-prov-dm-20111018, tr:WD-prov-dm-20111215)</span>
@@ -4389,7 +4393,7 @@
 <section id="term-collection">
 <h4><span class="secno">5.6.1 </span>Collection</h4>
 
-<span class="glossary-ref">   A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some <span class="delete">constituents, which are</span><span class="insert">constituents that must</span> themselves<span class="insert"> be</span> entities. These constituents are said to be <dfn id="dfn-member-of" class="internalDFN">member of</dfn><sup><a class="internalDFN" href="#dfn-member-of"><span class="diamond"> ◊</span></a></sup> the collections.  </span>
+<span class="glossary-ref">   A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some <span class="delete">constituents, which</span><span class="insert">constituents that must themselves be entities. These constituents</span> are <span class="delete">themselves entities. These constituents are </span>said to be <dfn id="dfn-member" class="internalDFN">member<span class="delete"> of</span></dfn><sup><a class="internalDFN" href="#dfn-member"><span class="diamond"> ◊</span></a></sup><span class="insert"> of</span> the collections.  </span>
 
 <span class="glossary-ref">   An <dfn id="concept-empty-collection" class="internalDFN">empty collection</dfn><sup><a class="internalDFN" href="#concept-empty-collection"><span class="diamond"> ◊</span></a></sup> is a collection without members.  </span>
 
@@ -4418,7 +4422,7 @@
 <section id="term-membership">
 <h4><span class="secno">5.6.2 </span>Membership</h4>
 
-<p>A <strong>membership</strong> relation is defined, to allow stating the  members of a Collection. </p>
+<p>A <strong>membership</strong> relation is <span class="delete">defined, to allow stating</span><span class="insert">defined</span> the  members of a <span class="delete">Collection.</span><span class="insert">Collection to be stated.</span> </p>
 
 <span class="glossary-ref"> <dfn id="concept-membership" class="internalDFN">Membership</dfn><sup><a class="internalDFN" href="#concept-membership"><span class="diamond"> ◊</span></a></sup> is the belonging of an entity  to a collection. </span>
 
@@ -4437,7 +4441,7 @@
 
 
 
-<p><span class="insert">Membership is not  defined as Influence, and therefore does not have an id and attributes.</span></p>
+<p><span class="insert">Membership is not, as defined here, also an influence, and therefore does not have an id and attributes.</span></p>
 
 
 <div class="anexample" id="example_47"><div class="anexampleTitle">Example <span class="delete">48</span><span class="insert">47</span><sup><a class="internalDFN" href="#example_47"><span class="diamond"> ◊</span></a></sup></div>
@@ -4563,7 +4567,7 @@
 <h5><span class="secno">5.7.2.3 </span>prov:role</h5>
 
 
-<p><span class="glossary-ref">   A <dfn id="concept-role" class="internalDFN">role</dfn><sup><a class="internalDFN" href="#concept-role"><span class="diamond"> ◊</span></a></sup> is the function of an entity or agent with respect to an activity, in the context of a <a>usage</a>, <a>generation</a>, <a>invalidation</a>,  <a href="#concept-activityAssociation" class="internalDFN">association</a>, <a>start</a>, and  <a>end</a>. </span></p>
+<p><span class="glossary-ref">   A <dfn id="concept-role" class="internalDFN">role</dfn><sup><a class="internalDFN" href="#concept-role"><span class="diamond"> ◊</span></a></sup> is the function of an entity or agent with respect to an activity, in the context of a <a>usage</a>, <a>generation</a>, <a>invalidation</a>,  <a href="#concept-association" class="internalDFN">association</a>, <a>start</a>, and  <a>end</a>. </span></p>
 
 <p>
 The attribute <span class="name">prov:role</span> is allowed to occur multiple times in a list of attribute-value pairs. The value associated with a <span class="name">prov:role</span> attribute <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>.</p>
--- a/model/prov-constraints.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/prov-constraints.html	Thu Nov 22 21:30:39 2012 +0000
@@ -985,6 +985,9 @@
 <li>Readers seeking to implement other PROV serializations
 should focus on PROV-DM and PROV-CONSTRAINTS.  PROV-O and PROV-N offer examples of mapping to RDF and text, respectively.</li>
 </ul>
+<h4>Please Comment By January 31, 2013</h4>
+
+The PROV Working Group seeks to gather experience from <a href="http://www.w3.org/2011/prov/wiki/ProvImplementations">implementations</a> in order to increase confidence in the specifications and meet specific <a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria">exit criteria</a>. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR">Proposed Recommendation</a> status.
 
 </section>
 
--- a/model/prov-dm.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/prov-dm.html	Thu Nov 22 21:30:39 2012 +0000
@@ -393,7 +393,7 @@
       
          implementationReportURI: "http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html",
 
-          testSuiteURI: "http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html",
+//          testSuiteURI: "http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html",
 
 
           // if this is a LCWD, uncomment and set the end of its review period
--- a/model/prov-n.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/prov-n.html	Thu Nov 22 21:30:39 2012 +0000
@@ -1343,6 +1343,11 @@
 <li>Readers seeking to implement other PROV serializations
 should focus on PROV-DM and PROV-CONSTRAINTS.  PROV-O and PROV-N offer examples of mapping to RDF and text, respectively.</li>
 </ul>
+
+<h4>Please Comment By January 31, 2013</h4>
+
+The PROV Working Group seeks to gather experience from <a href="http://www.w3.org/2011/prov/wiki/ProvImplementations">implementations</a> in order to increase confidence in the specifications and meet specific <a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria">exit criteria</a>. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR">Proposed Recommendation</a> status.
+
 </section>
 
 
@@ -3426,7 +3431,7 @@
     <p>The Internet Media Type / MIME Type for PROV-N is &quot;text/provenance-notation&quot;.</p> 
     <p>It is recommended that PROV-N files have the extension &quot;.provn&quot; (all lowercase) on all platforms.</p> 
     <p>It is recommended that PROV-N files stored on Macintosh HFS file systems be given a file type of &quot;TEXT&quot;.</p> 
-    <p>The information that follows has been <a href="TBD">submitted to the IESG</a> for review, approval, and registration with IANA.</p> 
+    <p>The information that follows has been <a href="https://lists.w3.org/Archives/Member/w3c-archive/2012Nov/0317.html">submitted to the IESG</a> for review, approval, and registration with IANA.</p> 
     <dl> 
       <dt>Type name:</dt> 
       <dd>text</dd> 
--- a/model/releases/CR-prov-constraints-20121211/Overview.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/releases/CR-prov-constraints-20121211/Overview.html	Thu Nov 22 21:30:39 2012 +0000
@@ -802,6 +802,9 @@
 <li>Readers seeking to implement other PROV serializations
 should focus on PROV-DM and PROV-CONSTRAINTS.  PROV-O and PROV-N offer examples of mapping to RDF and text, respectively.</li>
 </ul>
+<h4 id="please-comment-by-january-31-2013">Please Comment By January 31, 2013</h4>
+
+The PROV Working Group seeks to gather experience from <a href="http://www.w3.org/2011/prov/wiki/ProvImplementations">implementations</a> in order to increase confidence in the specifications and meet specific <a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria">exit criteria</a>. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR">Proposed Recommendation</a> status.
 
 
         <p>
@@ -4411,7 +4414,7 @@
 <span class="name">'agent' ∈ typeOf(ag)</span>.
 </li><li>
 <span class="conditional">IF</span> 
-   <span class="name">activity(a,attrs)</span>  
+   <span class="name">activity(a,t1,t2,attrs)</span>  
 <span class="conditional">THEN</span> 
 <span class="name">'activity' ∈ typeOf(a)</span>.
 
@@ -4568,7 +4571,7 @@
    <span class="name">entity(c,[prov:type='prov:EmptyCollection'])</span>  
 <span class="conditional">THEN</span> 
 <span class="name">'entity' ∈ typeOf(c)</span>  AND
-<span class="name">'prov:Collection' ∈ typeOf(c)</span>AND
+<span class="name">'prov:Collection' ∈ typeOf(c)</span> AND
 <span class="name">'prov:EmptyCollection' ∈ typeOf(c)</span>.
 
 </li></ol>
@@ -4716,7 +4719,7 @@
 <span class="name">actedOnBehalfOf</span>}, the following
   impossibility constraint holds:</p>
 
-<p>    <span class="conditional">IF</span> <span class="name">p(id,a<sub>1</sub>,...,a<sub>n</sub>)</span> and
+<p>    <span class="conditional">IF</span> <span class="name">p(id,a<sub>1</sub>,...,a<sub>m</sub>)</span> and
   <span class="name">r(id; b<sub>1</sub>,...,b<sub>n</sub>)</span> <span class="conditional">THEN INVALID</span>.
   </p>
   </div>
--- a/model/releases/CR-prov-constraints-20121211/diff-c.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/releases/CR-prov-constraints-20121211/diff-c.html	Thu Nov 22 21:30:39 2012 +0000
@@ -1721,11 +1721,12 @@
 <li>Readers seeking to implement other PROV serializations
 should focus on PROV-DM and PROV-CONSTRAINTS.  PROV-O and PROV-N offer examples of mapping to RDF and text, respectively.</li>
 </ul>
-
-
-
-
-        <p>
+<h4 id="please-comment-by-january-31-2013"><span class="insert">Please Comment By January 31, 2013</span></h4>
+
+<span class="insert">The PROV Working Group seeks to gather experience from </span><a href="http://www.w3.org/2011/prov/wiki/ProvImplementations"><span class="insert">implementations</span></a><span class="insert"> in order to increase confidence in the specifications and meet specific </span><a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria"><span class="insert">exit criteria</span></a><span class="insert">. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request </span><a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR"><span class="insert">Proposed Recommendation</span></a><span class="insert"> status.
+
+
+        </span><p>
           This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a <span class="delete">Last Call Working Draft. </span><span class="insert">Candidate Recommendation.
           
             </span>This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. 
@@ -5248,7 +5249,7 @@
 <span class="name">'agent' ∈ typeOf(ag)</span>.
 </li><li>
 <span class="conditional">IF</span> 
-   <span class="name">activity(a,attrs)</span>  
+   <span class="name"><span class="delete">activity(a,attrs)</span><span class="insert">activity(a,t1,t2,attrs)</span></span>  
 <span class="conditional">THEN</span> 
 <span class="name">'activity' ∈ typeOf(a)</span>.
 
@@ -5399,9 +5400,9 @@
 </li><li>
 
 <span class="conditional">IF</span> 
-   <span class="name"><span class="delete">hadMember(c,e)</span>  
-<span class="delete">THEN</span> 
-<span class="delete">'prov:Collection' ∈ typeOf(c)</span><span class="delete"> AND
+   <span class="name"><span class="delete">hadMember(c,e)</span><span class="insert">entity(c,[prov:type='prov:EmptyCollection'])</span></span>  
+<span class="conditional">THEN</span> 
+<span class="name"><span class="delete">'prov:Collection' ∈ typeOf(c)</span><span class="delete"> AND
 </span><span class="delete">'entity' ∈ typeOf(c)</span><span class="delete"> AND
 </span><span class="delete">'entity' ∈ typeOf(e)</span><span class="delete">.
 
@@ -5409,10 +5410,10 @@
 </span>
 
 <span class="delete">IF</span> 
-   entity(c,[prov:type='prov:EmptyCollection'])</span>  
-<span class="conditional">THEN</span> 
-<span class="name">'entity' ∈ typeOf(c)</span>  AND
-<span class="name">'prov:Collection' ∈ typeOf(c)</span>AND
+   <span class="delete">entity(c,[prov:type='prov:EmptyCollection'])</span>  
+<span class="delete">THEN</span> 
+'entity' ∈ typeOf(c)</span>  AND
+<span class="name">'prov:Collection' ∈ typeOf(c)</span> AND
 <span class="name">'prov:EmptyCollection' ∈ typeOf(c)</span>.
 
 </li></ol>
@@ -5542,7 +5543,7 @@
 <span class="name">actedOnBehalfOf</span>}, the following
   impossibility constraint holds:</p>
 
-<p>    <span class="conditional">IF</span> <span class="name">p(id,a<sub>1</sub>,...,a<sub>n</sub>)</span> and
+<p>    <span class="conditional">IF</span> <span class="name">p(id,a<sub>1</sub>,...,a<sub><span class="delete">n</span><span class="insert">m</span></sub>)</span> and
   <span class="name">r(id; b<sub>1</sub>,...,b<sub>n</sub>)</span> <span class="conditional">THEN INVALID</span>.
   </p>
   </div>
--- a/model/releases/CR-prov-dm-20121211/Overview.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/releases/CR-prov-dm-20121211/Overview.html	Thu Nov 22 21:30:39 2012 +0000
@@ -1187,9 +1187,6 @@
       <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</a></dd>
     
     
-      <dt>Test suite:</dt>
-      <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html">http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html</a></dd>
-    
     
       <dt>Implementation report:</dt>
       <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html">http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html</a></dd>
@@ -1311,6 +1308,12 @@
 should focus on PROV-DM and PROV-CONSTRAINTS.  PROV-O and PROV-N offer examples of mapping to RDF and text, respectively.</li>
 </ul>
 
+<h4 id="please-comment-by-january-31-2013">Please Comment By January 31, 2013</h4>
+
+The PROV Working Group seeks to gather experience from <a href="http://www.w3.org/2011/prov/wiki/ProvImplementations">implementations</a> in order to increase confidence in the specifications and meet specific <a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria">exit criteria</a>. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR">Proposed Recommendation</a> status.
+
+
+
         <p>
           This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a Candidate Recommendation.
           
@@ -1413,7 +1416,7 @@
 </li><li> component 2: derivations of entities from others;
 </li><li> component 3: agents bearing responsibility for entities that were generated and activities that happened;
 </li><li> component 4: bundles, a mechanism to support provenance of provenance;
-</li><li> component 5: properties to link entities that refer to a same thing;
+</li><li> component 5: properties to link entities that refer to the same thing;
 </li><li> component 6: collections forming a logical structure for its members.
 </li></ul>
 
@@ -1664,7 +1667,7 @@
 This is answered by
 considering that a single artifact may
 correspond to several entities; in this case, a car in Boston may be a
-different entity from a car in Cambridge.  
+different entity from the same car in Cambridge.  
 Thus, among other things,
 an entity "car in Boston" would be used, and a new entity "car in
 Cambridge" would be generated by this activity of driving.  The
@@ -1857,7 +1860,7 @@
 <p>Subtyping can be applied to core types. For example, a software agent is special kind of agent, defined as follows.</p>
 
 <span class="glossary-ref">
-   A <span class="dfn">software agent</span>  is running software. </span>
+   A <span class="dfn">SoftwareAgent</span>  is running software. </span>
 
 
 <p>Subtyping can also be applied to  core relations. For example, a revision is a special kind of derivation, defined as follows.</p>
@@ -1976,7 +1979,7 @@
 <h4><span class="secno">2.2.3 </span>Collections</h4>
 
 <p>
-<span class="glossary-ref">   A <span class="dfn">collection</span> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <span class="dfn">member of</span> the collections.  </span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>. 
+<span class="glossary-ref">   A <span class="dfn">collection</span> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <span class="dfn">member</span> of the collections.  </span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>. 
 Using Collections, one can express the provenance of the collection itself in addition to that of the members.  </p>
 
 <div class="anexample conceptexample" id="collection-example"><div class="anexampleTitle">Example 15<sup><a class="internalDFN" href="#collection-example"><span class="diamond"> ◊</span></a></sup></div>
@@ -2008,7 +2011,7 @@
 <tbody><tr><td style="border-width: 0px; "></td><td>Component</td><td>Core <br>Structures</td><td>Overview</td><td>Specification</td><td>Description</td></tr> 
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 <tr><td style="	padding: 8px;">1</td><td style="text-align: left;">Entities and Activities</td><td>✔</td><td><a href="#section-entity-activity">2.1.1</a></td><td><a href="#component1">5.1</a></td><td style="text-align: left;">about entities and activities, and their interrelations</td></tr> 
-<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component3">5.2</a></td><td style="text-align: left;">about derivations and its subtypes</td></tr> 
+<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component3">5.2</a></td><td style="text-align: left;">about derivation and its subtypes</td></tr> 
 <tr><td>3</td><td style="text-align: left;">Agent and Responsibility</td><td>✔</td><td><a href="#section-agents-attribution-association-delegation">2.1.3</a></td><td><a href="#component2">5.3</a></td><td style="text-align: left;">about agents and concepts ascribing responsibility to them</td></tr> 
 <tr><td>4</td><td style="text-align: left;">Bundles</td><td></td><td><a href="#section-provenance-of-provnance">2.2.2</a></td><td><a href="#component4">5.4</a></td><td style="text-align: left;">about bundles, a mechanism to support provenance of provenance</td></tr> 
 <tr><td>5</td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><a href="#component5">5.5</a></td><td style="text-align: left;">about relations linking entities referring the same thing</td></tr> 
@@ -2173,7 +2176,7 @@
 </p>
 
 <p>
-We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined IRIs (some of which refer archived email messages, available to <abbr title="World Wide Web Consortium">W3C</abbr> Members).</p>
+We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined IRIs (some of which refer to archived email messages, available to <abbr title="World Wide Web Consortium">W3C</abbr> Members).</p>
 
 <ul>
 <li> Two versions of a document were involved: <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft);</li>
@@ -2227,9 +2230,10 @@
 </pre>
 </li>
 
-<li>The activity was associated with the Consortium agent, and proceeded according to its publication policy: this is an <a title="concept-activityAssociation">Activity Association</a>.
+<li>The activity was associated with the Consortium agent, and proceeded according to its publication policy: this is an <a title="concept-association">Association</a>.
 <pre>wasAssociatedWith(ex:act2, w3:Consortium, process:rec-advance)
 </pre>
+This relation is illustrated in <a href="#prov-a-document2-top" class="fig-ref">Figure 3</a> with a multi-edge labelled <span class="name">wasAssociatedWith</span> pointing to an agent and entity (representing a plan).
 </li>
 </ul>
 
@@ -2694,7 +2698,7 @@
 
 <div class="anexample" id="anexample-start3"><div class="anexampleTitle">Example 25<sup><a class="internalDFN" href="#anexample-start3"><span class="diamond"> ◊</span></a></sup></div>
 <p>
-In this example, filling fuel was started as a consequence of
+In this example, filling the fuel tank was started as a consequence of
 observing low fuel. The trigger entity is unspecified, it could
 for instance have been the low fuel warning light, the fuel tank
 indicator needle position, or the engine not running properly.
@@ -2768,7 +2772,7 @@
 </li></ul>
 <p>In the first two cases, the entity has physically disappeared after its termination: there is no more soup, or painting.  In the third case, there may be an "offer voucher" that still exists, but it is no longer valid; likewise, on April 4th, the BBC news site still exists but it is not the same entity as BBC news Web site on April 3rd; or the 
 green traffic light (an entity with a fixed aspect green light) became the
-red traffic light (anohter entity with a fixed aspect red light).
+red traffic light (another entity with a fixed aspect red light).
 </p>
 
 
@@ -3107,7 +3111,7 @@
 There are three types of agents that are common across most anticipated domains of use; it is acknowledged that these types do not cover all kinds of agent. </p>
 <ul>
 <li><span class="name">SoftwareAgent</span>
-<div class="glossary-ref">   A <dfn id="concept-software-agent" title="software-agent" class="internalDFN">software agent</dfn><sup><a class="internalDFN" href="#concept-software-agent"><span class="diamond"> ◊</span></a></sup>  is running software. </div>
+<div class="glossary-ref">   A <dfn id="concept-software-agent" title="software-agent" class="internalDFN">SoftwareAgent</dfn><sup><a class="internalDFN" href="#concept-software-agent"><span class="diamond"> ◊</span></a></sup>  is running software. </div>
 
 <p></p></li>
 
@@ -3170,13 +3174,13 @@
 <section id="term-Association">
 <h4><span class="secno">5.3.3 </span>Association</h4>
 
-<div class="glossary-ref">   An activity <dfn id="concept-activityAssociation" class="internalDFN">association</dfn><sup><a class="internalDFN" href="#concept-activityAssociation"><span class="diamond"> ◊</span></a></sup> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </div>
+<div class="glossary-ref">   An activity <dfn id="concept-association" class="internalDFN">association</dfn><sup><a class="internalDFN" href="#concept-association"><span class="diamond"> ◊</span></a></sup> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </div>
 
 <p></p>
 <div class="glossary-ref">   A <dfn id="concept-plan" class="internalDFN">plan</dfn><sup><a class="internalDFN" href="#concept-plan"><span class="diamond"> ◊</span></a></sup> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals.  </div>
 
 
-<p></p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith" id="dfn-wasassociatedwith" class="internalDFN">activity association</dfn><sup><a class="internalDFN" href="#dfn-wasassociatedwith"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id; a, ag, pl, attrs)</span> in PROV-N,</span> has:
+<p></p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith" id="dfn-wasassociatedwith" class="internalDFN">association</dfn><sup><a class="internalDFN" href="#dfn-wasassociatedwith"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id; a, ag, pl, attrs)</span> in PROV-N,</span> has:
 <ul>
 <li><span class="attribute" id="association.id">id</span>:  an <em class="rfc2119" title="optional">optional</em> identifier for the association between an activity and an agent;</li> 
 <li><span class="attribute" id="association.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity;</li>
@@ -3290,7 +3294,7 @@
 
 <p>
 </p><div class="attributes" id="attributes-influence">
-A <dfn title="wasInfluencedBy" id="dfn-wasinfluencedby" class="internalDFN">Influence</dfn><sup><a class="internalDFN" href="#dfn-wasinfluencedby"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">wasInfluencedBy(id; o2, o1, attrs)</span> in PROV-N,</span> has:
+An <dfn title="wasInfluencedBy" id="dfn-wasinfluencedby" class="internalDFN">Influence</dfn><sup><a class="internalDFN" href="#dfn-wasinfluencedby"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">wasInfluencedBy(id; o2, o1, attrs)</span> in PROV-N,</span> has:
 <ul>
 <li><span class="attribute" id="influence.id">id</span>:  an <em class="rfc2119" title="optional">optional</em> identifier identifying the relation;</li> 
 <li><span class="attribute" id="influence.influencee">influencee</span>:  an identifier (<span class="name">o2</span>) for an entity, activity, or agent;
@@ -3299,14 +3303,14 @@
 </ul></div>
 
 <p>
-<a href="#concept-usage" class="internalDFN">Usage</a>, <a>start</a>, <a>end</a>, <a>generation</a>, <a>invalidation</a>, <a>communication</a>, <a href="#concept-derivation" class="internalDFN">derivation</a>, <a>attribution</a>, <a href="#concept-activityAssociation" class="internalDFN">association</a>, and <a>delegation</a> are also <a>influence</a>. It is <em class="rfc2119" title="recommended">recommended</em> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a href="#concept-influence" class="internalDFN">Influence</a> relation may be useful to express queries over provenance information.
+A <a href="#concept-usage" class="internalDFN">Usage</a>, <a>start</a>, <a>end</a>, <a>generation</a>, <a>invalidation</a>, <a>communication</a>, <a href="#concept-derivation" class="internalDFN">derivation</a>, <a>attribution</a>, <a href="#concept-association" class="internalDFN">association</a>, and <a>delegation</a> is also an <a>influence</a>. It is <em class="rfc2119" title="recommended">recommended</em> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a href="#concept-influence" class="internalDFN">Influence</a> relation may be useful to express queries over provenance information.
 </p>
 
 
 <div id="mapping-relations-to-influence-table_text" style="text-align: left;">
 The following table establishes the correspondence between 
 the attributes <a class="attribute" href="#influence.influencee">influencee</a> and <a class="attribute" href="#influence.influencer">influencer</a>, and attributes of
-<a>usage</a>, <a>start</a>, <a>end</a>, <a>generation</a>, <a>invalidation</a>, <a>communication</a>, <a href="#concept-derivation" class="internalDFN">derivation</a>, <a>attribution</a>, <a href="#concept-activityAssociation" class="internalDFN">association</a>, and <a>delegation</a>.
+<a>usage</a>, <a>start</a>, <a>end</a>, <a>generation</a>, <a>invalidation</a>, <a>communication</a>, <a href="#concept-derivation" class="internalDFN">derivation</a>, <a>attribution</a>, <a href="#concept-association" class="internalDFN">association</a>, and <a>delegation</a>.
 
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <caption id="mapping-relations-to-influence-table"><span>Table 7<sup><a class="internalDFN" href="#mapping-relations-to-influence-table"><span class="diamond"> ◊:</span></a></sup> </span>Mapping Relations to Influence</caption> <!-- Table 7-->
@@ -3558,7 +3562,7 @@
 </ul>
 </div>
 
-<p>Specialization is not  defined as Influence, and therefore does not have an id and attributes.</p>
+<p>A specialization is not, as  defined here, also an influence, and therefore does not have an id and attributes.</p>
 
 
 
@@ -3596,7 +3600,7 @@
 </ul>
 </div>
 
-<p>Alternate is not  defined as Influence, and therefore does not have an id and attributes.</p>  
+<p>An alternate is not, as  defined  here, also an influence, and therefore does not have an id and attributes.</p>  
 
 <p>
 Note that <a title="alternateOf" href="#dfn-alternateof" class="internalDFN">alternateOf</a> is a necessarily very general
@@ -3627,7 +3631,7 @@
 
 <div class="anexample" id="anexample-alternate2"><div class="anexampleTitle">Example 45<sup><a class="internalDFN" href="#anexample-alternate2"><span class="diamond"> ◊</span></a></sup></div>
 <p>
-Considering again the two versions of the technical report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft). They are alternate of each other.
+Considering again the two versions of the technical report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft). They are alternates of each other.
 </p><pre class="codeexample">entity(tr:WD-prov-dm-20111018)
 entity(tr:WD-prov-dm-20111215)
 alternateOf(tr:WD-prov-dm-20111018, tr:WD-prov-dm-20111215)
@@ -3662,7 +3666,7 @@
 <section id="term-collection">
 <h4><span class="secno">5.6.1 </span>Collection</h4>
 
-<span class="glossary-ref">   A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <dfn id="dfn-member-of" class="internalDFN">member of</dfn><sup><a class="internalDFN" href="#dfn-member-of"><span class="diamond"> ◊</span></a></sup> the collections.  </span>
+<span class="glossary-ref">   A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some constituents that must themselves be entities. These constituents are said to be <dfn id="dfn-member" class="internalDFN">member</dfn><sup><a class="internalDFN" href="#dfn-member"><span class="diamond"> ◊</span></a></sup> of the collections.  </span>
 
 <span class="glossary-ref">   An <dfn id="concept-empty-collection" class="internalDFN">empty collection</dfn><sup><a class="internalDFN" href="#concept-empty-collection"><span class="diamond"> ◊</span></a></sup> is a collection without members.  </span>
 
@@ -3688,7 +3692,7 @@
 <section id="term-membership">
 <h4><span class="secno">5.6.2 </span>Membership</h4>
 
-<p>A <strong>membership</strong> relation is defined, to allow stating the  members of a Collection. </p>
+<p>A <strong>membership</strong> relation is defined the  members of a Collection to be stated. </p>
 
 <span class="glossary-ref"> <dfn id="concept-membership" class="internalDFN">Membership</dfn><sup><a class="internalDFN" href="#concept-membership"><span class="diamond"> ◊</span></a></sup> is the belonging of an entity  to a collection. </span>
 
@@ -3703,7 +3707,7 @@
 </div>
 
 
-<p>Membership is not  defined as Influence, and therefore does not have an id and attributes.</p>
+<p>Membership is not, as defined here, also an influence, and therefore does not have an id and attributes.</p>
 
 
 <div class="anexample" id="example_47"><div class="anexampleTitle">Example 47<sup><a class="internalDFN" href="#example_47"><span class="diamond"> ◊</span></a></sup></div>
@@ -3829,7 +3833,7 @@
 <h5><span class="secno">5.7.2.3 </span>prov:role</h5>
 
 
-<p><span class="glossary-ref">   A <dfn id="concept-role" class="internalDFN">role</dfn><sup><a class="internalDFN" href="#concept-role"><span class="diamond"> ◊</span></a></sup> is the function of an entity or agent with respect to an activity, in the context of a <a>usage</a>, <a>generation</a>, <a>invalidation</a>,  <a href="#concept-activityAssociation" class="internalDFN">association</a>, <a>start</a>, and  <a>end</a>. </span></p>
+<p><span class="glossary-ref">   A <dfn id="concept-role" class="internalDFN">role</dfn><sup><a class="internalDFN" href="#concept-role"><span class="diamond"> ◊</span></a></sup> is the function of an entity or agent with respect to an activity, in the context of a <a>usage</a>, <a>generation</a>, <a>invalidation</a>,  <a href="#concept-association" class="internalDFN">association</a>, <a>start</a>, and  <a>end</a>. </span></p>
 
 <p>
 The attribute <span class="name">prov:role</span> is allowed to occur multiple times in a list of attribute-value pairs. The value associated with a <span class="name">prov:role</span> attribute <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>.</p>
--- a/model/releases/CR-prov-dm-20121211/diff.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/releases/CR-prov-dm-20121211/diff.html	Thu Nov 22 21:30:39 2012 +0000
@@ -1660,9 +1660,6 @@
       <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html</span></a></dd>
     
     
-      <dt><span class="insert">Test suite:</span></dt>
-      <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html</span></a></dd>
-    
     
       <dt><span class="insert">Implementation report:</span></dt>
       <dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/reports/prov-implementations.html</span></a></dd>
@@ -1798,7 +1795,13 @@
 </ul>
 
 
-        <p>
+<h4 id="please-comment-by-january-31-2013"><span class="insert">Please Comment By January 31, 2013</span></h4><span class="insert">
+
+The PROV Working Group seeks to gather experience from </span><a href="http://www.w3.org/2011/prov/wiki/ProvImplementations"><span class="insert">implementations</span></a><span class="insert"> in order to increase confidence in the specifications and meet specific </span><a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria"><span class="insert">exit criteria</span></a><span class="insert">. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request </span><a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR"><span class="insert">Proposed Recommendation</span></a><span class="insert"> status.
+
+
+
+        </span><p>
           This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a <span class="delete">Last Call Working Draft. </span><span class="insert">Candidate Recommendation.
           
             </span>This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. 
@@ -1918,7 +1921,7 @@
 </li><li> component 2: derivations of entities from others;
 </li><li> component 3: agents bearing responsibility for entities that were generated and activities that happened;
 </li><li> component 4: bundles, a mechanism to support provenance of provenance;
-</li><li> component 5: properties to link entities that refer to a same thing;
+</li><li> component 5: properties to link entities that refer to <span class="delete">a</span><span class="insert">the</span> same thing;
 </li><li> component 6: collections forming a logical structure for its members.
 </li></ul>
 
@@ -2208,7 +2211,7 @@
 This is answered by
 considering that a single artifact may
 correspond to several entities; in this case, a car in Boston may be a
-different entity from a car in Cambridge.  
+different entity from the same car in Cambridge.  
 Thus, among other things,
 an entity "car in Boston" would be used, and a new entity "car in
 Cambridge" would be generated by this activity of driving.  The
@@ -2410,7 +2413,7 @@
 <p>Subtyping can be applied to core types. For example, a software agent is special kind of agent, defined as follows.</p>
 
 <span class="glossary-ref">
-   A <span class="dfn">software agent</span>  is running software. </span>
+   A <span class="dfn"><span class="delete">software agent</span><span class="insert">SoftwareAgent</span></span>  is running software. </span>
 
 
 <p>Subtyping can also be applied to  core relations. For example, a revision is a special kind of derivation, defined as follows.</p>
@@ -2533,7 +2536,7 @@
 <h4><span class="secno">2.2.3 </span>Collections</h4>
 
 <p>
-<span class="glossary-ref">   A <span class="dfn">collection</span> is an entity that provides a structure to some <span class="delete">constituents, which are</span><span class="insert">constituents that must</span> themselves<span class="insert"> be</span> entities. These constituents are said to be <span class="dfn">member of</span> the collections.  </span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>. 
+<span class="glossary-ref">   A <span class="dfn">collection</span> is an entity that provides a structure to some <span class="delete">constituents, which are</span><span class="insert">constituents that must</span> themselves<span class="insert"> be</span> entities. These constituents are said to be <span class="dfn">member<span class="delete"> of</span></span><span class="insert"> of</span> the collections.  </span> Many different types of collections exist, such as <em>sets</em>, <em>dictionaries</em>, or <em>lists</em>. 
 Using Collections, one can express the provenance of the collection itself in addition to that of the members.  </p>
 
 <div class="anexample conceptexample" id="collection-example"><div class="anexampleTitle">Example <span class="delete">14</span><span class="insert">15</span><sup><a class="internalDFN" href="#collection-example"><span class="diamond"> ◊</span></a></sup></div>
@@ -2565,7 +2568,7 @@
 <tbody><tr><td style="border-width: 0px; "></td><td>Component</td><td>Core <br>Structures</td><td>Overview</td><td>Specification</td><td>Description</td></tr> 
 <tr><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td><td style="border-width: 0px; "></td></tr>
 <tr><td style="	padding: 8px;">1</td><td style="text-align: left;">Entities and Activities</td><td>✔</td><td><a href="#section-entity-activity">2.1.1</a></td><td><a href="#component1">5.1</a></td><td style="text-align: left;">about entities and activities, and their interrelations</td></tr> 
-<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component3">5.2</a></td><td style="text-align: left;">about derivations and its subtypes</td></tr> 
+<tr><td>2</td><td style="text-align: left;">Derivation</td><td>✔</td><td><a href="#section-derivation">2.1.2</a></td><td><a href="#component3">5.2</a></td><td style="text-align: left;">about <span class="delete">derivations</span><span class="insert">derivation</span> and its subtypes</td></tr> 
 <tr><td>3</td><td style="text-align: left;">Agent and Responsibility</td><td>✔</td><td><a href="#section-agents-attribution-association-delegation">2.1.3</a></td><td><a href="#component2">5.3</a></td><td style="text-align: left;">about agents and concepts ascribing responsibility to them</td></tr> 
 <tr><td>4</td><td style="text-align: left;">Bundles</td><td></td><td><a href="#section-provenance-of-provnance">2.2.2</a></td><td><a href="#component4">5.4</a></td><td style="text-align: left;">about bundles, a mechanism to support provenance of provenance</td></tr> 
 <tr><td>5</td><td style="text-align: left;">Alternate</td><td></td><td>—</td><td><a href="#component5">5.5</a></td><td style="text-align: left;">about relations linking entities referring the same thing</td></tr> 
@@ -2732,7 +2735,7 @@
 </p>
 
 <p>
-We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined <span class="delete">URIs</span><span class="insert">IRIs</span> (some of which refer archived email messages, available to <abbr title="World Wide Web Consortium">W3C</abbr> Members).</p>
+We describe the kind of provenance record that the <a href="http://www.w3.org/Consortium">WWW Consortium</a> could keep for auditors to check that due processes are followed. All entities involved in this example are Web resources, with well-defined <span class="delete">URIs</span><span class="insert">IRIs</span> (some of which refer <span class="insert">to </span>archived email messages, available to <abbr title="World Wide Web Consortium">W3C</abbr> Members).</p>
 
 <ul>
 <li> Two versions of a document were involved: <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft);</li>
@@ -2786,9 +2789,10 @@
 </pre>
 </li>
 
-<li>The activity was associated with the Consortium agent, and proceeded according to its publication policy: this is an <a title="concept-activityAssociation">Activity Association</a>.
+<li>The activity was associated with the Consortium agent, and proceeded according to its publication policy: this is an <span class="delete">Activity </span><a title="concept-association">Association</a>.
 <pre>wasAssociatedWith(ex:act2, w3:Consortium, process:rec-advance)
-</pre>
+</pre><span class="insert">
+This relation is illustrated in </span><a href="#prov-a-document2-top" class="fig-ref"><span class="insert">Figure 3</span></a><span class="insert"> with a multi-edge labelled </span><span class="name"><span class="insert">wasAssociatedWith</span></span><span class="insert"> pointing to an agent and entity (representing a plan).</span>
 </li>
 </ul>
 
@@ -3267,7 +3271,7 @@
 
 <div class="anexample" id="anexample-start3"><div class="anexampleTitle">Example <span class="delete">24</span><span class="insert">25</span><sup><a class="internalDFN" href="#anexample-start3"><span class="diamond"> ◊</span></a></sup></div>
 <p>
-In this example, filling fuel was started as a consequence of
+In this example, filling <span class="insert">the </span>fuel<span class="insert"> tank</span> was started as a consequence of
 observing low fuel. The trigger entity is unspecified, it could
 for instance have been the low fuel warning light, the fuel tank
 indicator needle position, or the engine not running properly.
@@ -3348,7 +3352,7 @@
 </li></ul>
 <p>In the first two cases, the entity has physically disappeared after its termination: there is no more soup, or painting.  In the <span class="delete">last three cases,</span><span class="insert">third case,</span> there may be an "offer voucher" that still exists, but it is no longer valid; likewise, on April 4th, the BBC news site still exists but it is not the same entity as BBC news Web site on April 3rd; or the<span class="insert"> 
 green</span> traffic light <span class="insert">(an entity with a fixed aspect green light) </span>became <span class="insert">the
-</span>red <span class="delete">and therefore is regarded as</span><span class="insert">traffic light (anohter entity with</span> a <span class="delete">different entity to the green light.</span><span class="insert">fixed aspect red light).</span>
+</span>red <span class="delete">and therefore is regarded as</span><span class="insert">traffic light (another entity with</span> a <span class="delete">different entity to the green light.</span><span class="insert">fixed aspect red light).</span>
 </p>
 
 
@@ -3698,7 +3702,7 @@
 There are three types of agents that are common across most anticipated domains of use; it is acknowledged that these types do not cover all kinds of agent. </p>
 <ul>
 <li><span class="name">SoftwareAgent</span>
-<div class="glossary-ref">   A <dfn id="concept-software-agent" title="software-agent" class="internalDFN">software agent</dfn><sup><a class="internalDFN" href="#concept-software-agent"><span class="diamond"> ◊</span></a></sup>  is running software. </div>
+<div class="glossary-ref">   A <dfn id="concept-software-agent" title="software-agent" class="internalDFN"><span class="delete">software agent</span><span class="insert">SoftwareAgent</span></dfn><sup><a class="internalDFN" href="#concept-software-agent"><span class="diamond"> ◊</span></a></sup>  is running software. </div>
 
 <p></p></li>
 
@@ -3768,13 +3772,13 @@
 <section id="term-Association">
 <h4><span class="secno">5.3.3 </span>Association</h4>
 
-<div class="glossary-ref">   An activity <dfn id="concept-activityAssociation" class="internalDFN">association</dfn><sup><a class="internalDFN" href="#concept-activityAssociation"><span class="diamond"> ◊</span></a></sup> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </div>
+<div class="glossary-ref">   An activity <dfn id="concept-association" class="internalDFN">association</dfn><sup><a class="internalDFN" href="#concept-association"><span class="diamond"> ◊</span></a></sup> is an assignment of responsibility to an agent for an activity, indicating that the agent had a role in the activity. It further allows for a plan to be specified, which is the plan intended by the agent to achieve some goals in the context of this activity. </div>
 
 <p></p>
 <div class="glossary-ref">   A <dfn id="concept-plan" class="internalDFN">plan</dfn><sup><a class="internalDFN" href="#concept-plan"><span class="diamond"> ◊</span></a></sup> is an entity that represents a set of actions or steps intended by one or more agents to achieve some goals.  </div>
 
 
-<p></p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith" id="dfn-wasassociatedwith" class="internalDFN">activity association</dfn><sup><a class="internalDFN" href="#dfn-wasassociatedwith"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id; a, ag, pl, attrs)</span> in PROV-N,</span> has:
+<p></p><div class="attributes" id="attributes-activity-association">An <dfn title="wasAssociatedWith" id="dfn-wasassociatedwith" class="internalDFN"><span class="delete">activity </span>association</dfn><sup><a class="internalDFN" href="#dfn-wasassociatedwith"><span class="diamond"> ◊</span></a></sup><span class="withPn">, written <span class="pnExpression">wasAssociatedWith(id; a, ag, pl, attrs)</span> in PROV-N,</span> has:
 <ul>
 <li><span class="attribute" id="association.id">id</span>:  an <em class="rfc2119" title="optional">optional</em> identifier for the association between an activity and an agent;</li> 
 <li><span class="attribute" id="association.activity">activity</span>: an identifier (<span class="name">a</span>) for the activity;</li>
@@ -3879,9 +3883,9 @@
 on  <span class="name">o1</span> that signifies some form of influence of <span class="name">o1</span> on <span class="name">o2</span>.</p>
 
 
-<p>
-</p><div class="attributes" id="attributes-influence">
-A <dfn title="wasInfluencedBy" id="dfn-wasinfluencedby" class="internalDFN">Influence</dfn><sup><a class="internalDFN" href="#dfn-wasinfluencedby"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">wasInfluencedBy(id; o2, o1, attrs)</span> in PROV-N,</span> has:
+<p><span class="delete">A</span>
+</p><div class="attributes" id="attributes-influence"><span class="insert">
+An</span> <dfn title="wasInfluencedBy" id="dfn-wasinfluencedby" class="internalDFN">Influence</dfn><sup><a class="internalDFN" href="#dfn-wasinfluencedby"><span class="diamond"> ◊</span></a></sup> relation<span class="withPn">, written <span class="pnExpression">wasInfluencedBy(id; o2, o1, attrs)</span> in PROV-N,</span> has:
 <ul>
 <li><span class="attribute" id="influence.id">id</span>:  an <em class="rfc2119" title="optional">optional</em> identifier identifying the relation;</li> 
 <li><span class="attribute" id="influence.influencee">influencee</span>:  an identifier (<span class="name">o2</span>) for an entity, activity, or agent;
@@ -3890,14 +3894,14 @@
 </ul></div>
 
 <p>
-<a href="#concept-usage" class="internalDFN">Usage</a>, <a>start</a>, <a>end</a>, <a>generation</a>, <a>invalidation</a>, <a>communication</a>, <a href="#concept-derivation" class="internalDFN">derivation</a>, <a>attribution</a>, <a href="#concept-activityAssociation" class="internalDFN">association</a>, and <a>delegation</a> are <span class="delete">particular cases of  influence.</span><span class="insert">also </span><a><span class="insert">influence</span></a><span class="insert">.</span> It is <em class="rfc2119" title="recommended">recommended</em> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a href="#concept-influence" class="internalDFN">Influence</a> relation may be useful to express queries over provenance information.
+<span class="insert">A </span><a href="#concept-usage" class="internalDFN">Usage</a>, <a>start</a>, <a>end</a>, <a>generation</a>, <a>invalidation</a>, <a>communication</a>, <a href="#concept-derivation" class="internalDFN">derivation</a>, <a>attribution</a>, <a href="#concept-association" class="internalDFN">association</a>, and <a>delegation</a> <span class="delete">are particular cases of  influence.</span><span class="insert">is also an </span><a><span class="insert">influence</span></a><span class="insert">.</span> It is <em class="rfc2119" title="recommended">recommended</em> to adopt these more specific relations when writing provenance descriptions. It is anticipated that the <a href="#concept-influence" class="internalDFN">Influence</a> relation may be useful to express queries over provenance information.
 </p>
 
 
 <div id="mapping-relations-to-influence-table_text" style="text-align: left;"><span class="insert">
 The following table establishes the correspondence between 
 the attributes </span><a class="attribute" href="#influence.influencee"><span class="insert">influencee</span></a><span class="insert"> and </span><a class="attribute" href="#influence.influencer"><span class="insert">influencer</span></a><span class="insert">, and attributes of
-</span><a><span class="insert">usage</span></a><span class="insert">, </span><a><span class="insert">start</span></a><span class="insert">, </span><a><span class="insert">end</span></a><span class="insert">, </span><a><span class="insert">generation</span></a><span class="insert">, </span><a><span class="insert">invalidation</span></a><span class="insert">, </span><a><span class="insert">communication</span></a><span class="insert">, </span><a href="#concept-derivation" class="internalDFN"><span class="insert">derivation</span></a><span class="insert">, </span><a><span class="insert">attribution</span></a><span class="insert">, </span><a href="#concept-activityAssociation" class="internalDFN"><span class="insert">association</span></a><span class="insert">, and </span><a><span class="insert">delegation</span></a><span class="insert">.</span>
+</span><a><span class="insert">usage</span></a><span class="insert">, </span><a><span class="insert">start</span></a><span class="insert">, </span><a><span class="insert">end</span></a><span class="insert">, </span><a><span class="insert">generation</span></a><span class="insert">, </span><a><span class="insert">invalidation</span></a><span class="insert">, </span><a><span class="insert">communication</span></a><span class="insert">, </span><a href="#concept-derivation" class="internalDFN"><span class="insert">derivation</span></a><span class="insert">, </span><a><span class="insert">attribution</span></a><span class="insert">, </span><a href="#concept-association" class="internalDFN"><span class="insert">association</span></a><span class="insert">, and </span><a><span class="insert">delegation</span></a><span class="insert">.</span>
 
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <caption id="mapping-relations-to-influence-table"><span><span class="insert">Table 7</span><sup><a class="internalDFN" href="#mapping-relations-to-influence-table"><span class="diamond"><span class="insert"> ◊:</span></span></a></sup> </span><span class="insert">Mapping Relations to Influence</span></caption> 
@@ -4156,7 +4160,7 @@
 
 
 
-<p><span class="insert">Specialization is not  defined as Influence, and therefore does not have an id and attributes.</span></p>
+<p><span class="insert">A specialization is not, as  defined here, also an influence, and therefore does not have an id and attributes.</span></p>
 
 
 
@@ -4199,7 +4203,7 @@
 </ul>
 </div>
 
-<p><span class="insert">Alternate is not  defined as Influence, and therefore does not have an id and attributes.</span></p>  
+<p><span class="insert">An alternate is not, as  defined  here, also an influence, and therefore does not have an id and attributes.</span></p>  
 
 <p><span class="insert">
 Note that </span><a title="alternateOf" href="#dfn-alternateof" class="internalDFN"><span class="insert">alternateOf</span></a><span class="insert"> is a necessarily very general
@@ -4230,7 +4234,7 @@
 
 <div class="anexample" id="anexample-alternate2"><div class="anexampleTitle">Example <span class="delete">44</span><span class="insert">45</span><sup><a class="internalDFN" href="#anexample-alternate2"><span class="diamond"> ◊</span></a></sup></div>
 <p>
-Considering again the two versions of the technical report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft). They are alternate of each other.
+Considering again the two versions of the technical report <span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111215">tr:WD-prov-dm-20111215</a></span> (second working draft) and <span class="name"><span class="name"><a href="http://www.w3.org/TR/2011/WD-prov-dm-20111018">tr:WD-prov-dm-20111018</a></span></span> (first working draft). They are <span class="delete">alternate</span><span class="insert">alternates</span> of each other.
 </p><pre class="codeexample">entity(tr:WD-prov-dm-20111018)
 entity(tr:WD-prov-dm-20111215)
 <span class="delete">alternateOf(tr:WD-prov-dm-20111018,tr:WD-prov-dm-20111215)</span><span class="insert">alternateOf(tr:WD-prov-dm-20111018, tr:WD-prov-dm-20111215)</span>
@@ -4389,7 +4393,7 @@
 <section id="term-collection">
 <h4><span class="secno">5.6.1 </span>Collection</h4>
 
-<span class="glossary-ref">   A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some <span class="delete">constituents, which are</span><span class="insert">constituents that must</span> themselves<span class="insert"> be</span> entities. These constituents are said to be <dfn id="dfn-member-of" class="internalDFN">member of</dfn><sup><a class="internalDFN" href="#dfn-member-of"><span class="diamond"> ◊</span></a></sup> the collections.  </span>
+<span class="glossary-ref">   A <dfn id="concept-collection" class="internalDFN">collection</dfn><sup><a class="internalDFN" href="#concept-collection"><span class="diamond"> ◊</span></a></sup> is an entity that provides a structure to some <span class="delete">constituents, which</span><span class="insert">constituents that must themselves be entities. These constituents</span> are <span class="delete">themselves entities. These constituents are </span>said to be <dfn id="dfn-member" class="internalDFN">member<span class="delete"> of</span></dfn><sup><a class="internalDFN" href="#dfn-member"><span class="diamond"> ◊</span></a></sup><span class="insert"> of</span> the collections.  </span>
 
 <span class="glossary-ref">   An <dfn id="concept-empty-collection" class="internalDFN">empty collection</dfn><sup><a class="internalDFN" href="#concept-empty-collection"><span class="diamond"> ◊</span></a></sup> is a collection without members.  </span>
 
@@ -4418,7 +4422,7 @@
 <section id="term-membership">
 <h4><span class="secno">5.6.2 </span>Membership</h4>
 
-<p>A <strong>membership</strong> relation is defined, to allow stating the  members of a Collection. </p>
+<p>A <strong>membership</strong> relation is <span class="delete">defined, to allow stating</span><span class="insert">defined</span> the  members of a <span class="delete">Collection.</span><span class="insert">Collection to be stated.</span> </p>
 
 <span class="glossary-ref"> <dfn id="concept-membership" class="internalDFN">Membership</dfn><sup><a class="internalDFN" href="#concept-membership"><span class="diamond"> ◊</span></a></sup> is the belonging of an entity  to a collection. </span>
 
@@ -4437,7 +4441,7 @@
 
 
 
-<p><span class="insert">Membership is not  defined as Influence, and therefore does not have an id and attributes.</span></p>
+<p><span class="insert">Membership is not, as defined here, also an influence, and therefore does not have an id and attributes.</span></p>
 
 
 <div class="anexample" id="example_47"><div class="anexampleTitle">Example <span class="delete">48</span><span class="insert">47</span><sup><a class="internalDFN" href="#example_47"><span class="diamond"> ◊</span></a></sup></div>
@@ -4563,7 +4567,7 @@
 <h5><span class="secno">5.7.2.3 </span>prov:role</h5>
 
 
-<p><span class="glossary-ref">   A <dfn id="concept-role" class="internalDFN">role</dfn><sup><a class="internalDFN" href="#concept-role"><span class="diamond"> ◊</span></a></sup> is the function of an entity or agent with respect to an activity, in the context of a <a>usage</a>, <a>generation</a>, <a>invalidation</a>,  <a href="#concept-activityAssociation" class="internalDFN">association</a>, <a>start</a>, and  <a>end</a>. </span></p>
+<p><span class="glossary-ref">   A <dfn id="concept-role" class="internalDFN">role</dfn><sup><a class="internalDFN" href="#concept-role"><span class="diamond"> ◊</span></a></sup> is the function of an entity or agent with respect to an activity, in the context of a <a>usage</a>, <a>generation</a>, <a>invalidation</a>,  <a href="#concept-association" class="internalDFN">association</a>, <a>start</a>, and  <a>end</a>. </span></p>
 
 <p>
 The attribute <span class="name">prov:role</span> is allowed to occur multiple times in a list of attribute-value pairs. The value associated with a <span class="name">prov:role</span> attribute <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>.</p>
--- a/model/releases/CR-prov-n-20121211/Overview.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/releases/CR-prov-n-20121211/Overview.html	Thu Nov 22 21:30:39 2012 +0000
@@ -1,4 +1,3 @@
-
 <!DOCTYPE html>
 <html lang="en" dir="ltr">
 <head> 
@@ -1281,6 +1280,11 @@
 should focus on PROV-DM and PROV-CONSTRAINTS.  PROV-O and PROV-N offer examples of mapping to RDF and text, respectively.</li>
 </ul>
 
+<h4 id="please-comment-by-january-31-2013">Please Comment By January 31, 2013</h4>
+
+The PROV Working Group seeks to gather experience from <a href="http://www.w3.org/2011/prov/wiki/ProvImplementations">implementations</a> in order to increase confidence in the specifications and meet specific <a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria">exit criteria</a>. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request <a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR">Proposed Recommendation</a> status.
+
+
         <p>
           This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a Candidate Recommendation.
           
@@ -3345,7 +3349,7 @@
     <p>The Internet Media Type / MIME Type for PROV-N is "text/provenance-notation".</p> 
     <p>It is recommended that PROV-N files have the extension ".provn" (all lowercase) on all platforms.</p> 
     <p>It is recommended that PROV-N files stored on Macintosh HFS file systems be given a file type of "TEXT".</p> 
-    <p>The information that follows has been <a href="TBD">submitted to the IESG</a> for review, approval, and registration with IANA.</p> 
+    <p>The information that follows has been <a href="https://lists.w3.org/Archives/Member/w3c-archive/2012Nov/0317.html">submitted to the IESG</a> for review, approval, and registration with IANA.</p> 
     <dl> 
       <dt>Type name:</dt> 
       <dd>text</dd> 
--- a/model/releases/CR-prov-n-20121211/diff-n.html	Thu Nov 22 21:21:19 2012 +0000
+++ b/model/releases/CR-prov-n-20121211/diff-n.html	Thu Nov 22 21:30:39 2012 +0000
@@ -1,4 +1,3 @@
-
 <!DOCTYPE html>
 <html lang="en" dir="ltr">
 <head><style type="text/css"><!--
@@ -1724,7 +1723,12 @@
 </ul>
 
 
-        <p>
+<h4 id="please-comment-by-january-31-2013"><span class="insert">Please Comment By January 31, 2013</span></h4><span class="insert">
+
+The PROV Working Group seeks to gather experience from </span><a href="http://www.w3.org/2011/prov/wiki/ProvImplementations"><span class="insert">implementations</span></a><span class="insert"> in order to increase confidence in the specifications and meet specific </span><a href="http://www.w3.org/2011/prov/wiki/ProvCRExitCriteria"><span class="insert">exit criteria</span></a><span class="insert">. This document will remain a Candidate Recommendation until at least 31 January 31, 2013. After that date, when and if the exit criteria are met, the group intends to request </span><a href="http://www.w3.org/2005/10/Process-20051014/tr.html#RecsPR"><span class="insert">Proposed Recommendation</span></a><span class="insert"> status.
+
+
+        </span><p>
           This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as a <span class="delete">Last Call Working Draft. </span><span class="insert">Candidate Recommendation.
           
             </span>This document is intended to become a <abbr title="World Wide Web Consortium">W3C</abbr> Recommendation. 
@@ -3974,7 +3978,7 @@
     <p>The Internet Media Type / MIME Type for PROV-N is "text/provenance-notation".</p> 
     <p>It is recommended that PROV-N files have the extension ".provn" (all lowercase) on all platforms.</p> 
     <p>It is recommended that PROV-N files stored on Macintosh HFS file systems be given a file type of "TEXT".</p> 
-    <p><span class="delete">This</span><span class="insert">The</span> information that follows <span class="delete">is being </span><span class="insert">has been </span><a href="TBD">submitted to the IESG</a> for review, approval, and registration with IANA.</p> 
+    <p><span class="delete">This</span><span class="insert">The</span> information that follows <span class="delete">is being </span><span class="insert">has been </span><a href="https://lists.w3.org/Archives/Member/w3c-archive/2012Nov/0317.html">submitted to the IESG</a> for review, approval, and registration with IANA.</p> 
     <dl> 
       <dt>Type name:</dt> 
       <dd>text</dd>
prov

Hosted by W3C Systems Team, please report bugs to sysreq@w3.org