ISSUE-501
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Tue, 25 Sep 2012 11:36:20 +0100
changeset 4478 0bbd5b38ab1b
parent 4477 fd73db6e4572
child 4479 8aa16461de6e
ISSUE-501
model/diff.html
model/prov-dm.html
--- a/model/diff.html	Mon Sep 24 17:24:11 2012 -0400
+++ b/model/diff.html	Tue Sep 25 11:36:20 2012 +0100
@@ -1,4 +1,3 @@
-
 <!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
 <html lang="en" dir="ltr">
 <head><style type="text/css"><!--
@@ -1027,7 +1026,7 @@
 pre.sh_sourceCode .sh_attribute { color: #006400; }
 
 </style><link href="./extra-dm.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-ED" rel="stylesheet" type="text/css" charset="utf-8"></head> 
-  <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">PROV-DM: The PROV Data Model</h1><h2 id="subtitle"><a href="diff.html"><span class="insert">Changes</span></a><span class="insert"> since LC release</span></h2><h2 id="w3c-editor-s-draft-18-september-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">18 September</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span><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>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd><dt>Latest editor's draft:</dt><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>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
+  <body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">PROV-DM: The PROV Data Model</h1><h2 id="subtitle"><a href="diff.html"><span class="insert">Changes</span></a><span class="insert"> since LC release</span></h2><h2 id="w3c-editor-s-draft-25-september-2012"><acronym title="World Wide Web Consortium">W3C</acronym> <span class="delete">Working</span><span class="insert">Editor's</span> Draft <span class="delete">24 July</span><span class="insert">25 September</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span><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>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a></dd><dt>Latest editor's draft:</dt><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>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-dm-20120503/</span><span class="delete"> (</span><span class="delete">color-coded diffs</span><span class="delete">)</span><a href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</span></a></dd><dt>Editors:</dt><dd><a href="http://www.ecs.soton.ac.uk/~lavm/">Luc Moreau</a>, University of Southampton</dd>
 <dd><a href="http://www.cs.ncl.ac.uk/people/Paolo.Missier">Paolo Missier</a>, Newcastle University</dd>
 <dt><span class="delete">Contributors:</span><span class="insert">Authors:</span></dt><dd><a href="http://semanticweb.org/wiki/Khalid_Belhajjame">Khalid Belhajjame</a>, University of Manchester</dd>
 <dd><span>Reza B'Far</span>, Oracle Corporation</dd>
@@ -1382,7 +1381,7 @@
 publication of a new version of a document.
 </p></div>
 
-<p>
+<span class="delete">
 One might reasonably ask what entities are used and generated by
 driving a car from Boston to Cambridge.  This is answered by
 considering that a single artifact may
@@ -1400,7 +1399,13 @@
 page reporting a traffic violation involving that car.  This breadth
 of provenance allows descriptions of interactions between physical and
 digital artifacts.
-</p>
+</span>
+
+
+
+
+
+
 
 
 
@@ -1412,6 +1417,30 @@
 </p></div>
 
 
+<div class="anexample conceptexample" id="driving-a-car"><div class="anexampleTitle"><span class="insert">Example 5</span><sup><a class="internalDFN" href="#driving-a-car"><span class="diamond"><span class="insert"> ◊</span></span></a></sup></div>
+<p><span class="insert">
+Let us consider the activity of driving a car from Boston to Cambridge.
+One might reasonably ask what entities are used and generated by this activity.
+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.  
+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
+provenance trace of the car might include: designed in Japan,
+manufactured in Korea, shipped to Boston USA, purchased by customer,
+driven to Cambridge, serviced by engineer in Cambridge, etc., all of
+which might be important information when deciding whether or not it
+represents a sensible second-hand purchase.  Or some of it might
+alternatively be relevant when trying to determine the truth of a web
+page reporting a traffic violation involving that car.  This breadth
+of provenance allows descriptions of interactions between physical and
+digital artifacts.
+</span></p>
+</div>
+
+
 <p>The generation of an entity by an activity and its subsequent usage by another activity is termed communication.</p>
 
 <p>
@@ -1422,7 +1451,7 @@
 
 
 
-<div class="anexample conceptexample" id="communication-example"><div class="anexampleTitle">Example 5<sup><a class="internalDFN" href="#communication-example"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample conceptexample" id="communication-example"><div class="anexampleTitle">Example <span class="delete">5</span><span class="insert">6</span><sup><a class="internalDFN" href="#communication-example"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The activity of writing a celebrity article was informed by (a
 communication instance) the activity of intercepting voicemails.
@@ -1448,7 +1477,7 @@
 
 
 
-<div class="anexample conceptexample" id="derivation-example"><div class="anexampleTitle">Example 6<sup><a class="internalDFN" href="#derivation-example"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample conceptexample" id="derivation-example"><div class="anexampleTitle">Example <span class="delete">6</span><span class="insert">7</span><sup><a class="internalDFN" href="#derivation-example"><span class="diamond"> ◊</span></a></sup></div>
 <p>Examples of derivation include  the transformation of a relational table into a
 linked data set, the transformation of a canvas into a painting, the transportation of a work of art from London to New York, and a physical transformation such as the melting of ice into water.</p>
 </div>
@@ -1501,7 +1530,7 @@
 
 
 
-<div class="anexample conceptexample" id="agent-example"><div class="anexampleTitle">Example 7<sup><a class="internalDFN" href="#agent-example"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample conceptexample" id="agent-example"><div class="anexampleTitle">Example <span class="delete">7</span><span class="insert">8</span><sup><a class="internalDFN" href="#agent-example"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 Software for checking the use of grammar in a document may be defined as an agent of a document preparation activity;  one can also describe its provenance, including for instance the vendor and the version history. 
 A site selling books on the Web, the services involved in the processing of orders, and the companies hosting them are also agents.
