prov-n issue 438
authorLuc Moreau <l.moreau@ecs.soton.ac.uk>
Tue, 10 Jul 2012 23:50:41 +0100
changeset 3932 720bc1d1a3bf
parent 3931 3bb1e74cf5de
child 3933 70370692b272
prov-n issue 438
model/diff-n.html
--- a/model/diff-n.html	Tue Jul 10 23:48:46 2012 +0100
+++ b/model/diff-n.html	Tue Jul 10 23:50:41 2012 +0100
@@ -568,20 +568,24 @@
 <li> <span class="delete">PROV-N,</span><a href="http://www.w3.org/TR/prov-n/"><span class="insert">PROV-N</span></a><span class="insert">,</span> a notation for provenance aimed at human consumption  (this document);</li>
 <li> <span class="delete">PROV-O,</span><a href="http://www.w3.org/TR/prov-o/"><span class="insert">PROV-O</span></a><span class="insert">,</span> the PROV ontology, an <span class="delete">OWL-RL</span><span class="insert">OWL2</span> ontology allowing the mapping of PROV to RDF;</li>
 <li> <span class="delete">PROV-AQ,</span><a href="http://www.w3.org/TR/prov-aq/"><span class="insert">PROV-AQ</span></a><span class="insert">,</span> the mechanisms for accessing and querying provenance; </li>
-<li> <span class="delete">PROV-PRIMER,</span><a href="http://www.w3.org/TR/prov-primer/"><span class="insert">PROV-PRIMER</span></a><span class="insert">,</span> a primer for the PROV data model;</li>
-<li> PROV-SEM, a formal semantics for the PROV data model;</li>
-<li> PROV-XML, an XML schema for the PROV data model.</li>
+<li> <span class="delete">PROV-PRIMER,</span><a href="http://www.w3.org/TR/prov-primer/"><span class="insert">PROV-PRIMER</span></a><span class="insert">,</span> a primer<span class="delete"> for the PROV data model;</span>
+<span class="delete"> PROV-SEM, a formal semantics for the PROV data model;</span>
+<span class="delete"> PROV-XML, an XML schema</span> for the PROV data model.</li>
+
+
 </ul>
 <h4 id="how-to-read-the-prov-family-of-specifications">How to read the PROV Family of Specifications</h4>
 <ul>
 <li>The primer is the entry point to PROV offering an introduction to the provenance model.</li>
-<li>The Linked Data and Semantic Web community should focus on PROV-O defining PROV classes and properties specified in an <span class="delete">OWL-RL</span><span class="insert">OWL2</span> ontology. For further details, PROV-DM and PROV-CONSTRAINTS specify the constraints applicable to the data model, and its interpretation. PROV-SEM provides a mathematical semantics.</li>
-<li>The XML community should focus on PROV-XML defining an XML schema for PROV. Further details can also be found in PROV-DM, PROV-CONSTRAINTS, and PROV-SEM.</li>
+<li>The Linked Data and Semantic Web community should focus on PROV-O defining PROV classes and properties specified in an <span class="delete">OWL-RL</span><span class="insert">OWL2</span> ontology. For further details, PROV-DM and PROV-CONSTRAINTS specify the constraints applicable to the data model, and its interpretation. <span class="delete">PROV-SEM provides a mathematical semantics.</span></li>
+<span class="delete">The XML community should focus on PROV-XML defining an XML schema for PROV. Further details can also be found in PROV-DM, PROV-CONSTRAINTS, and PROV-SEM.</span>
+
+
 <li>Developers seeking to retrieve or publish provenance should focus on PROV-AQ.</li>
 <li>Readers seeking to implement other PROV serializations
-should focus on PROV-DM and PROV-CONSTRAINTS.  PROV-O, PROV-N, PROV-XML offer examples of mapping to RDF, text, and XML, respectively.</li>
+should focus on PROV-DM and PROV-CONSTRAINTS.  <span class="delete">PROV-O, PROV-N, PROV-XML</span><span class="insert">PROV-O and PROV-N</span> offer examples of mapping to <span class="delete">RDF,</span><span class="insert">RDF and</span> text,<span class="delete"> and XML,</span> respectively.</li>
 </ul>
