Update spec references.

Fixes #50.

Author: gkellogg

common/algorithm-terms.html

@@ -49,8 +49,8 @@
     copied into a new <a>processor state</a> when entering a new
     <a>JSON object</a>.</dd>
   <dt><dfn data-lt="promises">promise</dfn></dt><dd>
-    A <a data-cite="ECMASCRIPT-6.0#sec-promise-objects" class="externalDFN">promise</a> is an object that represents the eventual result of a single asynchronous operation.
-    Promises are defined in [[ECMASCRIPT-6.0]].</dd>
+    A <a data-cite="ECMASCRIPT#sec-promise-objects" class="externalDFN">promise</a> is an object that represents the eventual result of a single asynchronous operation.
+    Promises are defined in [[ECMASCRIPT]].</dd>
   <dt><dfn>require all flag</dfn></dt><dd>
     A flag specifying that all properties present in the <a>input frame</a>
     MUST either have a default value or be present in the <a>JSON-LD

common/terms.html

@@ -10,19 +10,19 @@
     <a data-cite="JSON-LD11#sets-and-lists" class="externalDFN">Sets and Lists</a> in
     the JSON-LD Syntax specification [[JSON-LD11]]).</dd>
   <dt><dfn data-lt="JSON objects">JSON object</dfn></dt><dd>
-    In the JSON serialization, an <a data-cite="RFC7159#section-4" class="externalDFN">object</a> structure is represented as a pair of curly brackets surrounding zero or
+    In the JSON serialization, an <a data-cite="RFC8259#section-4" class="externalDFN">object</a> structure is represented as a pair of curly brackets surrounding zero or
     more key-value pairs. A key is a <a>string</a>. A single colon comes after
     each key, separating the key from the value. A single comma separates a value
     from a following key. In JSON-LD the keys in an object MUST be unique.
     In the <a>internal representation</a> a <a>JSON object</a> is equivalent to a
-    <dfn data-cite="WEBIDL#dfn-dictionary" data-lt="dictionaries" class="preserve">dictionary</dfn> (see [[WEBIDL]]).</dd>
+    <dfn data-cite="WEBIDL#dfn-dictionary" data-lt="dictionaries" class="preserve">dictionary</dfn> (see [[!WEBIDL]]).</dd>
   <dt class="changed"><dfn data-lt="internal representation">JSON-LD internal representation</dfn></dt><dd class="changed">The JSON-LD
     internal representation is the result of transforming a JSON syntactic structure
     into the core data structures suitable for direct processing:
     <a>arrays</a>, <a>dictionaries</a>,
     <a>strings</a>, <a>numbers</a>, <a>booleans</a>, and <a>null</a>.</dd>
   <dt><dfn>null</dfn></dt><dd>
-    The use of the <a data-cite="RFC7159#section-3" class="externalDFN">null</a> value within JSON-LD is used to
+    The use of the <a data-cite="RFC8259#section-3" class="externalDFN">null</a> value within JSON-LD is used to
     ignore or reset values. A key-value pair in the <code>@context</code> where
     the value, or the <code>@id</code> of the value, is <code>null</code>
     explicitly decouples a term's association with an IRI. A key-value pair in
@@ -32,22 +32,22 @@
     <code>null</code> in expanded form, then the entire <a>JSON
     object</a> is ignored.</dd>
   <dt><dfn data-lt="numbers|JSON number|JSON numbers">number</dfn></dt><dd>
-    In the JSON serialization, a <a data-cite="RFC7159#section-6" class="externalDFN">number</a> is similar to that used in most programming languages, except
+    In the JSON serialization, a <a data-cite="RFC8259#section-6" class="externalDFN">number</a> is similar to that used in most programming languages, except
     that the octal and hexadecimal formats are not used and that leading
     zeros are not allowed.
     In the <a>internal representation</a>, a <a>number</a> is equivalent to either
     a <dfn data-cite="WEBIDL#idl-long" class="preserve">long</dfn>
     or <dfn data-cite="WEBIDL#idl-double" class="preserve">double</dfn>, depending
-    on if the number has a non-zero fractional part (see [[WEBIDL]]).</dd>
+    on if the number has a non-zero fractional part (see [[!WEBIDL]]).</dd>
   <dt><dfn>scalar</dfn></dt><dd>
     A scalar is either a JSON <a>string</a>, <a>number</a>, <a>true</a>,
     or <a>false</a>.</dd>
   <dt><dfn data-lt="strings">string</dfn></dt><dd>
