Make sure references are up to date
authorMarkus Lanthaler <mark_lanthaler@gmx.net>
Wed, 27 Mar 2013 12:50:46 +0100
changeset 1482 a081bb1f9860
parent 1481 ee65df518a5c
child 1483 5e373674a84f
Make sure references are up to date

I didn't update the JSON-LD* references yet, i.e., they still use json-ld.org.

This addresses #224.
spec/latest/json-ld-api/index.html
spec/latest/json-ld-syntax/index.html
spec/latest/respec-w3c-extensions.js
--- a/spec/latest/json-ld-api/index.html	Wed Mar 27 11:49:46 2013 +0100
+++ b/spec/latest/json-ld-api/index.html	Wed Mar 27 12:50:46 2013 +0100
@@ -192,7 +192,7 @@
     intended to operate in a programming environment, it is useful to have working
     knowledge of the JavaScript programming language [[ECMA-262]] and
     WebIDL [[!WEBIDL]]. To understand how JSON-LD maps to RDF, it is helpful to be
-    familiar with the basic RDF concepts [[!RDF-CONCEPTS]].</p>
+    familiar with the basic RDF concepts [[RDF11-CONCEPTS]].</p>
 </section> <!-- end of Introduction -->
 
 
@@ -510,10 +510,10 @@
     <h2>RDF Conversion</h2>
 
     <p>JSON-LD can be used to serialize data expressed in RDF as described in
-      [[RDF-CONCEPTS]]. This ensures that data can be round-tripped to and from
+      [[RDF11-CONCEPTS]]. This ensures that data can be round-tripped to and from
       any RDF syntax without any loss in fidelity.</p>
 
-    <p>For example, assume the following RDF input serialized in Turtle [[TURTLE-TR]]:</p>
+    <p>For example, assume the following RDF input serialized in Turtle [[TURTLE]]:</p>
 
     <pre class="example" data-transform="updateExample"
          title="Sample Turtle document">
@@ -760,19 +760,19 @@
       or <tref>false</tref>.</dd>
     <dt><tdef>RDF subject</tdef></dt>
     <dd>A <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-subject">subject</tref>
-      as specified by [[RDF-CONCEPTS]].</dd>
+      as specified by [[RDF11-CONCEPTS]].</dd>
     <dt><tdef>RDF predicate</tdef></dt>
     <dd>A <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-predicate">predicate</tref>
-      as specified by [[RDF-CONCEPTS]].</dd>
+      as specified by [[RDF11-CONCEPTS]].</dd>
     <dt><tdef>RDF object</tdef></dt>
     <dd>An <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-object">object</tref>
-      as specified by [[RDF-CONCEPTS]].</dd>
+      as specified by [[RDF11-CONCEPTS]].</dd>
     <dt><tdef>RDF triple</tdef></dt>
     <dd>A <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-triple">triple</tref>
-      as specified by [[RDF-CONCEPTS]].</dd>
+      as specified by [[RDF11-CONCEPTS]].</dd>
     <dt><tdef>RDF dataset</tdef></dt>
     <dd>A <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-dataset">dataset</tref>
-      as specified by [[RDF-CONCEPTS]] representing a collection of
+      as specified by [[RDF11-CONCEPTS]] representing a collection of
       <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-graph">RDF graphs</tref>.</dd>
   </dl>
 </section> <!-- end of Algorithm Terms section -->
--- a/spec/latest/json-ld-syntax/index.html	Wed Mar 27 11:49:46 2013 +0100
+++ b/spec/latest/json-ld-syntax/index.html	Wed Mar 27 12:50:46 2013 +0100
@@ -190,7 +190,7 @@
   </ul>
 
   <p>Developers that require any of the facilities listed above or need to serialize
-    an RDF graph or dataset [[RDF-CONCEPTS]] in a JSON-based syntax will find
+    an RDF graph or dataset [[RDF11-CONCEPTS]] in a JSON-based syntax will find
     JSON-LD of interest. The syntax is designed to not disturb already deployed
     systems running on JSON, but provide a smooth upgrade path from JSON to
     JSON-LD. Since the shape of such data varies wildly, JSON-LD features mechanisms
@@ -2650,7 +2650,7 @@
     The embedded JSON-LD document might be extracted as is or, e.g., be converted
     to RDF.</p>
 
-  <p>If JSON-LD content is extracted as RDF [[RDF-CONCEPTS]], it should be expanded into an
+  <p>If JSON-LD content is extracted as RDF [[RDF11-CONCEPTS]], it should be expanded into an
     <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-dataset">RDF dataset</tref> using the
     <cite><a href="../json-ld-api/#convert-to-rdf-algorithm">Convert to RDF Algorithm</a></cite>
     [[JSON-LD-API]]. If multiple embedded JSON-LD documents are extracted as RDF,
