--- a/model/comments/issue-438-stian.txt Sun Jul 08 22:32:10 2012 +0100
+++ b/model/comments/issue-438-stian.txt Sun Jul 08 23:00:37 2012 +0100
@@ -164,6 +164,10 @@
> eIdentifier ( "," aIdentifierOrMarker "," timeOrMarker )? optionalAttributeValuePairs ")"
> This does not allow aIdentifierOrMarker without timeOrMarker - is this
> intentional?
+
+
+Yes, all optionals or none is the adopted convention.
+
>
>
> The following examples are not valid:
@@ -540,6 +544,9 @@
> It is not defined what is the meaning of this escaping. What do the
> HEX represent? If you mean "as in section 3.1. Mapping of IRIs to
> URIs of [RFC3987]" - then include this.
+
+Yes, Done.
+
>
> Should be "in corporated in *a* namespace URI denoted by a prefix" -
> as presumably that specific namespace binding does not exist yet if
@@ -584,6 +591,9 @@
>
> entity(ex:1234) // corresponds to IRI http://example.org/1/1234
>
+
+Yes, fixed.
+
>
> I would add:
>
@@ -591,6 +601,9 @@
> entity(ex:/) // corresponds to IRI http://example.org/1// //
> Strict concatenation
>
+
+Done.
+
>
>
> What does the following mean?
@@ -601,6 +614,12 @@
> to the production for prefix.
>
> With 'prefix' here - do you mean PN_PREFIX or the keyword 'prefix' within
+
+I mean PN_PREFIX.
+
+
+abc can be a PN_PREFIX or a QUALIFIED_NAME (PN_LOCAL only, no PN_PREFIX)
+
>
> > > namespaceDeclaration ::= "prefix" QUALIFIED_NAME namespace
> ?
@@ -632,6 +651,11 @@
>
> (Personally I think they should not be allowed - Turtle will overwrite
> sequentially - but nothing else in PROV-N depends on the sequence)
+
+Added:
+
+<p>A PROV-N document MUST not re-declare the same prefix.</p>
+
>
>
> 3.7.4 does neither not define that that prefixes and defaults are
@@ -645,6 +669,9 @@
> entity(fred) // Different fred!
> endBundle
> endBundle
+
+
+TODO
>
>
> > > Section 4
--- a/model/prov-n.html Sun Jul 08 22:32:10 2012 +0100
+++ b/model/prov-n.html Sun Jul 08 23:00:37 2012 +0100
@@ -2179,14 +2179,16 @@
entity(ex:a/) // corresponds to IRI http://example.org/1/a/
entity(ex:a/b) // corresponds to IRI http://example.org/1/a/b
entity(b) // corresponds to IRI http://example.org/2/b
- entity(ex:1234) // corresponds to IRI http://example.org/2/1234
+ entity(ex:1234) // corresponds to IRI http://example.org/1/1234
entity(4567) // corresponds to IRI http://example.org/2/4567
+ entity(c/) // corresponds to IRI http://example.org/2/c/
+ entity(ex:/) // corresponds to IRI http://example.org/1//
endBundle
</pre>
</div>
-<p><b>Note:</b>The productions for <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">qualifiedName</a></code> and <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">prefix</a></code> are conflicting. In the context of a <code class="content"><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code>, a parser should give precedence to the production for <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">prefix</a></code>.
+<p><b>Note:</b>The productions for <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> and <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> are conflicting. In the context of a <code class="content"><a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a></code>, a parser should give precedence to the production for <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">prefix</a></code>.
</p>
@@ -2374,8 +2376,7 @@
<p>A <a class="grammarRef" href="#prod-namespaceDeclaration">namespaceDeclaration</a> 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. The scope of a namespace declaration is the <a class="grammarRef" href="#prod-namedBundle">namedBundle</a> or <a class="grammarRef" href="#prod-bundle">toplevel bundle</a> in which it directly occurs.</p>
-
-
+<p>A PROV-N document MUST not re-declare the same prefix.</p>
<p>In PROV-N, the following prefixes are reserved:
<ul>