-    A <a data-cite="RFC7159#section-7" class="externalDFN">string</a> is a sequence of zero or more Unicode (UTF-8) characters,
+    A <a data-cite="RFC8259#section-7" class="externalDFN">string</a> is a sequence of zero or more Unicode (UTF-8) characters,
     wrapped in double quotes, using backslash escapes (if necessary). A
     character is represented as a single character string.</dd>
   <dt><dfn>true</dfn> and <dfn>false</dfn></dt><dd>
-    <a data-cite="RFC7159#section-3" class="externalDFN">Values</a> that are used to express one of two possible
+    <a data-cite="RFC8259#section-3" class="externalDFN">Values</a> that are used to express one of two possible
     <dfn data-cite="WEBIDL#idl-boolean" data-lt="booleans" class="preserve">boolean</dfn> states.</dd>
 </dl>
 
@@ -182,12 +182,12 @@
     section of the JSON-LD specification [[JSON-LD11]].
     A <a>linked data graph</a> is a generalized representation of an
     <a data-cite="RDF11-CONCEPTS#dfn-rdf-graph">RDF graph</a>
-    as defined in [[!RDF-CONCEPTS]].</dd>
+    as defined in [[!RDF11-CONCEPTS]].</dd>
   <dt><dfn data-lt="lists">list</dfn></dt><dd>
     A <a>list</a> is an ordered sequence of <a>IRIs</a>,
     <a>blank nodes</a>, and <a>JSON-LD values</a>.
     See <dfn data-cite="RDF-SCHEMA#ch_collectionvocab" data-lt="collection" class="preserve">RDF collection</dfn>
-    in [[RDF-SCHEMA]].</dd>
+    in [[!RDF-SCHEMA]].</dd>
   <dt><dfn data-lt="list objects">list object</dfn></dt><dd>
     A <a>list object</a> is a <a>JSON object</a> that has an <code>@list</code>
     member.</dd>
@@ -282,7 +282,7 @@
   <dt><dfn>typed literal</dfn></dt><dd>
     A <a data-cite="RDF11-CONCEPTS#dfn-typed-literal" class="externalDFN">typed literal</a> is a <a>literal</a> with an associated <a>IRI</a>
     which indicates the literal's datatype.
-    See <dfn data-cite="RDF11-CONCEPTS#dfn-literal" data-lt="RDF literals" class="preserve">RDF literal</dfn> in [[!RDF-CONCEPTS]].</dd>
+    See <dfn data-cite="RDF11-CONCEPTS#dfn-literal" data-lt="RDF literals" class="preserve">RDF literal</dfn> in [[!RDF11-CONCEPTS]].</dd>
   <dt><dfn data-lt="typed values">typed value</dfn></dt><dd>
     A <a>typed value</a> consists of a value, which is a <a>string</a>, and a type,
     which is an <a>IRI</a>.</dd>

index.html

@@ -183,7 +183,7 @@ <h1>Introduction</h1>
    different sites across the Web.</p>
 
   <p>JSON-LD is a lightweight syntax to serialize Linked Data in
-    JSON [[!RFC7159]]. Its design allows existing JSON to be interpreted as
+    JSON [[!RFC8259]]. Its design allows existing JSON to be interpreted as
     Linked Data with minimal changes. JSON-LD is primarily intended to be a
     way to use Linked Data in Web-based programming environments, to build
     interoperable Web services, and to store Linked Data in JSON-based storage engines. Since
@@ -245,7 +245,7 @@ <h2>How to Read this Document</h2>
       providing a standard library interface for common JSON-LD operations.</p>
 
     <p>To understand the basics in this specification you must first be familiar with
-      <a data-cite="RFC7159">JSON</a>, which is detailed in [[!RFC7159]].</p>
+      <a data-cite="RFC8259">JSON</a>, which is detailed in [[!RFC8259]].</p>
 
     <p>This document almost exclusively uses the term IRI
     (<a data-cite="ld-glossary#internationalized-resource-identifier">Internationalized Resource Indicator</a>)
@@ -282,8 +282,8 @@ <h2>Contributing</h2>
   <section class="normative">
     <h2>Terminology</h2>
 
-    <p>This document uses the following terms as defined in JSON [[!RFC7159]]. Refer
-      to the <a data-cite="RFC7159#section-2">JSON Grammar section</a> in [[!RFC7159]] for formal definitions.</p>
+    <p>This document uses the following terms as defined in JSON [[!RFC8259]]. Refer
+      to the <a data-cite="RFC8259#section-2">JSON Grammar section</a> in [[!RFC8259]] for formal definitions.</p>
 
     <div data-include="common/terms.html"
          data-oninclude="restrictReferences">
@@ -370,7 +370,7 @@ <h2>Data Model Overview</h2>
       section <a href="#relationship-to-rdf"></a>.</p>
 
     <p>At the surface level, a <a>JSON-LD document</a> is simply