@@ -1516,7 +1545,7 @@
 <p><span class="glossary-ref">   <span class="dfn">Attribution</span> is the ascribing of an entity to an agent. </span>
 [<a href="#term-attribution">Detailed specification</a>]</p>
 
-<div class="anexample conceptexample" id="attribution-example"><div class="anexampleTitle">Example 8<sup><a class="internalDFN" href="#attribution-example"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample conceptexample" id="attribution-example"><div class="anexampleTitle">Example <span class="delete">8</span><span class="insert">9</span><sup><a class="internalDFN" href="#attribution-example"><span class="diamond"> ◊</span></a></sup></div>
 <p>A blog post can be attributed to an author, a mobile phone to its manufacturer.</p>
 </div>
 
@@ -1531,7 +1560,7 @@
 [<a href="#term-Association">Detailed specification</a>]</p>
 
 
-<div class="anexample conceptexample" id="association-example"><div class="anexampleTitle">Example 9<sup><a class="internalDFN" href="#association-example"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample conceptexample" id="association-example"><div class="anexampleTitle">Example <span class="delete">9</span><span class="insert">10</span><sup><a class="internalDFN" href="#association-example"><span class="diamond"> ◊</span></a></sup></div>
 <p>Examples of association between an activity and an agent are:
 </p><ul>
 <li>creation of a web page under the guidance of a designer;</li>
@@ -1551,7 +1580,7 @@
 
 
 
-<div class="anexample conceptexample" id="delegation-example"><div class="anexampleTitle">Example 10<sup><a class="internalDFN" href="#delegation-example"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample conceptexample" id="delegation-example"><div class="anexampleTitle">Example <span class="delete">10</span><span class="insert">11</span><sup><a class="internalDFN" href="#delegation-example"><span class="diamond"> ◊</span></a></sup></div>
 <p>A student publishing a web page describing an academic
 department could result in both the student and the department being
 agents associated with the activity.  It may not matter which actual
@@ -1631,7 +1660,7 @@
 manage expectation failures, or to provide explanations.</p>
 
 
-<div class="anexample conceptexample" id="association-example2"><div class="anexampleTitle">Example 11<sup><a class="internalDFN" href="#association-example2"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample conceptexample" id="association-example2"><div class="anexampleTitle">Example <span class="delete">11</span><span class="insert">12</span><sup><a class="internalDFN" href="#association-example2"><span class="diamond"> ◊</span></a></sup></div>
 <p>An example of association between an activity and an agent involving a plan is:
 an XSLT transform (an activity) launched by a user (an agent) based on an XSL style sheet (a plan).
 
@@ -1652,7 +1681,7 @@
 more elements.  This optional identifier can then be used to refer to
 an instance as part of other concepts.</p>
 
-<div class="anexample conceptexample" id="identifier-example"><div class="anexampleTitle">Example 12<sup><a class="internalDFN" href="#identifier-example"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample conceptexample" id="identifier-example"><div class="anexampleTitle">Example <span class="delete">12</span><span class="insert">13</span><sup><a class="internalDFN" href="#identifier-example"><span class="diamond"> ◊</span></a></sup></div>
 <p>A service may read a same configuration file on two different occasions. Each  usage can be identifed by its own identifier, allowing them to be distinguished. 
 </p></div>
 
@@ -1692,7 +1721,7 @@
 expressed.
 </p>
 
-<div class="anexample conceptexample" id="bundle-example"><div class="anexampleTitle">Example 13<sup><a class="internalDFN" href="#bundle-example"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample conceptexample" id="bundle-example"><div class="anexampleTitle">Example <span class="delete">13</span><span class="insert">14</span><sup><a class="internalDFN" href="#bundle-example"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 In a decision making situation, decision makers may be presented with the same piece of knowledge, issued by multiple sources.  In order to validate this piece of knowledge, decision makers can consider its provenance, but also the provenance of their provenance, which may help determine whether it can be trusted.
 </p>
@@ -1706,7 +1735,7 @@
 <span class="glossary-ref">   A <span class="dfn">collection</span> is an entity that provides a structure to some constituents, which are themselves 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>. 
 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 14<sup><a class="internalDFN" href="#collection-example"><span class="diamond"> ◊</span></a></sup></div>
+<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>
 <p>
 An example of collection is an archive of documents. Each document has its own provenance, but the archive itself also has some provenance: who maintained it, which documents it contained at which point in time, how it was assembled, etc. 
 </p></div>
@@ -1777,7 +1806,7 @@
 </li>
 </ul>
 
-<div class="anexample" id="anexample-prov-n"><div class="anexampleTitle">Example 15<sup><a class="internalDFN" href="#anexample-prov-n"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-prov-n"><div class="anexampleTitle">Example <span class="delete">15</span><span class="insert">16</span><sup><a class="internalDFN" href="#anexample-prov-n"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 An activity with identifier <span class="name">a1</span> and an attribute <span class="name">type</span> with value <span class="name">createFile</span>.
 </p><pre class="codeexample">activity(a1, [prov:type="createFile"])
@@ -2176,7 +2205,7 @@
 <li><span class="attribute" id="entity.attributes">attributes</span>: an <em class="rfc2119" title="optional">optional</em> set of attribute-value  pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this entity.</li>
 </ul></div>
 
-<div class="anexample" id="anexample-entity"><div class="anexampleTitle">Example 16<sup><a class="internalDFN" href="#anexample-entity"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-entity"><div class="anexampleTitle">Example <span class="delete">16</span><span class="insert">17</span><sup><a class="internalDFN" href="#anexample-entity"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following expression</p>
 <pre class="codeexample">entity(tr:WD-prov-dm-20111215, [ prov:type="document", ex:version="2" ])