-<p>This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a> (<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archives</a>). All feedback is welcome.</p><p>Publication as an Editor's Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#purpose" class="tocxref"><span class="secno">1.1 </span>Purpose of this Document and target audience</a></li><li class="tocline"><a href="#structure-of-this-document" class="tocxref"><span class="secno">1.2 </span>Structure of this Document</a></li><li class="tocline"><a href="#notational-conventions" class="tocxref"><span class="secno">1.3 </span>Notational Conventions</a></li></ul></li><li class="tocline"><a href="#general-conventions" class="tocxref"><span class="secno">2. </span>General grammar considerations</a><ul class="toc"><li class="tocline"><a href="#functional-syntax" class="tocxref"><span class="secno">2.1 </span>Functional-style Syntax</a></li><li class="tocline"><a href="#grammar-notation" class="tocxref"><span class="secno">2.2 </span>EBNF Grammar</a></li><li class="tocline"><a href="#main-productions" class="tocxref"><span class="secno"><span class="insert">2.3 </span></span><span class="insert">Main Productions</span></a></li><li class="tocline"><a href="#prov-n-optionals" class="tocxref"><span class="secno"><span class="delete">2.3</span><span class="insert">2.4</span> </span>Optional terms in expressions</a></li><li class="tocline"><a href="#prov-n-standard-terms" class="tocxref"><span class="secno"><span class="delete">2.4</span><span class="insert">2.5</span> </span>Identifiers and attributes</a></li><li class="tocline"><a href="#comments" class="tocxref"><span class="secno"><span class="delete">2.5</span><span class="insert">2.6</span> </span>Comments</a></li></ul></li><li class="tocline"><a href="#prov-n-expressions" class="tocxref"><span class="secno">3. </span>PROV-N Productions per Component</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">3.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#expression-Entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#expression-Activity" class="tocxref"><span class="secno">3.1.2 </span>Activity</a></li><li class="tocline"><a href="#expression-Generation" class="tocxref"><span class="secno">3.1.3 </span>Generation</a></li><li class="tocline"><a href="#expression-Usage" class="tocxref"><span class="secno">3.1.4 </span>Usage</a></li><li class="tocline"><a href="#expression-wasInformedBy" class="tocxref"><span class="secno">3.1.5 </span>Communication</a></li><li class="tocline"><a href="#expression-Start" class="tocxref"><span class="secno">3.1.6 </span>Start</a></li><li class="tocline"><a href="#expression-End" class="tocxref"><span class="secno">3.1.7 </span>End</a></li><li class="tocline"><a href="#expression-Invalidation" class="tocxref"><span class="secno">3.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">3.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#Derivation-Relation" class="tocxref"><span class="secno">3.2.1 </span>Derivation</a></li><li class="tocline"><a href="#expression-Revision" class="tocxref"><span class="secno">3.2.2 </span>Revision</a></li><li class="tocline"><a href="#expression-quotation" class="tocxref"><span class="secno">3.2.3 </span>Quotation</a></li><li class="tocline"><a href="#expression-original-source" class="tocxref"><span class="secno">3.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</a><ul class="toc"><li class="tocline"><a href="#expression-Agent" class="tocxref"><span class="secno">3.3.1 </span>Agent</a></li><li class="tocline"><a href="#expression-attribution" class="tocxref"><span class="secno">3.3.2 </span>Attribution</a></li><li class="tocline"><a href="#expression-Association" class="tocxref"><span class="secno">3.3.3 </span>Association</a></li><li class="tocline"><a href="#expression-delegation" class="tocxref"><span class="secno">3.3.4 </span>Delegation</a></li><li class="tocline"><a href="#expression-influence" class="tocxref"><span class="secno">3.3.5 </span>Influence</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">3.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#expression-bundle-constructor" class="tocxref"><span class="secno">3.4.1 </span>Bundle <span class="delete">Declaration</span><span class="insert">Constructor</span></a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">3.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#expression-alternate" class="tocxref"><span class="secno">3.5.1 </span>Alternate</a></li><li class="tocline"><a href="#expression-specialization" class="tocxref"><span class="secno">3.5.2 </span>Specialization</a></li><li class="tocline"><a href="#expression-mention" class="tocxref"><span class="secno">3.5.3 </span>Mention</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">3.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#expression-collection-membership" class="tocxref"><span class="secno">3.6.1 </span>Membership</a></li></ul></li><li class="tocline"><a href="#subexpressions" class="tocxref"><span class="secno">3.7 </span>Further Expressions</a><ul class="toc"><li class="tocline"><a href="#expression-identifier" class="tocxref"><span class="secno">3.7.1 </span>Identifier</a></li><li class="tocline"><a href="#expression-attribute" class="tocxref"><span class="secno">3.7.2 </span>Attribute</a></li><li class="tocline"><a href="#expression-literal" class="tocxref"><span class="secno">3.7.3 </span>Literal</a><ul class="toc"><li class="tocline"><a href="#expression-types" class="tocxref"><span class="secno">3.7.3.1 </span>Reserved Type Values</a></li><li class="tocline"><a href="#expression-Time" class="tocxref"><span class="secno">3.7.3.2 </span>Time Values</a></li></ul></li><li class="tocline"><a href="#expression-NamespaceDeclaration" class="tocxref"><span class="secno">3.7.4 </span>Namespace Declaration</a></li></ul></li></ul></li><li class="tocline"><a href="#toplevelBundle" class="tocxref"><span class="secno">4. </span>Toplevel Bundle</a></li><li class="tocline"><a href="#extensibility" class="tocxref"><span class="secno"><span class="insert">5. </span></span><span class="insert">Extensibility</span></a></li><li class="tocline"><a href="#media-type" class="tocxref"><span class="secno"><span class="delete">5.</span><span class="insert">6.</span> </span>Media Type</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div> 
+<p>This document was published by the <a href="http://www.w3.org/2011/prov/">Provenance Working Group</a> as an Editor's Draft. If you wish to make comments regarding this document, please send them to <a href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a> (<a href="mailto:public-prov-comments-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-prov-comments/">archives</a>). All feedback is welcome.</p><p>Publication as an Editor's Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/46974/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p></div><div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#purpose" class="tocxref"><span class="secno">1.1 </span>Purpose of this Document and <span class="delete">target audience</span><span class="insert">Target Audience</span></a></li><li class="tocline"><a href="#structure-of-this-document" class="tocxref"><span class="secno">1.2 </span>Structure of this Document</a></li><li class="tocline"><a href="#notational-conventions" class="tocxref"><span class="secno">1.3 </span>Notational Conventions</a></li></ul></li><li class="tocline"><a href="#general-conventions" class="tocxref"><span class="secno">2. </span>General grammar considerations</a><ul class="toc"><li class="tocline"><a href="#functional-syntax" class="tocxref"><span class="secno">2.1 </span>Functional-style Syntax</a></li><li class="tocline"><a href="#grammar-notation" class="tocxref"><span class="secno">2.2 </span>EBNF Grammar</a></li><li class="tocline"><a href="#main-productions" class="tocxref"><span class="secno"><span class="insert">2.3 </span></span><span class="insert">Main Productions</span></a></li><li class="tocline"><a href="#prov-n-optionals" class="tocxref"><span class="secno"><span class="delete">2.3</span><span class="insert">2.4</span> </span>Optional terms in expressions</a></li><li class="tocline"><a href="#prov-n-standard-terms" class="tocxref"><span class="secno"><span class="delete">2.4</span><span class="insert">2.5</span> </span>Identifiers and attributes</a></li><li class="tocline"><a href="#comments" class="tocxref"><span class="secno"><span class="delete">2.5</span><span class="insert">2.6</span> </span>Comments</a></li></ul></li><li class="tocline"><a href="#prov-n-expressions" class="tocxref"><span class="secno">3. </span>PROV-N Productions per Component</a><ul class="toc"><li class="tocline"><a href="#component1" class="tocxref"><span class="secno">3.1 </span>Component 1: Entities and Activities</a><ul class="toc"><li class="tocline"><a href="#expression-Entity" class="tocxref"><span class="secno">3.1.1 </span>Entity</a></li><li class="tocline"><a href="#expression-Activity" class="tocxref"><span class="secno">3.1.2 </span>Activity</a></li><li class="tocline"><a href="#expression-Generation" class="tocxref"><span class="secno">3.1.3 </span>Generation</a></li><li class="tocline"><a href="#expression-Usage" class="tocxref"><span class="secno">3.1.4 </span>Usage</a></li><li class="tocline"><a href="#expression-wasInformedBy" class="tocxref"><span class="secno">3.1.5 </span>Communication</a></li><li class="tocline"><a href="#expression-Start" class="tocxref"><span class="secno">3.1.6 </span>Start</a></li><li class="tocline"><a href="#expression-End" class="tocxref"><span class="secno">3.1.7 </span>End</a></li><li class="tocline"><a href="#expression-Invalidation" class="tocxref"><span class="secno">3.1.8 </span>Invalidation</a></li></ul></li><li class="tocline"><a href="#component2" class="tocxref"><span class="secno">3.2 </span>Component 2: Derivations</a><ul class="toc"><li class="tocline"><a href="#Derivation-Relation" class="tocxref"><span class="secno">3.2.1 </span>Derivation</a></li><li class="tocline"><a href="#expression-Revision" class="tocxref"><span class="secno">3.2.2 </span>Revision</a></li><li class="tocline"><a href="#expression-quotation" class="tocxref"><span class="secno">3.2.3 </span>Quotation</a></li><li class="tocline"><a href="#expression-original-source" class="tocxref"><span class="secno">3.2.4 </span>Primary Source</a></li></ul></li><li class="tocline"><a href="#component3" class="tocxref"><span class="secno">3.3 </span>Component 3: Agents, Responsibility, and Influence</a><ul class="toc"><li class="tocline"><a href="#expression-Agent" class="tocxref"><span class="secno">3.3.1 </span>Agent</a></li><li class="tocline"><a href="#expression-attribution" class="tocxref"><span class="secno">3.3.2 </span>Attribution</a></li><li class="tocline"><a href="#expression-Association" class="tocxref"><span class="secno">3.3.3 </span>Association</a></li><li class="tocline"><a href="#expression-delegation" class="tocxref"><span class="secno">3.3.4 </span>Delegation</a></li><li class="tocline"><a href="#expression-influence" class="tocxref"><span class="secno">3.3.5 </span>Influence</a></li></ul></li><li class="tocline"><a href="#component4" class="tocxref"><span class="secno">3.4 </span>Component 4: Bundles</a><ul class="toc"><li class="tocline"><a href="#expression-bundle-constructor" class="tocxref"><span class="secno">3.4.1 </span>Bundle <span class="delete">Declaration</span><span class="insert">Constructor</span></a></li></ul></li><li class="tocline"><a href="#component5" class="tocxref"><span class="secno">3.5 </span>Component 5: Alternate Entities</a><ul class="toc"><li class="tocline"><a href="#expression-alternate" class="tocxref"><span class="secno">3.5.1 </span>Alternate</a></li><li class="tocline"><a href="#expression-specialization" class="tocxref"><span class="secno">3.5.2 </span>Specialization</a></li><li class="tocline"><a href="#expression-mention" class="tocxref"><span class="secno">3.5.3 </span>Mention</a></li></ul></li><li class="tocline"><a href="#component6" class="tocxref"><span class="secno">3.6 </span>Component 6: Collections</a><ul class="toc"><li class="tocline"><a href="#expression-collection-membership" class="tocxref"><span class="secno">3.6.1 </span>Membership</a></li></ul></li><li class="tocline"><a href="#subexpressions" class="tocxref"><span class="secno">3.7 </span>Further Expressions</a><ul class="toc"><li class="tocline"><a href="#expression-identifier" class="tocxref"><span class="secno">3.7.1 </span>Identifier</a></li><li class="tocline"><a href="#expression-attribute" class="tocxref"><span class="secno">3.7.2 </span>Attribute</a></li><li class="tocline"><a href="#expression-literal" class="tocxref"><span class="secno">3.7.3 </span>Literal</a><ul class="toc"><li class="tocline"><a href="#expression-types" class="tocxref"><span class="secno">3.7.3.1 </span>Reserved Type Values</a></li><li class="tocline"><a href="#expression-Time" class="tocxref"><span class="secno">3.7.3.2 </span>Time Values</a></li></ul></li><li class="tocline"><a href="#expression-NamespaceDeclaration" class="tocxref"><span class="secno">3.7.4 </span>Namespace Declaration</a></li></ul></li></ul></li><li class="tocline"><a href="#toplevelBundle" class="tocxref"><span class="secno">4. </span>Toplevel Bundle</a></li><li class="tocline"><a href="#extensibility" class="tocxref"><span class="secno"><span class="insert">5. </span></span><span class="insert">Extensibility</span></a></li><li class="tocline"><a href="#media-type" class="tocxref"><span class="secno"><span class="delete">5.</span><span class="insert">6.</span> </span>Media Type</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div> 
 
 
 
