--- a/links/comments/review-simon.txt	Mon Apr 08 22:13:53 2013 +0100
+++ b/links/comments/review-simon.txt	Mon Apr 08 22:21:59 2013 +0100
@@ -1,3 +1,15 @@
+
+Hi Simon,
+
+Thanks for your review. Changes have been implemented and a new version
+is  staged at
+https://dvcs.w3.org/hg/prov/raw-file/default/links/releases/NOTE-prov-links-20130430/Overview.html
+
+Responses to your comments interleaved below.
+Regards,
+Luc
+
+
 > 
 > 
 > Hello Luc, Tim,
@@ -87,6 +99,9 @@
 > o be Americanized)
 > 
 > 
+
+Done
+
 > 
 > Section 3
 > ---------

--- a/links/comments/review-tom.txt	Mon Apr 08 22:13:53 2013 +0100
+++ b/links/comments/review-tom.txt	Mon Apr 08 22:21:59 2013 +0100
@@ -1,3 +1,5 @@
+
+
 > Hello Luc and Tim,
 > 
 > Included below is my review of PROV-Links (latest ED)

--- a/links/diff.html	Mon Apr 08 22:13:53 2013 +0100
+++ b/links/diff.html	Mon Apr 08 22:21:59 2013 +0100
@@ -1138,13 +1138,15 @@
   <span class="delete">wasGeneratedBy(ex:g2; ex:report2,</span><span class="insert">wasGeneratedBy(ex:report2,</span> -, 2012-05-25T11:00:01)
   wasDerivedFrom(ex:report2, ex:report1)
 endBundle
-</pre><span class="insert">
-Bundle </span><span class="name"><span class="insert">obs:bundle1</span></span><span class="insert"> was attributed to agent </span><span class="name"><span class="insert">ex:observer01</span></span><span class="insert">, as described by the following:
-</span><pre class="codeexample"> 
+<span class="delete">entity(obs:bundle1, [ prov:type='prov:Bundle' ])
+wasAttributedTo(obs:bundle1, ex:observer01)
+</span></pre>
+Bundle <span class="name">obs:bundle1</span> <span class="insert">was attributed to agent </span><span class="name"><span class="insert">ex:observer01</span></span><span class="insert">, as described by the following:
+</span><pre class="codeexample"><span class="insert"> 
 entity(obs:bundle1, [ prov:type='prov:Bundle' ])
 wasAttributedTo(obs:bundle1, ex:observer01)
-</pre>
-<span class="delete">Bundle</span><span class="insert">Let us assume that bundle</span> <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may<span class="insert"> be</span> useful for the visualization layout of this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered.  The original  bundle obviously cannot be changed. However, one can create a new bundle, as follows.
+</span></pre><span class="insert">
+Let us assume that bundle </span><span class="name"><span class="insert">obs:bundle1</span></span> is rendered by a <span class="delete">visualisation</span><span class="insert">visualization</span> tool.  It may<span class="insert"> be</span> useful for the visualization layout of this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered.  The original  bundle obviously cannot be changed. However, one can create a new bundle, as follows.
 <pre class="codeexample"> 
 bundle tool:bundle2
   entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
@@ -1158,14 +1160,14 @@
 endBundle
 </pre>
 
-<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming visualisation-specific attributes, types or values.</p>
+<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming <span class="delete">visualisation-specific</span><span class="insert">visualization-specific</span> attributes, types or values.</p>
 
 <p>This example is typical of a common situation in distributed environments, where the consumer and producer of provenance are different.</p>
 
-<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualisation tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
+<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the <span class="delete">visualisation</span><span class="insert">visualization</span> tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
 </p>
 
-<p>The visualisation tool
+<p>The <span class="delete">visualisation</span><span class="insert">visualization</span> tool
  created  new identifiers <span class="name">tool:report1</span> and
 <span class="name">tool:report2</span>.
 They denote entities which are specializations of <span class="name">ex:report1</span> and <span class="name">ex:report2</span>, described in bundle <span class="name">obs:bundle1</span>, with visualization attribute for the color to be used when rendering these entities.   </p>

--- a/links/prov-links.html	Mon Apr 08 22:13:53 2013 +0100
+++ b/links/prov-links.html	Mon Apr 08 22:21:59 2013 +0100
@@ -975,7 +975,7 @@
 entity(obs:bundle1, [ prov:type='prov:Bundle' ])
 wasAttributedTo(obs:bundle1, ex:observer01)
 </pre>
-Let us assume that bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may be useful for the visualization layout of this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered.  The original  bundle obviously cannot be changed. However, one can create a new bundle, as follows.
+Let us assume that bundle <span class="name">obs:bundle1</span> is rendered by a visualization tool.  It may be useful for the visualization layout of this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered.  The original  bundle obviously cannot be changed. However, one can create a new bundle, as follows.
 <pre class="codeexample"> 
 bundle tool:bundle2
   entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
@@ -989,14 +989,14 @@
 endBundle
 </pre>
 
-<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming visualisation-specific attributes, types or values.</p>
+<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming visualization-specific attributes, types or values.</p>
 
 <p>This example is typical of a common situation in distributed environments, where the consumer and producer of provenance are different.</p>
 
-<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualisation tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
+<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualization tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
 </p>
 
-<p>The visualisation tool
+<p>The visualization tool
  created  new identifiers <span class="name">tool:report1</span> and
 <span class="name">tool:report2</span>.
 They denote entities which are specializations of <span class="name">ex:report1</span> and <span class="name">ex:report2</span>, described in bundle <span class="name">obs:bundle1</span>, with visualization attribute for the color to be used when rendering these entities.   </p>

--- a/links/releases/NOTE-prov-links-20130430/Overview.html	Mon Apr 08 22:13:53 2013 +0100
+++ b/links/releases/NOTE-prov-links-20130430/Overview.html	Mon Apr 08 22:21:59 2013 +0100
@@ -1109,7 +1109,7 @@
 entity(obs:bundle1, [ prov:type='prov:Bundle' ])
 wasAttributedTo(obs:bundle1, ex:observer01)
 </pre>
-Let us assume that bundle <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may be useful for the visualization layout of this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered.  The original  bundle obviously cannot be changed. However, one can create a new bundle, as follows.
+Let us assume that bundle <span class="name">obs:bundle1</span> is rendered by a visualization tool.  It may be useful for the visualization layout of this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered.  The original  bundle obviously cannot be changed. However, one can create a new bundle, as follows.
 <pre class="codeexample"> 
 bundle tool:bundle2
   entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
@@ -1123,14 +1123,14 @@
 endBundle
 </pre>
 
-<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming visualisation-specific attributes, types or values.</p>
+<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming visualization-specific attributes, types or values.</p>
 
 <p>This example is typical of a common situation in distributed environments, where the consumer and producer of provenance are different.</p>
 
-<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualisation tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
+<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualization tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
 </p>
 
-<p>The visualisation tool
+<p>The visualization tool
  created  new identifiers <span class="name">tool:report1</span> and
 <span class="name">tool:report2</span>.
 They denote entities which are specializations of <span class="name">ex:report1</span> and <span class="name">ex:report2</span>, described in bundle <span class="name">obs:bundle1</span>, with visualization attribute for the color to be used when rendering these entities.   </p>

--- a/links/releases/NOTE-prov-links-20130430/diff.html	Mon Apr 08 22:13:53 2013 +0100
+++ b/links/releases/NOTE-prov-links-20130430/diff.html	Mon Apr 08 22:21:59 2013 +0100
@@ -1138,13 +1138,15 @@
   <span class="delete">wasGeneratedBy(ex:g2; ex:report2,</span><span class="insert">wasGeneratedBy(ex:report2,</span> -, 2012-05-25T11:00:01)
   wasDerivedFrom(ex:report2, ex:report1)
 endBundle
-</pre><span class="insert">
-Bundle </span><span class="name"><span class="insert">obs:bundle1</span></span><span class="insert"> was attributed to agent </span><span class="name"><span class="insert">ex:observer01</span></span><span class="insert">, as described by the following:
-</span><pre class="codeexample"> 
+<span class="delete">entity(obs:bundle1, [ prov:type='prov:Bundle' ])
+wasAttributedTo(obs:bundle1, ex:observer01)
+</span></pre>
+Bundle <span class="name">obs:bundle1</span> <span class="insert">was attributed to agent </span><span class="name"><span class="insert">ex:observer01</span></span><span class="insert">, as described by the following:
+</span><pre class="codeexample"><span class="insert"> 
 entity(obs:bundle1, [ prov:type='prov:Bundle' ])
 wasAttributedTo(obs:bundle1, ex:observer01)
-</pre>
-<span class="delete">Bundle</span><span class="insert">Let us assume that bundle</span> <span class="name">obs:bundle1</span> is rendered by a visualisation tool.  It may<span class="insert"> be</span> useful for the visualization layout of this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered.  The original  bundle obviously cannot be changed. However, one can create a new bundle, as follows.
+</span></pre><span class="insert">
+Let us assume that bundle </span><span class="name"><span class="insert">obs:bundle1</span></span> is rendered by a <span class="delete">visualisation</span><span class="insert">visualization</span> tool.  It may<span class="insert"> be</span> useful for the visualization layout of this bundle to be shared along with the provenance descriptions, so that other users can render provenance as it was originally rendered.  The original  bundle obviously cannot be changed. However, one can create a new bundle, as follows.
 <pre class="codeexample"> 
 bundle tool:bundle2
   entity(tool:bundle2, [ prov:type='viz:Configuration', prov:type='prov:Bundle' ])
@@ -1158,14 +1160,14 @@
 endBundle
 </pre>
 
-<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming visualisation-specific attributes, types or values.</p>
+<p>In bundle <span class="name">tool:bundle2</span>, the prefix <span class="name">viz</span> is used for naming <span class="delete">visualisation-specific</span><span class="insert">visualization-specific</span> attributes, types or values.</p>
 
 <p>This example is typical of a common situation in distributed environments, where the consumer and producer of provenance are different.</p>
 
-<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the visualisation tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
+<p>Bundle <span class="name">tool:bundle2</span> is given type <span class="name">viz:Configuration</span> to indicate that it consists of descriptions that pertain to the configuration of the <span class="delete">visualisation</span><span class="insert">visualization</span> tool. This type attribute can be used for searching bundles containing visualization-related descriptions.
 </p>
 
-<p>The visualisation tool
+<p>The <span class="delete">visualisation</span><span class="insert">visualization</span> tool
  created  new identifiers <span class="name">tool:report1</span> and
 <span class="name">tool:report2</span>.
 They denote entities which are specializations of <span class="name">ex:report1</span> and <span class="name">ex:report2</span>, described in bundle <span class="name">obs:bundle1</span>, with visualization attribute for the color to be used when rendering these entities.   </p>