@@ -2204,7 +2233,7 @@
 <li><span class="attribute" id="activity.attributes">attributes</span>:  an <em class="rfc2119" title="optional">optional</em> set of attribute-value pairs ((<span class="name">attr1</span>, <span class="name">val1</span>), ...) representing additional information about this activity.</li>
 </ul></div>
 
-<div class="anexample" id="anexample-activity"><div class="anexampleTitle">Example 17<sup><a class="internalDFN" href="#anexample-activity"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-activity"><div class="anexampleTitle">Example <span class="delete">17</span><span class="insert">18</span><sup><a class="internalDFN" href="#anexample-activity"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following expression</p>
 <pre class="codeexample">activity(a1,2011-11-16T16:05:00,2011-11-16T16:06:00,
@@ -2247,7 +2276,7 @@
 
 
 
-<div class="anexample" id="anexample-generation1"><div class="anexampleTitle">Example 18<sup><a class="internalDFN" href="#anexample-generation1"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-generation1"><div class="anexampleTitle">Example <span class="delete">18</span><span class="insert">19</span><sup><a class="internalDFN" href="#anexample-generation1"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following expressions</p>
 <pre class="codeexample">  wasGeneratedBy(e1, a1, 2001-10-26T21:32:52, [ ex:port="p1" ])
@@ -2260,7 +2289,7 @@
 </div>
 
 
-<div class="anexample" id="anexample-generation2"><div class="anexampleTitle">Example 19<sup><a class="internalDFN" href="#anexample-generation2"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-generation2"><div class="anexampleTitle">Example <span class="delete">19</span><span class="insert">20</span><sup><a class="internalDFN" href="#anexample-generation2"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 In some cases, we may want to record the time at which an entity was generated without having to specify the activity that generated it. To support this requirement, the activity element in generation is optional. Hence,  the following expression indicates the time at which an entity is generated, without naming the activity that did it.</p>
 <pre class="codeexample">  wasGeneratedBy(e, -, 2001-10-26T21:32:52)
@@ -2294,7 +2323,7 @@
 </p>
 
 
-<div class="anexample" id="anexample-usage"><div class="anexampleTitle">Example 20<sup><a class="internalDFN" href="#anexample-usage"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-usage"><div class="anexampleTitle">Example <span class="delete">20</span><span class="insert">21</span><sup><a class="internalDFN" href="#anexample-usage"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following usages</p>
 <pre class="codeexample">  used(a1, e1, 2011-11-16T16:00:00, [ ex:parameter="p1" ])
   used(a1, e2, 2011-11-16T16:00:01, [ ex:parameter="p2" ])
@@ -2334,7 +2363,7 @@
 
 
 
-<div class="anexample" id="anexample-communication"><div class="anexampleTitle">Example 21<sup><a class="internalDFN" href="#anexample-communication"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-communication"><div class="anexampleTitle">Example <span class="delete">21</span><span class="insert">22</span><sup><a class="internalDFN" href="#anexample-communication"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 Consider two activities  <span class="name">a1</span> and <span class="name">a2</span>, the former performed by a government agency, and the latter by a driver caught speeding. 
 </p><pre class="codeexample">activity(a1, [ prov:type="traffic regulations enforcing" ])
@@ -2365,7 +2394,7 @@
 <p>While each of <a href="#start.id"><span class="attribute">id</span></a>, <a href="#start.trigger"><span class="attribute">trigger</span></a>, <a href="#start.starter"><span class="attribute">starter</span></a>, <a href="#start.time"><span class="attribute">time</span></a>, and  <a href="#start.attributes"><span class="attribute">attributes</span></a> is <em class="rfc2119" title="optional">optional</em>, at least one of them <em class="rfc2119" title="must">must</em> be present.</p>
 
 
-<div class="anexample" id="anexample-start1"><div class="anexampleTitle">Example 22<sup><a class="internalDFN" href="#anexample-start1"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-start1"><div class="anexampleTitle">Example <span class="delete">22</span><span class="insert">23</span><sup><a class="internalDFN" href="#anexample-start1"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following example contains the description of an activity <span class="name">a1</span> (a discussion), which was started at a specific time, and was triggered by an email message <span class="name">e1</span>.</p>
 <pre class="codeexample">entity(e1, [ prov:type="email message"] )
@@ -2385,7 +2414,7 @@
 </pre>
 </div>
 
-<div class="anexample" id="anexample-start2"><div class="anexampleTitle">Example 23<sup><a class="internalDFN" href="#anexample-start2"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-start2"><div class="anexampleTitle">Example <span class="delete">23</span><span class="insert">24</span><sup><a class="internalDFN" href="#anexample-start2"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 In the following example, a race is started by a bang, and responsibility for this trigger is attributed to an agent 
  <span class="name">ex:Bob</span>.
@@ -2397,7 +2426,7 @@
 </pre>
 </div>
 
-<div class="anexample" id="anexample-start3"><div class="anexampleTitle">Example 24<sup><a class="internalDFN" href="#anexample-start3"><span class="diamond"> ◊</span></a></sup></div>
+<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
 observing low fuel. The trigger entity is unspecified, it could
@@ -2440,7 +2469,7 @@
 <p>While each of <a href="#end.id"><span class="attribute">id</span></a>, <a href="#end.trigger"><span class="attribute">trigger</span></a>, <a href="#end.ender"><span class="attribute">ender</span></a>, <a href="#end.time"><span class="attribute">time</span></a>, and  <a href="#end.attributes"><span class="attribute">attributes</span></a> is <em class="rfc2119" title="optional">optional</em>, at least one of them <em class="rfc2119" title="must">must</em> be present.</p>
 
 
-<div class="anexample" id="anexample-end"><div class="anexampleTitle">Example 25<sup><a class="internalDFN" href="#anexample-end"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-end"><div class="anexampleTitle">Example <span class="delete">25</span><span class="insert">26</span><sup><a class="internalDFN" href="#anexample-end"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following example is a description of an activity <span class="name">a1</span> (editing) that was ended following an approval document <span class="name">e1</span>.</p>
 <pre class="codeexample">entity(e1, [ prov:type="approval document" ])
@@ -2488,7 +2517,7 @@
 
 
 
-<div class="anexample" id="anexample-invalidation1"><div class="anexampleTitle">Example 26<sup><a class="internalDFN" href="#anexample-invalidation1"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-invalidation1"><div class="anexampleTitle">Example <span class="delete">26</span><span class="insert">27</span><sup><a class="internalDFN" href="#anexample-invalidation1"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 <em>The Painter</em>, a Picasso painting, is known to have been destroyed in a <a href="http://en.wikipedia.org/wiki/Lost_artworks#20th_century">plane accident</a>.
 
@@ -2500,7 +2529,7 @@
 </pre>
 </div>
 
-<div class="anexample" id="anexample-invalidation2"><div class="anexampleTitle">Example 27<sup><a class="internalDFN" href="#anexample-invalidation2"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-invalidation2"><div class="anexampleTitle">Example <span class="delete">27</span><span class="insert">28</span><sup><a class="internalDFN" href="#anexample-invalidation2"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The BBC news home page on 2012-04-03 <span class="name">ex:bbcNews2012-04-03</span>
 contained a reference to a given news item
@@ -2513,12 +2542,12 @@
 </pre>
 
 We refer to example
-<a href="#anexample-specialization" class="anexample-ref"><span>Example 42</span></a>
+<a href="#anexample-specialization" class="anexample-ref"><span>Example <span class="delete">42</span><span class="insert">43</span></span></a>
  for further descriptions of the BBC Web site, and to  <a href="#term-membership">Section 5.6.2</a> for a description of the relation <a title="hadMember" href="#dfn-hadmember" class="internalDFN">hadMember</a>.
 </div>
 
 
-<div class="anexample" id="anexample-invalidation3"><div class="anexampleTitle">Example 28<sup><a class="internalDFN" href="#anexample-invalidation3"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-invalidation3"><div class="anexampleTitle">Example <span class="delete">28</span><span class="insert">29</span><sup><a class="internalDFN" href="#anexample-invalidation3"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 In this example, the  "buy one beer, get one free" offer expired at the end of the happy hour.</p>
 <pre class="codeexample">entity(buy_one_beer_get_one_free_offer_during_happy_hour)
@@ -2609,7 +2638,7 @@
 
 
 
-<div class="anexample" id="anexample-derivation"><div class="anexampleTitle">Example 29<sup><a class="internalDFN" href="#anexample-derivation"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-derivation"><div class="anexampleTitle">Example <span class="delete">29</span><span class="insert">30</span><sup><a class="internalDFN" href="#anexample-derivation"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following descriptions are about derivations between  <span class="name">e2</span> and  <span class="name">e1</span>, but no information is provided as to the identity of the activity (and usage and generation) underpinning the derivation. In the second line, a type attribute is also provided.</p>
 <pre class="codeexample">wasDerivedFrom(e2, e1)
 wasDerivedFrom(e2, e1, [ prov:type="physical transform" ])
@@ -2649,7 +2678,7 @@
 
 
 
-<div class="anexample" id="anexample-revision"><div class="anexampleTitle">Example 30<sup><a class="internalDFN" href="#anexample-revision"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-revision"><div class="anexampleTitle">Example <span class="delete">30</span><span class="insert">31</span><sup><a class="internalDFN" href="#anexample-revision"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 Revisiting the example of <a href="#section-example-two">Section 4.2</a>,
 we can now state that the report 
@@ -2682,7 +2711,7 @@
 
 
 
-<div class="anexample" id="anexample-quotation"><div class="anexampleTitle">Example 31<sup><a class="internalDFN" href="#anexample-quotation"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-quotation"><div class="anexampleTitle">Example <span class="delete">31</span><span class="insert">32</span><sup><a class="internalDFN" href="#anexample-quotation"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following paragraph is a quote from one of  <a href="http://thinklinks.wordpress.com/2012/03/07/thoughts-from-the-dagstuhl-principles-of-provenance-workshop/">the author's blogs</a>.
 </p><blockquote id="bl-dagstuhl"><em>
@@ -2734,7 +2763,7 @@
 
 
 
-<div class="anexample" id="anexample-primary-source1"><div class="anexampleTitle">Example 32<sup><a class="internalDFN" href="#anexample-primary-source1"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-primary-source1"><div class="anexampleTitle">Example <span class="delete">32</span><span class="insert">33</span><sup><a class="internalDFN" href="#anexample-primary-source1"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 Let us consider Charles Joseph Minard's flow map of Napoleon's March in
 1812, which was published in 1869. Although the map is not a primary source,
@@ -2822,7 +2851,7 @@
 
 
 
-<div class="anexample" id="example_33"><div class="anexampleTitle">Example 33<sup><a class="internalDFN" href="#example_33"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example_34"><div class="anexampleTitle">Example <span class="delete">33</span><span class="insert">34</span><sup><a class="internalDFN" href="#example_34"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following expression is about an agent identified by <span class="name">e1</span>, which is a person, named Alice, with employee number 1234.</p>
 <pre class="codeexample">agent(e1, [ex:employee="1234", ex:name="Alice", prov:type='prov:Person' ])
 </pre>
@@ -2847,7 +2876,7 @@
 </ul>
 </div>
 
-<div class="anexample" id="anexample-attribution"><div class="anexampleTitle">Example 34<sup><a class="internalDFN" href="#anexample-attribution"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-attribution"><div class="anexampleTitle">Example <span class="delete">34</span><span class="insert">35</span><sup><a class="internalDFN" href="#anexample-attribution"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 Revisiting the example of 
 <a class="section-ref" href="#section-example-one"><span>Section 4.1</span></a>,
@@ -2884,7 +2913,7 @@
 <p>While each of <a href="#association.id"><span class="attribute">id</span></a>, <a href="#association.agent"><span class="attribute">agent</span></a>,  <a href="#association.plan"><span class="attribute">plan</span></a>, and  <a href="#association.attributes"><span class="attribute">attributes</span></a> is <em class="rfc2119" title="optional">optional</em>, at least one of them <em class="rfc2119" title="must">must</em> be present.</p>
 
 
-<div class="anexample" id="anexample-wasAssociatedWith"><div class="anexampleTitle">Example 35<sup><a class="internalDFN" href="#anexample-wasAssociatedWith"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-wasAssociatedWith"><div class="anexampleTitle">Example <span class="delete">35</span><span class="insert">36</span><sup><a class="internalDFN" href="#anexample-wasAssociatedWith"><span class="diamond"> ◊</span></a></sup></div>
 <p>In the following example, a designer agent and an operator agent are associated with an activity. The designer's goals are achieved by a workflow <span class="name">ex:wf</span>, described as an an entity of type <span class="name"><a href="#concept-plan" class="internalDFN">plan</a></span>.   </p>
 <pre class="codeexample">activity(ex:a, [ prov:type="workflow execution" ])
 agent(ex:ag1,  [ prov:type="operator" ])
@@ -2899,7 +2928,7 @@
 for instance.
 </div>
 
-<div class="anexample" id="anexample-wasAssociatedWith-2"><div class="anexampleTitle">Example 36<sup><a class="internalDFN" href="#anexample-wasAssociatedWith-2"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-wasAssociatedWith-2"><div class="anexampleTitle">Example <span class="delete">36</span><span class="insert">37</span><sup><a class="internalDFN" href="#anexample-wasAssociatedWith-2"><span class="diamond"> ◊</span></a></sup></div>
 <p>In some cases, one wants to indicate a plan was followed, without having to specify which agent was involved.</p>
 <pre class="codeexample">activity(ex:a, [ prov:type="workflow execution" ])
 wasAssociatedWith(ex:a, -, ex:wf)
@@ -2942,7 +2971,7 @@
 </ul></div>
 
 
-<div class="anexample" id="example_37"><div class="anexampleTitle">Example 37<sup><a class="internalDFN" href="#example_37"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example_38"><div class="anexampleTitle">Example <span class="delete">37</span><span class="insert">38</span><sup><a class="internalDFN" href="#example_38"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following fragment describes three agents: a programmer, a researcher, and a funder.  The programmer and researcher are associated with a workflow activity.  The programmer acts on behalf
 of the researcher (line-management) encoding the commands specified by the researcher; the researcher acts on behalf of the funder, who has a contractual agreement with the researcher. The terms
 'line-management' and 'contract' used in this example are domain specific.</p>
@@ -2986,7 +3015,7 @@
 <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-start" class="internalDFN">start</a>, <a href="#concept-end" class="internalDFN">end</a>, <a href="#concept-generation" class="internalDFN">generation</a>, <a href="#concept-invalidation" class="internalDFN">invalidation</a>, <a href="#concept-communication" class="internalDFN">communication</a>, <a href="#concept-derivation" class="internalDFN">derivation</a>, <a href="#concept-attribution" class="internalDFN">attribution</a>, <a href="#concept-activityAssociation" class="internalDFN">association</a>, and <a href="#concept-delegation" class="internalDFN">delegation</a> are particular cases of  influence. 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 class="anexample" id="example_38"><div class="anexampleTitle">Example 38<sup><a class="internalDFN" href="#example_38"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example_39"><div class="anexampleTitle">Example <span class="delete">38</span><span class="insert">39</span><sup><a class="internalDFN" href="#example_39"><span class="diamond"> ◊</span></a></sup></div>
 <p>We refer to the example of <a class="section-ref" href="#section-example-two"><span>Section 4.2</span></a>, and specifically to <a href="#prov-a-document2-top">Figure 3</a>.
 We could have expressed that the influence of
 <span class="name">w3:Consortium</span> 
@@ -3078,11 +3107,11 @@
 
 
 <p>The provenance of provenance can then be described using PROV constructs, as illustrated by
-<a href="#anexample-provenance-of-provenance" class="anexample-ref"><span>Example 39</span></a>
+<a href="#anexample-provenance-of-provenance" class="anexample-ref"><span>Example <span class="delete">39</span><span class="insert">40</span></span></a>
 and
-<a href="#anexample-provenance-aggregation" class="anexample-ref"><span>Example 40</span></a>.</p>
-
-<div class="anexample" id="anexample-provenance-of-provenance"><div class="anexampleTitle">Example 39<sup><a class="internalDFN" href="#anexample-provenance-of-provenance"><span class="diamond"> ◊</span></a></sup></div>
+<a href="#anexample-provenance-aggregation" class="anexample-ref"><span>Example <span class="delete">40</span><span class="insert">41</span></span></a>.</p>
+
+<div class="anexample" id="anexample-provenance-of-provenance"><div class="anexampleTitle">Example <span class="delete">39</span><span class="insert">40</span><sup><a class="internalDFN" href="#anexample-provenance-of-provenance"><span class="diamond"> ◊</span></a></sup></div>
 <p>Let us consider two entities <span class="name">ex:report1</span> and <span class="name">ex:report2</span>.</p>
 <pre class="codeexample"> 
 entity(ex:report1, [ prov:type="report", ex:version=1 ])
@@ -3129,7 +3158,7 @@
 </pre>
 </div>
 
-<div class="anexample" id="anexample-provenance-aggregation"><div class="anexampleTitle">Example 40<sup><a class="internalDFN" href="#anexample-provenance-aggregation"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-provenance-aggregation"><div class="anexampleTitle">Example <span class="delete">40</span><span class="insert">41</span><sup><a class="internalDFN" href="#anexample-provenance-aggregation"><span class="diamond"> ◊</span></a></sup></div>
 <p>A provenance aggregator could merge two bundles, resulting in a novel bundle, whose provenance is described as follows.</p>
 <pre class="codeexample"> 
 bundle agg:bundle3
@@ -3178,7 +3207,7 @@
 
 
 <p>Two provenance descriptions about the same thing may emphasize differents aspects of that thing.</p>
-<div class="anexample" id="entity-example1"><div class="anexampleTitle">Example 41<sup><a class="internalDFN" href="#entity-example1"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="entity-example1"><div class="anexampleTitle">Example <span class="delete">41</span><span class="insert">42</span><sup><a class="internalDFN" href="#entity-example1"><span class="diamond"> ◊</span></a></sup></div>
 <p>User Alice writes an article. In its provenance, she wishes to refer to the precise version of the article with a date-specific IRI, as she might edit the article later. Alternatively, user Bob refers to the article in general, independently of its variants over time.</p>
 </div>
 <p>
@@ -3211,7 +3240,7 @@
 </div>
 
 
-<div class="anexample" id="anexample-specialization"><div class="anexampleTitle">Example 42<sup><a class="internalDFN" href="#anexample-specialization"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-specialization"><div class="anexampleTitle">Example <span class="delete">42</span><span class="insert">43</span><sup><a class="internalDFN" href="#anexample-specialization"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The BBC news home page on 2012-03-23 <span class="name">ex:bbcNews2012-03-23</span>
 is a specialization of the BBC news page in general
@@ -3246,7 +3275,7 @@
 </ul>
 </div>
 
-<div class="anexample" id="anexample-alternate"><div class="anexampleTitle">Example 43<sup><a class="internalDFN" href="#anexample-alternate"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-alternate"><div class="anexampleTitle">Example <span class="delete">43</span><span class="insert">44</span><sup><a class="internalDFN" href="#anexample-alternate"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 A given news item on the BBC News site 
  <a href="http://www.bbc.co.uk/news/science-environment-17526723">bbc:news/science-environment-17526723</a> for desktop
@@ -3262,7 +3291,7 @@
 </div>
 
 
-<div class="anexample" id="anexample-alternate2"><div class="anexampleTitle">Example 44<sup><a class="internalDFN" href="#anexample-alternate2"><span class="diamond"> ◊</span></a></sup></div>
+<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.
 </p><pre class="codeexample">entity(tr:WD-prov-dm-20111018)
@@ -3324,7 +3353,7 @@
 </ul>
 </div>
 
-<div class="anexample" id="anexample-mention-rating"><div class="anexampleTitle">Example 45<sup><a class="internalDFN" href="#anexample-mention-rating"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-mention-rating"><div class="anexampleTitle">Example <span class="delete">45</span><span class="insert">46</span><sup><a class="internalDFN" href="#anexample-mention-rating"><span class="diamond"> ◊</span></a></sup></div>
 <p>This example is concerned with a performance rating tool that reads and processes provenance to determine the performance of agents.  To keep the example simple, an agent's performance is determined by the duration of the activities it is associated with. </p>
 <p>As an illustration, we consider that two bundles <span class="name">ex:run1</span> and <span class="name">ex:run2</span> refer to an agent <span class="name">ex:Bob</span> that controlled two activities <span class="name">ex:a1</span> and <span class="name">ex:a2</span>. </p>
 
@@ -3351,7 +3380,7 @@
 </div>
 
 
-<div class="anexample" id="aexample-mention-viz"><div class="anexampleTitle">Example 46<sup><a class="internalDFN" href="#aexample-mention-viz"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="aexample-mention-viz"><div class="anexampleTitle">Example <span class="delete">46</span><span class="insert">47</span><sup><a class="internalDFN" href="#aexample-mention-viz"><span class="diamond"> ◊</span></a></sup></div>
 <p>Consider the following bundle of descriptions, in which derivation and generations have been identified.
 </p><pre class="codeexample"> 
 bundle obs:bundle1
@@ -3436,7 +3465,7 @@
 </li></ul>
 
 
-<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>
+<div class="anexample" id="example_48"><div class="anexampleTitle">Example <span class="delete">47</span><span class="insert">48</span><sup><a class="internalDFN" href="#example_48"><span class="diamond"> ◊</span></a></sup></div>
 <pre class="codeexample">entity(c0, [prov:type='prov:EmptyCollection' ])  // c0 is an empty collection
 entity(c1, [prov:type='prov:Collection'  ])      // c1 is a collection, with unknown content
 </pre>
@@ -3464,7 +3493,7 @@
 
 
 
-<div class="anexample" id="example_48"><div class="anexampleTitle">Example 48<sup><a class="internalDFN" href="#example_48"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example_49"><div class="anexampleTitle">Example <span class="delete">48</span><span class="insert">49</span><sup><a class="internalDFN" href="#example_49"><span class="diamond"> ◊</span></a></sup></div>
 <p>In this example, <span class="name">c</span> is a collection known to have <span class="name">e0</span>, <span class="name">e1</span>, and <span class="name">e2</span> as members, and may have other members.</p>
 <pre class="codeexample">entity(e0)
 entity(e1)
@@ -3541,7 +3570,7 @@
 <span class="glossary-ref">    The attribute <dfn id="concept-label" title="label" class="internalDFN"><span class="name">prov:label</span></dfn><sup><a class="internalDFN" href="#concept-label"><span class="diamond"> ◊</span></a></sup> provides a human-readable representation of an instance of a PROV-DM type or relation.   </span>
 The value associated with the attribute <span class="name">prov:label</span> <em class="rfc2119" title="must">must</em> be a string.</p>
 
-<div class="anexample" id="example_49"><div class="anexampleTitle">Example 49<sup><a class="internalDFN" href="#example_49"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example_50"><div class="anexampleTitle">Example <span class="delete">49</span><span class="insert">50</span><sup><a class="internalDFN" href="#example_50"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following entity is provided with a label attribute.</p>
 <pre class="codeexample"> entity(ex:e1, [ prov:label="This is a human-readable label" ])
 </pre>
@@ -3565,7 +3594,7 @@
 The attribute <span class="name">prov:location</span> is an <em class="rfc2119" title="optional">optional</em> attribute of <a href="#concept-entity" class="internalDFN">Entity</a>, <a href="#concept-activity" class="internalDFN">Activity</a>, <a href="#concept-agent" class="internalDFN">Agent</a>, <a href="#concept-usage" class="internalDFN">Usage</a>, <a href="#concept-generation" class="internalDFN">Generation</a>, <a href="#concept-invalidation" class="internalDFN">Invalidation</a>, <a href="#concept-start" class="internalDFN">Start</a>, and <a href="#concept-end" class="internalDFN">End</a>.  The value associated with the  attribute <span class="name">prov:location</span> <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>, expected to denote a location.
 </p>
 
-<div class="anexample" id="example-location"><div class="anexampleTitle">Example 50<sup><a class="internalDFN" href="#example-location"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example-location"><div class="anexampleTitle">Example <span class="delete">50</span><span class="insert">51</span><sup><a class="internalDFN" href="#example-location"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following expression describes entity Mona Lisa, a painting, with a location attribute. </p>
 <pre class="codeexample"> entity(ex:MonaLisa, [ prov:location="Le Louvre, Paris", prov:type="StillImage" ])
 </pre>
@@ -3586,7 +3615,7 @@
 <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>
 
-<div class="anexample" id="anexample-role"><div class="anexampleTitle">Example 51<sup><a class="internalDFN" href="#anexample-role"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-role"><div class="anexampleTitle">Example <span class="delete">51</span><span class="insert">52</span><sup><a class="internalDFN" href="#anexample-role"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following activity is associated with an agent acting as the operator. </p>
 <pre class="codeexample"> wasAssociatedWith(a, ag, [ prov:role="operator" ])
 </pre>
@@ -3607,7 +3636,7 @@
 the value associated with a <span class="name">prov:type</span> attribute <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value.</a> The attribute <span class="name">prov:type</span>
 is allowed to occur multiple times.</p>
 
-<div class="anexample" id="example_52"><div class="anexampleTitle">Example 52<sup><a class="internalDFN" href="#example_52"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example_53"><div class="anexampleTitle">Example <span class="delete">52</span><span class="insert">53</span><sup><a class="internalDFN" href="#example_53"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following describes an agent of type software agent.</p>
 <pre class="codeexample">   agent(ag, [ prov:type='prov:SoftwareAgent' ])
 </pre>
@@ -3644,7 +3673,7 @@
 
 <p>The attribute <span class="name">prov:value</span> is an <em class="rfc2119" title="optional">optional</em> attribute of entity.  The value associated with the  attribute <span class="name">prov:value</span> <em class="rfc2119" title="must">must</em> be a PROV-DM <a title="value" href="#concept-value" class="internalDFN">Value</a>. The attribute <span class="name">prov:value</span> <em class="rfc2119" title="may">may</em> occur at most once in a set of attribute-value pairs.</p>
 
-<div class="anexample" id="example_53"><div class="anexampleTitle">Example 53<sup><a class="internalDFN" href="#example_53"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="example_54"><div class="anexampleTitle">Example <span class="delete">53</span><span class="insert">54</span><sup><a class="internalDFN" href="#example_54"><span class="diamond"> ◊</span></a></sup></div>
 <p>The following example illustrates the provenance of the number <span class="name">4</span> obtained by an activity that computed the length of an input string <span class="name">"abcd"</span>.
 The input and the output are expressed as entities <span class="name">ex:in</span> and <span class="name">ex:out</span>, respectively. They each have a <span class="name">prov:value</span> attribute associated with the corresponding value.
 </p>
@@ -3706,7 +3735,7 @@
 
 
 
-<div class="anexample" id="anexample-value"><div class="anexampleTitle">Example 54<sup><a class="internalDFN" href="#anexample-value"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-value"><div class="anexampleTitle">Example <span class="delete">54</span><span class="insert">55</span><sup><a class="internalDFN" href="#anexample-value"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 The following examples respectively are the string "abc", the integer number 1, and the IRI "http://example.org/foo".
 </p><pre class="codeexample">  "abc"
@@ -3728,7 +3757,7 @@
 <p>We note that PROV-DM <dfn title="time" id="dfn-time" class="internalDFN">time instants</dfn><sup><a class="internalDFN" href="#dfn-time"><span class="diamond"> ◊</span></a></sup> are defined according to xsd:dateTime [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p> 
 
 
-<div class="anexample" id="anexample-time"><div class="anexampleTitle">Example 55<sup><a class="internalDFN" href="#anexample-time"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-time"><div class="anexampleTitle">Example <span class="delete">55</span><span class="insert">56</span><sup><a class="internalDFN" href="#anexample-time"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 In the following example, the generation time of entity <span class="name">e1</span> is expressed according to 
 <a href="http://www.w3.org/TR/xmlschema11-2/#dateTime">xsd:dateTime</a>  [<cite><a class="bibref" rel="biblioentry" href="#bib-XMLSCHEMA11-2">XMLSCHEMA11-2</a></cite>].</p>
@@ -3792,7 +3821,7 @@
 <li>Sub-types and sub-relations can be expressed by means of the reserved attribute 
 <a href="#term-attribute-type"><span class="name">prov:type</span></a>.
 
-<div class="anexample" id="anexample-sub-relation"><div class="anexampleTitle">Example 56<sup><a class="internalDFN" href="#anexample-sub-relation"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-sub-relation"><div class="anexampleTitle">Example <span class="delete">56</span><span class="insert">57</span><sup><a class="internalDFN" href="#anexample-sub-relation"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 In the following example,  <span class="name">e2</span> is a translation of <span class="name">e1</span>,
 expressed as a sub-type of derivation.
@@ -3801,7 +3830,7 @@
 </pre>
 </div>
 
-<div class="anexample" id="anexample-sub-type"><div class="anexampleTitle">Example 57<sup><a class="internalDFN" href="#anexample-sub-type"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-sub-type"><div class="anexampleTitle">Example <span class="delete">57</span><span class="insert">58</span><sup><a class="internalDFN" href="#anexample-sub-type"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 In the following example,  <span class="name">e</span> is described as a Car, a type of entity.
 </p><pre class="codeexample"> 
@@ -3817,7 +3846,7 @@
 <li>Application and domain specific roles can be expressed by means of the reserved attribute 
 <a href="#term-attribute-role"><span class="name">prov:role</span></a>.
 
-<div class="anexample" id="anexample-usage-with-role"><div class="anexampleTitle">Example 58<sup><a class="internalDFN" href="#anexample-usage-with-role"><span class="diamond"> ◊</span></a></sup></div>
+<div class="anexample" id="anexample-usage-with-role"><div class="anexampleTitle">Example <span class="delete">58</span><span class="insert">59</span><sup><a class="internalDFN" href="#anexample-usage-with-role"><span class="diamond"> ◊</span></a></sup></div>
 <p>
 In the following example,  two computers  <span class="name">ex:laptop4</span> and <span class="name">ex:desktop9</span> are used in different roles in a work activity.
 </p><pre class="codeexample"> 
@@ -4110,8 +4139,9 @@
 
 </p><ul>
 <li> <a href="http://www.w3.org/2011/prov/track/issues/506"><span class="insert">ISSUE-506</span></a><span class="insert">: Updated role from author to contributor, in line with text.
-</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/492"><span class="insert">ISSUE-492</span></a><span class="insert">: Fixed typos in  </span><a href="#anexample-invalidation3" class="anexample-ref"><span><span class="insert">Example 28</span></span></a><span class="insert">.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/492"><span class="insert">ISSUE-492</span></a><span class="insert">: Fixed typos in  </span><a href="#anexample-invalidation3" class="anexample-ref"><span><span class="insert">Example 29</span></span></a><span class="insert">.
 </span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/508"><span class="insert">ISSUE-508</span></a><span class="insert">: Clarified the bold names and parameters  in  text preceding </span><a href="#prov-dm-types-and-relations-fig"><span class="insert">Table 5</span></a><span class="insert">.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/501"><span class="insert">ISSUE-501</span></a><span class="insert">: Put the example about driving a car to Boston in a box.
 </span></li></ul>
 
 </div>
--- a/model/prov-dm.html	Mon Sep 24 17:24:11 2012 -0400
+++ b/model/prov-dm.html	Tue Sep 25 11:36:20 2012 +0100
@@ -853,9 +853,22 @@
 publication of a new version of a document.
 </div>
 
+
+
+
+
+<div class="anexample conceptexample" id="usage-example">
+<p>Usage examples include a procedure beginning to consume an argument, a service starting to read a value on a port, a program beginning to read a configuration
+file, or the point at which an ingredient, such as eggs, is being added in a baking activity. Usage may entirely consume an entity (e.g. eggs are no longer available after being added to
+the mix); in contrast, the same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
+</div>
+
+
+<div class="anexample conceptexample" id="driving-a-car">
 <p>
-One might reasonably ask what entities are used and generated by
-driving a car from Boston to Cambridge.  This is answered by
+Let us consider the activity of driving a car from Boston to Cambridge.
+One might reasonably ask what entities are used and generated by this activity.
+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.  
@@ -872,14 +885,6 @@
 of provenance allows descriptions of interactions between physical and
 digital artifacts.
 </p>
-
-
-
-
-<div class="anexample conceptexample" id="usage-example">
-<p>Usage examples include a procedure beginning to consume an argument, a service starting to read a value on a port, a program beginning to read a configuration
-file, or the point at which an ingredient, such as eggs, is being added in a baking activity. Usage may entirely consume an entity (e.g. eggs are no longer available after being added to
-the mix); in contrast, the same entity may be used multiple times, possibly by different activities (e.g. a file on a file system can be read indefinitely).
 </div>
 
 
@@ -4058,6 +4063,7 @@
 <li> <a href="http://www.w3.org/2011/prov/track/issues/506">ISSUE-506</a>: Updated role from author to contributor, in line with text.
 <li> <a href="http://www.w3.org/2011/prov/track/issues/492">ISSUE-492</a>: Fixed typos in  <a href="#anexample-invalidation3" class="anexample-ref"><span>Example REF</span></a>.
 <li> <a href="http://www.w3.org/2011/prov/track/issues/508">ISSUE-508</a>: Clarified the bold names and parameters  in  text preceding <a href="#prov-dm-types-and-relations-fig">Table 5</a>.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/501">ISSUE-501</a>: Put the example about driving a car to Boston in a box.
 </ul>
 
 </section>