@@ -601,7 +605,7 @@
 </p>
 
 <div id="purpose" class="section"> 
-<h3><span class="secno">1.1 </span>Purpose of this Document and target audience</h3>
+<h3><span class="secno">1.1 </span>Purpose of this Document and <span class="delete">target audience</span><span class="insert">Target Audience</span></h3>
 
 A key goal of PROV is the specification of a machine-processable data model for provenance. However, communicating provenance between humans is also important when teaching, illustrating, formalizing, and discussing provenance-related issues. 
 
@@ -628,8 +632,8 @@
 <p>Its target audience is twofold:
 </p><ul>
 <li>Developers of provenance management applications, as well as implementors of new PROV data model encodings, and thus in particular of PROV-N parsers. These readers may be interested in the entire structure of the grammar, starting from the top level nonterminal 
-<a class="grammarRef" href="#prod-bundle">bundle</a>.</li>
-<li>Readers of the  [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] and of  [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] documents, who are interested in the details of the formal language underpinning the notation used in the examples and in the definition of the constraints. Those readers may find the  <a class="grammarRef" href="#prod-expression">expression</a> nonterminal a useful entry point into the grammar.</li>
+<code><a class="grammarRef" href="#prod-bundle">bundle</a></code>.</li>
+<li>Readers of the  [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-DM">PROV-DM</a></cite>] and of  [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-CONSTRAINTS">PROV-CONSTRAINTS</a></cite>] documents, who are interested in the details of the formal language underpinning the notation used in the examples and in the definition of the constraints. Those readers may find the  <code><a class="grammarRef" href="#prod-expression">expression</a></code> nonterminal a useful entry point into the grammar.</li>
 </ul>
 
 </div>
