--- a/model/prov-dm.html	Wed Jun 13 09:40:15 2012 +0100
+++ b/model/prov-dm.html	Wed Jun 13 10:36:42 2012 +0100
@@ -527,7 +527,7 @@
 <tr><td><a><b>prefix</b></a></td><td><b>namespace uri</b></td> <td><b>definition</b></td></tr>
 <tr><td><a>prov</a></td><td>http://www.w3.org/ns/prov#</td><td>The PROV namespace (see <a class="section-ref" href="#term-NamespaceDeclaration"><span>TBD</span></a>)</td></tr>
 <tr><td><a>xsd</a></td><td>http://www.w3.org/2000/10/XMLSchema#</td><td>XML Schema Namespace [[!XMLSCHEMA11-2]]</td></tr>
-<tr><td><a>rdf</a></td><td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td><td>The RDF namespace  [[RDF-CONCEPTS11]]</td></tr>
+<tr><td><a>rdf</a></td><td>http://www.w3.org/1999/02/22-rdf-syntax-ns#</td><td>The RDF namespace  [[!RDF-CONCEPTS]]</td></tr>
 <tr><td><a>(others)</a></td><td>(various)</td><td>All other namespace prefixes are used in examples only. <br/> In particular, URIs starting with "http://example.com" represent<br/> some application-dependent URI [[!URI]]</td></tr>
 </table>
 </div>
@@ -3450,17 +3450,17 @@
 <p>Each kind of such values is called a <em>datatype</em>.
  Use of the following data types is RECOMMENDED. </p>
 <ul>
-<li> The RDF-compatible [[RDF-CONCEPTS11]]  built-in types taken from 
+<li> The RDF-compatible [[!RDF-CONCEPTS]]  built-in types taken from 
 the set of XML Schema Datatypes, version 1.1 [[!XMLSCHEMA11-2]];</li>
 <li> Qualified names introduced in this specification;</li>
-<li> RDF literal types for html and xml [[RDF-CONCEPTS11]].</li>
+<li> RDF literal types for html and xml [[!RDF-CONCEPTS]].</li>
 </ul>
 <p>
 The normative definitions of these datatypes are provided by their respective specifications, and listed in Table 8.
 </p>
 
-<p>PROV accepts the RDF-Compatible XSD types that RDF lists in its own specification  [[RDF-CONCEPTS11]].
-New RDF releases may extend the list of datatypes, and PROV would naturally use those too.</p>
+<p>PROV accepts the RDF-Compatible XSD types that RDF lists in its own specification  [[!RDF-CONCEPTS]].
+New RDF releases [[RDF-CONCEPTS11]] may extend the list of datatypes, and PROV would naturally use those too.</p>
 
 
 

--- a/model/prov-n.html	Wed Jun 13 09:40:15 2012 +0100
+++ b/model/prov-n.html	Wed Jun 13 10:36:42 2012 +0100
@@ -2521,14 +2521,14 @@
 <tbody class="grammar-ref" data-ref="prod-literal"></tbody>
 <tbody class="grammar-ref" data-ref="prod-typedLiteral"></tbody>
 <tbody class="grammar-ref" data-ref="prod-datatype"></tbody>
-<tbody><tr valign="baseline"><td></td><td></td><td></td><td><em>where</em> <a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a> <em>is listed in Table <a href="#permitted-datatypes">permitted-datatypes</a></em></td></tbody>
+<tbody><tr valign="baseline"><td></td><td></td><td></td></tbody>
 <tbody class="grammar-ref" data-ref="prod-convenienceNotation"></tbody>
 <tbody class="grammar-ref" data-ref="prod-STRING_LITERAL"></tbody>
 <tbody class="grammar-ref" data-ref="prod-INT_LITERAL"></tbody>
 <tbody class="grammar-ref" data-ref="prod-QUALIFIED_NAME_LITERAL"></tbody>
 </table>
 
-
+<p>In production <code class="content"><a class="grammarRef" href="#prod-datatype">prod-datatype</a></code>, the <code class="content"><a class="grammarRef" href="#prod-QUALIFIED_NAME">QUALIFIED_NAME</a></code> is used to denote a <a href="http://dvcs.w3.org/hg/prov/raw-file/default/model/prov-dm.html#term-value">PROV RECOMMENDED data type</a> [[PROV-DM]].
 
 
 <p>The non terminals
@@ -2544,6 +2544,7 @@
 
 <p> In particular, a Literal may be an IRI-typed string (with datatype <span class="name">xsd:anyURI</span>);  such IRI has no specific interpretation in the context of PROV.</p>
 
+<!--
 <table border="1" style="margin-left: auto; margin-right: auto;">
 <caption id="permitted-datatypes">Permitted datatypes in literals</caption>
 <tr><td><a href="http://www.w3.org/TR/xmlschema-2/#decimal">xsd:decimal</a></td> <td><a href="http://www.w3.org/TR/xmlschema-2/#double">xsd:double</a></td>  <td><a href="http://www.w3.org/TR/xmlschema-2/#dateTime">xsd:dateTime</a></td> </tr>
@@ -2561,7 +2562,7 @@
 <tr><td><a href="http://www.w3.org/TR/xmlschema-2/#unsignedShort">xsd:unsignedShort</a></td><td><a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:anyURI</a></td> <td></td></tr>
 <tr><td><a href="http://www.w3.org/TR/xmlschema-2/#unsignedByte">xsd:unsignedByte</a></td> <td><a href="http://www.w3.org/TR/xmlschema-2/#anyURI">xsd:QName</a></td><td></td></tr>
 </table>
-
+-->
 <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