--- a/spec/identity-respec.html	Fri Jun 14 10:10:38 2013 +0200
+++ b/spec/identity-respec.html	Fri Jun 14 11:11:28 2013 +0200
@@ -53,16 +53,11 @@
 span.element { color: green; }
 </style>
 
-    <script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove'></script>
-<!--    <script src='/ReSpec.js/js/respec.js' class='remove'></script> -->
+    <script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script>
     <script class='remove'>
       var preProc = {
           apply:  function(c) {
                     // extend the bibliography entries
-                    berjon.biblio["SWBP-VOCAB-PU"] = "Diego Berrueta, Jon Phipps <a href='http://www.w3.org/TR/swbp-vocab-pub/'><cite>Best Practice Recipes for Publishing RDF Vocabularies</cite></a> W3C Working Group Note 28 August 2008";
-                    berjon.biblio["TURTLE-TR"] =  "David Beckett, Tim Berners-Lee. <a href='http://www.w3.org/TR/turtle/'><cite>Turtle: Terse RDF Triple Language.</cite></a> W3C Working Draft 09 August 2011 URL: <a href='http://www.w3.org/TR/turtle/'>http://www.w3.org/TR/turtle/</a> ";
-                    berjon.biblio["FOAF"] =  "Dan Brickley, Libby Miller. <a href='http://xmlns.com/foaf/0.1/'><cite>FOAF: Vocabulary Specification 0.98.</cite></a>";
-                    berjon.biblio["RDF-XML"] = "Beckett D. (Editor), W3C Recommendation, 10 February 2004. <a href='http://www.w3.org/TR/rdf-syntax-grammar/'><cite>RDF/XML Syntax Specification (Revised)</cite></a>";
                     // process the document before anything else is done
                     var refs = document.querySelectorAll('adef') ;
                     for (var i = 0; i < refs.length; i++) {
@@ -316,7 +311,7 @@
     <p>There are a number of concepts that are covered in this document that the
     reader may want to be aware of before continuing. General knowledge of RDF 
     [[!RDF-PRIMER]] is necessary to understand how to implement this specification. 
-    WebID uses a number of specific technologies like Turtle [[!TURTLE-TR]] and RDFa 
+    WebID uses a number of specific technologies like Turtle [[!turtle]] and RDFa
     [[!RDFA-CORE]].</p>
 
     <p>A general <a href="#introduction">Introduction</a> is provided for all that
@@ -354,7 +349,7 @@
 <p>
 A WebID is an HTTP URI which refers to an Agent (Person, Organization, Group, Device, etc.). A description of the WebID can be found in the <tref>Profile Document</tref>, a type of web page that any Social Network user is familiar with.</p>
 <p>
-A WebID <tref>Profile Document</tref> is a Web resource that MUST be available as <code>text/turtle</code> [[!TURTLE-TR]], but MAY be available in other RDF serialization formats (e.g. [[!RDFA-CORE]]) if requested through content negotiation. 
+A WebID <tref>Profile Document</tref> is a Web resource that MUST be available as <code>text/turtle</code> [[!turtle]], but MAY be available in other RDF serialization formats (e.g. [[!RDFA-CORE]]) if requested through content negotiation.
 </p>
 <p>
 WebIDs can be used to build a Web of trust using vocabularies such as FOAF [[!FOAF]] by allowing people to link together their profiles in a public or protected manner. 
@@ -392,7 +387,7 @@
 
 <dt><tdef>WebID Profile</tdef> or <tdef>Profile Document</tdef></dt>
 <dd>
-A WebID Profile is an RDF document which uniquely describes the Agent denoted by the WebID in relation to that WebID. The server MUST provide a <code>text/turtle</code> [[!TURTLE-TR]] representation of the requested profile. This document MAY be available in other RDF serialization formats, such as RDFa [[!RDFA-CORE]], or [[!RDF-XML]] if so requested through content negotiation.
+A WebID Profile is an RDF document which uniquely describes the Agent denoted by the WebID in relation to that WebID. The server MUST provide a <code>text/turtle</code> [[!turtle]] representation of the requested profile. This document MAY be available in other RDF serialization formats, such as RDFa [[!RDFA-CORE]], or [[!RDF-SYNTAX-GRAMMAR]] if so requested through content negotiation.
 </dd>
 </dl>
 
@@ -482,7 +477,7 @@
 
 <section class='informative'>
 <h1>Publishing a WebID Profile using Turtle</h1>
-<p>A widely used format for writing RDF graphs by hand is the <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[!TURTLE-TR]] notation.
+<p>A widely used format for writing RDF graphs by hand is the <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[!turtle]] notation.
     It is easy to learn, and very handy for communicating over e-mail and on mailing lists.
     The syntax is very similar to the <a href="http://www.w3.org/TR/rdf-sparql-query/">SPARQL</a> query language.
     Turtle profile documents should be served with the <code>text/turtle</code> content type.
@@ -590,7 +585,7 @@
 <h2>Processing the WebID Profile</h2>
 
 <p>The <tref>Requesting Agent</tref> needs to fetch the document, if it does not have a valid one in cache.  
-The Agent requesting the WebID document MUST be able to parse documents in Turtle [[!TURTLE-TR]], but MAY also be able to parse documents in RDF/XML [[!RDF-SYNTAX-GRAMMAR]] and RDFa [[!RDFA-CORE]].
+The Agent requesting the WebID document MUST be able to parse documents in Turtle [[!turtle]], but MAY also be able to parse documents in RDF/XML [[!RDF-SYNTAX-GRAMMAR]] and RDFa [[!RDFA-CORE]].
 The result of this processing should be a graph of RDF relations that is queryable, as explained in the next section.</p>
 <p class="note">
 It is recommended that the <tref>Requesting Agent</tref>  set the HTTP <code>Accept-Header</code>'s  <code>text/turtle</code> qvalue with a higher priority than <code>application/xhtml+xml</code> or <code>text/html</code>, as sites may produce HTML without RDFa markup but with a link to graph encoded in a pure RDF format such as Turtle. 

--- a/spec/tls-respec.html	Fri Jun 14 10:10:38 2013 +0200
+++ b/spec/tls-respec.html	Fri Jun 14 11:11:28 2013 +0200
@@ -40,19 +40,13 @@
 span.element { color: green; }
 </style>
 
-    <script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove'></script>
-<!--    <script src='/ReSpec.js/js/respec.js' class='remove'></script> -->
+    <script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script>
     <script class='remove'>
       var preProc = {
           apply:  function(c) {
                     // extend the bibliography entries
-                    berjon.biblio["RFC5246"] = "T. Dierks; E. Rescorla. <a href=\"http://tools.ietf.org/html/rfc5246\"><cite>The Transport Layer Security (TLS) Protocol Version 1.2</cite></a> August 2008. Internet RFC 5246. URL: <a href=\"http://tools.ietf.org/html/rfc5246\">http://tools.ietf.org/html/rfc5246</a> ";
-                    berjon.biblio["RFC5746"] = "E. Rescorla, M. Ray, S. Dispensa, N. Oskov,  <a href=\"http://tools.ietf.org/html/rfc5746\"><cite>Transport Layer Security (TLS) Renegotiation Indication Extension</cite></a> February 2010. Internet RFC 5246. URL: <a href=\"http://tools.ietf.org/html/rfc5746\">http://tools.ietf.org/html/rfc5746</a> ";
-                    berjon.biblio["SWBP-VOCAB-PU"] = "Diego Berrueta, Jon Phipps <a href='http://www.w3.org/TR/swbp-vocab-pub/'><cite>Best Practice Recipes for Publishing RDF Vocabularies</cite></a> W3C Working Group Note 28 August 2008";
-                    berjon.biblio["TURTLE-TR"] =  "David Beckett, Tim Berners-Lee. <a href='http://www.w3.org/TR/turtle/'><cite>Turtle: Terse RDF Triple Language.</cite></a> W3C Working Draft 09 August 2011 URL: <a href='http://www.w3.org/TR/turtle/'>http://www.w3.org/TR/turtle/</a>";
-                    berjon.biblio["FOAF"] =  "Dan Brickley, Libby Miller. <a href='http://xmlns.com/foaf/0.1/'><cite>FOAF: Vocabulary Specification 0.98.</cite></a>";
-                    berjon.biblio["RDF-XML"] = "Beckett D. (Editor), W3C Recommendation, 10 February 2004. <a href='http://www.w3.org/TR/rdf-syntax-grammar/'><cite>RDF/XML Syntax Specification (Revised)</cite></a>";
-                    berjon.biblio["WEBID"] =  "Andrei Sambra, Stéphane Corlosquet. <a href='https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html'><cite>WebID 1.0: Web Identity and Discovery.</cite></a>";
+//                    berjon.biblio["RFC5746"] = "E. Rescorla, M. Ray, S. Dispensa, N. Oskov,  <a href=\"http://tools.ietf.org/html/rfc5746\"><cite>Transport Layer Security (TLS) Renegotiation Indication Extension</cite></a> February 2010. Internet RFC 5246. URL: <a href=\"http://tools.ietf.org/html/rfc5746\">http://tools.ietf.org/html/rfc5746</a> ";
+//                    berjon.biblio["WEBID"] =  "Andrei Sambra, Stéphane Corlosquet. <a href='https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html'><cite>WebID 1.0: Web Identity and Discovery.</cite></a>";
 
                     // process the document before anything else is done
                     var refs = document.querySelectorAll('adef') ;
@@ -306,7 +300,7 @@
 and RDF [[!RDF-PRIMER]] is necessary to understand how
 to implement this specification. <tref>WebID</tref> uses a number of specific technologies
 like HTTP over TLS [[!HTTP-TLS]], X.509 certificates [[!X509V3]],
-Turtle [[!TURTLE-TR]] and RDFa [[!RDFA-CORE]].</p>
+Turtle [[!turtle]] and RDFa [[!RDFA-CORE]].</p>
 
 <p>A general <a href="#introduction">Introduction</a> is provided for all that
 would like to understand why this specification is necessary to simplify usage
@@ -380,8 +374,8 @@
 <dt><tdef>WebID Profile</tdef> or <tdef>Profile Document</tdef></dt>
 <dd>
 A WebID Profile is an RDF document which MUST uniquely describe the Agent denoted by the WebID in relation to that WebID. 
-This document MUST be available as Turtle [[!TURTLE-TR]]. 
-This document MAY be available in other RDF serialization formats, such as RDFa [[!RDFA-CORE] or RDF/XML [[!RDF-XML]] if so requested through content negotiation.
+This document MUST be available as Turtle [[!turtle]].
+This document MAY be available in other RDF serialization formats, such as RDFa [[!RDFA-CORE] or RDF/XML [[!RDF-SYNTAX-GRAMMAR]] if so requested through content negotiation.
 
 Any other serializations MUST be transformable automatically and in a standard manner to an RDF Graph, using technologies such as GRDDL [[!GRDDL-PRIMER]]. Refer to [[!WEBID]] for the normative definition.
 </dd>
@@ -417,7 +411,7 @@
 <dt><tdef>TLS Service</tdef></dt>
 <dd>A TLS Service is a transport level service listening on the <tref>Service</tref> port. 
 It secures the transport layer before passing messages to the Application layer <tref>Service</tref> itself.
-The TLS protocol [[!RFC5246]] is applied to incoming connections: it identifies the server to the client, securing the channel and is able to request authentication credentials from the <tref>Client</tref> if needed. 
+The TLS protocol [[!TLS]] is applied to incoming connections: it identifies the server to the client, securing the channel and is able to request authentication credentials from the <tref>Client</tref> if needed.
 Server Credentials and Client credentials traditionally take the form of X.509 Certificates containing a public key. 
 The TLS protocol enables the TLS Service to verify that the <tref>Client</tref> controls the private key of the <tref>Public Key</tref> published in the certificate.
 Trust decisions on other attributes of the <tref>Subject</tref> published in the Certificate - such as his name - are traditionally based on the trust in the Agent that signed the Certificate - known as a <tref>Certificate Authority</tref>.
@@ -458,7 +452,7 @@
 
 <dt><tdef>Verification Agent</tdef> or <tdef>WebID Verifier</tdef></dt>
 <dd>A WebID Verifier takes a <tref>WebID Claim</tref> and checks that it is currently true, as explained in <a href="#verifying-the-webids">Verifying the WebIDs</a> section. 
-A WebID Verification Agent MUST be able to parse documents in TURTLE [[!TURTLE-TR]], RDF/XML [[!RDF-SYNTAX-GRAMMAR]] and RDFa [[!RDFA-CORE]].
+A WebID Verification Agent MUST be able to parse documents in TURTLE [[!turtle]], RDF/XML [[!RDF-SYNTAX-GRAMMAR]] and RDFa [[!RDFA-CORE]].
 </dd>
 
 <dt><tdef>WebID Certificate</tdef></dt>
@@ -666,7 +660,7 @@
 </section>
 <section class='informative'>
 <h1>Turtle</h1>
-<p>A widely used format for writing RDF graphs by hand is the <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[!TURTLE-TR]] notation.
+<p>A widely used format for writing RDF graphs by hand is the <a href="http://www.w3.org/TR/turtle/">Turtle</a> [[!turtle]] notation.
     It is easy to learn, and very handy for communicating over e-mail and on mailing lists.
     The syntax is very similar to the SPARQL query language.
     Turtle should be served with the <code>text/turtle</code> mime type.
@@ -720,7 +714,7 @@
 <img width="90%" src="img/WebIDSequence-friendly.jpg">
 <p>The steps in detail are as follows:</p>
 <ol>
-    <li><tref>Bob</tref>'s <tref>Client</tref> MUST open a TLS [[!RFC5246]] connection with the server which authenticates itself using well known TLS mechanisms.
+    <li><tref>Bob</tref>'s <tref>Client</tref> MUST open a TLS [[!TLS]] connection with the server which authenticates itself using well known TLS mechanisms.
         This MAY be done as the first part of an HTTPS connection [[!HTTP-TLS]].
     </li>
     <li>Once the Transport Layer Security [TLS] has been set up, the application protocol exchange can start.
@@ -816,7 +810,7 @@
 <section class='normative'>
 <h2>Requesting the Client Certificate</h2>
 
-<p>TLS allows the server to request a Certificate from the Client using the <code>CertificateRequest</code> message [Section 7.4.4] of TLS v1.1 [[!RFC5246]].  Since WebID TLS authentication does not rely on CAs signing the certificate to verify the <tref>WebID Claim</tref>s made therein, the Server does not need to restrict the certificate it receives by the CAs they were signed by. It can therefore leave the  <code>certificate_authorities</code> field blank in the request. </p>
+<p>TLS allows the server to request a Certificate from the Client using the <code>CertificateRequest</code> message [Section 7.4.4] of TLS v1.1 [[!TLS]].  Since WebID TLS authentication does not rely on CAs signing the certificate to verify the <tref>WebID Claim</tref>s made therein, the Server does not need to restrict the certificate it receives by the CAs they were signed by. It can therefore leave the  <code>certificate_authorities</code> field blank in the request. </p>
 <p class="note">From our experience leaving the certificate_authorities field empty leads to the correct behavior on all browsers and all TLS versions.</p>
 <p class="note">A security issue with TLS renegotiation was discovered in 2009, and an IETF fix was proposed in [[!RFC5746]] which is widely implemented.</p>
 <p>If the Client does not send a certificate, because either it does not have one or it does not wish to send one, other authentication procedures can be pursued at the application layer with protocols such as OpenID, OAuth, BrowserID, etc... </p>
@@ -849,7 +843,7 @@
 <h2>Processing the WebID Profile</h2>
 
 <p>The Verification Agent needs to fetch the document, if it does not have a valid one in cache.  
-The WebID <tref>Verification Agent</tref> MUST be able to parse documents in TURTLE [[!TURTLE-TR]], and MAY be able to also parse them in RDFa [[!RDFA-CORE]] and RDF/XML [[!RDF-SYNTAX-GRAMMAR]].
+The WebID <tref>Verification Agent</tref> MUST be able to parse documents in TURTLE [[!turtle]], and MAY be able to also parse them in RDFa [[!RDFA-CORE]] and RDF/XML [[!RDF-SYNTAX-GRAMMAR]].
 The result of this processing should be a graph of RDF relations that is queryable, as explained in the next section.</p>
 <p class="note">
 The <tref>Verification Agent</tref> MUST set the Accept-Header to request <code>text/turtle</code> with a higher priority than <code>text/html</code> and <code>application/rdf+xml</code>.  The reason is that it is quite likely that many sites will produce non marked up HTML and leave the graph to the pure RDF formats.