@@ -646,7 +650,11 @@
 <p><a href="#toplevelBundle">Section 4</a> defines the grammar of toplevel bundles, a house-keeping construct of PROV-N capable of packaging up PROV-N expressions and namespace declarations.</p>
 
 
-<p><a href="#media-type">Section 5</a> defines media type for the PROV-N notation.</p>
+
+
+<p><a href="#extensibility"><span class="insert">Section 5</span></a><span class="insert"> defines the extensibility mechanism for the PROV-N notation.</span></p>
+
+<p><a href="#media-type">Section <span class="delete">5</span><span class="insert">6</span></a> defines media type for the PROV-N notation.</p>
 
 
     </div> 
@@ -740,8 +748,8 @@
 
 <p>
   <span class="delete">Each</span><span class="insert">EBNF specifies a series of</span> production <span class="delete">rule (or </span><span class="insert">rules (</span><dfn id="dfn-production">production</dfn><span class="delete">, for short)</span><span class="insert">). 
-A production rule</span> in the grammar defines <span class="delete">one </span><span class="insert">a symbol 
- </span><code class="grammarRef"><span class="insert">expr</span></code><span class="insert">  (</span><dfn id="dfn-non-terminal-symbol">non-terminal symbol <span class="delete">E</span><span class="delete">, in</span></dfn><span class="insert">)
+A production rule</span> in the grammar defines <span class="delete">one non-terminal</span><span class="insert">a</span> symbol <span class="delete">E</span><span class="delete">, in</span> 
+ <code class="grammarRef"><span class="insert">expr</span></code><span class="insert">  (</span><dfn id="dfn-nonterminal-symbol"><span class="insert">nonterminal symbol</span></dfn><span class="insert">)
   using</span> the following form:</p>
 
 <span class="delete">E</span>
@@ -769,7 +777,7 @@
 </p><ul>
 <li> 
 <span class="delete">E</span> 
- <code class="grammarRef"><span class="insert">expr</span></code>: matches <span class="delete">term satisfying rule</span><span class="insert">production</span> for <span class="insert">non-terminal </span>symbol <span class="delete">E.</span><code class="grammarRef"><span class="insert">expr</span></code>
+ <code class="grammarRef"><span class="insert">expr</span></code>: matches <span class="delete">term satisfying rule</span><span class="insert">production</span> for <span class="insert">nonterminal </span>symbol <span class="delete">E.</span><code class="grammarRef"><span class="insert">expr</span></code>
 </li>
 
 
@@ -806,44 +814,53 @@
 </ul>
 
 
+
+<p><span class="insert">Where suitable, the PROV-N grammar reuses production and terminal names of the SPARQL grammar [</span><cite><a class="bibref" rel="biblioentry" href="#bib-RDF-SPARQL-QUERY"><span class="insert">RDF-SPARQL-QUERY</span></a></cite><span class="insert">].</span></p>
+
 </div>
 
 <div id="main-productions" class="section">
 <h3><span class="secno"><span class="insert">2.3 </span></span><span class="insert">Main Productions</span></h3>
-The grammar <span class="insert">groups the general PROV-N </span><em><span class="insert">non-terminals</span></em><span class="insert"> in a
-</span><em><span class="insert">production rule</span></em><span class="insert"> called </span><code class="grammarRef"><span class="insert">expression</span></code><span class="insert">
-(shown below). This production </span>is <span class="delete">centered on nonterminals</span><span class="insert">introduced as it provides an 
-entry point</span> for <span class="delete">various types</span><span class="insert">the core expressions</span> of <span class="delete">expression</span><span class="delete">. The main</span><span class="insert">this grammar. Note that parser
-developers should use the</span> production <span class="delete">is introduced here below</span><span class="insert">rule for the </span><a href="#prod-bundle"><span class="insert">top
-level </span><span class="grammarRef"><span class="insert">bundle</span></span></a> as <span class="delete">it reflects the rationale for the design of the entire grammar. Note that parser developers may use the top level
-</span><span class="delete">bundle</span><span class="delete">  nonterminal as </span>a starting point 
-instead.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-<table class="grammar">
+
+<p><span class="insert">Two productions are entry points to the grammar.</span></p>
+
+<p>The <span class="delete">grammar is centered on nonterminals for various types of </span><span class="insert">production </span><code class="grammarRef"><a class="grammarRef" href="#prod-expression">expression</a><span class="delete">. The main production is introduced here below as it reflects the rationale</span></code><span class="insert">
+provides the structure</span> for the <span class="delete">design</span><em><span class="insert">core expressions</span></em> of <span class="delete">the entire grammar. Note that parser developers may use the top level
+</span><span class="delete">bundle</span><span class="delete">  nonterminal as a starting point instead.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+</span><span class="insert">PROV-N. 
+
+
+
+
+</span></p><table class="grammar">
 <tbody class="prod"> <tr valign="baseline"> <td><a id="prod-expression" name="prod-expression"></a>[<span class="prodNo">2</span>]&nbsp;&nbsp;&nbsp;</td> <td><code class="production prod">expression</code></td> <td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-entityExpression">entityExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-activityExpression">activityExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-generationExpression">generationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-usageExpression">usageExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-startExpression">startExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-endExpression">endExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-invalidationExpression">invalidationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-communicationExpression">communicationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-agentExpression">agentExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-associationExpression">associationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-attributionExpression">attributionExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-delegationExpression">delegationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-derivationExpression">derivationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-influenceExpression">influenceExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-alternateExpression">alternateExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-specializationExpression">specializationExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-mentionExpression">mentionExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-membershipExpression">membershipExpression</a></span> <span class="insert">| </span><span class="prod"><a class="grammarRef" href="#prod-extensibilityExpression"><span class="insert">extensibilityExpression</span></a></span><span class="insert"> | </span><span class="prod"><a class="grammarRef" href="#prod-insertionExpression"><span class="insert">insertionExpression</span></a></span><span class="insert"> | </span><span class="prod"><a class="grammarRef" href="#prod-removalExpression"><span class="insert">removalExpression</span></a></span><span class="insert"> | </span><span class="prod"><a class="grammarRef" href="#prod-dictMembershipExpression"><span class="insert">dictMembershipExpression</span></a></span> )</code></td> </tr> </tbody>
 </table>
 
 