-      <a data-cite="RFC7159">JSON</a>, detailed in [[!RFC7159]].
+      <a data-cite="RFC8259">JSON</a>, detailed in [[!RFC8259]].
       For the purpose of describing the core data structures,
       this is limited to <a>arrays</a>, <a>dictionaries</a> (the parsed version of a <a>JSON Object</a>),
       <a>strings</a>, <a>numbers</a>, <a>booleans</a>, and <a>null</a>,
@@ -538,7 +538,7 @@ <h2>Syntax Tokens and Keywords</h2>
 <section class="informative">
   <h1>Basic Concepts</h1>
 
-  <p>JSON [[RFC7159]] is a lightweight, language-independent data interchange format.
+  <p>JSON [[RFC8259]] is a lightweight, language-independent data interchange format.
     It is easy to parse and easy to generate. However, it is difficult to integrate JSON
     from different sources as the data may contain keys that conflict with other
     data sources. Furthermore, JSON has no
@@ -687,7 +687,7 @@ <h2>The Context</h2>
       is ignored when the document is used as an external JSON-LD context document.</p>
 
     <p>JSON documents can be interpreted as JSON-LD without having to be modified by
-      referencing a <a>context</a> via an <a data-cite="RFC5988#section-5">HTTP Link Header</a>
+      referencing a <a>context</a> via an <a data-cite="RFC8288#section-3">HTTP Link Header</a>
       as described in <a class="sectionRef" href="#interpreting-json-as-json-ld"></a>. It is also
       possible to apply a custom context using the JSON-LD 1.1 API [[JSON-LD11-API]].</p>
 
@@ -2555,7 +2555,7 @@ <h3>Using the Document Base as the Default Vocabulary</h3>
 
 <p class="changed">In JSON-LD 1.1, lists of lists, where the value of
   a <a>list object</a>, may itself be a <a>list object</a>, are
-  fully supported. For example, in <em>GeoJSON</em> (see [[RFC7946]]),
+  fully supported. For example, in <a data-cite="RFC7946">GeoJSON</a> (see [[RFC7946]]),
   <em>coordinates</em> are an ordered list of <em>positions</em>, which are
   represented as an array of two or more numbers:</p>
 
@@ -4738,17 +4738,17 @@ <h3>Graph Containers</h3>
   <p>Ordinary JSON documents can be interpreted as JSON-LD
     by providing an explicit JSON-LD <a>context</a> document. One way
     to provide this is by using referencing a JSON-LD
-    <a>context</a> document in an <a data-cite="RFC5988#section-5">HTTP Link Header</a>.
+    <a>context</a> document in an <a data-cite="RFC8288#section-3">HTTP Link Header</a>.
     Doing so allows JSON to be unambiguously machine-readable without requiring developers to drastically
     change their documents and provides an upgrade path for existing infrastructure
     without breaking existing clients that rely on the <code>application/json</code>
     media type or a media type with a <code>+json</code> suffix as defined in
-    [[RFC6839]].</p>
+    [[!RFC6839]].</p>
 
   <p>In order to use an external context with an ordinary JSON document,
     when retrieving an ordinary JSON document via HTTP, processors MUST
     retrieve any <a>JSON-LD document</a> referenced by a
-    <a data-cite="RFC5988#section-5">Link Header</a> with:</p>
+    <a data-cite="RFC8288#section-3">Link Header</a> with:</p>
 
   <ul>
     <li><code>rel="http://www.w3.org/ns/json-ld#context"</code>, and</li>
@@ -4764,7 +4764,7 @@ <h3>Graph Containers</h3>
     of the <code>@context</code> subtree in the referenced document MUST be
     discarded. Effectively this means that the <a>active context</a> is
     initialized with the referenced external <a>context</a>. A response MUST NOT
-    contain more than one <a data-cite="RFC5988#section-5">HTTP Link Header</a> [[!RFC5988]] using the
+    contain more than one <a data-cite="RFC8288#section-3">HTTP Link Header</a> [[!RFC8288]] using the
     <code>http://www.w3.org/ns/json-ld#context</code> link relation.</p>
 
   <p>Other mechanisms for providing a JSON-LD Context MAY be described for other
@@ -4805,7 +4805,7 @@ <h3>Graph Containers</h3>
     served with the <code>application/ld+json</code>
     media type MUST have all context information, including references to external
     contexts, within the body of the document. Contexts linked via a
-    <code>http://www.w3.org/ns/json-ld#context</code> <a data-cite="RFC5988#section-5">HTTP Link Header</a> MUST be
+    <code>http://www.w3.org/ns/json-ld#context</code> <a data-cite="RFC8288#section-3">HTTP Link Header</a> MUST be
     ignored for such documents.</p>
 </section>
 
