--- a/spec/latest/json-ld-api/index.html Tue May 21 14:05:22 2013 -0400
+++ b/spec/latest/json-ld-api/index.html Tue May 21 14:06:08 2013 -0400
@@ -12,10 +12,10 @@
"localBiblio": localBibliography,
doRDFa: "1.1",
- // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "ED",
+ // specification status (e.g. WD, LC, NOTE, etc.). If in doubt use ED.
+ specStatus: "LC",
// if you wish the publication date to be other than today, set this
- //publishDate: "2012-12-25",
+ publishDate: "2013-05-16",
copyrightStart: "2010",
// the specification's short name, as in http://www.w3.org/TR/short-name/
@@ -23,9 +23,9 @@
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
- previousPublishDate: "2012-07-12",
- previousMaturity: "WD",
- previousURI: "http://www.w3.org/TR/2012/WD-json-ld-api-20120712/",
+ previousPublishDate: "2013-04-11",
+ previousMaturity: "LC",
+ previousURI: "http://www.w3.org/TR/2013/WD-json-ld-api-20130411/",
// if there a publicly available Editor's Draft, this is the link
edDraftURI: "http://json-ld.org/spec/latest/json-ld-api/index.html",
@@ -33,7 +33,7 @@
testSuiteURI: "http://www.w3.org/2013/json-ld-tests/",
// if this is a LCWD, uncomment and set the end of its review period
- // lcEnd: "2009-08-05",
+ lcEnd: "2013-06-06",
// if you want to have extra CSS, append them to this list
// it is recommended that the respec.css stylesheet be kept
@@ -85,7 +85,7 @@
wgPatentURI: "http://www.w3.org/2004/01/pp-impl/46168/status",
maxTocLevel: 2,
preProcess: [ preProc ],
- //alternateFormats: [ {uri: "diff-20120712.html", label: "diff to previous version"} ],
+ alternateFormats: [ {uri: "diff-20130411.html", label: "diff to previous version"} ]
};
//]]>
</script>
@@ -113,11 +113,11 @@
</section>
<section id="sotd">
- <p>This document has been under development for over 25 months in the
+ <p>This document has been under development for over 34 months in the
JSON for Linking Data Community Group. The document has recently been
transferred to the RDF Working Group for review, improvement, and publication
along the Recommendation track. The specification has undergone significant
- development, review, and changes during the course of the last 25 months.</p>
+ development, review, and changes during the course of the last 34 months.</p>
<p>There are several independent
<a href="http://json-ld.org/#impl">interoperable implementations</a> of
@@ -128,7 +128,7 @@
the test suite, and the live editor, they are believed to be mature enough
to be integrated into a non-production system at this point in time. There
is an expectation that they could be used in a production system within the
- next six months.</p>
+ next three months.</p>
<p>There are a number of ways that one may participate in the development of
this specification:</p>
@@ -142,7 +142,7 @@
<a href="http://lists.w3.org/Archives/Public/public-linked-json/">public-linked-json@w3.org</a></li>
<li><a href="http://json-ld.org/minutes/">Public JSON-LD Community Group teleconferences</a>
- are held on Tuesdays at 1500UTC every week. Participation is open to the
+ are held on Tuesdays at 1400UTC every week. Participation is open to the
public.</li>
<li>RDF Working Group teleconferences are held on Wednesdays at 1500UTC
@@ -160,8 +160,9 @@
IRC channel is available for real-time discussion on irc.freenode.net.</li>
</ul>
- <p>Changes since the
- <a href="http://www.w3.org/TR/2013/WD-json-ld-api-20130411/">11 April 2013 Last Call Working Draft</a>:</p>
+ <p>This is a second Last Call Working Draft for this document.
+ Changes since the
+ <a href="http://www.w3.org/TR/2013/WD-json-ld-api-20130411/">11 April 2013 Last Call Working Draft</a>:</p>
<ul>
<li>Use of DOM Futures instead of callbacks in the Application Programming Interface</li>
@@ -169,13 +170,9 @@
<code class="error"><a href="#idl-def-JsonLdErrorCode.cyclic-IRI-mapping">cyclic IRI mapping</a></code> error</li>
<li>Raise an <code class="error"><a href="#idl-def-JsonLdErrorCode.invalid-IRI-mapping">invalid IRI mapping</a></code>
error if relative URLs are used in term definitions</li>
- <li>Support relative IRIs in <code>@base</code></li>
- <li>Remove default value of <code class="idlMemberName"><a href="#idl-def-JsonLdOptions">JsonLdOption's</a></code>
- <code class="idlMemberName"><a href="#widl-JsonLdOptions-base">base</a></code> member</li>
<li>Support lists of lists when converting from RDF to JSON-LD</li>
- <li>Convert all RDF numeric literals (except <code>xsd:decimal</code>) to <tref title="number">numbers</tref>
- when converting from RDF; convert all <tref title="number">numbers</tref> to
- <code>xsd:double</code>-typed literals when converting to RDF</li>
+ <li>Support for relative URLs in <code>@base</code> and documents that
+ do not have a base value.</li>
</ul>
</section>
@@ -300,7 +297,7 @@
and regular way of expressing of values in JSON-LD; all contextual
information from the document is instead stored locally with each value.
Running the <a href="#expansion-algorithm">Expansion algorithm</a>
- (<code class="idlMemberName"><a href="#widl-JsonLdProcessor-expand-Future-JsonLdInput-input-JsonLdOptions-options">expand</a></code>
+ (<code class="idlMemberName"><a href="#widl-JsonLdProcessor-expand-Future-any-input-JsonLdOptions-options">expand</a></code>
operation) against the above examples results in the following output:</p>
<pre class="example" data-transform="updateExample"
@@ -388,7 +385,7 @@
</pre>
<p>Running the <a href="#compaction-algorithm">Compaction Algorithm</a>
- (<code class="idlMemberName"><a href="#widl-JsonLdProcessor-compact-Future-JsonLdInput-input-JsonLdContext-context-JsonLdOptions-options">compact</a></code>
+ (<code class="idlMemberName"><a href="#widl-JsonLdProcessor-compact-Future-any-input-JsonLdContext-context-JsonLdOptions-options">compact</a></code>
operation) given the context supplied above against the JSON-LD input
document provided above would result in the following output:</p>
@@ -455,7 +452,7 @@
</pre>
<p>Running the <a href="#flattening-algorithm">Flattening algorithm</a>
- (<code class="idlMemberName"><a href="#widl-JsonLdProcessor-flatten-Future-JsonLdInput-input-JsonLdContext-context-JsonLdOptions-options">flatten</a></code>
+ (<code class="idlMemberName"><a href="#widl-JsonLdProcessor-flatten-Future-any-input-JsonLdContext-context-JsonLdOptions-options">flatten</a></code>
operation) with a context set to <tref>null</tref> to prevent compaction
returns the following document:</p>
@@ -638,7 +635,7 @@
the collection is <em>unordered</em> by default. While order is
preserved in regular JSON arrays, it is not in regular JSON-LD arrays
unless specifically defined (see
- <cite><a href="../json-ld/#sets-and-lists">Sets and Lists</a></cite> in
+ <cite><a href="http://www.w3.org/TR/json-ld-syntax/#sets-and-lists">Sets and Lists</a></cite> in
the JSON-LD specification [[JSON-LD]]).</dd>
<dt><tdef>string</tdef></dt>
<dd>A string is a sequence of zero or more Unicode characters,
@@ -666,11 +663,11 @@
<dl>
<dt><tdef>keyword</tdef></dt>
<dd>A JSON key that is specific to JSON-LD, specified in the section
- <cite><a href="../json-ld/#syntax-tokens-and-keywords">Syntax Tokens and Keywords</a></cite>
+ <cite><a href="http://www.w3.org/TR/json-ld-syntax/#syntax-tokens-and-keywords">Syntax Tokens and Keywords</a></cite>
of the JSON-LD specification [[!JSON-LD]].</dd>
<dt><tdef>context</tdef></dt>
<dd>A set of rules for interpreting a JSON-LD document as specified in the section
- <cite><a href="../json-ld/#the-context">The Context</a></cite> of the JSON-LD
+ <cite><a href="http://www.w3.org/TR/json-ld-syntax/#the-context">The Context</a></cite> of the JSON-LD
specification [[!JSON-LD]].</dd>
<dt><tdef>JSON-LD document</tdef></dt>
<dd>A <tref>JSON-LD document</tref> is a serialization of a collection of
@@ -684,7 +681,7 @@
<dt><tdef>JSON-LD graph</tdef></dt>
<dd>A labeled directed graph, i.e., a set of <tref title="node">nodes</tref>
connected by <tref title="edge">edges</tref>,
- as specified in the <cite><a href="../json-ld/#data-model">Data Model</a></cite>
+ as specified in the <cite><a href="http://www.w3.org/TR/json-ld-syntax/#data-model">Data Model</a></cite>
section of the JSON-LD specification [[!JSON-LD]].</dd>
<dt><tdef>edge</tdef></dt>
<dd>Every <tref>edge</tref> has a direction associated with it and is labeled with
@@ -1565,7 +1562,7 @@
<li>Otherwise, if <i>key</i>'s <tref>container mapping</tref> in
<tref>active context</tref> is <code>@language</code> and
<i>value</i> is a <tref>JSON object</tref> then <i>value</i>
- is expanded from a <tref href="../json-ld/#dfn-language-map">language map</tref>
+ is expanded from a <tref href="http://www.w3.org/TR/json-ld-syntax/#dfn-language-map">language map</tref>
as follows:
<ol class="algorithm">
<li>Initialize <i>expanded value</i> to an empty
@@ -2772,7 +2769,7 @@
which collects all properties of a <tref>node</tref> in a single
<tref>JSON object</tref>. In the next step, the <i>node map</i> is
converted to a JSON-LD document in
- <tref href="../json-ld/#flattened-document-form">flattened document form</tref>.
+ <tref href="http://www.w3.org/TR/json-ld-syntax/#flattened-document-form">flattened document form</tref>.
Finally, if a <tref>context</tref> has been passed, the flattened document
is compacted using the <a href="#compaction-algorithm">Compaction algorithm</a>
before being returned.</p>
@@ -3075,7 +3072,7 @@
<tref title="prefix">prefixes</tref> are used in
<tref title="compact iri">compact IRIs</tref>:</p>
- <table rules="all">
+ <table class="simple">
<thead>
<th>Prefix</th>
<th>IRI</th>
@@ -3109,7 +3106,7 @@
<cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
of [[RDF11-CONCEPTS]].</p>
- <div class="issue atrisk" data-number="3" title="Allow blank nodes to be used as graph name or property">
+ <div class="issue atrisk" data-number="1" title="Allow blank nodes to be used as graph name or property">
<p class="atrisk-head">Note: This feature is
<a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and
may be removed from this specification based on feedback. Please send feedback to
@@ -3256,13 +3253,24 @@
<a class="sectionRef" href="#data-round-tripping">Data Round Tripping</a>
If <i>datatype</i> is <tref>null</tref>, set it to
<code>xsd:boolean</code>.</li>
- <li>Otherwise, if <i>value</i> is a <tref>number</tref>, convert <i>value</i>
- to a <tref>string</tref> in <tref>canonical lexical form</tref> of
+ <li>Otherwise, if <i>value</i> is a <tref>number</tref> with fractions
+ or <i>value</i> is a <tref>number</tref> and <i>datatype</i> equals
+ <code>xsd:double</code>, convert <i>value</i> to a
+ <tref>string</tref> in <tref>canonical lexical form</tref> of
an <code>xsd:double</code> as defined in [[!XMLSCHEMA11-2]]
and described in
<a class="sectionRef" href="#data-round-tripping">Data Round Tripping</a>.
If <i>datatype</i> is <tref>null</tref>, set it to
<code>xsd:double</code>.</li>
+ <li>Otherwise, if <i>value</i> is a <tref>number</tref> without fractions
+ or <i>value</i> is a <tref>number</tref> and <i>datatype</i> equals
+ <code>xsd:integer</code>, convert <i>value</i> to a
+ <tref>string</tref> in <tref>canonical lexical form</tref> of
+ an <code>xsd:integer</code> as defined in [[!XMLSCHEMA11-2]]
+ and described in
+ <a class="sectionRef" href="#data-round-tripping">Data Round Tripping</a>.
+ If <i>datatype</i> is <tref>null</tref>, set it to
+ <code>xsd:integer</code>.</li>
<li>Otherwise, if <i>datatype</i> is <tref>null</tref>, set it to
<code>xsd:string</code> or <code>rdf:langString</code>, depending on if
item has an <code>@language</code> member.</li>
@@ -3342,9 +3350,15 @@
<tref title="RDF literal">RDF literals</tref>, <tref title="IRI">IRIs</tref>
and <tref title="blank node identifier">blank node identifiers</tref>.
If the <i>use native types</i> flag is set to <tref>true</tref>,
- some <tref title="RDF literal">RDF literals</tref> are converted to
- <tref title="number">JSON numbers</tref> or the boolean values <tref>true</tref>
- or <tref>false</tref> as described in
+ <tref title="RDF literal">RDF literals</tref> with a
+ <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-datatype-iri">datatype IRI</tref>
+ that equals <code>xsd:integer</code> or <code>xsd:double</code> are converted
+ to a <tref title="number">JSON numbers</tref> and <tref title="RDF literal">RDF literals</tref>
+ with a <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-datatype-iri">datatype IRI</tref>
+ that equals <code>xsd:boolean</code> are converted to <tref>true</tref> or
+ <tref>false</tref> based on their
+ <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-lexical-form">lexical form</tref>
+ as described in
<a class="sectionRef" href="#data-round-tripping">Data Round Tripping</a>.</p>
</section>
@@ -3522,22 +3536,14 @@
If the <i>use native types</i> flag is set to <tref>true</tref>,
<tref title="RDF literal">RDF literals</tref> with a
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-datatype-iri">datatype IRI</tref>
- that equals <code>xsd:integer</code>, <code>xsd:double</code>, <code>xsd:float</code>,
- <code>xsd:byte</code>, <code>xsd:short</code>, <code>xsd:int</code>, <code>xsd:long</code>,
- <code>xsd:unsignedByte</code>, <code>xsd:unsignedShort</code>,
- <code>xsd:unsignedInt</code>, <code>xsd:unsignedLong</code>,
- <code>xsd:positiveInteger</code>, <code>xsd:nonNegativeInteger</code>,
- <code>xsd:negativeInteger</code>, or <code>xsd:nonPositiveInteger</code> are converted
+ that equals <code>xsd:integer</code> or <code>xsd:double</code> are converted
to a <tref title="number">JSON numbers</tref> and <tref title="RDF literal">RDF literals</tref>
with a <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-datatype-iri">datatype IRI</tref>
that equals <code>xsd:boolean</code> are converted to <tref>true</tref> or
<tref>false</tref> based on their
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-lexical-form">lexical form</tref>
- as described in <a class="sectionRef" href="#data-round-tripping">Data Round Tripping</a>.
- <tref title="RDF literal">RDF literals</tref> with a
- <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-datatype-iri">datatype IRI</tref>
- that equals <code>xsd:decimal</code> are not converted to
- <tref title="number">JSON numbers</tref>.</p>
+ as described in
+ <a class="sectionRef" href="#data-round-tripping">Data Round Tripping</a>.</p>
</section>
<section>
@@ -3575,16 +3581,12 @@
set <i>type</i> to <code>xsd:boolean</code>.</li>
<li>Otherwise, if the
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-datatype-iri">datatype IRI</tref>
- of <i>value</i> equals <code>xsd:integer</code>, <code>xsd:double</code>,
- <code>xsd:float</code>, <code>xsd:byte</code>, <code>xsd:short</code>,
- <code>xsd:int</code>, <code>xsd:long</code>, <code>xsd:unsignedByte</code>,
- <code>xsd:unsignedShort</code>, <code>xsd:unsignedInt</code>,
- <code>xsd:unsignedLong</code>, <code>xsd:positiveInteger</code>,
- <code>xsd:nonNegativeInteger</code>, <code>xsd:negativeInteger</code>,
- or <code>xsd:nonPositiveInteger</code> and its
+ of <i>value</i> equals <code>xsd:integer</code> or
+ <code>xsd:double</code> and its
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-lexical-form">lexical form</tref>
- is in the corresponding <tref>canonical lexical form</tref> as defined by
- [[!XMLSCHEMA11-2]], set <i>converted value</i> to the result of converting the
+ is a valid <code>xsd:integer</code> or <code>xsd:double</code>
+ according [[!XMLSCHEMA11-2]], set <i>converted value</i>
+ to the result of converting the
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-lexical-form">lexical form</tref>
to a JSON <tref>number</tref>.</li>
</ol>
@@ -3611,16 +3613,43 @@
<section>
<h2>Data Round Tripping</h2>
+ <div class="issue atrisk" data-number="2" title="Conversion to/from JSON Native Types">
+ <p class="atrisk-head">Note: This feature is
+ <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and may
+ be removed or modified heavily from the feature described in this specification
+ based on reviewer feedback. Please send feedback to
+ <a href="mailto:public-rdf-comments@w3.org">public-rdf-comments@w3.org</a>.
+ For the current status see
+ <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
+ <p>The JSON-LD-API allows certain RDF literals to be mapped to JSON numbers (if the "use native types" flag is set). The mapping rules are currently being debated as is which JSON-LD API methods the "use native types" will have an effect in. There may be changes made to the algorithm and API based on feedback during the 2nd Last Call. Implementers and reviewers should keep a close eye on the details for this mechanism and comment on any round-tripping concerns that they may have. The algorithm and API will most likely change after the LC2 period.</p>
+ </div>
+
<p>When <a href="#convert-to-rdf-algorithm">converting JSON-LD to RDF</a>
JSON-native <tref title="number">numbers</tref> are automatically
- type-coerced to <code>xsd:double</code>, the boolean values
- <tref>true</tref> and <tref>false</tref> are coerced to
- <code>xsd:boolean</code>, and <tref title="string">strings</tref>
+ type-coerced to <code>xsd:integer</code> or <code>xsd:double</code>
+ depending on whether the <tref>number</tref> has fractions or not,
+ the boolean values <tref>true</tref> and <tref>false</tref> are
+ coerced to <code>xsd:boolean</code>, and <tref title="string">strings</tref>
are coerced to <code>xsd:string</code>. The numeric or boolean values
itself are converted to <tdef>canonical lexical form</tdef>, i.e., a
deterministic string representation as defined in
[[!XMLSCHEMA11-2]].</p>
+ <p>The <tref>canonical lexical form</tref> of an <em>integer</em>, i.e.,
+ a <tref>number</tref> without fractions or a <tref>number</tref> coerced
+ to <code>xsd:integer</code>, is a finite-length sequence of decimal
+ digits (<code>0-9</code>) with an optional leading minus sign; leading
+ zeros are prohibited. In JavaScript, implementers can use the following
+ snippet of code to convert an integer to
+ <tref>canonical lexical form</tref>:</p>
+
+ <pre class="example" data-transform="updateExample"
+ title="Sample integer serialization implementation in JavaScript">
+ <!--
+ (value).toFixed(0).toString()
+ -->
+ </pre>
+
<p>The <tref>canonical lexical form</tref> of a <em>double</em>, i.e., a
<tref>number</tref> with fractions or a <tref>number</tref> coerced to
<code>xsd:double</code>, consists of a mantissa followed by the
@@ -3659,13 +3688,13 @@
errors might occur. When converting
<a href="#convert-from-rdf-algorithm">RDF to JSON-LD</a>, similar
rounding errors might occur. Furthermore, the datatype or the lexical
- representation might be lost. An <code>xsd:integer</code> with a value
- of <code>2</code> will, e.g., result in an <code>xsd:double</code>
- with a value of <code>2.0E0</code> in <tref>canonical lexical form</tref>
+ representation might be lost. An <code>xsd:double</code> with a value
+ of <code>2.0</code> will, e.g., result in an <code>xsd:integer</code>
+ with a value of <code>2</code> in <tref>canonical lexical form</tref>
when converted from RDF to JSON-LD and back to RDF. It is important
to highlight that in practice it might be impossible to losslessly
- convert some RDF literals to <tref title="number">numbers</tref> because
- their value space is not limited. While the JSON specification [[RFC4627]]
+ convert an <code>xsd:integer</code> to a <tref>number</tref> because
+ its value space is not limited. While the JSON specification [[RFC4627]]
does not limit the value space of <tref title="number">numbers</tref>
either, concrete implementations typically do have a limited value
space.</p>
@@ -3675,21 +3704,11 @@
specifies a <i>use native types</i> flag which controls whether
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-literal">RDF literals</tref>
with a <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-datatype-iri">datatype IRI</tref>
- equal to <code>xsd:integer</code>, <code>xsd:double</code>, <code>xsd:float</code>,
- <code>xsd:byte</code>, <code>xsd:short</code>, <code>xsd:int</code>,
- <code>xsd:long</code>, <code>xsd:unsignedByte</code>, <code>xsd:unsignedShort</code>,
- <code>xsd:unsignedInt</code>, <code>xsd:unsignedLong</code>, <code>xsd:positiveInteger</code>,
- <code>xsd:nonNegativeInteger</code>, <code>xsd:negativeInteger</code>,
- <code>xsd:nonPositiveInteger</code>, or <code>xsd:boolean</code> are converted to
- their JSON-native counterparts. If the <i>use native types</i> flag is set to
- <tref>false</tref>, all
- <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-literal">RDF literals</tref> remain
- in their original string representation.
- <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-literal">Literals</tref> with a
- <tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-datatype-iri">datatype IRI</tref>
- that equals <code>xsd:decimal</code> are not automatically converted to
- <tref title="number">numbers</tref> because their primary use is for values
- where rounding errors have to be avoided.</p>
+ equal to <code>xsd:integer</code>, <code>xsd:double</code>, or
+ <code>xsd:boolean</code> are converted to their JSON-native
+ counterparts. If the <i>use native types</i> flag is set to
+ <tref>false</tref>, all literals remain in their original string
+ representation.</p>
<p>Some JSON serializers, such as PHP's native implementation in some versions,
backslash-escape the forward slash character. For example, the value
@@ -3716,6 +3735,17 @@
<cite><a href="http://dom.spec.whatwg.org/#futures">section 4 Futures</a></cite>
of [[!DOM-WHATWG]].</p>
+ <div class="issue atrisk" data-number="3" title="Properly referencing the DOM Futures spec">
+ <p class="atrisk-head">Note: This feature is
+ <a href="http://www.w3.org/2005/10/Process-20051014/tr#cfi">"at risk"</a> and may
+ be removed or modified heavily from the feature described in this specification
+ based on reviewer feedback. Please send feedback to
+ <a href="mailto:public-rdf-comments@w3.org">public-rdf-comments@w3.org</a>.
+ For the current status see
+ <a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
+ <p>The JSON-LD API specification currently only refers to the "Future" interface and does not attempt to provide any details on the specific implementation of Futures. That is, it does not reference whether or not '.then()' must be specified. This is done in order to allow for some implementation flexibility in the event the DOM Futures spec changes. The editors of the WHATWG DOM specification have asserted that the Future interface is ready to be incorporated into specifications. The issue relates to how to properly refer to a spec living in the WHATWG as a living standard as well as how to ensure that the interface provided by the spec is stable.</p>
+ </div>
+
<section>
<h3>The <a>JsonLdProcessor</a> Interface</h3>
@@ -4091,7 +4121,7 @@
<dd>A <tref>set object</tref> or <tref>list object</tref> with
disallowed members has been detected.</dd>
<dt>invalid language map value</dt>
- <dd>An invalid value in a <tref href="../json-ld/#dfn-language-map">language map</tref>
+ <dd>An invalid value in a <tref href="http://www.w3.org/TR/json-ld-syntax/#dfn-language-map">language map</tref>
has been detected. It has to be a <tref>string</tref> or an <tref>array</tref> of
<tref title="string">strings</tref>.</dd>
<dt>compaction to list of lists</dt>
@@ -4125,9 +4155,11 @@
and performing several implementations of the specification. Ian Davis is
thanked for his work on RDF/JSON. Thanks also to Nathan Rixham,
Bradley P. Allen, Kingsley Idehen, Glenn McDonald, Alexandre Passant,
- Danny Ayers, Ted Thibodeau Jr., Olivier Grisel, Josh Mandel, Eric Prud'hommeaux,
- David Wood, Guus Schreiber, Pat Hayes, Sandro Hawke, and Richard Cyganiak
- for their input on the specification.</p>
+ Danny Ayers, Ted Thibodeau Jr., Olivier Grisel, Josh Mandel,
+ Eric Prud'hommeaux, David Wood, Guus Schreiber, Pat Hayes, Sandro Hawke,
+ Tab Atkins Jr., Anne van Kesteren, Robin Berjon, Marcos Caceres,
+ Boris Zbarsky,
+ and Richard Cyganiak for their input on the specification.</p>
</section>
</body>