--- a/model/diff-n.html Tue Nov 06 17:04:18 2012 +0000
+++ b/model/diff-n.html Tue Nov 06 17:05:14 2012 +0000
@@ -965,7 +965,7 @@
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><link href="./extra.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-N: The Provenance Notation</h1><h2 id="subtitle"><a href="diff-n.html"><span class="insert">Diffs</span></a><span class="insert"> since LC Release </span></h2><h2 id="w3c-editor-s-draft-30-october-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">30 October</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-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-n-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-n-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-N: The Provenance Notation</h1><h2 id="subtitle"><a href="diff-n.html"><span class="insert">Diffs</span></a><span class="insert"> since LC Release </span></h2><h2 id="w3c-editor-s-draft-06-november-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">06 November</span> 2012</h2><dl><dt>This version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-20120724/</span><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html"><span class="insert">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</span></a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html">http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-n.html</a></dd><dt>Previous version:</dt><dd><span class="delete">http://www.w3.org/TR/2012/WD-prov-n-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-n-20120724/"><span class="insert">http://www.w3.org/TR/2012/WD-prov-n-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://homepages.inf.ed.ac.uk/jcheney/">James Cheney</a>, University of Edinburgh</dd>
<dd><a href="http://soiland-reyes.com/stian/">Stian Soiland-Reyes</a>, University of Manchester</dd>
@@ -2251,14 +2251,14 @@
<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-bundle" name="prod-bundle"></a>[<span class="prodNo">23</span>] </td> <td><code class="production prod"><span class="delete">namedBundle</span><span class="insert">bundle</span></code></td> <td> ::= </td> <td><code class="content">"bundle" <span class="prod"><a class="grammarRef" href="#prod-identifier">identifier</a></span> (<span class="prod"><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></span>)? (<span class="prod"><a class="grammarRef" href="#prod-expression">expression</a></span>)* "endBundle"</code></td> </tr> </tbody>
</table>
-<p><span class="delete">Named bundles</span><span class="insert">Bundles</span> cannot be nested because <code><span class="delete">namedBundle</span><a class="grammarRef" href="#prod-bundle"><span class="insert">bundle</span></a></code> is not an <code><a class="grammarRef" href="#prod-expression">expression</a></code>, and therefore cannot occurs inside another <code><span class="delete">namedBundle</span><a class="grammarRef" href="#prod-bundle"><span class="insert">bundle</span></a></code>.</p>
-
-<p><span class="delete">Named bundles</span><span class="insert">Bundles</span> are self-contained: each identifier occuring in a<span class="delete"> named</span> bundle, including the bundle identifier itself, <em class="rfc2119" title="must">must</em> be interpreted with respect to the namespace declarations of that bundle. In other words, for every identifier with a prefix <code>p</code> within a <span class="delete">named </span>bundle, there <em class="rfc2119" title="must">must</em> be a namespace declaration for <code>p</code> in this <span class="delete">named </span>bundled; for every identifier without prefix, there <em class="rfc2119" title="must">must</em> be a default namespace declaration in this <span class="delete">named bundled.</span><span class="insert">bundle.</span></p>
-
-
-
-
-<p><span class="insert">The following table summarizes how each constituent of a PROV-DM bundle maps to a PROV-N syntax element.</span></p>
+<p><span class="delete">Named bundles</span><span class="insert">Bundles</span> cannot be nested because <code><span class="delete">namedBundle</span><a class="grammarRef" href="#prod-bundle"><span class="insert">bundle</span></a></code> is not an <code><a class="grammarRef" href="#prod-expression">expression</a></code>, and therefore cannot <span class="delete">occurs</span><span class="insert">occur</span> inside another <code><span class="delete">namedBundle</span><a class="grammarRef" href="#prod-bundle"><span class="insert">bundle</span></a></code>.</p>
+
+<p><span class="delete">Named bundles are self-contained: each</span><span class="insert">Each</span> identifier occuring in a<span class="delete"> named</span> bundle, including the bundle identifier itself, <em class="rfc2119" title="must">must</em> be interpreted with respect to the namespace declarations of that <span class="delete">bundle. In other words, for every identifier</span><span class="insert">bundle, or if the identifier's prefix is not declared in the bundle,</span> with <span class="insert">respect to the namespace declaration in the document. </span></p>
+
+
+<p><span class="insert">The following table summarizes how each constituent of </span>a <span class="delete">prefix </span><span class="delete">p</span><span class="delete"> within</span><span class="insert">PROV-DM bundle maps to</span> a <span class="delete">named bundle, there </span><span class="delete">must</span><span class="delete"> be a namespace declaration for </span><span class="delete">p</span><span class="delete"> in this named bundled; for every identifier without prefix, there </span><span class="delete">must</span><span class="delete"> be a default namespace declaration in this named bundled.</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><a href="http://www.w3.org/TR/prov-dm/#dfn-bundle-constructor"><span class="insert">Bundle</span></a></b></td><td><b><span class="insert">Non-Terminal</span></b></td></tr>
@@ -2834,18 +2834,20 @@
</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 belongs to this namespace.
-A <code><a class="grammarRef" href="#prod-defaultNamespaceDeclaration">defaultNamespaceDeclaration</a></code> 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:</p>
+A <code><a class="grammarRef" href="#prod-defaultNamespaceDeclaration">defaultNamespaceDeclaration</a></code> consists of a namespace. Every qualified name without prefix in the scope of this declaration belongs to this namespace. Scope of a <span class="insert">prefix-namespace </span>declaration is specified as follows:</p>
<ul>
<li>
-The scope of a namespace declaration directly occurring in a <code><span class="delete">namedBundle</span><a class="grammarRef" href="#prod-bundle"><span class="insert">bundle</span></a></code> is the <span class="delete">namedBundle</span><span class="delete"> itself;</span>
+The scope of a <span class="delete">namespace declaration directly occurring in a </span><span class="delete">namedBundle</span><span class="delete"> is the </span><span class="delete">namedBundle</span><span class="delete"> itself;</span>
<span class="delete">
-the scope of a namespace declaration directly occurring in a</span> <code><a class="grammarRef" href="#prod-bundle"><span class="delete">toplevel </span>bundle</a></code> <span class="insert">itself.</span></li>
+the scope of a namespace</span><span class="insert">prefix-namespace</span> declaration directly occurring in a <code><a class="grammarRef" href="#prod-bundle"><span class="delete">toplevel </span>bundle</a></code> is the <code><a class="grammarRef" href="#prod-bundle"><span class="delete">toplevel </span>bundle</a></code> <span class="delete">itself, except and</span><span class="insert">itself.</span></li>
<li><span class="insert">
-The scope of a namespace declaration directly occurring in a </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code> is<span class="insert"> the </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code><span class="insert"> itself, excluding</span> the <code><a class="grammarRef" href="#prod-bundle"><span class="delete">toplevel bundle</span><span class="delete"> itself, except and </span><span class="delete">namedBundle</span><span class="insert">bundles</span></a></code> it may contain.</li>
+The scope of a prefix-namespace declaration directly occurring in a</span> <code><span class="delete">namedBundle</span><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code><span class="insert"> is the </span><code><a class="grammarRef" href="#prod-document"><span class="insert">document</span></a></code><span class="insert"> including the </span><code><a class="grammarRef" href="#prod-bundle"><span class="insert">bundles</span></a></code> it <span class="delete">may contain.</span><span class="insert">contains but excluding those </span><code><a class="grammarRef" href="#prod-bundle"><span class="insert">bundles</span></a></code><span class="insert"> that redeclare this prefix-namespace pair.</span></li>
</ul>
<p>A set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code> <em class="rfc2119" title="must not">must not</em> re-declare the same prefix.</p>
+<p><span class="insert">A set of namespace declarations </span><code><a class="grammarRef" href="#prod-namespaceDeclarations"><span class="insert">namespaceDeclarations</span></a></code><span class="insert"> occurring in a bundle </span><em class="rfc2119" title="may"><span class="insert">may</span></em><span class="insert"> re-declare a prefix declared in a surrounding document.</span></p>
+
<p>A namespace declaration <code><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code> <em class="rfc2119" title="must not">must not</em> declare prefixes <span class="name">prov</span> and <span class="name">xsd</span> (see <a href="#namespace-table">Table 1</a> for their IRI).</p>
@@ -2878,7 +2880,24 @@
default <http://example.org/2/>
entity(e001) // IRI: http://example.org/2/e001
endBundle
-<span class="delete">endBundle</span><span class="insert">endDocument</span>
+<span class="insert">endDocument
+</span></pre>
+</div>
+
+
+<div class="anexample" id="anexample-namespace-scope2"><div class="anexampleTitle"><a class="internalDFN" href="#anexample-namespace-scope2"><span class="insert">Example 42</span></a></div>
+<p><span class="insert">In the following example, a document declares a namespace with prefix </span><code><span class="insert">ex</span></code><span class="insert"> and the occurrence of
+</span><code><span class="insert">ex:e001</span></code><span class="insert"> directly occurring in the document refers to that namespace.
+In a nested bundle, the occurrence of
+</span><code><span class="insert">ex:e001</span></code><span class="insert"> also refers to the same namespace.</span></p>
+<pre class="codeexample"><span class="insert">document
+ prefix ex <http://example.org/1/>
+ entity(ex:e001) // IRI: http://example.org/1/e001
+
+ bundle b
+ entity(ex:001) // IRI: http://example.org/1/e001
+ </span>endBundle<span class="insert">
+endDocument</span>
</pre>
</div>
@@ -2977,18 +2996,18 @@
</ul>
-<p>Thus, <span class="delete">named </span>bundles can occur inside a <span class="delete">toplevel bundle.</span><span class="insert">document.</span>
-<span class="delete">Named bundles</span><span class="insert">Bundles</span> are self-contained: each identifier occuring in a <span class="delete">named </span>bundle, including the<span class="delete"> named</span> bundle's identifier itself, <em class="rfc2119" title="must">must</em> be interpreted with respect to the namespace declarations of that<span class="delete"> named </span> bundle. In other words,<span class="delete"> named </span> bundles <em class="rfc2119" title="should">should</em> not inherit namespaces declarations from the <span class="delete">toplevel bundle.</span><span class="insert">document.</span>
-</p>
-
-
-
-<div class="anexample" id="example_42"><div class="anexampleTitle"><a class="internalDFN" href="#example_42">Example 42</a></div>
-<p>
-The following <span class="delete">bundle</span><span class="insert">document</span> contains expressions related to the provenance of entity
-<span class="name">e2</span>.
-</p>
-<pre class="codeexample"><span class="delete">bundle</span><span class="insert">document</span>
+<p>Thus, <span class="delete">named </span>bundles <span class="delete">can occur inside a toplevel bundle.
+Named bundles are self-contained: each identifier occuring in a named bundle, including the named bundle's identifier itself, </span><span class="delete">must</span><span class="delete"> be interpreted with respect to the namespace declarations of that named bundle. In other words, named bundles </span><span class="delete">should</span><span class="delete"> not inherit namespaces declarations from the toplevel bundle.
+</span>
+
+
+
+<span class="delete">Example 42</span>
+<span class="delete">
+The following bundle contains expressions related to the provenance of entity
+</span><span class="delete">e2</span><span class="delete">.
+</span>
+<span class="delete">bundle
default <http://anotherexample.org/>
prefix ex <http://example.org/>
@@ -2999,10 +3018,64 @@
wasAssociatedWith(a1, ag2, -, [prov:role="author"])
agent(ag2, [ prov:type='prov:Person', ex:name="Bob" ])
-<span class="delete">endBundle</span><span class="insert">endDocument</span>
-</pre>
-<p>This container could for instance be returned as the result of a query to a provenance store for the provenance of entity <span class="name">e2</span> [<cite><a class="bibref" rel="biblioentry" href="#bib-PROV-AQ">PROV-AQ</a></cite>].
-</p>
+endBundle
+</span>
+<span class="delete">This container could for instance be returned as the result of a query to a provenance store for the provenance of entity </span><span class="delete">e2</span><span class="delete"> [</span><span class="delete">PROV-AQ</span><span class="delete">].
+</span>
+
+
+
+
+
+
+
+<span class="delete">5. </span><span class="delete">Extensibility</span>
+
+<span class="delete">The PROV data model is extensible by means of attributes </span><span class="delete">prov:type</span><span class="delete"> and </span><span class="delete">prov:role</span><span class="delete"> allowing subtyping of expressions. For some applications, novel syntax may also be convenient. Hence, the normative requirements are as follow.
+</span>
+<span class="delete"> PROV-N compliant parsers </span><span class="delete">must</span><span class="delete"> be able to parse expressions matching the </span><span class="delete">extensibilityExpression</span><span class="delete"> production defined below.
+</span><span class="delete"> As PROV provides no definition for these expressions, PROV compliant implementations
+ </span><em class="rfc2119" title="may">may</em> <span class="delete">ignore these expressions.</span>
+<span class="delete"> Extensions to PROV and PROV-N </span><span class="delete">may</span><span class="delete"> specify more specific productions and interpretations for these expressions, which applications </span><span class="delete">may</span><span class="delete"> adopt to follow. </span>
+
+
+
+
+
+ <span class="delete">[</span><span class="delete">51</span><span class="delete">] </span> <span class="delete">extensibilityExpression</span> <span class="delete"> ::= </span> <span class="delete">QUALIFIED_NAME</span><span class="delete"> "(" </span><span class="delete">optionalIdentifier</span> <span class="delete">extensibilityArgument</span><span class="delete"> ( "," </span><span class="delete">extensibilityArgument</span><span class="delete"> )* </span><span class="delete">optionalAttributeValuePairs</span><span class="delete"> ")"</span>
+ <span class="delete">[</span><span class="delete">52</span><span class="delete">] </span> <span class="delete">extensibilityArgument</span> <span class="delete"> ::= </span> <span class="delete">( </span><span class="delete">identifierOrMarker</span><span class="delete"> | </span><span class="delete">literal</span><span class="delete"> | </span><span class="delete">time</span><span class="delete"> | </span><span class="delete">extensibilityExpression</span><span class="delete"> | </span><span class="delete">extensibilityTuple</span><span class="delete"> )</span>
+ <span class="delete">[</span><span class="delete">53</span><span class="delete">] </span> <span class="delete">extensibilityTuple</span> <span class="delete"> ::= </span> <span class="delete">"{" </span><span class="delete">extensibilityArgument</span><span class="delete"> ( "," </span><span class="delete">extensibilityArgument</span><span class="delete"> )* "}"</span><span class="delete"> | "(" </span><span class="delete">extensibilityArgument</span><span class="delete"> ( "," </span><span class="delete">extensibilityArgument</span><span class="delete"> )* ")"</span>
+
+
+
+<span class="delete">Expressions compatible with the
+</span><span class="delete">extensibilityExpression</span><span class="delete"> production follow</span><span class="insert">occur inside</span> a <span class="delete">general form of functional syntax, in which the predicate </span><span class="delete">must</span><span class="delete"> be a
+</span><span class="delete">qualifiedName</span><span class="delete">
+with a non-empty </span><span class="delete">prefix</span><span class="delete">.</span><span class="insert">document, but do not appear inside other bundles.
+</span></p>
+
+
+
+<div class="anexample" id="example_43"><div class="anexampleTitle"><a class="internalDFN" href="#example_43">Example 43</a></div>
+<p>
+<span class="insert">The following document contains expressions related to the provenance of entity
+</span><span class="name"><span class="insert">e2</span></span><span class="insert">.
+</span></p>
+<pre class="codeexample"><span class="insert">document
+ default <http://anotherexample.org/>
+ prefix ex <http://example.org/>
+
+ entity(e2, [ prov:type="File", ex:path="/shared/crime.txt", ex:creator="Alice",
+ ex:content="There was a lot of crime in London last month."])
+ activity(a1, 2011-11-16T16:05:00, -, [prov:type="edit"])
+ wasGeneratedBy(e2, a1, -, [ex:fct="save"])
+ wasAssociatedWith(a1, ag2, -, [prov:role="author"])
+ agent(ag2, [ prov:type='prov:Person', ex:name="Bob" ])
+
+endDocument
+</span></pre>
+<p><span class="insert">This container could for instance be returned as the result of a query to a provenance store for the provenance of entity </span><span class="name"><span class="insert">e2</span></span><span class="insert"> [</span><cite><a class="bibref" rel="biblioentry" href="#bib-PROV-AQ"><span class="insert">PROV-AQ</span></a></cite><span class="insert">].
+</span></p>
</div>
@@ -3010,37 +3083,33 @@
</div>
<div id="extensibility" class="section">
-<h2><span class="secno">5. </span>Extensibility</h2>
-
-<p>The PROV data model is extensible by means of attributes <span class="name">prov:type</span> and <span class="name">prov:role</span> allowing subtyping of expressions. For some applications, novel syntax may also be convenient. Hence, the normative requirements are as follow.
-</p>
+<h2><span class="secno"><span class="insert">5. </span></span><span class="insert">Extensibility</span></h2>
+
+<p><span class="insert">The PROV data model is extensible by means of attributes </span><span class="name"><span class="insert">prov:type</span></span><span class="insert"> and </span><span class="name"><span class="insert">prov:role</span></span><span class="insert"> allowing subtyping of expressions. For some applications, novel syntax may also be convenient. Hence, the normative requirements are as follow.</span></p>
<ul>
-<li> PROV-N compliant parsers <em class="rfc2119" title="must">must</em> be able to parse expressions matching the <code class="content"><a class="grammarRef" href="#prod-extensibilityExpression">extensibilityExpression</a></code> production defined below.
-</li><li> As PROV provides no definition for these expressions, PROV compliant implementations
- <em class="rfc2119" title="may">may</em> ignore these expressions.</li>
-<li> Extensions to PROV and PROV-N <em class="rfc2119" title="may">may</em> specify more specific productions and interpretations for these expressions, which applications <em class="rfc2119" title="may">may</em> adopt to follow. </li>
+<li><span class="insert"> PROV-N compliant parsers </span><em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> be able to parse expressions matching the </span><code class="content"><a class="grammarRef" href="#prod-extensibilityExpression"><span class="insert">extensibilityExpression</span></a></code><span class="insert"> production defined below.
+</span></li><li><span class="insert"> As PROV provides no definition for these expressions, PROV compliant implementations
+ </span><em class="rfc2119" title="may"><span class="insert">may</span></em><span class="insert"> ignore these expressions.</span></li>
+<li><span class="insert"> Extensions to PROV and PROV-N </span><em class="rfc2119" title="may"><span class="insert">may</span></em><span class="insert"> specify more specific productions and interpretations for these expressions, which applications </span><em class="rfc2119" title="may"><span class="insert">may</span></em><span class="insert"> adopt to follow. </span></li>
</ul>
-
-
-
<table class="grammar">
-<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-extensibilityExpression" name="prod-extensibilityExpression"></a>[<span class="prodNo">51</span>] </td> <td><code class="production prod">extensibilityExpression</code></td> <td> ::= </td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></span> "(" <span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier">optionalIdentifier</a></span> <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> )* <span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs">optionalAttributeValuePairs</a></span> ")"</code></td> </tr> </tbody>
-<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-extensibilityArgument" name="prod-extensibilityArgument"></a>[<span class="prodNo">52</span>] </td> <td><code class="production prod">extensibilityArgument</code></td> <td> ::= </td> <td><code class="content">( <span class="prod"><a class="grammarRef" href="#prod-identifierOrMarker">identifierOrMarker</a></span> | <span class="prod"><a class="grammarRef" href="#prod-literal">literal</a></span> | <span class="prod"><a class="grammarRef" href="#prod-time">time</a></span> | <span class="prod"><a class="grammarRef" href="#prod-extensibilityExpression">extensibilityExpression</a></span> | <span class="prod"><a class="grammarRef" href="#prod-extensibilityTuple">extensibilityTuple</a></span> )</code></td> </tr> </tbody>
-<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-extensibilityTuple" name="prod-extensibilityTuple"></a>[<span class="prodNo">53</span>] </td> <td><code class="production prod">extensibilityTuple</code></td> <td> ::= </td> <td><code class="content">"{" <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> )* "}"<br> | "(" <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> ( "," <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument">extensibilityArgument</a></span> )* ")"</code></td> </tr> </tbody>
+<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-extensibilityExpression" name="prod-extensibilityExpression"></a><span class="insert">[</span><span class="prodNo"><span class="insert">51</span></span><span class="insert">] </span></td> <td><code class="production prod"><span class="insert">extensibilityExpression</span></code></td> <td><span class="insert"> ::= </span></td> <td><code class="content"><span class="prod"><a class="grammarRef" href="#prod-QUALIFIED_NAME"><span class="insert">QUALIFIED_NAME</span></a></span><span class="insert"> "(" </span><span class="prod"><a class="grammarRef" href="#prod-optionalIdentifier"><span class="insert">optionalIdentifier</span></a></span> <span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument"><span class="insert">extensibilityArgument</span></a></span><span class="insert"> ( "," </span><span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument"><span class="insert">extensibilityArgument</span></a></span><span class="insert"> )* </span><span class="prod"><a class="grammarRef" href="#prod-optionalAttributeValuePairs"><span class="insert">optionalAttributeValuePairs</span></a></span><span class="insert"> ")"</span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-extensibilityArgument" name="prod-extensibilityArgument"></a><span class="insert">[</span><span class="prodNo"><span class="insert">52</span></span><span class="insert">] </span></td> <td><code class="production prod"><span class="insert">extensibilityArgument</span></code></td> <td><span class="insert"> ::= </span></td> <td><code class="content"><span class="insert">( </span><span class="prod"><a class="grammarRef" href="#prod-identifierOrMarker"><span class="insert">identifierOrMarker</span></a></span><span class="insert"> | </span><span class="prod"><a class="grammarRef" href="#prod-literal"><span class="insert">literal</span></a></span><span class="insert"> | </span><span class="prod"><a class="grammarRef" href="#prod-time"><span class="insert">time</span></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-extensibilityTuple"><span class="insert">extensibilityTuple</span></a></span><span class="insert"> )</span></code></td> </tr> </tbody>
+<tbody class="prod"> <tr valign="baseline"> <td><a id="prod-extensibilityTuple" name="prod-extensibilityTuple"></a><span class="insert">[</span><span class="prodNo"><span class="insert">53</span></span><span class="insert">] </span></td> <td><code class="production prod"><span class="insert">extensibilityTuple</span></code></td> <td><span class="insert"> ::= </span></td> <td><code class="content"><span class="insert">"{" </span><span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument"><span class="insert">extensibilityArgument</span></a></span><span class="insert"> ( "," </span><span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument"><span class="insert">extensibilityArgument</span></a></span><span class="insert"> )* "}"</span><br><span class="insert"> | "(" </span><span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument"><span class="insert">extensibilityArgument</span></a></span><span class="insert"> ( "," </span><span class="prod"><a class="grammarRef" href="#prod-extensibilityArgument"><span class="insert">extensibilityArgument</span></a></span><span class="insert"> )* ")"</span></code></td> </tr> </tbody>
</table>
-<p>Expressions compatible with the
-<code class="content"><a class="grammarRef" href="#prod-extensibilityExpression">extensibilityExpression</a></code> production follow a general form of functional syntax, in which the predicate <em class="rfc2119" title="must">must</em> be a
-<code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">qualifiedName</a></code>
-with a non-empty <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">prefix</a></code>.</p>
-
-
-
-<div class="anexample" id="example_43"><div class="anexampleTitle"><a class="internalDFN" href="#example_43">Example 43</a></div>
+<p><span class="insert">Expressions compatible with the
+</span><code class="content"><a class="grammarRef" href="#prod-extensibilityExpression"><span class="insert">extensibilityExpression</span></a></code><span class="insert"> production follow a general form of functional syntax, in which the predicate </span><em class="rfc2119" title="must"><span class="insert">must</span></em><span class="insert"> be a
+</span><code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME"><span class="insert">qualifiedName</span></a></code><span class="insert">
+with a non-empty </span><code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX"><span class="insert">prefix</span></a></code><span class="insert">.</span></p>
+
+
+
+<div class="anexample" id="example_44"><div class="anexampleTitle"><a class="internalDFN" href="#example_44"><span class="insert">Example 44</span></a></div>
<p>
<a href="#component6">Collections</a> are sets of entities, whose membership can be expressed using the <span class="name">hadMember</span> relation. The following example shows how one can express membership for <em><span class="insert">dictionaries</span></em><span class="insert">, </span>an <span class="insert">illustrative </span>extension of <span class="delete">Collections, namely</span><span class="insert">Collections consisting of</span> sets of <span class="delete">key-value pairs.</span><span class="insert">key-entity pairs, where a key is a </span><code><a class="grammarRef" href="#prod-literal"><span class="insert">literal</span></a></code><span class="insert">.</span> The notation is a variation of that used for Collections membership, allowing multiple member elements to be declared, and in which the elements are pairs. The name of the relation is qualified with the extension-specific namespace <span class="name">http://example.org/dictionaries</span>.
</p>
@@ -3159,13 +3228,15 @@
<div class="appendix informative section" id="changes-since-last-version">
<h2><span class="secno">A. </span><span class="insert">Changes since last version</span></h2><p><em><span class="insert">This section is non-normative.</span></em></p>
- <p>
-</p><ul>
+<p><span class="insert"> Please see the </span><a href="http://www.w3.org/2011/prov/wiki/ResponsesToPublicComments"><span class="insert">Responses to Public Comments on the Last Call Working Draft</span></a><span class="insert"> for more details about the justification of these changes.</span></p>
+<ul>
<li> <a href="http://www.w3.org/2011/prov/track/issues/543"><span class="insert">ISSUE-543</span></a><span class="insert">: Uses key-entity pair terminology for example 43.
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/538"><span class="insert">ISSUE-538</span></a><span class="insert">: Rephrasing of text in example 10.
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/547"><span class="insert">ISSUE-547</span></a><span class="insert">: Aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/496"><span class="insert">ISSUE-496</span></a><span class="insert">: For each prov-n term, added a cross-reference to corresponding prov-dm term (see table following each production). Rephrased text related to scope of a namespace declaration. Added an informative file with all productions.
</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/573"><span class="insert">ISSUE-573</span></a><span class="insert">: Updated Media Type section.
+</span></li><li> <a href="http://www.w3.org/2011/prov/track/issues/589"><span class="insert">ISSUE-589</span></a><span class="insert">: Updated scoping rule for prefix-namespace declaration. Also refrained from saying bundles are self-contained.
+
</span></li></ul>
</div>
--- a/model/prov-n.html Tue Nov 06 17:04:18 2012 +0000
+++ b/model/prov-n.html Tue Nov 06 17:05:14 2012 +0000
@@ -1574,9 +1574,9 @@
<tbody class="grammar-ref" data-ref="prod-bundle"></tbody>
</table>
-<p>Bundles cannot be nested because <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> is not an <code><a class="grammarRef" href="#prod-expression">expression</a></code>, and therefore cannot occurs inside another <code><a class="grammarRef" href="#prod-bundle">bundle</a></code>.</p>
-
-<p>Bundles are self-contained: each identifier occuring in a bundle, including the bundle identifier itself, MUST be interpreted with respect to the namespace declarations of that bundle. In other words, for every identifier with a prefix <code>p</code> within a bundle, there MUST be a namespace declaration for <code>p</code> in this bundled; for every identifier without prefix, there MUST be a default namespace declaration in this bundle.</p>
+<p>Bundles cannot be nested because <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> is not an <code><a class="grammarRef" href="#prod-expression">expression</a></code>, and therefore cannot occur inside another <code><a class="grammarRef" href="#prod-bundle">bundle</a></code>.</p>
+
+<p>Each identifier occuring in a bundle, including the bundle identifier itself, MUST be interpreted with respect to the namespace declarations of that bundle, or if the identifier's prefix is not declared in the bundle, with respect to the namespace declaration in the document. </p>
<p>The following table summarizes how each constituent of a PROV-DM bundle maps to a PROV-N syntax element.</p>
@@ -2202,11 +2202,13 @@
<li>
The scope of a prefix-namespace declaration directly occurring in a <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> is the <code><a class="grammarRef" href="#prod-bundle">bundle</a></code> itself.</li>
<li>
-The scope of a prefix-namespace declaration directly occurring in a <code><a class="grammarRef" href="#prod-document">document</a></code> is the <code><a class="grammarRef" href="#prod-document">document</a></code> including the <code><a class="grammarRef" href="#prod-bundle">bundles</a></code> it contains but excluding those <code><a class="grammarRef" href="#prod-bundle">bundles</a></code> that redeclares this prefix-namespace pair.</li>
+The scope of a prefix-namespace declaration directly occurring in a <code><a class="grammarRef" href="#prod-document">document</a></code> is the <code><a class="grammarRef" href="#prod-document">document</a></code> including the <code><a class="grammarRef" href="#prod-bundle">bundles</a></code> it contains but excluding those <code><a class="grammarRef" href="#prod-bundle">bundles</a></code> that redeclare this prefix-namespace pair.</li>
</ul>
<p>A set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code> MUST NOT re-declare the same prefix.</p>
+<p>A set of namespace declarations <code><a class="grammarRef" href="#prod-namespaceDeclarations">namespaceDeclarations</a></code> occurring in a bundle MAY re-declare a prefix declared in a surrounding document.</p>
+
<p>A namespace declaration <code><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code> MUST NOT declare prefixes <span class="name">prov</span> and <span class="name">xsd</span> (see <a href="#namespace-table">Table 1</a> for their IRI).</p>
@@ -2358,8 +2360,7 @@
</ul>
-<p>Thus, bundles can occur inside a document.
-Bundles are self-contained: each identifier occuring in a bundle, including the bundle's identifier itself, MUST be interpreted with respect to the namespace declarations of that bundle. In other words, bundles SHOULD not inherit namespaces declarations from the document.
+<p>Thus, bundles MAY occur inside a document, but do not appear inside other bundles.
</p>
@@ -2553,7 +2554,7 @@
<li> <a href="http://www.w3.org/2011/prov/track/issues/547">ISSUE-547</a>: Aligned terminology and productions with prov-constraints document, renaming 'toplevel bundle' to 'document', and renaming 'named bundle' to 'bundle'.
<li> <a href="http://www.w3.org/2011/prov/track/issues/496">ISSUE-496</a>: For each prov-n term, added a cross-reference to corresponding prov-dm term (see table following each production). Rephrased text related to scope of a namespace declaration. Added an informative file with all productions.
<li> <a href="http://www.w3.org/2011/prov/track/issues/573">ISSUE-573</a>: Updated Media Type section.
-<li> <a href="http://www.w3.org/2011/prov/track/issues/589">ISSUE-589</a>: updated scoping rule for prefix-namespace declaration.
+<li> <a href="http://www.w3.org/2011/prov/track/issues/589">ISSUE-589</a>: Updated scoping rule for prefix-namespace declaration. Also refrained from saying bundles are self-contained.
</ul>
</section>