@@ -4851,7 +4851,7 @@ <h1>Data Model</h1>
 
   <p>JSON-LD is a serialization format for Linked Data based on JSON.
     It is therefore important to distinguish between the syntax, which is
-    defined by JSON in [[!RFC7159]], and the <dfn>data model</dfn> which is
+    defined by JSON in [[!RFC8259]], and the <dfn>data model</dfn> which is
     an extension of the <a data-cite="RDF11-CONCEPTS#data-model">RDF data model</a> [[!RDF11-CONCEPTS]]. The precise
     details of how JSON-LD relates to the RDF data model are given in
     <a class="sectionRef" href="#relationship-to-rdf"></a>.</p>
@@ -4930,7 +4930,7 @@ <h1>Data Model</h1>
     <li>A <a>list</a> is a sequence of zero or more <a>IRIs</a>,
       <a>blank nodes</a>, and <a>JSON-LD values</a>.
       <a>Lists</a> are interpreted as
-      <dfn data-cite="RDF11-MT#rdf-collections">RDF list structures</dfn> [[RDF11-MT]].</li>
+      <dfn data-cite="RDF11-MT#rdf-collections">RDF list structures</dfn> [[!RDF11-MT]].</li>
   </ul>
 
   <p><a>JSON-LD documents</a> MAY contain data
@@ -4959,10 +4959,10 @@ <h1>JSON-LD Grammar</h1>
   <p>This appendix restates the syntactic conventions described in the
     previous sections more formally.</p>
 
-  <p>A <a>JSON-LD document</a> MUST be valid <a data-cite="RFC7159#section-2">JSON text</a> as described
-    in [[!RFC7159]], <span class="changed">or some format that can be represented
+  <p>A <a>JSON-LD document</a> MUST be valid <a data-cite="RFC8259#section-2">JSON text</a> as described
+    in [[!RFC8259]], <span class="changed">or some format that can be represented
       in the <a>JSON-LD internal representation</a> that is equivalent to
-      valid <a data-cite="RFC7159#section-2">JSON text</a></span>.</p>
+      valid <a data-cite="RFC8259#section-2">JSON text</a></span>.</p>
 
   <p>A <a>JSON-LD document</a> MUST be a single <a>node object</a>,
     a <a>JSON object</a> consisting of only
@@ -5505,7 +5505,7 @@ <h2>Relationship to RDF</h2>
     <li>In JSON-LD <a>lists</a> use native JSON syntax, either contained in a
       list object, or described as such within a context. Consequently, developers
       using the JSON representation can access list elements directly rather than
-      using the vocabulary for collections described in [[RDF-SCHEMA]]..</li>
+      using the vocabulary for collections described in [[!RDF-SCHEMA]]..</li>
     <li>RDF values are either typed <em>literals</em>
       (<a>typed values</a>) or
       <a>language-tagged strings</a> whereas
@@ -6094,7 +6094,7 @@ <h3>application/ld+json</h3>
         <dt><code>profile</code></dt>
         <dd>
           <p>A non-empty list of space-separated URIs identifying specific
-            constraints or conventions that apply to a JSON-LD document according to [[RFC6906]].
+            constraints or conventions that apply to a JSON-LD document according to [[!RFC6906]].
             A profile does not change the semantics of the resource representation
             when processed without profile knowledge, so that clients both with
             and without knowledge of a profiled resource can safely use the same
@@ -6104,7 +6104,7 @@ <h3>application/ld+json</h3>
             honors the profiles in the list which are recognized by the server.
             It is RECOMMENDED that profile URIs are dereferenceable and provide
             useful documentation at that URI. For more information and background
-            please refer to [[RFC6906]].</p>
+            please refer to [[!RFC6906]].</p>
           <p>This specification defines three values for the <code>profile</code> parameter.
             To request or specify <a href="#expanded-document-form">expanded JSON-LD document form</a>,
             the URI <code>http://www.w3.org/ns/json-ld#expanded</code> SHOULD be used.
@@ -6126,7 +6126,7 @@ <h3>application/ld+json</h3>
     <dt>Encoding considerations:</dt>
     <dd>See <a data-cite="RFC6839#section-3.1">RFC&nbsp;6839, section 3.1</a>.</dd>
     <dt>Security considerations:</dt>
-    <dd>See [[!RFC7159]]
+    <dd>See [[!RFC8259]]
       <p>Since JSON-LD is intended to be a pure data exchange format for
         directed graphs, the serialization SHOULD NOT be passed through a
         code execution mechanism such as JavaScript's <code>eval()</code>