@@ -2714,7 +2714,7 @@
   </ul>
 
   <p class="issue atrisk" data-number="217">In contrast to the RDF data model as defined in
-    [[RDF-CONCEPTS]], JSON-LD allows blank nodes as property labels and graph names. Thus,
+    [[RDF11-CONCEPTS]], JSON-LD allows blank nodes as property labels and graph names. Thus,
     some data that is valid JSON-LD cannot be converted to RDF. This feature may be removed
     in the future.</p>
 
@@ -3092,7 +3092,7 @@
 <section class="appendix normative">
   <h2>Relationship to RDF</h2>
 
-  <p>The RDF data model, as outlined in [[RDF-CONCEPTS]], is an abstract syntax for
+  <p>The RDF data model, as outlined in [[RDF11-CONCEPTS]], is an abstract syntax for
     representing a directed graph of information. It is a subset of
     <tref title="JSON-LD data model">JSON-LD's data model</tref> with a few
     additional constraints. The differences between the two data models are:</p>
@@ -3246,7 +3246,7 @@
   <section class="informative">
     <h3>Turtle</h3>
 
-    <p>The following are examples of converting RDF expressed in Turtle [[TURTLE-TR]]
+    <p>The following are examples of converting RDF expressed in Turtle [[TURTLE]]
       into JSON-LD.</p>
 
     <section>
@@ -3600,7 +3600,7 @@
             parameter MAY also be used by clients to express their preferences in the
             content negotiation process. It is RECOMMENDED that profile IRIs are
             dereferenceable and provide useful documentation at that IRI. For more
-            information and background please refer to [[PROFILE-LINK]].</p>
+            information and background please refer to [[RFC6906]].</p>
           <p>This specification defines four values for the <code>profile</code> parameter.
             To request or specify Expanded JSON-LD document form, the IRI
             <code>http://www.w3.org/ns/json-ld#expanded</code> SHOULD be used.
@@ -3669,7 +3669,7 @@
   <p>Fragment identifiers used with <a href="#application-ld-json">application/ld+json</a>
     are treated as in RDF syntaxes, as per
     <cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-fragID">RDF 1.1 Concepts and Abstract Syntax</a></cite>
-    [[RDF-CONCEPTS]].</p>
+    [[RDF11-CONCEPTS]].</p>
 </section>
 
 <section class="appendix informative">
--- a/spec/latest/respec-w3c-extensions.js	Wed Mar 27 11:49:46 2013 +0100
+++ b/spec/latest/respec-w3c-extensions.js	Wed Mar 27 12:50:46 2013 +0100
@@ -3,12 +3,13 @@
     "JSON-LD": "Manu Sporny, Gregg Kellogg, Markus Lanthaler, Editors. <cite><a href=\"http://json-ld.org/spec/latest/json-ld-syntax/\">JSON-LD 1.0</a>.</cite> W3C Editor's Draft (work in progress). URL: <a href=\"http://json-ld.org/spec/latest/json-ld-syntax/\">http://json-ld.org/spec/latest/json-ld-syntax/</a>",
     "JSON-LD-API": "Markus Lanthaler, Gregg Kellogg, Manu Sporny, Editors. <cite><a href=\"http://json-ld.org/spec/latest/json-ld-api/\">JSON-LD 1.0 Processing Algorithms and API</a>.</cite> W3C Editor's Draft (work in progress). URL: <a href=\"http://json-ld.org/spec/latest/json-ld-api/\">http://json-ld.org/spec/latest/json-ld-api/</a>",
     "JSON-LD-TESTS": "<cite><a href=\"http://dvcs.w3.org/hg/json-ld/raw-file/default/test-suite/\">JSON-LD Test Suite</a></cite> (work in progress).",
