--- a/paq/prov-aq.html	Thu Jan 05 13:59:36 2012 +0000
+++ b/paq/prov-aq.html	Thu Jan 05 14:26:23 2012 +0000
@@ -16,31 +16,47 @@
               berjon.biblio[k] = extraReferences[k];
       };
       var extraReferences = {
+
         "LINK-REL" : "M. Nottingham, <a href='http://www.ietf.org/rfc/rfc5988.txt'><cite>Web Linking</cite></a>, October 2010, Internet RFC 5988. URL: <a href='http://www.ietf.org/rfc/rfc5988.txt'>http://www.ietf.org/rfc/rfc5988.txt</a>",
+
         "RFC2387" : "E. Levinson. <a href=\"http://www.ietf.org/rfc/rfc2387.txt\"><cite>The MIME Multipart/Related Content-type.</cite></a> August 1998. Internet RFC 2387. URL: <a href=\"http://www.ietf.org/rfc/rfc2387.txt\">http://www.ietf.org/rfc/rfc2387.txt</a>",
+
         "RFC3297" : "G. Klyne; R. Iwazaki; D. Crocker. <a href=\"http://www.ietf.org/rfc/rfc3297.txt\"><cite>Content Negotiation for Messaging Services based on Email.</cite></a> July 2002. Internet RFC 3297. URL: <a href=\"http://www.ietf.org/rfc/rfc3297.txt\">http://www.ietf.org/rfc/rfc3297.txt</a>",
+
         "PRISM" : "International Digital Enterprise Alliance, Inc. <a href=\"http://www.prismstandard.org/specifications/2.0/PRISM_prism_namespace_2.0.pdf\"><cite>PRISM: Publishing Requirements for Industry Standard Metadata</cite></a>. February 2008. URL: <a href=\"http://www.prismstandard.org/specifications/2.0/PRISM_prism_namespace_2.0.pdf\">http://www.prismstandard.org/specifications/2.0/PRISM_prism_namespace_2.0.pdf</a>",
+
         "FABIO" : "D. Shotton; S. Peroni. <a href=\"http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations\"><cite>FaBiO, the FRBR-aligned Bibliographic Ontology.</cite></a> June 2011. URL: <a href=\"http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations\">http://speroni.web.cs.unibo.it/cgi-bin/lode/req.py?req=http:/purl.org/spar/fabio#namespacedeclarations</a>",
+
         "URI-template": 
           "J. Gregorio; R. Fielding, ed.; M. Hadley; M. Nottingham. "+
-          "<a href=\"http://tools.ietf.org/html/draft-gregorio-uritemplate-06\"><cite>URI Template</cite></a>. "+
-          "July 2011, Work in progress. "+
-          "URL: <a href=\"http://tools.ietf.org/html/draft-gregorio-uritemplate-06\"><cite>http://tools.ietf.org/html/draft-gregorio-uritemplate-06</cite></a>",
+          "<a href=\"https://datatracker.ietf.org/doc/draft-gregorio-uritemplate/\"><cite>URI Template</cite></a>. "+
+          "September 2011, Work in progress. "+
+          "URL: <a href=\"https://datatracker.ietf.org/doc/draft-gregorio-uritemplate/\"><cite>https://datatracker.ietf.org/doc/draft-gregorio-uritemplate/</cite></a>",
+
         "REST-APIs": 
           "R. Fielding. "+
           "<a href=\"http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven\">REST APIs must be hypertext driven</a>. "+
           "October 2008 (blog post), "+
           "URL: <a href=\"http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven\">http://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypertext-driven</a>",
+
         "PROV-DM":
           "L. Moreau; P. Missier. "+
           "<a href=\"http://www.w3.org/TR/prov-dm/\"><cite>The PROV Data Model and Abstract Syntax Notation</cite></a>. "+
           "2011, Work in progress. "+
           "URL: <a href=\"http://www.w3.org/TR/prov-dm/\">http://www.w3.org/TR/prov-dm/</a>",
+
         "PROV-O":
           "S. Sahoo; D. McGuinness. "+
           "<a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html\"><cite>PROV Ontology Model</cite></a>. "+
           "2011, Work in progress. "+
           "URL: <a href=\"http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html/\">http://dvcs.w3.org/hg/prov/raw-file/default/ontology/ProvenanceFormalModel.html</a>",
+
+        "SPARQL-SD":
+          "G. T. Williams. "+
+          "<a href=\"http://www.w3.org/TR/sparql11-service-description/\"><cite>SPARQL 1.1 Service Description</cite></a>. "+
+          "2011, Work in progress. "+
+          "URL: <a href=\"http://www.w3.org/TR/sparql11-service-description/\">http://www.w3.org/TR/sparql11-service-description/</a>",
+
       };
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -557,7 +573,7 @@
 
     </section>
  
-<!-- ===================================================================================== -->
+<!-- == Sect 5 =================================================================================== -->
     
     <section>
       <h2>Querying provenance information</h2>
@@ -576,6 +592,9 @@
       <p>
         The details of a provenance query service is an implementation choice, but for interoperability between different providers and users we recommend use of SPARQL [[RDF-SPARQL-PROTOCOL]] [[RDF-SPARQL-QUERY]].  The query service URI would then be the URI of a SPARQL endpoint  (or, to use the SPARQL specification language, a <a href="http://www.w3.org/TR/rdf-sparql-protocol/#conformant-sparql-protocol-service">SPARQL protocol service</a>).  The following subsections provide examples for what are considered to be some plausible common scenarios for using SPARQL, and are not intended to cover all possibilities.
       </p>
+      <p>
+        A SPARQL protocol service description may be published using the <cite>SPARQL 1.1 Service Description</cite> vocabulary [[SPARQL-SD]].
+      </p>
 
       <section>
         <h2>Find provenance-URI given entity-URI of resource</h2>