--- a/model/comments/issue-438-stian.txt	Sun Jul 08 22:21:15 2012 +0100
+++ b/model/comments/issue-438-stian.txt	Sun Jul 08 22:32:10 2012 +0100
@@ -448,7 +448,10 @@
    > Again, I don't see this conflict, as the former requires 'single'
    > quotes and the latter does not allow that.
 
+There is misunderstanding here. This note is exactly the point you made above.
 
+The conflict is between INT_LITERAL and QUALIFIED_NAME, and not
+QUALIFIED_NAME_LITERAL.
 
    > 
    > 
@@ -461,6 +464,10 @@
    > 
    > It would be good if a (separate) example in 3.7.3 showed all of these
    > equivalences.
+
+
+TODO: revisit example 33, and make the conveninence notation clearer.
+
    > 
    > 
    > 
@@ -489,11 +496,22 @@
    > 
    > 
    >   namespaceDeclaration	   ::=   	"prefix" PN_PREFIX namespace
+
+Yes, it is a mistake in the document.
+The production you suggest is the one I had in my reference implementation.
+
    > 
    > To match all valid prefixes in QUALIFIED_NAME.
    > 
    > Note that QUALIFIED_NAME allows the empty prefix, ie ":ex1" (which is
    > different from "ex1"). ((And thus also ":"))
+
+No, this is not correct.
+PN_PREFIX always has at least one character.
+
+PN_PREFIX	  ::=  	PN_CHARS_BASE ((PN_CHARS|'.')* PN_CHARS)?
+
+
    > 
    > However this would be difficult to declare ":" in the current prefix
    > rule,  because unlike say in Sparql and Turtle, the prefix is not
@@ -512,6 +530,10 @@
    >    prefix ex: <http://www.example.org/>
    >  endBundle
    > 
+
+This is not necessary given the above.
+
+
    > 
    > > >  Instead, they can be %-escaped or incorporated in the IRI denoted by a prefix.
    > > > <PERCENT>	   ::=   	"%" HEX HEX

--- a/model/prov-n.html	Sun Jul 08 22:21:15 2012 +0100
+++ b/model/prov-n.html	Sun Jul 08 22:32:10 2012 +0100
@@ -2133,7 +2133,10 @@
 </p>
 
 
-<p>Qualified names <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> consist of a prefix and a local part. Prefixes follow the production <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> defined by SPARQL [[!RDF-SPARQL-QUERY]]. Local parts have to be conformant with <code class="content"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></code>, which extends the original SPARQL <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_LOCAL">PN_LOCAL</a></code> definition by allowing further characters and %-escaped charaters (see <code class="content"><a class="grammarRef" href="#prod-PN_CHARS_OTHERS">PN_CHARS_OTHERS</a></code>).</p>
+<p>Qualified names <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> consist of a prefix and a local part. Prefixes follow the production <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_PREFIX">PN_PREFIX</a></code> defined by SPARQL [[!RDF-SPARQL-QUERY]]. Local parts have to be conformant with <code class="content"><a class="grammarRef" href="#prod-PN_LOCAL">PN_LOCAL</a></code>, which extends the original SPARQL <code class="content"><a class="grammarRef" href="http://www.w3.org/TR/rdf-sparql-query/#rPN_LOCAL">PN_LOCAL</a></code> definition by allowing further characters (see <code class="content"><a class="grammarRef" href="#prod-PN_CHARS_OTHERS">PN_CHARS_OTHERS</a></code>)  and %-escaped charaters (see <code class="content"><a class="grammarRef" href="#prod-PERCENT">PERCENT</a></code>). %-escaped characters are to be interpreted as per
+ section 3.1.  Mapping of IRIs to URIs in [[!RFC3987]].</p>
+
+
 
  
 <table class="grammar">