-    "IEEE-754-1985": "IEEE. <cite>IEEE Standard for Binary Floating-Point Arithmetic.</cite> See <a href=\"http://standards.ieee.org/reading/ieee/std_public/description/busarch/754-1985_desc.html\">http://standards.ieee.org/reading/ieee/std_public/description/busarch/754-1985_desc.html</a>",
-    "RFC5988": "M. Nottingham. <cite><a href=\"http://tools.ietf.org/rfc/rfc5988\">Web Linking</a>.</cite> October 2010. Internet RFC 5988. URL: <a href=\"http://tools.ietf.org/rfc/rfc5988.txt\">http://tools.ietf.org/rfc/rfc5988.txt</a>",
-    "RDF-CONCEPTS": "Richard Cyganiak, David Wood, Editors. <cite><a href=\"http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/\">RDF 1.1 Concepts and Abstract Syntax.</a></cite> 15 January 2013. W3C Working Draft (work in progress). URL: <a href=\"http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/\">http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/</a>",
-    "TURTLE-TR": "Eric Prud'hommeaux, Gavin Carothers, Editors. <cite><a href=\"http://www.w3.org/TR/2011/WD-turtle-20110809/\">Turtle: Terse RDF Triple Language.</a></cite> 09 August 2011. W3C Working Draft (work in progress). URL: <a href=\"http://www.w3.org/TR/2011/WD-turtle-20110809/\">http://www.w3.org/TR/2011/WD-turtle-20110809/</a>",
-    "MICRODATA": "Ian Hickson, Editor. <cite><a href=\"http://www.w3.org/TR/2012/WD-microdata-20120329/\">HTML Microdata</a>.</cite> 29 March 2012. W3C Working Draft (work in progress). URL: <a href=\"http://www.w3.org/TR/2012/WD-microdata-20120329/\">http://www.w3.org/TR/2012/WD-microdata-20120329/</a>",
-    "PROFILE-LINK": "Erik Wilde. <cite><a href=\"http://tools.ietf.org/html/draft-wilde-profile-link\">The 'profile' Link Relation Type</a>.</cite> 17 October 2012. IETF Internet Draft (work in progress). URL: <a href=\"http://tools.ietf.org/html/draft-wilde-profile-link\">http://tools.ietf.org/html/draft-wilde-profile-link</a>"
+    "IEEE-754-1985": "IEEE. <cite>IEEE Standard for Binary Floating-Point Arithmetic.</cite> URL: <a href=\"http://standards.ieee.org/reading/ieee/std_public/description/busarch/754-1985_desc.html\">http://standards.ieee.org/reading/ieee/std_public/description/busarch/754-1985_desc.html</a>",
+    "RDF11-CONCEPTS": "Richard Cyganiak, David Wood, Editors. <cite><a href=\"http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/\">RDF 1.1 Concepts and Abstract Syntax.</a></cite> 15 January 2013. W3C Working Draft (work in progress). URL: <a href=\"http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/\">http://www.w3.org/TR/2013/WD-rdf11-concepts-20130115/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/rdf11-concepts/\">http://www.w3.org/TR/rdf11-concepts/</a>",
+    "MICRODATA": "Ian Hickson, Editor. <cite><a href=\"http://www.w3.org/TR/2012/WD-microdata-20121025/\">HTML Microdata</a>.</cite> 25 October 2012. W3C Working Draft (work in progress). URL: <a href=\"http://www.w3.org/TR/2012/WD-microdata-20121025/\">http://www.w3.org/TR/2012/WD-microdata-20121025/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/microdata/\">http://www.w3.org/TR/microdata/</a>",
+    "RFC5988": "M. Nottingham. <cite><a href=\"http://www.ietf.org/rfc/rfc5988.txt\">Web Linking</a>.</cite> October 2010. Internet RFC 5988. URL: <a href=\"http://www.ietf.org/rfc/rfc5988.txt\">http://www.ietf.org/rfc/rfc5988.txt</a>",
+    "RFC6906": "Erik Wilde. <cite><a href=\"http://www.ietf.org/rfc/rfc6906.txt\">The 'profile' Link Relation Type</a>.</cite> March 2013. Internet RFC 6906. URL: <a href=\"http://www.ietf.org/rfc/rfc6906.txt\">http://www.ietf.org/rfc/rfc6906.txt</a>",
+    "TURTLE": "Eric Prud'hommeaux, Gavin Carothers, Editors. <cite><a href=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\">Turtle: Terse RDF Triple Language.</a></cite> 19 February 2013. W3C Candidate Recommendation (work in progress). URL: <a href=\"http://www.w3.org/TR/2013/CR-turtle-20130219/\">http://www.w3.org/TR/2013/CR-turtle-20130219/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/turtle/\">http://www.w3.org/TR/turtle/</a>",
+    "WEBIDL": "Cameron McCormack, Editor. <cite><a href=\"http://www.w3.org/TR/2012/CR-WebIDL-20120419/\">Web IDL.</a></cite> 19 April 2012. W3C Candidate Recommendation (work in progress). URL: <a href=\"http://www.w3.org/TR/2012/CR-WebIDL-20120419/\">http://www.w3.org/TR/2012/CR-WebIDL-20120419/</a>. The latest edition is available at <a href=\"http://www.w3.org/TR/WebIDL/\">http://www.w3.org/TR/WebIDL/</a>"
 };
 
 var preProc = {