--- a/model/comments/issue-438-stian.txt	Sun Jul 08 22:13:13 2012 +0100
+++ b/model/comments/issue-438-stian.txt	Sun Jul 08 22:21:15 2012 +0100
@@ -391,6 +391,8 @@
    > > > dIdentifier	   ::=   	identifier
    > 
    > This is not used anywhere and can be removed. (Dictionary?)
+
+Removed
    > 
    > 
    > A qualified name's prefix is optional. If a prefix occurs in a qualified name, 
@@ -405,6 +407,10 @@
    > 
    > without declaring the prefix "fred".
    > 
+
+
+Yes, MUST added.
+
    > 
    > 
    > 
@@ -428,6 +434,12 @@
    > However I don't think there is anywhere that allows both a literal and
    > an identifier in the same position, so we MIGHT be safe. Parser heads
    > converge here.
+
+
+It is correct that 1337 can be a QUALIFIED_NAME and an
+INT_LITERAL. The context allows us to disambiguate:
+INT_LITERAL are only allowed as convenienceNotation for literals.
+
    > 
    > 
    > > > 3.7.3 Literal
@@ -435,6 +447,9 @@
    > a parser should give precedence to the production for INT_LITERAL.
    > Again, I don't see this conflict, as the former requires 'single'
    > quotes and the latter does not allow that.
+
+
+
    > 
    > 
    > entity(e1, [ex:value='1337'])   // equivalent to

--- a/model/prov-n.html	Sun Jul 08 22:13:13 2012 +0100
+++ b/model/prov-n.html	Sun Jul 08 22:21:15 2012 +0100
@@ -2099,7 +2099,7 @@
 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.
 <p>A qualified name's prefix is OPTIONAL. If a prefix occurs in a
- qualified name, it refers to a <a>namespace</a> declared in a namespace declaration.  In the absence of prefix, the qualified name 
+ qualified name, it MUST refer 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>
 
 <!--
@@ -2265,8 +2265,10 @@
 
 
 <p><b>Note:</b>The productions for <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">prov:QUALIFIED_NAME</a></code> and
-<code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code> are conflicting.  In the context of a 
-<code class="content"><a class="grammarRef" href="#prod-literal">literal</a></code>, a parser should give precedence to the production for
+<code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code> are conflicting.  
+Indeed <code>1234</code> can be both a <code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code> and a <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">prov:QUALIFIED_NAME</a></code> (without prefix).  To resolve this conflict,
+in the context of the production
+<code class="content"><a class="grammarRef" href="#prod-literal">literal</a></code>, a parser SHOULD give precedence to the production for
 <code class="content"><a class="grammarRef" href="#prod-INT_LITERAL">INT_LITERAL</a></code>. 
 </p>