wording changes
authorHenry Story <henry.story@bblfish.net>
Thu, 09 May 2013 10:02:58 +0200
changeset 373 0f277c03b3bd
parent 372 2e8047f3d290
child 374 c776d5856868
wording changes
--- a/spec/identity-respec.html	Fri Apr 19 16:40:25 2013 +0200
+++ b/spec/identity-respec.html	Thu May 09 10:02:58 2013 +0200
@@ -62,7 +62,7 @@
                     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["RFC5988"] = "M. Nottingham. <a href=\"http://tools.ietf.org/html/rfc5988\"><cite>Web Linking</cite></a> October 2010. Internet RFC 5988. URL: <a href=\"http://tools.ietf.org/html/rfc5988\">http://tools.ietf.org/html/rfc5988</a> ";
                     // process the document before anything else is done
                     var refs = document.querySelectorAll('adef') ;
                     for (var i = 0; i < refs.length; i++) {
@@ -521,11 +521,11 @@
-<p>If a WebID provider would rather prefer not to mark up his WebID profile in HTML+RDFa, but
+<p>If a WebID provider would prefer not to mark up his WebID profile in HTML+RDFa, but
 just provide a human readable format for users in plain HTML and have the RDF graph appear
-in a machine readable format such as Turtle, then a link from
-the HTML to a machine readable format MAY be published
-as follows:</p>
+in a machine readable format such as Turtle, then he SHOULD provide a link of type <code>alternate</code>
+to a machine readable format [[!RFC5988]]. This can be placed in the HTTP header or in the
+html as shown here:</p>
 <pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">