-<p>Each <span class="insert">of the symbols included in </span><code>expression<span class="delete"> non-terminal </span><span class="delete">expression</span><span class="delete">,</span></code><span class="insert"> above,</span> i.e., <code><a class="grammarRef" href="#prod-entityExpression">entityExpression</a></code>,  <code><a class="grammarRef" href="#prod-activityExpression">activityExpression</a></code> etc., corresponds to one element <span class="delete">(entity,</span><span class="insert">(e.g., entity,</span> activity, etc.) of the PROV data model.
-</p>
-
-<p>A PROV-N document consists of a collection of <a title="expression">expressions</a>, wrapped in a <a class="grammarRef" href="#prod-bundle">toplevel bundle</a> with some namespace declarations, such that the text for an element matches the corresponding <a class="grammarRef" href="#prod-expression">expression</a> production of the grammar.
-
-</p></div>
+<p>Each <span class="insert">of the symbols included in </span><code>expression<span class="delete"> non-terminal </span></code><span class="insert"> above, i.e., </span><code><a class="grammarRef" href="#prod-entityExpression"><span class="insert">entityExpression</span></a></code><span class="insert">,  </span><code><a class="grammarRef" href="#prod-activityExpression"><span class="insert">activityExpression</span></a></code><span class="insert"> etc., corresponds to one concept (e.g., Entity, Activity, etc.) of the PROV data model.</span></p>
+
+
+<p><span class="insert">Alternatively,  the production rule </span><code><a href="#prod-bundle"><span class="grammarRef"><span class="insert">bundle</span></span></a></code><span class="insert">
+provides the overall structure of PROV-N descriptions.  It is a wrapper  for
+ a set of expressions, such that the text for an element matches the corresponding </span><code><a class="grammarRef" href="#prod-expression">expression</a><span class="delete">, i.e., </span><span class="delete">entityExpression</span><span class="delete">,</span></code><span class="insert"> production,</span>  <span class="delete">activityExpression</span><span class="delete"> etc., corresponds to one element (entity, activity, etc.) of the PROV data model.
+</span><span class="delete">A PROV-N document consists of a collection of </span><span class="delete">expressions</span><span class="delete">, wrapped in a </span><span class="delete">toplevel bundle</span><span class="delete"> with</span><span class="insert">and</span> some namespace <span class="delete">declarations, such that the text for an element matches the corresponding </span><span class="delete">expression</span><span class="delete"> production of the grammar.</span><span class="insert">declarations.</span></p>
+
+</div>
 
 
 <div id="prov-n-optionals" class="section"> 
@@ -906,7 +923,7 @@
 <div id="prov-n-standard-terms" class="section"> 
 <h3><span class="secno"><span class="delete">2.4</span><span class="insert">2.5</span> </span>Identifiers and attributes</h3>
 
-<p><span class="insert">Almost all expressions defined in the grammar include an identifier. </span>Most expressions<span class="delete"> defined</span><span class="insert">
+<p><span class="insert">Almost all expressions defined in the grammar include an identifier (see </span><a href="#expression-identifier"><span class="insert">Section 3.7.1</span></a><span class="insert"> for the full syntax of identifiers). </span>Most expressions<span class="delete"> defined</span><span class="insert">
 can aslo include a set of attribute-value pairs, delimited by square brackets. Identifiers are optional except for Entities, Activites, and Agents. Identifiers are always the first term</span> in <span class="delete">the grammar include the use of two terms: an identifier and</span><span class="insert">any expression.  Optional identifiers </span><em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> be separated using</span> a <span class="delete">set of attribute-value pairs, delimited by square brackets. Identifiers</span><span class="insert">semi-colon ';', but where the identifiers</span> are <span class="delete">optional except for Entities, Activites, and Agents. Identifiers are always the first term in any expression. By convention, optional identifiers are separated using</span><span class="insert">required,</span> a <span class="delete">semi-colon ';'.</span><span class="insert">regular comma ',' </span><em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> be used.</span> This makes it possible to completely omit an optional identifier with no ambiguity arising. Also, if the set of attribute-value pairs is present, it is always the last term in any expression.</p>
 
 <div class="anexample" id="example_9"><div class="anexampleTitle"><a class="internalDFN" href="#example_9">Example <span class="delete">7</span><span class="insert">9</span></a></div>
@@ -922,12 +939,13 @@
 
 
 <div class="anexample" id="example_10"><div class="anexampleTitle"><a class="internalDFN" href="#example_10">Example <span class="delete">8</span><span class="insert">10</span></a></div>
-<p>The first and second activities have no <span class="delete">attributes.</span><span class="insert">attributes, and are equivalent.</span>
-
-The third activity  has two attributes. 
-</p><pre class="codeexample">activity(ex:a10)
-activity(ex:a10, [])
-activity(ex:a10, [ex:param1="a", ex:param2="b"])
+<p>The first and second <span class="delete">activities</span><span class="insert">activity expressions</span> have no <span class="delete">attributes.</span><span class="insert">attributes, and are equivalent.</span>
+
+The third activity  <span class="insert"> expression </span>has two attributes. 
+</p><pre class="codeexample"><span class="delete">activity(ex:a10)
+activity(ex:a10,</span><span class="insert">activity(ex:a1)
+activity(ex:a1,</span> [])
+<span class="delete">activity(ex:a10,</span><span class="insert">activity(ex:a1,</span> [ex:param1="a", ex:param2="b"])
 </pre>
 </div>
 
@@ -973,7 +991,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM Entity maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Entity maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Entity</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1009,7 +1027,7 @@
 <tbody class="prod"> <tr valign="baseline"> <td><a id="prod-timeOrMarker" name="prod-timeOrMarker"></a>[<span class="prodNo">8</span>]&nbsp;&nbsp;&nbsp;</td> <td><code class="production prod">timeOrMarker</code></td> <td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-time">time</a></span> | "-" )</code></td> </tr> </tbody>
 </table>
 
-<p>The following table summarizes how each constituent of a PROV-DM Activity maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Activity maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Activity</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1061,7 +1079,7 @@
 
 </table>
 
-<p>The following table summarizes how each constituent of a PROV-DM Generation maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Generation maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Generation</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1113,7 +1131,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM Usage maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Usage maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Usage</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1145,7 +1163,7 @@
 </div>
 
 
-<p>Even though the production <code class="content"><a class="grammarRef" href="#prod-usageExpression">usageExpression</a></code> allows for expressions <span class="name">used(a2, -, -)</span>  and <span class="name">used(-; <span class="delete">e2,</span><span class="insert">a2,</span> -, -)</span>, these expressions are not valid in PROV-N, since at least one  of <a href="http://www.w3.org/TR/prov-dm/#usage.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/prov-dm/#usage.entity"><span class="attribute">entity</span></a>, <a href="http://www.w3.org/TR/prov-dm/#usage.time"><span class="attribute">time</span></a>, and  <a href="http://www.w3.org/TR/prov-dm/#usage.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="must">must</em> be present.</p>
+<p><strong><span class="insert">Note:</span></strong> Even though the production <code class="content"><a class="grammarRef" href="#prod-usageExpression">usageExpression</a></code> allows for expressions <span class="name">used(a2, -, -)</span>  and <span class="name">used(-; <span class="delete">e2,</span><span class="insert">a2,</span> -, -)</span>, these expressions are not valid in PROV-N, since at least one  of <a href="http://www.w3.org/TR/prov-dm/#usage.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/prov-dm/#usage.entity"><span class="attribute">entity</span></a>, <a href="http://www.w3.org/TR/prov-dm/#usage.time"><span class="attribute">time</span></a>, and  <a href="http://www.w3.org/TR/prov-dm/#usage.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="must">must</em> be present.</p>
 
 
 
@@ -1164,7 +1182,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM Communication maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Communication maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Communication</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1204,7 +1222,7 @@
 <tbody class="prod"> <tr valign="baseline"> <td><a id="prod-startExpression" name="prod-startExpression"></a>[<span class="prodNo">14</span>]&nbsp;&nbsp;&nbsp;</td> <td><code class="production prod">startExpression</code></td> <td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td> <td><code class="content">"wasStartedBy" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-aIdentifier">aIdentifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifierOrMarker">eIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-timeOrMarker">timeOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
 </table>
 
-<p>The following table summarizes how each constituent of a PROV-DM Start maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Start maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Start</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1256,7 +1274,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM End maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM End maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>End</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1314,7 +1332,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM Invalidation maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Invalidation maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Invalidation</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1346,7 +1364,7 @@
 </pre>
 </div>
 
-<p>Even though the production  <code class="content"><a class="grammarRef" href="#prod-invalidationExpression">invalidationExpression</a></code> allows for expressions <span class="name">wasInvalidatedBy(e2, -, -)</span>  and <span class="name">wasInvalidatedBy(-; e2, -, -)</span>, these expressions are not valid in PROV-N, since 
+<p><strong><span class="insert">Note:</span></strong> Even though the production  <code class="content"><a class="grammarRef" href="#prod-invalidationExpression">invalidationExpression</a></code> allows for expressions <span class="name">wasInvalidatedBy(e2, -, -)</span>  and <span class="name">wasInvalidatedBy(-; e2, -, -)</span>, these expressions are not valid in PROV-N, since 
 since at least one  of <a href="http://www.w3.org/TR/prov-dm/#invalidation.id"><span class="attribute">id</span></a>, <a href="http://www.w3.org/TR/prov-dm/#invalidation.activity"><span class="attribute">activity</span></a>, <a href="http://www.w3.org/TR/prov-dm/#invalidation.time"><span class="attribute">time</span></a>, and  <a href="http://www.w3.org/TR/prov-dm/#invalidation.attributes"><span class="attribute">attributes</span></a> <em class="rfc2119" title="must">must</em> be present.</p>
 
 
@@ -1369,7 +1387,7 @@
 <tbody class="prod"> <tr valign="baseline"> <td><a id="prod-derivationExpression" name="prod-derivationExpression"></a>[<span class="prodNo">17</span>]&nbsp;&nbsp;&nbsp;</td> <td><code class="production prod">derivationExpression</code></td> <td>&nbsp;&nbsp;&nbsp;::=&nbsp;&nbsp;&nbsp;</td> <td><code class="content">"wasDerivedFrom" "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-eIdentifier">eIdentifier</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-aIdentifierOrMarker">aIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-gIdentifierOrMarker">gIdentifierOrMarker</a></span> "," <span class="prod"><a class="grammarRef" href="#prod-uIdentifierOrMarker">uIdentifierOrMarker</a></span> )? <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
 </table>
 
-<p>The following table summarizes how each constituent of a PROV-DM Derivation maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Derivation maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Derivation</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1400,7 +1418,7 @@
 
 
 <div class="anexample" id="anexample-derivation"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-derivation">Example <span class="delete">17</span><span class="insert">19</span></a></div>
-    <pre class="codeexample">wasDerivedFrom(d, e2, e1, a, g2, u1, [ex:comment="a righteous derivation"])
+    <pre class="codeexample"><span class="delete">wasDerivedFrom(d,</span><span class="insert">wasDerivedFrom(d;</span> e2, e1, a, g2, u1, [ex:comment="a righteous derivation"])
   </pre>
 <p>  Here
     <span class="name">d</span> is the optional derivation identifier,
@@ -1497,7 +1515,7 @@
 
 </table>
 
-<p>The following table summarizes how each constituent of a PROV-DM Agent maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Agent maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Agent</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1535,7 +1553,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM Attribution maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Attribution maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Attribution</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1580,7 +1598,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM Association maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Association maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Association</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1637,7 +1655,7 @@
 
 </table>
 
-<p>The following table summarizes how each constituent of a PROV-DM Delegation maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Delegation maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Delegation</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1691,7 +1709,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM Influence maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Influence maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Influence</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1714,7 +1732,7 @@
 <p>  Here
     <span class="name">id</span> is the optional influence identifier,
   <span class="name">e2</span> is an entity identifier,
-  <span class="name">e1</span> is the identifier for an ancestor entity that   <span class="name">e2</span> depends on,
+  <span class="name">e1</span> is the identifier for an ancestor entity that   <span class="name">e2</span> <span class="delete">depends on,</span><span class="insert">is influenced by,</span>
   and <span class="name">[ex:param="a"]</span> is the optional set of attributes. </p>
 The remaining examples show cases where some of the optionals are omitted.
 
@@ -1779,7 +1797,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM Alternate maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Alternate maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Alternate</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1814,7 +1832,7 @@
 
 </table>
 
-<p>The following table summarizes how each constituent of a PROV-DM Specialization maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Specialization maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Specialization</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1857,7 +1875,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM Mention maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Mention maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Mention</b></td><td><b>Non-Terminal</b></td></tr>
@@ -1915,7 +1933,7 @@
 </table>
 
 
-<p>The following table summarizes how each constituent of a PROV-DM Membership maps to a non-terminal.</p>
+<p>The following table summarizes how each constituent of a PROV-DM Membership maps to a <span class="delete">non-terminal.</span><span class="insert">PROV-N syntax element.</span></p>
 <div style="text-align: left; ">
 <table class="thinborder" style="margin-left: auto; margin-right: auto;">
 <tbody><tr><td><b>Collection Membership</b></td><td><b>Non-Terminal</b></td></tr>
@@ -2011,11 +2029,11 @@
 A <dfn id="dfn-qualifiedName">qualified name</dfn> is a name subject to <a>namespace</a> interpretation. It consists of a <a>namespace</a>, denoted by an optional prefix, and a local name.
 The PROV data model  stipulates that a qualified name can be mapped into an IRI
  by concatenating the IRI associated with the prefix and the local part.
-<span class="insert">  This section provides the exact details of this procedure for qualified names supported by PROV-N. </span></p>
+<span class="insert">  This section provides the exact details of this procedure for qualified names defined by PROV-N. </span></p>
 
 <p>A qualified name's prefix is <em class="rfc2119" title="optional">optional</em>. If a prefix occurs in a
- qualified name, it <span class="delete">refers</span><em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> refer</span> to a <a>namespace</a> declared in a namespace declaration.  In the absence of prefix, the qualified name 
- refers to the <a title="default namespace declaration">default namespace</a>.</p>
+ qualified name, <span class="delete">it refers</span><span class="insert">the prefix </span><em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> refer</span> to a <a>namespace</a> declared in a namespace declaration.  In the absence of prefix, the qualified name 
+ <span class="delete">refers</span><span class="insert">belongs</span> to the <a title="default namespace declaration">default namespace</a>.</p>
 
 
 
@@ -2331,8 +2349,8 @@
 
 </table>
 
-<p>A <code><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this declaration refers to this namespace. <span class="insert">
-A </span><code><a class="grammarRef" href="#prod-defaultNamespaceDeclaration"><span class="insert">defaultNamespaceDeclaration</span></a></code><span class="insert"> consists of a namespace. Every qualified name without prefix in the scope of this declaration refers to this namespace. Scope of a declaration is specified as follows:</span></p>
+<p>A <code><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code> consists of a binding between a prefix and a namespace. Every qualified name with this prefix in the scope of this declaration <span class="delete">refers</span><span class="insert">belongs</span> to this namespace. <span class="insert"> 
+A </span><code><a class="grammarRef" href="#prod-defaultNamespaceDeclaration"><span class="insert">defaultNamespaceDeclaration</span></a></code><span class="insert"> consists of a namespace. Every qualified name without prefix in the scope of this declaration belongs to this namespace. Scope of a declaration is specified as follows:</span></p>
 <ul>
 <li> 
 The scope of a namespace declaration <span class="delete">is the </span><span class="insert">directly occurring in a </span><code><a class="grammarRef" href="#prod-namedBundle">namedBundle</a><span class="delete"> or </span></code><span class="insert"> is the </span><code><a class="grammarRef" href="#prod-namedBundle"><span class="insert">namedBundle</span></a></code><span class="insert"> itself;</span></li>
@@ -2517,12 +2535,13 @@
 <a href="#component6"><span class="insert">Collections</span></a><span class="insert"> are sets of entities, whose membership can be expressed using the </span><span class="name"><span class="insert">hadMembers</span></span><span class="insert"> relation.  The following example shows how one can express membership for an extension of Collections, namely sets of key-value pairs. The notation is a variation of that used for Collections membership, in which the elements of the set are pairs. The name of the relation is qualified with the extension-specific namespace </span><span class="name"><span class="insert">http://example.org/dictionaries</span></span><span class="insert">.
 </span></p>
 <pre class="codeexample"><span class="insert">  prefix dictExt &lt;http://example.org/dictionaries&gt;
-  dictExt:hadMembers(mId; d, {(k1,e1), (k2,e2), (k3,e3)}, []) 
+  dictExt:hadMembers(mId; d, {("k1",e1), ("k2",e2), ("k3",e3)}, []) 
 </span></pre><span class="insert">
 
 Note that the generic </span><code class="content"><a class="grammarRef" href="#prod-extensibilityExpression"><span class="insert">extensibilityExpression</span></a></code><span class="insert"> production  above allows for alternative notations to be used for expressing membership, if the designers of the extensions so desire. Here is an alternate syntax that is consistent with the productions:
 </span><pre class="codeexample"><span class="insert">  prefix dictExt &lt;http://example.org/dictionaries&gt;
-  dictExt:hadMembers(mid; d, dictExt:set(dictExt:pair(k1,e1), dictExt:pair(k2,e2), dictExt:pair(k3,e3), [dictExt:uniqueKeys="true"]) 
+  dictExt:hadMembers(mid; d, dictExt:set(dictExt:pair("k1",e1), dictExt:pair("k2",e2), dictExt:pair("k3",e3)), 
+                            [dictExt:uniqueKeys="true"]) 
 </span></pre>
 
   
@@ -2542,11 +2561,11 @@
 The media type of PROV-N is <span class="name"><span class="delete">text/prov-n</span><span class="insert">text/provenance-notation</span></span>. The content encoding of PROV-N content is UTF-8.
 </p>
 
-<div class="note">
-<p>
-See <a href="http://www.w3.org/2002/06/registering-mediatype">http://www.w3.org/2002/06/registering-mediatype</a> for Register an Internet Media Type for a <acronym title="World Wide Web Consortium">W3C</acronym> Spec.</p>
-Following text adapted from <a href="http://www.w3.org/TeamSubmission/turtle/#sec-mediaReg">turtle</a>.
-</div>
+
+<span class="delete">
+See </span><span class="delete">http://www.w3.org/2002/06/registering-mediatype</span><span class="delete"> for Register an Internet Media Type for a </span><span class="delete">W3C</span><span class="delete"> Spec.</span><span class="delete">
+Following text adapted from </span><span class="delete">turtle</span><span class="delete">.
+</span>
 
 
  <dl> 
@@ -2597,7 +2616,7 @@
       <dt>Interoperability considerations:</dt> 
       <dd>There are no known interoperability issues.</dd> 
       <dt>Published specification:</dt> 
-      <dd><span class="delete">This specification.</span><span class="insert">PROV-N: The Provenance Notation, Moreau and Missier, eds,
+      <dd><span class="delete">This specification.</span><span class="insert">PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney, Soiland-Reyes
       </span><a href="http://www.w3.org/TR/prov-n/"><span class="insert">http://www.w3.org/TR/prov-n/</span></a></dd> 
       <dt>Applications which use this media type:</dt> 
       <dd>No widely deployed applications are known to use this media type. It may be used by some web services and clients consuming their data.</dd> 
@@ -2717,7 +2736,7 @@
 </dd><dt id="bib-PROV-DM">[PROV-DM]</dt><dd>Luc Moreau and Paolo Missier (eds.) Khalid Belhajjame, Reza B'Far, Stephen Cresswell, Yolanda Gil, Paul Groth, Graham Klyne, Jim McCusker, Simon Miles, James Myers, Satya Sahoo, and Curt Tilmes<a href="http://www.w3.org/TR/prov-dm/"><cite>PROV-DM: The PROV Data Model</cite></a>. 2012, Working Draft. URL: <a href="http://www.w3.org/TR/prov-dm/">http://www.w3.org/TR/prov-dm/</a>
 </dd><dt id="bib-PROV-RDF">[PROV-RDF]</dt><dd>James Cheney<a href="http://www.w3.org/2011/prov/wiki/ProvRDF"><cite>PROV-RDF Mapping </cite></a>2012, Working in Progress. URL: <a href="http://www.w3.org/2011/prov/wiki/ProvRDF">http://www.w3.org/2011/prov/wiki/ProvRDF</a>
 </dd><dt id="bib-PROV-SEM">[PROV-SEM]</dt><dd>James Cheney <a href="http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman"><cite>Formal Semantics Strawman</cite></a>. 2011, Work in progress. URL: <a href="http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman">http://www.w3.org/2011/prov/wiki/FormalSemanticsStrawman</a>
-</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>James Cheney<a href="http://www.w3.org/2011/prov/wiki/ProvXML"><cite>PROV-XML Mapping </cite></a>2012, Working in Progress. URL: <a href="http://www.w3.org/2011/prov/wiki/ProvXML">http://www.w3.org/2011/prov/wiki/ProvXML</a>
+</dd><dt id="bib-PROV-XML">[PROV-XML]</dt><dd>James Cheney <a href="http://www.w3.org/2011/prov/wiki/ProvXML"><cite>PROV-XML Mapping </cite></a>2012, Working in Progress. URL: <a href="http://www.w3.org/2011/prov/wiki/ProvXML">http://www.w3.org/2011/prov/wiki/ProvXML</a>
 </dd><dt id="bib-UNICODE5">[UNICODE5]</dt><dd>The Unicode Consortium. <a href="http://www.unicode.org/versions/Unicode5.1.0/"><cite>The Unicode Standard, Version 5.1.0.</cite></a> Addison-Wesley. 2007. ISBN 0-321-48091-0. URL: <a href="http://www.unicode.org/versions/Unicode5.1.0/">http://www.unicode.org/versions/Unicode5.1.0/</a> 
 </dd><dt id="bib-UNISEC">[UNISEC]</dt><dd> Mark Davis and Michel Suignard. <a href="http://www.unicode.org/reports/tr36/"><cite>Unicode Security Considerations<cite></cite></cite></a>.  4 August 2010. URL: <a href="http://www.unicode.org/reports/tr36/">http://www.unicode.org/reports/tr36/</a>
 </dd></dl></div></div></body></html>