--- a/spec/WD/20130411/json-ld-api/index.html Fri Apr 05 17:14:56 2013 +0200
+++ b/spec/WD/20130411/json-ld-api/index.html Fri Apr 05 17:31:25 2013 +0200
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.1//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd'>
-<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" prefix='bibo: http://purl.org/ontology/bibo/' typeof="bibo:Document">
+<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" typeof="bibo:Document">
<head>
<title>JSON-LD 1.0 Processing Algorithms and API</title>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
@@ -17,7 +17,7 @@
font-style: italic;
}
</style>
-<style>
+<style type="text/css">
/* --- INLINES --- */
em.rfc2119 {
text-transform: lowercase;
@@ -128,7 +128,7 @@
.section dl.attrs dd, .section dl.eldef dd {
margin-bottom: 0;
}
-</style><style>/* --- EXAMPLES --- */
+</style><style type="text/css">/* --- EXAMPLES --- */
div.example-title {
min-width: 7.5em;
color: #b9ab2d;
@@ -160,7 +160,7 @@
aside.example div.example div.example-title {
color: #999;
}
-</style><style>/* --- ISSUES/NOTES --- */
+</style><style type="text/css">/* --- ISSUES/NOTES --- */
div.issue-title, div.note-title {
padding-right: 1em;
min-width: 7.5em;
@@ -199,7 +199,7 @@
}
-</style><style>/* --- WEB IDL --- */
+</style><style type="text/css">/* --- WEB IDL --- */
pre.idl {
border-top: 1px solid #90b8de;
border-bottom: 1px solid #90b8de;
@@ -429,9 +429,6 @@
width: 100%;
}
</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" />
-<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
-
-<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
</head>
<body><div class="head">
@@ -466,11 +463,11 @@
<dt>Editors:</dt>
- <dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>, <a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">Graz University of Technology</a></span>
+ <dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>, <a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">Graz University of Technology</a></span>
</dd>
-<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">Gregg Kellogg</a>, <a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">Kellogg Associates</a></span>
+<dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">Gregg Kellogg</a>, <a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">Kellogg Associates</a></span>
</dd>
-<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://manu.sporny.org/">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
+<dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://manu.sporny.org/">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
</dd>
@@ -514,12 +511,12 @@
<hr />
</div>
-<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter"><h2>Abstract</h2>
+<div id="abstract" class="introductory section" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter"><h2>Abstract</h2>
<p>This specification defines an Application Programming Interface (API)
and a set of algorithms for programmatic transformations of JSON-LD
documents. Restructuring data according the defined transformations
often dramatically simplifies its usage.</p>
-</section><section id="sotd" class="introductory" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter"><h2>Status of This Document</h2>
+</div><div id="sotd" class="introductory section" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter"><h2>Status of This Document</h2>
@@ -600,12 +597,12 @@
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#features" class="tocxref"><span class="secno">2. </span>Features</a><ul class="toc"><li class="tocline"><a href="#expansion" class="tocxref"><span class="secno">2.1 </span>Expansion</a></li><li class="tocline"><a href="#compaction" class="tocxref"><span class="secno">2.2 </span>Compaction</a></li><li class="tocline"><a href="#flattening" class="tocxref"><span class="secno">2.3 </span>Flattening</a></li><li class="tocline"><a href="#rdf-conversion" class="tocxref"><span class="secno">2.4 </span>RDF Conversion</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">3. </span>Conformance</a></li><li class="tocline"><a href="#general-terminology" class="tocxref"><span class="secno">4. </span>General Terminology</a></li><li class="tocline"><a href="#algorithm-terms" class="tocxref"><span class="secno">5. </span>Algorithm Terms</a></li><li class="tocline"><a href="#context-processing-algorithms" class="tocxref"><span class="secno">6. </span>Context Processing Algorithms</a><ul class="toc"><li class="tocline"><a href="#context-processing-algorithm" class="tocxref"><span class="secno">6.1 </span>Context Processing Algorithm</a></li><li class="tocline"><a href="#create-term-definition" class="tocxref"><span class="secno">6.2 </span>Create Term Definition</a></li><li class="tocline"><a href="#iri-expansion" class="tocxref"><span class="secno">6.3 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a></li></ul></li><li class="tocline"><a href="#expansion-algorithms" class="tocxref"><span class="secno">7. </span>Expansion Algorithms</a><ul class="toc"><li class="tocline"><a href="#expansion-algorithm" class="tocxref"><span class="secno">7.1 </span>Expansion Algorithm</a></li><li class="tocline"><a href="#value-expansion" class="tocxref"><span class="secno">7.2 </span>Value Expansion</a></li></ul></li><li class="tocline"><a href="#compaction-algorithms" class="tocxref"><span class="secno">8. </span>Compaction Algorithms</a><ul class="toc"><li class="tocline"><a href="#compaction-algorithm" class="tocxref"><span class="secno">8.1 </span>Compaction Algorithm</a></li><li class="tocline"><a href="#inverse-context-creation" class="tocxref"><span class="secno">8.2 </span>Inverse Context Creation</a></li><li class="tocline"><a href="#iri-compaction" class="tocxref"><span class="secno">8.3 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a></li><li class="tocline"><a href="#term-selection" class="tocxref"><span class="secno">8.4 </span>Term Selection</a></li><li class="tocline"><a href="#value-compaction" class="tocxref"><span class="secno">8.5 </span>Value Compaction</a></li></ul></li><li class="tocline"><a href="#flattening-algorithms" class="tocxref"><span class="secno">9. </span>Flattening Algorithms</a><ul class="toc"><li class="tocline"><a href="#flattening-algorithm" class="tocxref"><span class="secno">9.1 </span>Flattening Algorithm</a></li><li class="tocline"><a href="#node-map-generation" class="tocxref"><span class="secno">9.2 </span>Node Map Generation</a></li><li class="tocline"><a href="#generate-blank-node-identifier" class="tocxref"><span class="secno">9.3 </span>Generate Blank Node Identifier</a></li></ul></li><li class="tocline"><a href="#rdf-conversion-algorithms" class="tocxref"><span class="secno">10. </span>RDF Conversion Algorithms</a><ul class="toc"><li class="tocline"><a href="#convert-to-rdf-algorithm" class="tocxref"><span class="secno">10.1 </span>Convert to RDF Algorithm</a></li><li class="tocline"><a href="#object-to-rdf-conversion" class="tocxref"><span class="secno">10.2 </span>Object to RDF Conversion</a></li><li class="tocline"><a href="#list-to-rdf-conversion" class="tocxref"><span class="secno">10.3 </span>List to RDF Conversion</a></li><li class="tocline"><a href="#convert-from-rdf-algorithm" class="tocxref"><span class="secno">10.4 </span>Convert from RDF Algorithm</a></li><li class="tocline"><a href="#rdf-to-object-conversion" class="tocxref"><span class="secno">10.5 </span>RDF to Object Conversion</a></li><li class="tocline"><a href="#data-round-tripping" class="tocxref"><span class="secno">10.6 </span>Data Round Tripping</a></li></ul></li><li class="tocline"><a href="#the-application-programming-interface" class="tocxref"><span class="secno">11. </span>The Application Programming Interface</a><ul class="toc"><li class="tocline"><a href="#the-jsonldprocessor-interface" class="tocxref"><span class="secno">11.1 </span>The <span class="formerLink"><code>JsonLdProcessor</code></span> Interface</a></li><li class="tocline"><a href="#callbacks" class="tocxref"><span class="secno">11.2 </span>Callbacks</a></li><li class="tocline"><a href="#data-structures" class="tocxref"><span class="secno">11.3 </span>Data Structures</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></section>
-
-
-
-
-<section class="informative" id="introduction">
+</div><div class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#features" class="tocxref"><span class="secno">2. </span>Features</a><ul class="toc"><li class="tocline"><a href="#expansion" class="tocxref"><span class="secno">2.1 </span>Expansion</a></li><li class="tocline"><a href="#compaction" class="tocxref"><span class="secno">2.2 </span>Compaction</a></li><li class="tocline"><a href="#flattening" class="tocxref"><span class="secno">2.3 </span>Flattening</a></li><li class="tocline"><a href="#rdf-conversion" class="tocxref"><span class="secno">2.4 </span>RDF Conversion</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">3. </span>Conformance</a></li><li class="tocline"><a href="#general-terminology" class="tocxref"><span class="secno">4. </span>General Terminology</a></li><li class="tocline"><a href="#algorithm-terms" class="tocxref"><span class="secno">5. </span>Algorithm Terms</a></li><li class="tocline"><a href="#context-processing-algorithms" class="tocxref"><span class="secno">6. </span>Context Processing Algorithms</a><ul class="toc"><li class="tocline"><a href="#context-processing-algorithm" class="tocxref"><span class="secno">6.1 </span>Context Processing Algorithm</a></li><li class="tocline"><a href="#create-term-definition" class="tocxref"><span class="secno">6.2 </span>Create Term Definition</a></li><li class="tocline"><a href="#iri-expansion" class="tocxref"><span class="secno">6.3 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</a></li></ul></li><li class="tocline"><a href="#expansion-algorithms" class="tocxref"><span class="secno">7. </span>Expansion Algorithms</a><ul class="toc"><li class="tocline"><a href="#expansion-algorithm" class="tocxref"><span class="secno">7.1 </span>Expansion Algorithm</a></li><li class="tocline"><a href="#value-expansion" class="tocxref"><span class="secno">7.2 </span>Value Expansion</a></li></ul></li><li class="tocline"><a href="#compaction-algorithms" class="tocxref"><span class="secno">8. </span>Compaction Algorithms</a><ul class="toc"><li class="tocline"><a href="#compaction-algorithm" class="tocxref"><span class="secno">8.1 </span>Compaction Algorithm</a></li><li class="tocline"><a href="#inverse-context-creation" class="tocxref"><span class="secno">8.2 </span>Inverse Context Creation</a></li><li class="tocline"><a href="#iri-compaction" class="tocxref"><span class="secno">8.3 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</a></li><li class="tocline"><a href="#term-selection" class="tocxref"><span class="secno">8.4 </span>Term Selection</a></li><li class="tocline"><a href="#value-compaction" class="tocxref"><span class="secno">8.5 </span>Value Compaction</a></li></ul></li><li class="tocline"><a href="#flattening-algorithms" class="tocxref"><span class="secno">9. </span>Flattening Algorithms</a><ul class="toc"><li class="tocline"><a href="#flattening-algorithm" class="tocxref"><span class="secno">9.1 </span>Flattening Algorithm</a></li><li class="tocline"><a href="#node-map-generation" class="tocxref"><span class="secno">9.2 </span>Node Map Generation</a></li><li class="tocline"><a href="#generate-blank-node-identifier" class="tocxref"><span class="secno">9.3 </span>Generate Blank Node Identifier</a></li></ul></li><li class="tocline"><a href="#rdf-conversion-algorithms" class="tocxref"><span class="secno">10. </span>RDF Conversion Algorithms</a><ul class="toc"><li class="tocline"><a href="#convert-to-rdf-algorithm" class="tocxref"><span class="secno">10.1 </span>Convert to RDF Algorithm</a></li><li class="tocline"><a href="#object-to-rdf-conversion" class="tocxref"><span class="secno">10.2 </span>Object to RDF Conversion</a></li><li class="tocline"><a href="#list-to-rdf-conversion" class="tocxref"><span class="secno">10.3 </span>List to RDF Conversion</a></li><li class="tocline"><a href="#convert-from-rdf-algorithm" class="tocxref"><span class="secno">10.4 </span>Convert from RDF Algorithm</a></li><li class="tocline"><a href="#rdf-to-object-conversion" class="tocxref"><span class="secno">10.5 </span>RDF to Object Conversion</a></li><li class="tocline"><a href="#data-round-tripping" class="tocxref"><span class="secno">10.6 </span>Data Round Tripping</a></li></ul></li><li class="tocline"><a href="#the-application-programming-interface" class="tocxref"><span class="secno">11. </span>The Application Programming Interface</a><ul class="toc"><li class="tocline"><a href="#the-jsonldprocessor-interface" class="tocxref"><span class="secno">11.1 </span>The <span class="formerLink"><code>JsonLdProcessor</code></span> Interface</a></li><li class="tocline"><a href="#callbacks" class="tocxref"><span class="secno">11.2 </span>Callbacks</a></li><li class="tocline"><a href="#data-structures" class="tocxref"><span class="secno">11.3 </span>Data Structures</a></li></ul></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">A. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">B. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">B.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">B.2 </span>Informative references</a></li></ul></li></ul></div>
+
+
+
+
+<div class="informative section" id="introduction">
<!--OddPage-->
<h2><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
@@ -631,12 +628,12 @@
knowledge of the JavaScript programming language [<cite><a class="bibref" href="#bib-ECMA-262">ECMA-262</a></cite>] and
WebIDL [<cite><a class="bibref" href="#bib-WEBIDL">WEBIDL</a></cite>]. To understand how JSON-LD maps to RDF, it is helpful to be
familiar with the basic RDF concepts [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>].</p>
-</section>
+</div>
<!-- end of Introduction -->
-<section class="informative" id="features">
+<div class="informative section" id="features">
<!--OddPage-->
<h2><span class="secno">2. </span>Features</h2><p><em>This section is non-normative.</em></p>
@@ -667,7 +664,7 @@
<p>There are four major types of transformation that are discussed in this
document: expansion, compaction, flattening, and RDF conversion.</p>
- <section class="informative" id="expansion">
+ <div class="informative section" id="expansion">
<h3><span class="secno">2.1 </span>Expansion</h3><p><em>This section is non-normative.</em></p>
<p>The algorithm that removes <a class="tref internalDFN" title="context" href="#dfn-context">context</a> is
@@ -745,11 +742,11 @@
output is more verbose and difficult for a human to read, it establishes a
baseline that makes JSON-LD processing easier because of its very regular
structure.</p>
- </section>
+ </div>
<!-- end of Expansion -->
- <section class="informative" id="compaction">
+ <div class="informative section" id="compaction">
<h3><span class="secno">2.2 </span>Compaction</h3><p><em>This section is non-normative.</em></p>
<p>While <a class="tref internalDFN" title="expansion" href="#dfn-expansion">expansion</a> removes <a class="tref internalDFN" title="context" href="#dfn-context">context</a> from a given
@@ -821,11 +818,11 @@
into an application-specific compacted document. While the context provided
above mapped <code>http://xmlns.com/foaf/0.1/name</code> to <code>name</code>, it
could also have been mapped to any other term provided by the developer.</p>
- </section>
+ </div>
<!-- end of Compaction -->
- <section class="informative" id="flattening">
+ <div class="informative section" id="flattening">
<h3><span class="secno">2.3 </span>Flattening</h3><p><em>This section is non-normative.</em></p>
<p>While expansion ensures that a document is in a uniform structure,
@@ -908,11 +905,11 @@
<p>Please note that the result of flattening and compacting a document
is always a <a class="tref internalDFN" title="json-object" href="#dfn-json-object">JSON object</a> which contains an <code>@graph</code>
member that represents the <a class="tref internalDFN" title="default-graph" href="#dfn-default-graph">default graph</a>.</p>
- </section>
+ </div>
<!-- end of Flattening -->
- <section class="informative" id="rdf-conversion">
+ <div class="informative section" id="rdf-conversion">
<h3><span class="secno">2.4 </span>RDF Conversion</h3><p><em>This section is non-normative.</em></p>
<p>JSON-LD can be used to serialize data expressed in RDF as described in
@@ -942,15 +939,15 @@
<p>Note that the output above could easily be compacted using the technique outlined
in the previous section. It is also possible to transform the JSON-LD document back
to RDF using the <a href="#convert-to-rdf-algorithm">Convert to RDF algorithm</a>.</p>
- </section>
+ </div>
<!-- end of RDF Conversion -->
-</section>
+</div>
<!-- end of Features section -->
-<section id="conformance">
+<div class="section" id="conformance">
<!--OddPage-->
<h2><span class="secno">3. </span>Conformance</h2>
@@ -1002,12 +999,12 @@
suite [<cite><a class="bibref" href="#bib-JSON-LD-TESTS">JSON-LD-TESTS</a></cite>]. Note, however, that passing all the tests in the test
suite does not imply complete conformance to this specification. It only implies
that the implementation conforms to aspects tested by the test suite.</p></div>
-</section>
+</div>
<!-- end of Conformance section -->
-<section id="general-terminology">
+<div class="section" id="general-terminology">
<!--OddPage-->
<h2><span class="secno">4. </span>General Terminology</h2>
@@ -1119,12 +1116,12 @@
<a class="tref internalDFN" title="blank-node" href="#dfn-blank-node">blank nodes</a>, and
<a class="tref internalDFN" title="json-ld-value" href="#dfn-json-ld-value">JSON-LD values</a>.</dd>
</dl>
-</section>
+</div>
<!-- end of General Terminology section -->
-<section id="algorithm-terms">
+<div class="section" id="algorithm-terms">
<!--OddPage-->
<h2><span class="secno">5. </span>Algorithm Terms</h2>
@@ -1195,17 +1192,17 @@
as specified by [<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>] representing a collection of
<a class="tref externalDFN" title="rdf-graphs" href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-graph">RDF graphs</a>.</dd>
</dl>
-</section>
+</div>
<!-- end of Algorithm Terms section -->
-<section id="context-processing-algorithms">
+<div class="section" id="context-processing-algorithms">
<!--OddPage-->
<h2><span class="secno">6. </span>Context Processing Algorithms</h2>
- <section id="context-processing-algorithm">
+ <div class="section" id="context-processing-algorithm">
<h3><span class="secno">6.1 </span>Context Processing Algorithm</h3>
<p>When processing a JSON-LD data structure, each processing rule is applied
@@ -1233,7 +1230,7 @@
Given that <a class="tref internalDFN" title="local-context" href="#dfn-local-context">local contexts</a> may contain
references to remote contexts, this includes their retrieval.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview">Overview</h4><p><em>This section is non-normative.</em></p>
<p>First we prepare a new <a class="tref internalDFN" title="active-context" href="#dfn-active-context">active context</a> <i>result</i> by cloning
@@ -1270,9 +1267,9 @@
which may be a <a class="tref internalDFN" title="keyword-alias" href="#dfn-keyword-alias">keyword alias</a>.</p>
<p>Finally, we return <i>result</i> as the new <a class="tref internalDFN" title="active-context" href="#dfn-active-context">active context</a>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm">Algorithm</h4>
<p>This algorithm specifies how a new <a class="tref internalDFN" title="active-context" href="#dfn-active-context">active context</a> is updated
@@ -1400,12 +1397,12 @@
</li>
<li>Return <i>result</i>.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Context Processing -->
- <section id="create-term-definition">
+ <div class="section" id="create-term-definition">
<h3><span class="secno">6.2 </span>Create Term Definition</h3>
<p>This algorithm is called from the
@@ -1413,7 +1410,7 @@
to create a <a class="tref internalDFN" title="term-definition" href="#dfn-term-definition">term definition</a> in the <a class="tref internalDFN" title="active-context" href="#dfn-active-context">active context</a>
for a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> being processed in a <a class="tref internalDFN" title="local-context" href="#dfn-local-context">local context</a>.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-1">Overview</h4><p><em>This section is non-normative.</em></p>
<p><a class="tref internalDFN" title="term-definition" href="#dfn-term-definition">Term definitions</a> are created by
@@ -1437,9 +1434,9 @@
<a class="tref internalDFN" title="iri-mapping" href="#dfn-iri-mapping"><abbr title="Internationalized Resource Identifier">IRI</abbr> mapping</a>, <a class="tref internalDFN" title="container-mapping" href="#dfn-container-mapping">container mapping</a>, and
<a class="tref internalDFN" title="type-mapping" href="#dfn-type-mapping">type mapping</a> or <a class="tref internalDFN" title="language-mapping" href="#dfn-language-mapping">language mapping</a> for the
<a class="tref internalDFN" title="term" href="#dfn-term">term</a>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-1">Algorithm</h4>
<p>The algorithm has four required inputs which are:
@@ -1615,12 +1612,12 @@
associated with <i>defined</i>'s key <i>term</i> to
<a class="tref internalDFN" title="true" href="#dfn-true">true</a>.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Term Creation -->
- <section id="iri-expansion">
+ <div class="section" id="iri-expansion">
<h3><span class="secno">6.3 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion</h3>
<p>In JSON-LD documents, some keys and values may represent
@@ -1638,7 +1635,7 @@
dependencies to be processed via the
<a href="#create-term-definition">Create Term Definition algorithm</a>.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-2">Overview</h4><p><em>This section is non-normative.</em></p>
<p>In order to expand <i>value</i> to an <a class="tref internalDFN" title="absolute-iri" href="#dfn-absolute-iri">absolute <abbr title="Internationalized Resource Identifier">IRI</abbr></a>, we must
@@ -1662,9 +1659,9 @@
in the process of being defined. We create a
<a class="tref internalDFN" title="term-definition" href="#dfn-term-definition">term definition</a> by using the
<a href="#create-term-definition">Create Term Definition algorithm</a>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-2">Algorithm</h4>
<p>The algorithm takes two required and four optional input variables. The
@@ -1743,21 +1740,21 @@
error has been detected and processing is aborted.</li>
<li>Otherwise, return <i>value</i> as is.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of IRI Expansion -->
-</section>
+</div>
<!-- end of Context Processing section -->
-<section id="expansion-algorithms">
+<div class="section" id="expansion-algorithms">
<!--OddPage-->
<h2><span class="secno">7. </span>Expansion Algorithms</h2>
- <section id="expansion-algorithm">
+ <div class="section" id="expansion-algorithm">
<h3><span class="secno">7.1 </span>Expansion Algorithm</h3>
<p>This algorithm expands a JSON-LD document, such that all <a class="tref internalDFN" title="context" href="#dfn-context">context</a>
@@ -1769,7 +1766,7 @@
<a class="tref internalDFN" title="json-ld-value" href="#dfn-json-ld-value">JSON-LD values</a> are expressed in
<a class="tref internalDFN" title="array" href="#dfn-array">arrays</a> in <a class="tref internalDFN" title="expanded-form" href="#dfn-expanded-form">expanded form</a>.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-3">Overview</h4><p><em>This section is non-normative.</em></p>
<p>Starting with its root <i>element</i>, we can process the
@@ -1801,9 +1798,9 @@
<p>Finally, after ensuring <i>result</i> is in an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>,
we return <i>result</i>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-3">Algorithm</h4>
<p>The algorithm takes three input variables: an <a class="tref internalDFN" title="active-context" href="#dfn-active-context">active context</a>,
@@ -2155,13 +2152,13 @@
is <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, set it to an empty <a class="tref internalDFN" title="array" href="#dfn-array">array</a>. Finally, if
the result is not an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>, then set the result to an
<a class="tref internalDFN" title="array" href="#dfn-array">array</a> containing only the result.</p>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Expansion Algorithm -->
- <section id="value-expansion">
+ <div class="section" id="value-expansion">
<h3><span class="secno">7.2 </span>Value Expansion</h3>
<p>Some values in JSON-LD can be expressed in a
@@ -2170,7 +2167,7 @@
JSON-LD documents. A value is said to be in <dfn title="expanded-form" id="dfn-expanded-form">expanded form</dfn>
after the application of this algorithm.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-4">Overview</h4><p><em>This section is non-normative.</em></p>
<p>If <a class="tref internalDFN" title="active-property" href="#dfn-active-property">active property</a> has a <a class="tref internalDFN" title="type-mapping" href="#dfn-type-mapping">type mapping</a> in the
@@ -2187,9 +2184,9 @@
or an <code>@language</code> member if <i>value</i> is a
<a class="tref internalDFN" title="string" href="#dfn-string">string</a> and there is <a class="tref internalDFN" title="language-mapping" href="#dfn-language-mapping">language mapping</a> associated
with the <a class="tref internalDFN" title="active-property" href="#dfn-active-property">active property</a>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-4">Algorithm</h4>
<p>The algorithm takes three required inputs: an <a class="tref internalDFN" title="active-context" href="#dfn-active-context">active context</a>,
@@ -2235,22 +2232,22 @@
</li>
<li>Return <i>result</i>.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Value Expansion -->
-</section>
+</div>
<!-- end of Expansion section -->
-<section id="compaction-algorithms">
+<div class="section" id="compaction-algorithms">
<!--OddPage-->
<h2><span class="secno">8. </span>Compaction Algorithms</h2>
- <section id="compaction-algorithm">
+ <div class="section" id="compaction-algorithm">
<h3><span class="secno">8.1 </span>Compaction Algorithm</h3>
<p>This algorithm compacts a JSON-LD document, such that the given
@@ -2265,7 +2262,7 @@
<a class="tref internalDFN" title="string" href="#dfn-string">strings</a> or
<a class="tref internalDFN" title="number" href="#dfn-number">numbers</a>.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-5">Overview</h4><p><em>This section is non-normative.</em></p>
<p>Starting with its root <i>element</i>, we can process the
@@ -2300,9 +2297,9 @@
is either <i>result</i> or a wrapper for it where <i>result</i> appears
as the value of an (aliased) <code>@graph</code> key because <i>result</i>
contained two or more items in an <a class="tref internalDFN" title="array" href="#dfn-array">array</a>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-5">Algorithm</h4>
<p>The algorithm takes five required input variables: an <a class="tref internalDFN" title="active-context" href="#dfn-active-context">active context</a>,
@@ -2596,12 +2593,12 @@
<i>result</i>. Finally, if a <i>context</i> has been passed, add an
<code>@context</code> member to <i>result</i> and set its value to
the passed <i>context</i>.</p>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Compaction -->
- <section id="inverse-context-creation">
+ <div class="section" id="inverse-context-creation">
<h3><span class="secno">8.2 </span>Inverse Context Creation</h3>
<p>When there is more than one <a class="tref internalDFN" title="term" href="#dfn-term">term</a> that could be chosen
@@ -2627,7 +2624,7 @@
which will find the <a class="tref internalDFN" title="term" href="#dfn-term">term</a> that most appropriately
matches the value's mappings.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-6">Overview</h4><p><em>This section is non-normative.</em></p>
<p>To create an <a class="tref internalDFN" title="inverse-context" href="#dfn-inverse-context">inverse context</a> for a given
@@ -2649,9 +2646,9 @@
to choosing more generic <a class="tref internalDFN" title="term" href="#dfn-term">terms</a> when a more
specifically-matching <a class="tref internalDFN" title="term" href="#dfn-term">term</a> is not available for a particular
<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> and value combination.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-6">Algorithm</h4>
<p>The algorithm takes one required input: the <a class="tref internalDFN" title="active-context" href="#dfn-active-context">active context</a> that
@@ -2749,12 +2746,12 @@
</li>
<li>Return <i>result</i>.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Inverse Context Creation -->
- <section id="iri-compaction">
+ <div class="section" id="iri-compaction">
<h3><span class="secno">8.3 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction</h3>
<p>This algorithm compacts an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> to a <a class="tref internalDFN" title="term" href="#dfn-term">term</a> or
@@ -2763,7 +2760,7 @@
<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> may be passed in order to assist in selecting the most
context-appropriate <a class="tref internalDFN" title="term" href="#dfn-term">term</a>.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-7">Overview</h4><p><em>This section is non-normative.</em></p>
<p>If the passed <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> is <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, we simply
@@ -2793,9 +2790,9 @@
<a class="tref internalDFN" title="base-iri" href="#dfn-base-iri">base <abbr title="Internationalized Resource Identifier">IRI</abbr></a>. Finally, if the <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> or
<a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> still could not be compacted, it is returned
as is.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-7">Algorithm</h4>
<p>This algorithm takes three required inputs and three optional inputs.
@@ -3005,12 +3002,12 @@
the document's base <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</li>
<li>Finally, return <i>iri</i> as is.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of IRI Compaction -->
- <section id="term-selection">
+ <div class="section" id="term-selection">
<h3><span class="secno">8.4 </span>Term Selection</h3>
<p>This algorithm, invoked via the <a href="#iri-compaction"><abbr title="Internationalized Resource Identifier">IRI</abbr> Compaction algorithm</a>,
@@ -3022,7 +3019,7 @@
and which <a class="tref internalDFN" title="type-mapping" href="#dfn-type-mapping">type mapping</a> or <a class="tref internalDFN" title="language-mapping" href="#dfn-language-mapping">language mapping</a> would
be best used to express the value.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-8">Overview</h4><p><em>This section is non-normative.</em></p>
<p>The <a class="tref internalDFN" title="inverse-context" href="#dfn-inverse-context">inverse context's</a> entry for
@@ -3046,9 +3043,9 @@
resolved automatically because they were previously resolved when the
<a href="#inverse-context-creation">Inverse Context Creation algorithm</a>
was used to create the <a class="tref internalDFN" title="inverse-context" href="#dfn-inverse-context">inverse context</a>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-8">Algorithm</h4>
<p>This algorithm has five required inputs. They are:
@@ -3089,12 +3086,12 @@
</li>
<li>No matching term has been found. Return <a class="tref internalDFN" title="null" href="#dfn-null">null</a>.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Term Selection -->
- <section id="value-compaction">
+ <div class="section" id="value-compaction">
<h3><span class="secno">8.5 </span>Value Compaction</h3>
<p><a class="tref internalDFN" title="expansion" href="#dfn-expansion">Expansion</a> transforms all values into <a class="tref internalDFN" title="expanded-form" href="#dfn-expanded-form">expanded form</a>
@@ -3104,7 +3101,7 @@
<a class="tref internalDFN" title="active-context" href="#dfn-active-context">active context</a> that is associated with the value's associated
<a class="tref internalDFN" title="active-property" href="#dfn-active-property">active property</a>.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-9">Overview</h4><p><em>This section is non-normative.</em></p>
<p>The <i>value</i> to compact has either an <code>@id</code> or an
@@ -3133,9 +3130,9 @@
no <a class="tref internalDFN" title="default-language" href="#dfn-default-language">default language</a>, or there is an explicit
<a class="tref internalDFN" title="null" href="#dfn-null">null</a> <a class="tref internalDFN" title="language-mapping" href="#dfn-language-mapping">language mapping</a> for the
<a class="tref internalDFN" title="active-property" href="#dfn-active-property">active property</a>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-9">Algorithm</h4>
<p>This algorithm has four required inputs: an <a class="tref internalDFN" title="active-context" href="#dfn-active-context">active context</a>, an
@@ -3185,21 +3182,21 @@
<code>@value</code> member.</li>
<li>Otherwise, return <i>value</i> as is.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Value Compaction algorithm -->
-</section>
+</div>
<!-- end of Compaction section -->
-<section id="flattening-algorithms">
+<div class="section" id="flattening-algorithms">
<!--OddPage-->
<h2><span class="secno">9. </span>Flattening Algorithms</h2>
- <section id="flattening-algorithm">
+ <div class="section" id="flattening-algorithm">
<h3><span class="secno">9.1 </span>Flattening Algorithm</h3>
<p>This algorithm flattens an expanded JSON-LD document by collecting all
@@ -3209,7 +3206,7 @@
This resulting uniform shape of the document, may drastically simplify
the code required to process JSON-LD data in certain applications.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-10">Overview</h4><p><em>This section is non-normative.</em></p>
<p>First, a <i>node map</i> is generated using the
@@ -3221,9 +3218,9 @@
Finally, if a <a class="tref internalDFN" title="context" href="#dfn-context">context</a> has been passed, the flattened document
is compacted using the <a href="#compaction-algorithm">Compaction algorithm</a>
before being returned.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-10">Algorithm</h4>
<p>The algorithm takes two input variables, an <i>element</i> to flatten and
@@ -3264,12 +3261,12 @@
put in the <code>@graph</code> <a class="tref internalDFN" title="array" href="#dfn-array">array</a>. This ensures that the returned
document has a deterministic structure.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Flattening Algorithm -->
- <section id="node-map-generation">
+ <div class="section" id="node-map-generation">
<h3><span class="secno">9.2 </span>Node Map Generation</h3>
<p>This algorithm creates a <a class="tref internalDFN" title="json-object" href="#dfn-json-object">JSON object</a> <i>node map</i> holding an indexed
@@ -3281,7 +3278,7 @@
The default graph is stored under the <code>@default</code> member, all other graphs are
stored under their <a class="tref internalDFN" title="graph-name" href="#dfn-graph-name">graph name</a>.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-11">Overview</h4><p><em>This section is non-normative.</em></p>
<p>The algorithm recursively runs over an expanded JSON-LD document to
@@ -3301,9 +3298,9 @@
of <a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifiers</a> is
also be done for <a class="tref internalDFN" title="property" href="#dfn-property">properties</a> and values of
<code>@type</code>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-11">Algorithm</h4>
<p>The algorithm takes as input an expanded JSON-LD document <i>element</i> and a reference to
@@ -3460,12 +3457,12 @@
</ol>
</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Node Map Generation -->
- <section id="generate-blank-node-identifier">
+ <div class="section" id="generate-blank-node-identifier">
<h3><span class="secno">9.3 </span>Generate Blank Node Identifier</h3>
<p>This algorithm is used to determine if two generate new
@@ -3473,7 +3470,7 @@
relabel an existing <a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifier</a> to avoid collision
by the introduction of new ones.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-12">Overview</h4><p><em>This section is non-normative.</em></p>
<p>The simplest case is if there exists already a <a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifier</a>
@@ -3485,9 +3482,9 @@
<i>identifier</i> with the <a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifier</a>. Finally,
the <i>counter</i> is increased by one and the new
<a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifier</a> is returned.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-12">Algorithm</h4>
<p>The algorithm takes a single input variable <i>identifier</i> which may
@@ -3509,16 +3506,16 @@
to the new <a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifier</a>.</li>
<li>Return the new <a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifier</a>.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Generate Blank Node Identifier -->
-</section>
+</div>
<!-- end of Flattening section -->
-<section id="rdf-conversion-algorithms">
+<div class="section" id="rdf-conversion-algorithms">
<!--OddPage-->
<h2><span class="secno">10. </span>RDF Conversion Algorithms</h2>
@@ -3552,7 +3549,7 @@
</tbody>
</table>
- <section id="convert-to-rdf-algorithm">
+ <div class="section" id="convert-to-rdf-algorithm">
<h3><span class="secno">10.1 </span>Convert to RDF Algorithm</h3>
<p>This algorithms converts a JSON-LD document to an <a class="tref internalDFN" title="rdf-dataset" href="#dfn-rdf-dataset">RDF dataset</a>.
@@ -3585,7 +3582,7 @@
send in a comment.</p>
</div></div>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-13">Overview</h4><p><em>This section is non-normative.</em></p>
<p>The JSON-LD document is expanded and converted to a <i>node map</i> using the
@@ -3606,9 +3603,9 @@
are transformed into an
<a class="tref externalDFN" title="rdf-collection" href="http://www.w3.org/TR/rdf-schema/#ch_collectionvocab">RDF Collection</a>
using the <a href="#list-to-rdf-conversion">List to RDF Conversion algorithm.</a></p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-13">Algorithm</h4>
<p>The algorithm takes a JSON-LD document <i>element</i> and returns an
@@ -3666,12 +3663,12 @@
</li>
<li>Return <i>dataset</i>.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Convert to RDF Algorithm -->
- <section id="object-to-rdf-conversion">
+ <div class="section" id="object-to-rdf-conversion">
<h3><span class="secno">10.2 </span>Object to RDF Conversion</h3>
<p>This algorithm takes a <a class="tref internalDFN" title="node-object" href="#dfn-node-object">node object</a> or <a class="tref internalDFN" title="value-object" href="#dfn-value-object">value object</a>
@@ -3679,7 +3676,7 @@
<a class="tref externalDFN" title="rdf-resource" href="http://www.w3.org/TR/rdf11-concepts/#dfn-resource">RDF resource</a>
to be used as the <a class="tref internalDFN" title="object" href="http://www.w3.org/TR/rdf11-concepts/#dfn-object">object</a> of an <a class="tref internalDFN" title="rdf-triple" href="#dfn-rdf-triple">RDF triple</a>.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-14">Overview</h4><p><em>This section is non-normative.</em></p>
<p><a class="tref internalDFN" title="value-object" href="#dfn-value-object">Value objects</a> are transformed to
@@ -3688,9 +3685,9 @@
whereas <a class="tref internalDFN" title="node-object" href="#dfn-node-object">node objects</a> are transformed
to <a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a> or
<a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifiers</a>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-14">Algorithm</h4>
<p>The algorithm takes as its sole argument <i>item</i> which must be
@@ -3741,12 +3738,12 @@
<li>Return <i>literal</i>.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Object to RDF Conversion -->
- <section id="list-to-rdf-conversion">
+ <div class="section" id="list-to-rdf-conversion">
<h3><span class="secno">10.3 </span>List to RDF Conversion</h3>
<p>List Conversion is the process of taking a <a class="tref internalDFN" title="list-object" href="#dfn-list-object">list object</a>
@@ -3754,7 +3751,7 @@
<a class="tref externalDFN" title="rdf-collection" href="http://www.w3.org/TR/rdf-schema/#ch_collectionvocab">RDF Collection</a>
as defined in RDF Semantics [<cite><a class="bibref" href="#bib-RDF-MT">RDF-MT</a></cite>].</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-15">Overview</h4><p><em>This section is non-normative.</em></p>
<p>For each element of the <a class="tref internalDFN" title="list" href="#dfn-list">list</a> a new <a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifier</a>
@@ -3763,9 +3760,9 @@
algorithm returns the list head, which is either the the first allocated
<a class="tref internalDFN" title="blank-node-identifier" href="#dfn-blank-node-identifier">blank node identifier</a> or <code>rdf:nil</code> if the
<a class="tref internalDFN" title="list" href="#dfn-list">list</a> is empty.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-15">Algorithm</h4>
<p>The algorithm takes two inputs: an <a class="tref internalDFN" title="array" href="#dfn-array">array</a> <i>list</i>
@@ -3793,12 +3790,12 @@
<li>Return the first <a class="tref internalDFN" title="blank-node" href="#dfn-blank-node">blank node</a> from <i>bnodes</i> or
<code>rdf:nil</code> if <i>bnodes</i> is empty.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of List to RDF -->
- <section id="convert-from-rdf-algorithm">
+ <div class="section" id="convert-from-rdf-algorithm">
<h3><span class="secno">10.4 </span>Convert from RDF Algorithm</h3>
<p>This algorithm converts an <a class="tref internalDFN" title="rdf-dataset" href="#dfn-rdf-dataset">RDF dataset</a> consisting of a
@@ -3823,7 +3820,7 @@
structures be disallowed.</p>
</div></div>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-16">Overview</h4><p><em>This section is non-normative.</em></p>
<p>Iterate through each graph in the dataset, converting
@@ -3842,9 +3839,9 @@
<a class="tref externalDFN" title="lexical-form" href="http://www.w3.org/TR/rdf11-concepts/#dfn-lexical-form">lexical form</a>
as described in
<a class="sectionRef" href="#data-round-tripping">section 10.6 Data Round Tripping</a>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-16">Algorithm</h4>
<p>The algorithm takes two required inputs: an <a class="tref internalDFN" title="rdf-dataset" href="#dfn-rdf-dataset">RDF dataset</a> and a flag
@@ -3992,18 +3989,18 @@
</li>
<li>Return <i>result</i>.</li>
</ol>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Convert from RDF algorithm -->
- <section id="rdf-to-object-conversion">
+ <div class="section" id="rdf-to-object-conversion">
<h3><span class="secno">10.5 </span>RDF to Object Conversion</h3>
<p>This algorithm transforms an RDF literal to a JSON-LD <a class="tref internalDFN" title="value-object" href="#dfn-value-object">value object</a>
and a RDF blank node or <abbr title="Internationalized Resource Identifier">IRI</abbr> to an JSON-LD <a class="tref internalDFN" title="node-object" href="#dfn-node-object">node object</a>.</p>
- <section class="informative">
+ <div class="informative section">
<h4 id="overview-17">Overview</h4><p><em>This section is non-normative.</em></p>
<p><a class="tref internalDFN" title="rdf-literal" href="http://www.w3.org/TR/rdf11-concepts/#dfn-literal">RDF literals</a> are transformed to
@@ -4021,9 +4018,9 @@
<a class="tref externalDFN" title="lexical-form" href="http://www.w3.org/TR/rdf11-concepts/#dfn-lexical-form">lexical form</a>
as described in
<a class="sectionRef" href="#data-round-tripping">section 10.6 Data Round Tripping</a>.</p>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="algorithm-17">Algorithm</h4>
<p>This algorithm takes two required inputs: a <i>value</i> to be converted
@@ -4092,10 +4089,10 @@
</ol>
</li>
</ol>
- </section>
- </section>
-
- <section id="data-round-tripping">
+ </div>
+ </div>
+
+ <div class="section" id="data-round-tripping">
<h3><span class="secno">10.6 </span>Data Round Tripping</h3>
<p>When <a href="#convert-to-rdf-algorithm">converting JSON-LD to RDF</a>
@@ -4181,13 +4178,13 @@
There is no need to backslash-escape forward slashes in JSON-LD. To aid
interoperability between JSON-LD processors, forward slashes <em class="rfc2119" title="MUST NOT">MUST NOT</em> be
backslash-escaped.</p>
- </section>
+ </div>
<!-- end of Data Round Tripping -->
-</section>
-
-
-<section id="the-application-programming-interface">
+</div>
+
+
+<div class="section" id="the-application-programming-interface">
<!--OddPage-->
<h2><span class="secno">11. </span>The Application Programming Interface</h2>
@@ -4197,7 +4194,7 @@
work with. A conformant <a class="tref internalDFN" title="json-ld-api-implementation" href="#dfn-json-ld-api-implementation">JSON-LD API Implementation</a> <em class="rfc2119" title="MUST">MUST</em>
implement the entirety of the following API.</p>
- <section id="the-jsonldprocessor-interface">
+ <div class="section" id="the-jsonldprocessor-interface">
<h3><span class="secno">11.1 </span>The <a href="#idl-def-JsonLdProcessor" class="idlType"><code>JsonLdProcessor</code></a> Interface</h3>
<p>The <a href="#idl-def-JsonLdProcessor" class="idlType"><code>JsonLdProcessor</code></a> interface is the high-level programming structure
@@ -4215,7 +4212,7 @@
<span class="idlMethod"> <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-expand-void-JsonLdInput-input-JsonLdCallback-callback-JsonLdOptions-options">expand</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdInput" class="idlType"><code>JsonLdInput</code></a></span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a>?</span> <span class="idlParamName">options</span></span>);</span>
<span class="idlMethod"> <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-compact-void-JsonLdInput-input-JsonLdContext-context-JsonLdCallback-callback-JsonLdOptions-options">compact</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdInput" class="idlType"><code>JsonLdInput</code></a></span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdContext" class="idlType"><code>JsonLdContext</code></a>?</span> <span class="idlParamName">context</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a>?</span> <span class="idlParamName">options</span></span>);</span>
<span class="idlMethod"> <span class="idlMethType"><a>void</a></span> <span class="idlMethName"><a href="#widl-JsonLdProcessor-flatten-void-JsonLdInput-input-JsonLdContext-context-JsonLdCallback-callback-JsonLdOptions-options">flatten</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdInput" class="idlType"><code>JsonLdInput</code></a></span> <span class="idlParamName">input</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdContext" class="idlType"><code>JsonLdContext</code></a>?</span> <span class="idlParamName">context</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></span> <span class="idlParamName">callback</span></span>, <span class="idlParam">optional <span class="idlParamType"><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a>?</span> <span class="idlParamName">options</span></span>);</span>
-};</span></pre><section><h4 id="methods">Methods</h4><dl class="methods"><dt id="widl-JsonLdProcessor-compact-void-JsonLdInput-input-JsonLdContext-context-JsonLdCallback-callback-JsonLdOptions-options"><code>compact</code></dt><dd>
+};</span></pre><div class="section"><h4 id="methods">Methods</h4><dl class="methods"><dt id="widl-JsonLdProcessor-compact-void-JsonLdInput-input-JsonLdContext-context-JsonLdCallback-callback-JsonLdOptions-options"><code>compact</code></dt><dd>
<p><a href="#compaction">Compacts</a> the given <i>input</i> using the
<i>context</i> according to the steps in the
<a href="#compaction-algorithm">Compaction algorithm</a>:</p>
@@ -4344,7 +4341,7 @@
in expanded form.</td></tr><tr><td class="prmName">callback</td><td class="prmType"><code><a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a></code></td><td class="prmNullFalse">✘</td><td class="prmOptFalse">✘</td><td class="prmDesc">A callback that is called when processing completed successfully
on the given <code>input</code>, or a fatal error prevented
processing from completing.</td></tr><tr><td class="prmName">options</td><td class="prmType"><code><a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a></code></td><td class="prmNullTrue">✔</td><td class="prmOptTrue">✔</td><td class="prmDesc">A set of options to configure the used algorithms such. This allows, e.g.,
- to set the input document's base <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</td></tr></table><div><em>Return type: </em><code><a>void</a></code></div></dd></dl></section>
+ to set the input document's base <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>.</td></tr></table><div><em>Return type: </em><code><a>void</a></code></div></dd></dl></div>
<pre class="idl"><span class="idlTypedef" id="idl-def-JsonLdInput">typedef <span class="idlTypedefType">(<a>object</a> or <a>object[]</a> or <a>DOMString</a>)</span> <span class="idlTypedefID">JsonLdInput</span>;</span></pre><div class="idlTypedefDesc">
<p>The identifier <a href="#idl-def-JsonLdInput" class="idlType"><code>JsonLdInput</code></a> is used to refer to the
@@ -4355,59 +4352,59 @@
<p>The identifier <a href="#idl-def-JsonLdContext" class="idlType"><code>JsonLdContext</code></a> is used to refer to the
<span class="idlTypedefType">(object or DOMString)</span> type.</p>
</div>
- </section>
+ </div>
<!-- end of JsonLdProcessor -->
- <section id="callbacks">
+ <div class="section" id="callbacks">
<h3><span class="secno">11.2 </span>Callbacks</h3>
<p><a class="tref internalDFN" title="json-ld-api-implementation" href="#dfn-json-ld-api-implementation">JSON-LD API Implementations</a>
utilize callbacks in order to exchange information in an asynchronous manner
with applications. This section details the parameters of those callbacks.</p>
- <section>
+ <div class="section">
<h4 id="jsonldcallback">JsonLdCallback</h4>
<p>The <a href="#idl-def-JsonLdCallback" class="idlType"><code>JsonLdCallback</code></a> is called when an API method of
<a href="#idl-def-JsonLdProcessor" class="idlType"><code>JsonLdProcessor</code></a> has been completed, either successfully or
by a fatal error.</p>
- <pre class="idl"><span class="idlCallback" id="idl-def-JsonLdCallback">callback <span class="idlCallbackID">JsonLdCallback</span> = <span class="idlCallbackType"><a>void</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdError" class="idlType"><code>JsonLdError</code></a></span> <span class="idlParamName">error</span></span>, <span class="idlParam"><span class="idlParamType">(<a>object</a> or <a>object[]</a>)</span> <span class="idlParamName">document</span></span>);</span></pre><section><h5 id="callback-jsonldcallback-parameters">Callback <a class="idlType" href="#idl-def-JsonLdCallback"><code>JsonLdCallback</code></a> Parameters</h5><dl class="callback-members"><dt id="widl-JsonLdCallback-error"><code>error</code> of type <span class="idlMemberType"><a href="#idl-def-JsonLdError" class="idlType"><code>JsonLdError</code></a></span></dt><dd>If the value is <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, then no issue was detected
+ <pre class="idl"><span class="idlCallback" id="idl-def-JsonLdCallback">callback <span class="idlCallbackID">JsonLdCallback</span> = <span class="idlCallbackType"><a>void</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdError" class="idlType"><code>JsonLdError</code></a></span> <span class="idlParamName">error</span></span>, <span class="idlParam"><span class="idlParamType">(<a>object</a> or <a>object[]</a>)</span> <span class="idlParamName">document</span></span>);</span></pre><div class="section"><h5 id="callback-jsonldcallback-parameters">Callback <a class="idlType" href="#idl-def-JsonLdCallback"><code>JsonLdCallback</code></a> Parameters</h5><dl class="callback-members"><dt id="widl-JsonLdCallback-error"><code>error</code> of type <span class="idlMemberType"><a href="#idl-def-JsonLdError" class="idlType"><code>JsonLdError</code></a></span></dt><dd>If the value is <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, then no issue was detected
during processing. Otherwise, a processing error was detected and
- the details are contained within the <em>error</em> object.</dd><dt id="widl-JsonLdCallback-document"><code>document</code> of type <span class="idlMemberType"><a>(object or object[])</a></span></dt><dd>The processed JSON-LD document.</dd></dl></section>
- </section>
-
- <section>
+ the details are contained within the <em>error</em> object.</dd><dt id="widl-JsonLdCallback-document"><code>document</code> of type <span class="idlMemberType"><a>(object or object[])</a></span></dt><dd>The processed JSON-LD document.</dd></dl></div>
+ </div>
+
+ <div class="section">
<h4 id="loadcontextcallback">LoadContextCallback</h4>
<p>The <a href="#idl-def-LoadContextCallback" class="idlType"><code>LoadContextCallback</code></a> defines the callback that custom context loaders
have to implement to be used to retrieve remote contexts.</p>
- <pre class="idl"><span class="idlCallback" id="idl-def-LoadContextCallback">callback <span class="idlCallbackID">LoadContextCallback</span> = <span class="idlCallbackType"><a>void</a></span> (<span class="idlParam"><span class="idlParamType"><a>DOMString</a></span> <span class="idlParamName">url</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-ContextLoadedCallback" class="idlType"><code>ContextLoadedCallback</code></a></span> <span class="idlParamName">callback</span></span>);</span></pre><section><h5 id="callback-loadcontextcallback-parameters">Callback <a class="idlType" href="#idl-def-LoadContextCallback"><code>LoadContextCallback</code></a> Parameters</h5><dl class="callback-members"><dt id="widl-LoadContextCallback-url"><code>url</code> of type <span class="idlMemberType"><a>DOMString</a></span></dt><dd>The URL of the remote context to load.</dd><dt id="widl-LoadContextCallback-callback"><code>callback</code> of type <span class="idlMemberType"><a href="#idl-def-ContextLoadedCallback" class="idlType"><code>ContextLoadedCallback</code></a></span></dt><dd>The callback that is called when the remote context has been
+ <pre class="idl"><span class="idlCallback" id="idl-def-LoadContextCallback">callback <span class="idlCallbackID">LoadContextCallback</span> = <span class="idlCallbackType"><a>void</a></span> (<span class="idlParam"><span class="idlParamType"><a>DOMString</a></span> <span class="idlParamName">url</span></span>, <span class="idlParam"><span class="idlParamType"><a href="#idl-def-ContextLoadedCallback" class="idlType"><code>ContextLoadedCallback</code></a></span> <span class="idlParamName">callback</span></span>);</span></pre><div class="section"><h5 id="callback-loadcontextcallback-parameters">Callback <a class="idlType" href="#idl-def-LoadContextCallback"><code>LoadContextCallback</code></a> Parameters</h5><dl class="callback-members"><dt id="widl-LoadContextCallback-url"><code>url</code> of type <span class="idlMemberType"><a>DOMString</a></span></dt><dd>The URL of the remote context to load.</dd><dt id="widl-LoadContextCallback-callback"><code>callback</code> of type <span class="idlMemberType"><a href="#idl-def-ContextLoadedCallback" class="idlType"><code>ContextLoadedCallback</code></a></span></dt><dd>The callback that is called when the remote context has been
successfully loaded or an error preventing its loading has been
- detected.</dd></dl></section>
- </section>
-
- <section>
+ detected.</dd></dl></div>
+ </div>
+
+ <div class="section">
<h4 id="contextloadedcallback">ContextLoadedCallback</h4>
<p>The <a href="#idl-def-ContextLoadedCallback" class="idlType"><code>ContextLoadedCallback</code></a> is called in response to a call
of the <a href="#idl-def-LoadContextCallback" class="idlType"><code>LoadContextCallback</code></a>.</p>
- <pre class="idl"><span class="idlCallback" id="idl-def-ContextLoadedCallback">callback <span class="idlCallbackID">ContextLoadedCallback</span> = <span class="idlCallbackType"><a>void</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdError" class="idlType"><code>JsonLdError</code></a></span> <span class="idlParamName">error</span></span>, <span class="idlParam"><span class="idlParamType"><a>DOMString</a></span> <span class="idlParamName">url</span></span>, <span class="idlParam"><span class="idlParamType"><a>DOMString</a></span> <span class="idlParamName">context</span></span>);</span></pre><section><h5 id="callback-contextloadedcallback-parameters">Callback <a class="idlType" href="#idl-def-ContextLoadedCallback"><code>ContextLoadedCallback</code></a> Parameters</h5><dl class="callback-members"><dt id="widl-ContextLoadedCallback-error"><code>error</code> of type <span class="idlMemberType"><a href="#idl-def-JsonLdError" class="idlType"><code>JsonLdError</code></a></span></dt><dd>If the value is <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, then no issue was detected
+ <pre class="idl"><span class="idlCallback" id="idl-def-ContextLoadedCallback">callback <span class="idlCallbackID">ContextLoadedCallback</span> = <span class="idlCallbackType"><a>void</a></span> (<span class="idlParam"><span class="idlParamType"><a href="#idl-def-JsonLdError" class="idlType"><code>JsonLdError</code></a></span> <span class="idlParamName">error</span></span>, <span class="idlParam"><span class="idlParamType"><a>DOMString</a></span> <span class="idlParamName">url</span></span>, <span class="idlParam"><span class="idlParamType"><a>DOMString</a></span> <span class="idlParamName">context</span></span>);</span></pre><div class="section"><h5 id="callback-contextloadedcallback-parameters">Callback <a class="idlType" href="#idl-def-ContextLoadedCallback"><code>ContextLoadedCallback</code></a> Parameters</h5><dl class="callback-members"><dt id="widl-ContextLoadedCallback-error"><code>error</code> of type <span class="idlMemberType"><a href="#idl-def-JsonLdError" class="idlType"><code>JsonLdError</code></a></span></dt><dd>If the value is <a class="tref internalDFN" title="null" href="#dfn-null">null</a>, then no issue was detected
during processing. Otherwise, a processing issue was detected and
the details are contained within the <em>error</em> object. All
errors <em class="rfc2119" title="MUST">MUST</em> have a <a href="#idl-def-JsonLdErrorCode" class="idlType"><code>JsonLdErrorCode</code></a> of
<code class="error"><a href="#idl-def-JsonLdErrorCode.loading-remote-context-failed">loading remote context failed</a></code>.</dd><dt id="widl-ContextLoadedCallback-url"><code>url</code> of type <span class="idlMemberType"><a>DOMString</a></span></dt><dd>The final URL of the loaded JSON-LD context. This is important
- to handle HTTP redirects properly.</dd><dt id="widl-ContextLoadedCallback-context"><code>context</code> of type <span class="idlMemberType"><a>DOMString</a></span></dt><dd>The raw content of the retrieved JSON-LD context.</dd></dl></section>
- </section>
- </section>
+ to handle HTTP redirects properly.</dd><dt id="widl-ContextLoadedCallback-context"><code>context</code> of type <span class="idlMemberType"><a>DOMString</a></span></dt><dd>The raw content of the retrieved JSON-LD context.</dd></dl></div>
+ </div>
+ </div>
<!-- end of Callbacks -->
- <section id="data-structures">
+ <div class="section" id="data-structures">
<h3><span class="secno">11.3 </span>Data Structures</h3>
<p>This section describes datatype definitions used within the JSON-LD API.</p>
- <section>
+ <div class="section">
<h4 id="jsonldoptions">JsonLdOptions</h4>
<p>The <a href="#idl-def-JsonLdOptions" class="idlType"><code>JsonLdOptions</code></a> type is used to pass various options to the
<a href="#idl-def-JsonLdProcessor" class="idlType"><code>JsonLdProcessor</code></a> methods.</p>
@@ -4417,7 +4414,7 @@
<span class="idlMember"> <span class="idlMemberType"><a href="#idl-def-LoadContextCallback" class="idlType"><code>LoadContextCallback</code></a></span> <span class="idlMemberName"><a href="#widl-JsonLdOptions-loadContext">loadContext</a></span>;</span>
<span class="idlMember"> <span class="idlMemberType">(<a>object</a> or <a>DOMString</a>)</span> <span class="idlMemberName"><a href="#widl-JsonLdOptions-expandContext">expandContext</a></span> = <span class="idlMemberValue">null</span>;</span>
<span class="idlMember"> <span class="idlMemberType"><a>DOMString</a></span> <span class="idlMemberName"><a href="#widl-JsonLdOptions-processingMode">processingMode</a></span> = <span class="idlMemberValue">"json-ld-1.0"</span>;</span>
-};</span></pre><section><h5 id="dictionary-jsonldoptions-members">Dictionary <a class="idlType" href="#idl-def-JsonLdOptions"><code>JsonLdOptions</code></a> Members</h5><dl class="dictionary-members"><dt id="widl-JsonLdOptions-base"><code>base</code> of type <span class="idlMemberType"><a>DOMString</a></span></dt><dd>The base <abbr title="Internationalized Resource Identifier">IRI</abbr> to use when expanding or compacting the document. This overrides the value of
+};</span></pre><div class="section"><h5 id="dictionary-jsonldoptions-members">Dictionary <a class="idlType" href="#idl-def-JsonLdOptions"><code>JsonLdOptions</code></a> Members</h5><dl class="dictionary-members"><dt id="widl-JsonLdOptions-base"><code>base</code> of type <span class="idlMemberType"><a>DOMString</a></span></dt><dd>The base <abbr title="Internationalized Resource Identifier">IRI</abbr> to use when expanding or compacting the document. This overrides the value of
<em>input</em> if it is an <abbr title="Internationalized Resource Identifier">IRI</abbr>. If not specified and <em>input</em> is not
an <abbr title="Internationalized Resource Identifier">IRI</abbr>, the base <abbr title="Internationalized Resource Identifier">IRI</abbr> defaults to the current document <abbr title="Internationalized Resource Identifier">IRI</abbr> if in a browser context,
or the empty string if there is no document context.
@@ -4450,10 +4447,10 @@
not defined. Consequently, different implementations <em class="rfc2119" title="MAY">MAY</em> implement
different optimizations. Developers <em class="rfc2119" title="MUST NOT">MUST NOT</em> define modes beginning
with <code>json-ld</code> as they are reserved for future versions
- of this specification.</dd></dl></section>
- </section>
-
- <section>
+ of this specification.</dd></dl></div>
+ </div>
+
+ <div class="section">
<h4 id="jsonlderror">JsonLdError</h4>
<p>The <a href="#idl-def-JsonLdError" class="idlType"><code>JsonLdError</code></a> type is used to report processing errors
@@ -4462,13 +4459,13 @@
<pre class="idl"><span class="idlDictionary" id="idl-def-JsonLdError">dictionary <span class="idlDictionaryID">JsonLdError</span> {
<span class="idlMember"> <span class="idlMemberType"><a href="#idl-def-JsonLdErrorCode" class="idlType"><code>JsonLdErrorCode</code></a></span> <span class="idlMemberName"><a href="#widl-JsonLdError-code">code</a></span>;</span>
<span class="idlMember"> <span class="idlMemberType"><a>DOMString</a>?</span> <span class="idlMemberName"><a href="#widl-JsonLdError-message">message</a></span>;</span>
-};</span></pre><section><h5 id="dictionary-jsonlderror-members">Dictionary <a class="idlType" href="#idl-def-JsonLdError"><code>JsonLdError</code></a> Members</h5><dl class="dictionary-members"><dt id="widl-JsonLdError-code"><code>code</code> of type <span class="idlMemberType"><a href="#idl-def-JsonLdErrorCode" class="idlType"><code>JsonLdErrorCode</code></a></span></dt><dd>a string representing the particular error type, as described in
+};</span></pre><div class="section"><h5 id="dictionary-jsonlderror-members">Dictionary <a class="idlType" href="#idl-def-JsonLdError"><code>JsonLdError</code></a> Members</h5><dl class="dictionary-members"><dt id="widl-JsonLdError-code"><code>code</code> of type <span class="idlMemberType"><a href="#idl-def-JsonLdErrorCode" class="idlType"><code>JsonLdErrorCode</code></a></span></dt><dd>a string representing the particular error type, as described in
the various algorithms in this document.</dd><dt id="widl-JsonLdError-message"><code>message</code> of type <span class="idlMemberType"><a>DOMString</a></span>, nullable</dt><dd>an optional error message containing additional debugging information.
The specific contents of error messages are outside the scope of this
- specification.</dd></dl></section>
- </section>
-
- <section>
+ specification.</dd></dl></div>
+ </div>
+
+ <div class="section">
<h4 id="jsonlderrorcode">JsonLdErrorCode</h4>
<p>The <a href="#idl-def-JsonLdErrorCode" class="idlType"><code>JsonLdErrorCode</code></a> represents the collection of valid JSON-LD error
codes.</p>
@@ -4543,15 +4540,15 @@
are allowed in reverse property maps.</td></tr><tr><td><code id="idl-def-JsonLdErrorCode.invalid--reverse-value">invalid @reverse value</code></td><td>An invalid value for an <code>@reverse</code> member has been detected,
i.e., the value was not a <a class="tref internalDFN" title="json-object" href="#dfn-json-object">JSON object</a>.</td></tr><tr><td><code id="idl-def-JsonLdErrorCode.invalid-reverse-property-value">invalid reverse property value</code></td><td>An invalid value for a reverse property has been detected. The value of an inverse
property must be a <a class="tref internalDFN" title="node-object" href="#dfn-node-object">node object</a>.</td></tr></table>
- </section>
- </section>
+ </div>
+ </div>
<!-- end of Data Structures -->
-</section>
+</div>
<!-- end of The Application Programming Interfaces -->
-<section class="appendix informative" id="acknowledgements">
+<div class="appendix informative section" id="acknowledgements">
<!--OddPage-->
<h2><span class="secno">A. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
@@ -4569,13 +4566,13 @@
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>
-</section>
-
-
-
-<section id="references" class="appendix" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter">
+</div>
+
+
+
+<div id="references" class="appendix section" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter">
<!--OddPage-->
-<h2><span class="secno">B. </span>References</h2><section id="normative-references" typeof="bibo:Chapter" resource="#normative-references" rel="bibo:chapter"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-IEEE-754-1985">[IEEE-754-1985]</dt><dd rel="dcterms:requires">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>
+<h2><span class="secno">B. </span>References</h2><div class="section" id="normative-references" typeof="bibo:Chapter" resource="#normative-references" rel="bibo:chapter"><h3><span class="secno">B.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-IEEE-754-1985">[IEEE-754-1985]</dt><dd rel="dcterms:requires">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>
</dd><dt id="bib-JSON-LD">[JSON-LD]</dt><dd rel="dcterms:requires">Manu Sporny, Gregg Kellogg, Markus Lanthaler, Editors. <cite><a href="http://www.w3.org/TR/2013/WD-json-ld-20130411/">JSON-LD 1.0</a>.</cite> W3C Working Draft (work in progress). URL: <a href="http://www.w3.org/TR/2013/WD-json-ld-20130411/">http://www.w3.org/TR/2013/WD-json-ld-20130411/</a>. The latest edition is available at <a href="http://www.w3.org/TR/json-ld/">http://www.w3.org/TR/json-ld/</a>
</dd><dt id="bib-RDF-MT">[RDF-MT]</dt><dd rel="dcterms:requires">Patrick Hayes. <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210"><cite>RDF Semantics</cite></a>. 10 February 2004. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2004/REC-rdf-mt-20040210">http://www.w3.org/TR/2004/REC-rdf-mt-20040210</a>
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
@@ -4585,9 +4582,9 @@
</dd><dt id="bib-RFC5988">[RFC5988]</dt><dd rel="dcterms:requires">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>
</dd><dt id="bib-WEBIDL">[WEBIDL]</dt><dd rel="dcterms:requires">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>
</dd><dt id="bib-XMLSCHEMA11-2">[XMLSCHEMA11-2]</dt><dd rel="dcterms:requires">Henry S. Thompson et al. <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/"><cite>W3C XML Schema Definition Language (XSD) 1.1 Part 2: Datatypes</cite></a>. 5 April 2012. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/">http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/</a>
-</dd></dl></section><section id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:chapter"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-BCP47">[BCP47]</dt><dd rel="dcterms:references">A. Phillips; M. Davis. <a href="http://tools.ietf.org/html/bcp47"><cite>Tags for Identifying Languages</cite></a>. September 2009. IETF Best Current Practice. URL: <a href="http://tools.ietf.org/html/bcp47">http://tools.ietf.org/html/bcp47</a>
+</dd></dl></div><div class="section" id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:chapter"><h3><span class="secno">B.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-BCP47">[BCP47]</dt><dd rel="dcterms:references">A. Phillips; M. Davis. <a href="http://tools.ietf.org/html/bcp47"><cite>Tags for Identifying Languages</cite></a>. September 2009. IETF Best Current Practice. URL: <a href="http://tools.ietf.org/html/bcp47">http://tools.ietf.org/html/bcp47</a>
</dd><dt id="bib-ECMA-262">[ECMA-262]</dt><dd rel="dcterms:references"><a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm"><cite>ECMAScript Language Specification, Edition 5.1</cite></a>. June 2011. URL: <a href="http://www.ecma-international.org/publications/standards/Ecma-262.htm">http://www.ecma-international.org/publications/standards/Ecma-262.htm</a>
</dd><dt id="bib-JSON-LD-TESTS">[JSON-LD-TESTS]</dt><dd rel="dcterms:references"><cite><a href="http://www.w3.org/2013/json-ld-tests/">JSON-LD 1.0 Test Suite</a></cite>. W3C Test Suite (work in progress). URL: <a href="http://www.w3.org/2013/json-ld-tests/">http://www.w3.org/2013/json-ld-tests/</a>
</dd><dt id="bib-RDF11-CONCEPTS">[RDF11-CONCEPTS]</dt><dd rel="dcterms:references">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>
</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd rel="dcterms:references">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>
-</dd></dl></section></section></body></html>
+</dd></dl></div></div></body></html>
--- a/spec/WD/20130411/json-ld/index.html Fri Apr 05 17:14:56 2013 +0200
+++ b/spec/WD/20130411/json-ld/index.html Fri Apr 05 17:31:25 2013 +0200
@@ -1,6 +1,6 @@
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.1//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-2.dtd'>
-<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" prefix='bibo: http://purl.org/ontology/bibo/' typeof="bibo:Document">
+<html dir="ltr" xmlns="http://www.w3.org/1999/xhtml" typeof="bibo:Document">
<head>
<title>JSON-LD 1.0</title>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
@@ -9,7 +9,7 @@
table, thead, tr, td { padding: 5px; border-width: 1px; border-spacing: 0px; border-style: solid; border-collapse: collapse; }
.atrisk-head { font-style: italic; }
</style>
-<style>
+<style type="text/css">
/* --- INLINES --- */
em.rfc2119 {
text-transform: lowercase;
@@ -120,7 +120,7 @@
.section dl.attrs dd, .section dl.eldef dd {
margin-bottom: 0;
}
-</style><style>/* --- EXAMPLES --- */
+</style><style type="text/css">/* --- EXAMPLES --- */
div.example-title {
min-width: 7.5em;
color: #b9ab2d;
@@ -152,7 +152,7 @@
aside.example div.example div.example-title {
color: #999;
}
-</style><style>/* --- ISSUES/NOTES --- */
+</style><style type="text/css">/* --- ISSUES/NOTES --- */
div.issue-title, div.note-title {
padding-right: 1em;
min-width: 7.5em;
@@ -192,9 +192,6 @@
</style><link rel="stylesheet" href="http://www.w3.org/StyleSheets/TR/W3C-WD" />
-<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
-
-<!--[if lt IE 9]><script src='http://www.w3.org/2008/site/js/html5shiv.js'></script><![endif]-->
</head>
<body><div class="head">
@@ -228,11 +225,11 @@
<dt>Editors:</dt>
- <dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://manu.sporny.org/">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
+ <dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="http://manu.sporny.org/">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://digitalbazaar.com/">Digital Bazaar</a></span>
</dd>
-<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">Gregg Kellogg</a>, <a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">Kellogg Associates</a></span>
+<dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Gregg Kellogg" href="http://greggkellogg.net/">Gregg Kellogg</a>, <a rel="foaf:workplaceHomepage" href="http://kellogg-assoc.com/">Kellogg Associates</a></span>
</dd>
-<dd rel="bibo:editor" inlist=""><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>, <a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">Graz University of Technology</a></span>
+<dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Markus Lanthaler" href="http://www.markus-lanthaler.com/">Markus Lanthaler</a>, <a rel="foaf:workplaceHomepage" href="http://www.tugraz.at/">Graz University of Technology</a></span>
</dd>
@@ -278,7 +275,7 @@
<hr />
</div>
-<section id="abstract" class="introductory" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter"><h2>Abstract</h2>
+<div id="abstract" class="introductory section" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" resource="#abstract" rel="bibo:chapter"><h2>Abstract</h2>
<p>JSON has proven to be a highly useful object serialization and messaging
format. This specification defines JSON-LD, a JSON-based format to serialize
Linked Data. The syntax is designed to not disturb already deployed systems
@@ -286,7 +283,7 @@
It 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.</p>
-</section><section id="sotd" class="introductory" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter"><h2>Status of This Document</h2>
+</div><div id="sotd" class="introductory section" typeof="bibo:Chapter" resource="#sotd" rel="bibo:chapter"><h2>Status of This Document</h2>
@@ -368,11 +365,11 @@
-</section><section id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#how-to-read-this-document" class="tocxref"><span class="secno">1.1 </span>How to Read this Document</a></li></ul></li><li class="tocline"><a href="#design-goals-and-rationale" class="tocxref"><span class="secno">2. </span>Design Goals and Rationale</a></li><li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">3. </span>Terminology</a><ul class="toc"><li class="tocline"><a href="#general-terminology" class="tocxref"><span class="secno">3.1 </span>General Terminology</a></li><li class="tocline"><a href="#syntax-tokens-and-keywords" class="tocxref"><span class="secno">3.2 </span>Syntax Tokens and Keywords</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">4. </span>Conformance</a></li><li class="tocline"><a href="#basic-concepts" class="tocxref"><span class="secno">5. </span>Basic Concepts</a><ul class="toc"><li class="tocline"><a href="#the-context" class="tocxref"><span class="secno">5.1 </span>The Context</a></li><li class="tocline"><a href="#iris" class="tocxref"><span class="secno">5.2 </span>IRIs</a></li><li class="tocline"><a href="#node-identifiers" class="tocxref"><span class="secno">5.3 </span>Node Identifiers</a></li><li class="tocline"><a href="#specifying-the-type" class="tocxref"><span class="secno">5.4 </span>Specifying the Type</a></li></ul></li><li class="tocline"><a href="#advanced-concepts" class="tocxref"><span class="secno">6. </span>Advanced Concepts</a><ul class="toc"><li class="tocline"><a href="#base-iri" class="tocxref"><span class="secno">6.1 </span>Base <abbr title="Internationalized Resource Identifier">IRI</abbr></a></li><li class="tocline"><a href="#default-vocabulary" class="tocxref"><span class="secno">6.2 </span>Default Vocabulary</a></li><li class="tocline"><a href="#compact-iris" class="tocxref"><span class="secno">6.3 </span>Compact IRIs</a></li><li class="tocline"><a href="#typed-values" class="tocxref"><span class="secno">6.4 </span>Typed Values</a></li><li class="tocline"><a href="#type-coercion" class="tocxref"><span class="secno">6.5 </span>Type Coercion</a></li><li class="tocline"><a href="#embedding" class="tocxref"><span class="secno">6.6 </span>Embedding</a></li><li class="tocline"><a href="#advanced-context-usage" class="tocxref"><span class="secno">6.7 </span>Advanced Context Usage</a></li><li class="tocline"><a href="#interpreting-json-as-json-ld" class="tocxref"><span class="secno">6.8 </span>Interpreting JSON as JSON-LD</a></li><li class="tocline"><a href="#string-internationalization" class="tocxref"><span class="secno">6.9 </span>String Internationalization</a></li><li class="tocline"><a href="#iri-expansion-within-a-context" class="tocxref"><span class="secno">6.10 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion within a Context</a></li><li class="tocline"><a href="#sets-and-lists" class="tocxref"><span class="secno">6.11 </span>Sets and Lists</a></li><li class="tocline"><a href="#reverse-properties" class="tocxref"><span class="secno">6.12 </span>Reverse Properties</a></li><li class="tocline"><a href="#named-graphs" class="tocxref"><span class="secno">6.13 </span>Named Graphs</a></li><li class="tocline"><a href="#identifying-blank-nodes" class="tocxref"><span class="secno">6.14 </span>Identifying Blank Nodes</a></li><li class="tocline"><a href="#aliasing-keywords" class="tocxref"><span class="secno">6.15 </span>Aliasing Keywords</a></li><li class="tocline"><a href="#data-indexing" class="tocxref"><span class="secno">6.16 </span>Data Indexing</a></li><li class="tocline"><a href="#expanded-document-form" class="tocxref"><span class="secno">6.17 </span>Expanded Document Form</a></li><li class="tocline"><a href="#compact-document-form" class="tocxref"><span class="secno">6.18 </span>Compact Document Form</a></li><li class="tocline"><a href="#flattened-document-form" class="tocxref"><span class="secno">6.19 </span>Flattened Document Form</a></li><li class="tocline"><a href="#embedding-json-ld-in-html-documents" class="tocxref"><span class="secno">6.20 </span>Embedding JSON-LD in HTML Documents</a></li></ul></li><li class="tocline"><a href="#data-model" class="tocxref"><span class="secno">A. </span>Data Model</a></li><li class="tocline"><a href="#json-ld-grammar" class="tocxref"><span class="secno">B. </span>JSON-LD Grammar</a><ul class="toc"><li class="tocline"><a href="#terms" class="tocxref"><span class="secno">B.1 </span>Terms</a></li><li class="tocline"><a href="#node-objects" class="tocxref"><span class="secno">B.2 </span>Node Objects</a></li><li class="tocline"><a href="#value-objects" class="tocxref"><span class="secno">B.3 </span>Value Objects</a></li><li class="tocline"><a href="#lists-and-sets" class="tocxref"><span class="secno">B.4 </span>Lists and Sets</a></li><li class="tocline"><a href="#language-maps" class="tocxref"><span class="secno">B.5 </span>Language Maps</a></li><li class="tocline"><a href="#index-maps" class="tocxref"><span class="secno">B.6 </span>Index Maps</a></li><li class="tocline"><a href="#context-definitions" class="tocxref"><span class="secno">B.7 </span>Context Definitions</a></li></ul></li><li class="tocline"><a href="#relationship-to-rdf" class="tocxref"><span class="secno">C. </span>Relationship to RDF</a><ul class="toc"><li class="tocline"><a href="#transformation-from-json-ld-to-rdf" class="tocxref"><span class="secno">C.1 </span>Transformation from JSON-LD to RDF</a></li></ul></li><li class="tocline"><a href="#relationship-to-other-linked-data-formats" class="tocxref"><span class="secno">D. </span>Relationship to Other Linked Data Formats</a><ul class="toc"><li class="tocline"><a href="#turtle" class="tocxref"><span class="secno">D.1 </span>Turtle</a></li><li class="tocline"><a href="#rdfa" class="tocxref"><span class="secno">D.2 </span>RDFa</a></li><li class="tocline"><a href="#microformats" class="tocxref"><span class="secno">D.3 </span>Microformats</a></li><li class="tocline"><a href="#microdata" class="tocxref"><span class="secno">D.4 </span>Microdata</a></li></ul></li><li class="tocline"><a href="#iana-considerations" class="tocxref"><span class="secno">E. </span>IANA Considerations</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">F. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">G. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">G.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">G.2 </span>Informative references</a></li></ul></li></ul></section>
-
-
-
-<section class="informative" id="introduction">
+</div><div class="section" id="toc"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a><ul class="toc"><li class="tocline"><a href="#how-to-read-this-document" class="tocxref"><span class="secno">1.1 </span>How to Read this Document</a></li></ul></li><li class="tocline"><a href="#design-goals-and-rationale" class="tocxref"><span class="secno">2. </span>Design Goals and Rationale</a></li><li class="tocline"><a href="#terminology" class="tocxref"><span class="secno">3. </span>Terminology</a><ul class="toc"><li class="tocline"><a href="#general-terminology" class="tocxref"><span class="secno">3.1 </span>General Terminology</a></li><li class="tocline"><a href="#syntax-tokens-and-keywords" class="tocxref"><span class="secno">3.2 </span>Syntax Tokens and Keywords</a></li></ul></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">4. </span>Conformance</a></li><li class="tocline"><a href="#basic-concepts" class="tocxref"><span class="secno">5. </span>Basic Concepts</a><ul class="toc"><li class="tocline"><a href="#the-context" class="tocxref"><span class="secno">5.1 </span>The Context</a></li><li class="tocline"><a href="#iris" class="tocxref"><span class="secno">5.2 </span>IRIs</a></li><li class="tocline"><a href="#node-identifiers" class="tocxref"><span class="secno">5.3 </span>Node Identifiers</a></li><li class="tocline"><a href="#specifying-the-type" class="tocxref"><span class="secno">5.4 </span>Specifying the Type</a></li></ul></li><li class="tocline"><a href="#advanced-concepts" class="tocxref"><span class="secno">6. </span>Advanced Concepts</a><ul class="toc"><li class="tocline"><a href="#base-iri" class="tocxref"><span class="secno">6.1 </span>Base <abbr title="Internationalized Resource Identifier">IRI</abbr></a></li><li class="tocline"><a href="#default-vocabulary" class="tocxref"><span class="secno">6.2 </span>Default Vocabulary</a></li><li class="tocline"><a href="#compact-iris" class="tocxref"><span class="secno">6.3 </span>Compact IRIs</a></li><li class="tocline"><a href="#typed-values" class="tocxref"><span class="secno">6.4 </span>Typed Values</a></li><li class="tocline"><a href="#type-coercion" class="tocxref"><span class="secno">6.5 </span>Type Coercion</a></li><li class="tocline"><a href="#embedding" class="tocxref"><span class="secno">6.6 </span>Embedding</a></li><li class="tocline"><a href="#advanced-context-usage" class="tocxref"><span class="secno">6.7 </span>Advanced Context Usage</a></li><li class="tocline"><a href="#interpreting-json-as-json-ld" class="tocxref"><span class="secno">6.8 </span>Interpreting JSON as JSON-LD</a></li><li class="tocline"><a href="#string-internationalization" class="tocxref"><span class="secno">6.9 </span>String Internationalization</a></li><li class="tocline"><a href="#iri-expansion-within-a-context" class="tocxref"><span class="secno">6.10 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion within a Context</a></li><li class="tocline"><a href="#sets-and-lists" class="tocxref"><span class="secno">6.11 </span>Sets and Lists</a></li><li class="tocline"><a href="#reverse-properties" class="tocxref"><span class="secno">6.12 </span>Reverse Properties</a></li><li class="tocline"><a href="#named-graphs" class="tocxref"><span class="secno">6.13 </span>Named Graphs</a></li><li class="tocline"><a href="#identifying-blank-nodes" class="tocxref"><span class="secno">6.14 </span>Identifying Blank Nodes</a></li><li class="tocline"><a href="#aliasing-keywords" class="tocxref"><span class="secno">6.15 </span>Aliasing Keywords</a></li><li class="tocline"><a href="#data-indexing" class="tocxref"><span class="secno">6.16 </span>Data Indexing</a></li><li class="tocline"><a href="#expanded-document-form" class="tocxref"><span class="secno">6.17 </span>Expanded Document Form</a></li><li class="tocline"><a href="#compact-document-form" class="tocxref"><span class="secno">6.18 </span>Compact Document Form</a></li><li class="tocline"><a href="#flattened-document-form" class="tocxref"><span class="secno">6.19 </span>Flattened Document Form</a></li><li class="tocline"><a href="#embedding-json-ld-in-html-documents" class="tocxref"><span class="secno">6.20 </span>Embedding JSON-LD in HTML Documents</a></li></ul></li><li class="tocline"><a href="#data-model" class="tocxref"><span class="secno">A. </span>Data Model</a></li><li class="tocline"><a href="#json-ld-grammar" class="tocxref"><span class="secno">B. </span>JSON-LD Grammar</a><ul class="toc"><li class="tocline"><a href="#terms" class="tocxref"><span class="secno">B.1 </span>Terms</a></li><li class="tocline"><a href="#node-objects" class="tocxref"><span class="secno">B.2 </span>Node Objects</a></li><li class="tocline"><a href="#value-objects" class="tocxref"><span class="secno">B.3 </span>Value Objects</a></li><li class="tocline"><a href="#lists-and-sets" class="tocxref"><span class="secno">B.4 </span>Lists and Sets</a></li><li class="tocline"><a href="#language-maps" class="tocxref"><span class="secno">B.5 </span>Language Maps</a></li><li class="tocline"><a href="#index-maps" class="tocxref"><span class="secno">B.6 </span>Index Maps</a></li><li class="tocline"><a href="#context-definitions" class="tocxref"><span class="secno">B.7 </span>Context Definitions</a></li></ul></li><li class="tocline"><a href="#relationship-to-rdf" class="tocxref"><span class="secno">C. </span>Relationship to RDF</a><ul class="toc"><li class="tocline"><a href="#transformation-from-json-ld-to-rdf" class="tocxref"><span class="secno">C.1 </span>Transformation from JSON-LD to RDF</a></li></ul></li><li class="tocline"><a href="#relationship-to-other-linked-data-formats" class="tocxref"><span class="secno">D. </span>Relationship to Other Linked Data Formats</a><ul class="toc"><li class="tocline"><a href="#turtle" class="tocxref"><span class="secno">D.1 </span>Turtle</a></li><li class="tocline"><a href="#rdfa" class="tocxref"><span class="secno">D.2 </span>RDFa</a></li><li class="tocline"><a href="#microformats" class="tocxref"><span class="secno">D.3 </span>Microformats</a></li><li class="tocline"><a href="#microdata" class="tocxref"><span class="secno">D.4 </span>Microdata</a></li></ul></li><li class="tocline"><a href="#iana-considerations" class="tocxref"><span class="secno">E. </span>IANA Considerations</a></li><li class="tocline"><a href="#acknowledgements" class="tocxref"><span class="secno">F. </span>Acknowledgements</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">G. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">G.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">G.2 </span>Informative references</a></li></ul></li></ul></div>
+
+
+
+<div class="informative section" id="introduction">
<!--OddPage-->
<h2><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
@@ -418,7 +415,7 @@
to reshape documents into a deterministic structure which simplifies their
processing.</p>
- <section class="informative" id="how-to-read-this-document">
+ <div class="informative section" id="how-to-read-this-document">
<h3><span class="secno">1.1 </span>How to Read this Document</h3><p><em>This section is non-normative.</em></p>
<p>This document is a detailed specification for a serialization of Linked
@@ -440,10 +437,10 @@
<p>To understand the basics in this specification you must first be familiar with
JSON, which is detailed in [<cite><a class="bibref" href="#bib-RFC4627">RFC4627</a></cite>].</p>
- </section>
-</section>
-
-<section class="informative" id="design-goals-and-rationale">
+ </div>
+</div>
+
+<div class="informative section" id="design-goals-and-rationale">
<!--OddPage-->
<h2><span class="secno">2. </span>Design Goals and Rationale</h2><p><em>This section is non-normative.</em></p>
@@ -480,14 +477,14 @@
a design goal, it is not always possible without adding great complexity
to the language. We should focus on simplicity when possible.</dd>
</dl>
-</section>
-
-<section class="normative" id="terminology">
+</div>
+
+<div class="normative section" id="terminology">
<!--OddPage-->
<h2><span class="secno">3. </span>Terminology</h2>
- <section class="normative" id="general-terminology">
+ <div class="normative section" id="general-terminology">
<h3><span class="secno">3.1 </span>General Terminology</h3>
<p>This document uses the following terms as defined in JSON [<cite><a class="bibref" href="#bib-RFC4627">RFC4627</a></cite>]. Refer
@@ -528,9 +525,9 @@
<code>@set</code> is set to <a class="tref internalDFN" title="null" href="#dfn-null">null</a> in expanded form, then
the entire <a class="tref internalDFN" title="json-object" href="#dfn-json-object">JSON object</a> is ignored.</dd>
</dl>
- </section>
-
- <section class="normative" id="syntax-tokens-and-keywords">
+ </div>
+
+ <div class="normative section" id="syntax-tokens-and-keywords">
<h3><span class="secno">3.2 </span>Syntax Tokens and Keywords</h3>
<p>JSON-LD specifies a number of syntax tokens and <dfn title="keyword" id="dfn-keyword">keywords</dfn>
@@ -590,10 +587,10 @@
</dl>
<p>All keys, <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keywords</a>, and values in JSON-LD are case-sensitive.</p>
- </section>
-</section>
-
-<section class="normative" id="conformance">
+ </div>
+</div>
+
+<div class="normative section" id="conformance">
<!--OddPage-->
<h2><span class="secno">4. </span>Conformance</h2>
@@ -613,9 +610,9 @@
<p>The key words <em class="rfc2119" title="MUST">MUST</em>, <em class="rfc2119" title="MUST NOT">MUST NOT</em>, <em class="rfc2119" title="REQUIRED">REQUIRED</em>, <em class="rfc2119" title="SHALL">SHALL</em>, <em class="rfc2119" title="SHALL NOT">SHALL NOT</em>, <em class="rfc2119" title="SHOULD">SHOULD</em>, <em class="rfc2119" title="SHOULD NOT">SHOULD NOT</em>,
<em class="rfc2119" title="RECOMMENDED">RECOMMENDED</em>, <em class="rfc2119" title="NOT RECOMMENDED">NOT RECOMMENDED</em>, <em class="rfc2119" title="MAY">MAY</em>, and <em class="rfc2119" title="OPTIONAL">OPTIONAL</em> in this specification have the
meaning defined in [<cite><a class="bibref" href="#bib-RFC2119">RFC2119</a></cite>].</p>
-</section>
-
-<section class="informative" id="basic-concepts">
+</div>
+
+<div class="informative section" id="basic-concepts">
<!--OddPage-->
<h2><span class="secno">5. </span>Basic Concepts</h2><p><em>This section is non-normative.</em></p>
@@ -664,7 +661,7 @@
to work with for human developers. To address this issue, JSON-LD introduces the notion
of a <a class="tref internalDFN" title="context" href="#dfn-context">context</a> as described in the next section.</p>
- <section class="informative" id="the-context">
+ <div class="informative section" id="the-context">
<h3><span class="secno">5.1 </span>The Context</h3><p><em>This section is non-normative.</em></p>
<p>Simply speaking, a <dfn title="context" id="dfn-context">context</dfn> is used to map <a class="tref internalDFN" title="term" href="#dfn-term">terms</a> to
@@ -759,9 +756,9 @@
"homepage": "http://manu.sporny.org/",
"image": "http://manu.sporny.org/images/manu.png"
}</pre></div>
- </section>
-
-<section class="informative" id="iris">
+ </div>
+
+<div class="informative section" id="iris">
<h3><span class="secno">5.2 </span>IRIs</h3><p><em>This section is non-normative.</em></p>
<p><a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a> (Internationalized Resource Identifiers
@@ -866,9 +863,9 @@
are <a class="tref internalDFN" title="coercion" href="#dfn-coercion">coercion</a> rules that contain a <code>@type</code> key that is
set to a value of <code>@id</code> or <code>@vocab</code>.</li>
</ol>
-</section>
-
-<section class="informative" id="node-identifiers">
+</div>
+
+<div class="informative section" id="node-identifiers">
<h3><span class="secno">5.3 </span>Node Identifiers</h3><p><em>This section is non-normative.</em></p>
<p>To be able to externally reference <a class="tref internalDFN" title="node" href="#dfn-node">nodes</a>
@@ -896,9 +893,9 @@
<p>The example above contains a <a class="tref internalDFN" title="node-object" href="#dfn-node-object">node object</a> identified by the <abbr title="Internationalized Resource Identifier">IRI</abbr>
<code>http://me.markus-lanthaler.com/</code>.</p>
-</section>
-
-<section class="informative" id="specifying-the-type">
+</div>
+
+<div class="informative section" id="specifying-the-type">
<h3><span class="secno">5.4 </span>Specifying the Type</h3><p><em>This section is non-normative.</em></p>
<p>The type of a particular node can be specified using the <code>@type</code>
@@ -932,10 +929,10 @@
<span class="diff">"@type": [ "Restaurant", "Brewery" ]</span>,
...
}</pre></div>
-</section>
-</section>
-
-<section class="normative" id="advanced-concepts">
+</div>
+</div>
+
+<div class="normative section" id="advanced-concepts">
<!--OddPage-->
<h2><span class="secno">6. </span>Advanced Concepts</h2>
@@ -944,7 +941,7 @@
the core functionality described above. The following section describes this
advanced functionality in more detail.</p>
-<section class="informative" id="base-iri">
+<div class="informative section" id="base-iri">
<h3><span class="secno">6.1 </span>Base <abbr title="Internationalized Resource Identifier">IRI</abbr></h3><p><em>This section is non-normative.</em></p>
<div class="issue atrisk"><div class="issue-title"><span>Feature at Risk 1</span>: @base keyword</div><div class="atrisk">
@@ -991,9 +988,9 @@
"@id": "",
"label": "Just a simple document"
}</pre></div>
-</section>
-
-<section class="informative" id="default-vocabulary">
+</div>
+
+<div class="informative section" id="default-vocabulary">
<h3><span class="secno">6.2 </span>Default Vocabulary</h3><p><em>This section is non-normative.</em></p>
<p>At times, all properties and types may come from the same vocabulary. JSON-LD's
@@ -1030,9 +1027,9 @@
"name": "Brew Eats",
<span class="diff">"databaseId"</span>: "23987520"
}</pre></div>
-</section>
-
-<section class="informative" id="compact-iris">
+</div>
+
+<div class="informative section" id="compact-iris">
<h3><span class="secno">6.3 </span>Compact IRIs</h3><p><em>This section is non-normative.</em></p>
<p>A <dfn title="compact-iri" id="dfn-compact-iri">compact <abbr title="Internationalized Resource Identifier">IRI</abbr></dfn> is a way of expressing an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>
@@ -1093,9 +1090,9 @@
"foaf:homepage": "http://www.markus-lanthaler.com/",
"picture": "http://twitter.com/account/profile_image/markuslanthaler"
}</pre></div>
-</section>
-
-<section class="informative" id="typed-values">
+</div>
+
+<div class="informative section" id="typed-values">
<h3><span class="secno">6.4 </span>Typed Values</h3><p><em>This section is non-normative.</em></p>
<p>
@@ -1234,9 +1231,9 @@
</tbody>
</table>
-</section>
-
-<section class="informative" id="type-coercion">
+</div>
+
+<div class="informative section" id="type-coercion">
<h3><span class="secno">6.5 </span>Type Coercion</h3><p><em>This section is non-normative.</em></p>
<p>JSON-LD supports the coercion of values to particular data types.
@@ -1377,9 +1374,9 @@
great deal of confusion among developers attempting to understand the JSON-LD document.</p></div>
-</section>
-
-<section class="informative" id="embedding">
+</div>
+
+<div class="informative section" id="embedding">
<h3><span class="secno">6.6 </span>Embedding</h3><p><em>This section is non-normative.</em></p>
<p><dfn title="embedding" id="dfn-embedding">Embedding</dfn> is a JSON-LD feature that allows an author to
@@ -1403,9 +1400,9 @@
<p>
A <a class="tref internalDFN" title="node-object" href="#dfn-node-object">node object</a>, like the one used above, may be used in
any value position in the body of a JSON-LD document.</p>
-</section>
-
-<section class="informative" id="advanced-context-usage">
+</div>
+
+<div class="informative section" id="advanced-context-usage">
<h3><span class="secno">6.7 </span>Advanced Context Usage</h3><p><em>This section is non-normative.</em></p>
<p>Section <a href="#the-context" class="sec-ref"><span class="secno">5.1</span> <span class="sec-title">The Context</span></a> introduced the basics of what makes
@@ -1503,9 +1500,9 @@
they are ignored unless mapped to an <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a>. Furthermore, the use of
empty <a class="tref internalDFN" title="term" href="#dfn-term">terms</a> (<code>""</code>) is not allowed as
not all programming languages are able to handle empty JSON keys.</p></div>
-</section>
-
-<section class="normative" id="interpreting-json-as-json-ld">
+</div>
+
+<div class="normative section" id="interpreting-json-as-json-ld">
<h3><span class="secno">6.8 </span>Interpreting JSON as JSON-LD</h3>
<p>Ordinary JSON documents can be interpreted as JSON-LD by referencing a JSON-LD
@@ -1554,9 +1551,9 @@
contexts, within the body of the document. Contexts linked via a
<code>http://www.w3.org/ns/json-ld#context</code> HTTP Link Header <em class="rfc2119" title="MUST">MUST</em> be
ignored for such documents.</p>
-</section>
-
-<section class="informative" id="string-internationalization">
+</div>
+
+<div class="informative section" id="string-internationalization">
<h3><span class="secno">6.9 </span>String Internationalization</h3><p><em>This section is non-normative.</em></p>
<p>At times, it is important to annotate a <a class="tref internalDFN" title="string" href="#dfn-string">string</a>
@@ -1692,9 +1689,9 @@
"speciality": "手裏剣"
}</pre></div>
-</section>
-
-<section class="informative" id="iri-expansion-within-a-context">
+</div>
+
+<div class="informative section" id="iri-expansion-within-a-context">
<h3><span class="secno">6.10 </span><abbr title="Internationalized Resource Identifier">IRI</abbr> Expansion within a Context</h3><p><em>This section is non-normative.</em></p>
<p>In general, normal <abbr title="Internationalized Resource Identifier">IRI</abbr> expansion rules apply
anywhere an <abbr title="Internationalized Resource Identifier">IRI</abbr> is expected (see <a class="sectionRef sec-ref" href="#iris">section 5.2 IRIs</a>). Within
@@ -1834,9 +1831,9 @@
},
...
}</pre></div>
-</section>
-
-<section class="informative" id="sets-and-lists">
+</div>
+
+<div class="informative section" id="sets-and-lists">
<h3><span class="secno">6.11 </span>Sets and Lists</h3><p><em>This section is non-normative.</em></p>
<p>A JSON-LD author can express multiple values in a compact way by using
@@ -1975,9 +1972,9 @@
JSON-LD documents easier as the data is always in array form, even if the
array only contains a single value.</p>
-</section>
-
-<section class="informative" id="reverse-properties">
+</div>
+
+<div class="informative section" id="reverse-properties">
<h3><span class="secno">6.12 </span>Reverse Properties</h3><p><em>This section is non-normative.</em></p>
<div class="issue atrisk"><div class="issue-title"><span>Feature at Risk 2</span>: Reverse properties</div><div class="atrisk">
@@ -2061,10 +2058,10 @@
}
]
}</pre></div>
-</section>
-
-
-<section class="informative" id="named-graphs">
+</div>
+
+
+<div class="informative section" id="named-graphs">
<h3><span class="secno">6.13 </span>Named Graphs</h3><p><em>This section is non-normative.</em></p>
<p>At times, it is necessary to make statements about a <a class="tref internalDFN" title="json-ld-graph" href="#dfn-json-ld-graph">JSON-LD graph</a>
@@ -2225,9 +2222,9 @@
}
]</pre></div>
-</section>
-
-<section class="informative" id="identifying-blank-nodes">
+</div>
+
+<div class="informative section" id="identifying-blank-nodes">
<h3><span class="secno">6.14 </span>Identifying Blank Nodes</h3><p><em>This section is non-normative.</em></p>
<p>At times, it becomes necessary to be able to express information without
@@ -2262,9 +2259,9 @@
If a developer finds that they refer to the <a class="tref internalDFN" title="blank-node" href="#dfn-blank-node">blank node</a> more than once,
they should consider naming the node using a dereferenceable <a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> so that
it can also be referenced from other documents.</p>
-</section>
-
-<section class="informative" id="aliasing-keywords">
+</div>
+
+<div class="informative section" id="aliasing-keywords">
<h3><span class="secno">6.15 </span>Aliasing Keywords</h3><p><em>This section is non-normative.</em></p>
<p>Each of the JSON-LD <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keywords</a>,
@@ -2292,9 +2289,9 @@
<p>Since keywords cannot be redefined, they can also not be aliased to
other keywords.</p>
-</section>
-
-<section class="informative" id="data-indexing">
+</div>
+
+<div class="informative section" id="data-indexing">
<h3><span class="secno">6.16 </span>Data Indexing</h3><p><em>This section is non-normative.</em></p>
<p>Databases are typically used to make access to
@@ -2405,9 +2402,9 @@
</tr>
</tbody>
</table>
-</section>
-
-<section class="informative" id="expanded-document-form">
+</div>
+
+<div class="informative section" id="expanded-document-form">
<h3><span class="secno">6.17 </span>Expanded Document Form</h3><p><em>This section is non-normative.</em></p>
<p>The JSON-LD Processing Algorithms and API specification [<cite><a class="bibref" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>]
@@ -2444,9 +2441,9 @@
]
}
]</pre></div>
-</section>
-
-<section class="informative" id="compact-document-form">
+</div>
+
+<div class="informative section" id="compact-document-form">
<h3><span class="secno">6.18 </span>Compact Document Form</h3><p><em>This section is non-normative.</em></p>
<p>The JSON-LD Processing Algorithms and API specification [<cite><a class="bibref" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>] defines
@@ -2499,9 +2496,9 @@
"name": "Manu Sporny",
"homepage": "http://manu.sporny.org/"
}</pre></div>
-</section>
-
-<section class="informative" id="flattened-document-form">
+</div>
+
+<div class="informative section" id="flattened-document-form">
<h3><span class="secno">6.19 </span>Flattened Document Form</h3><p><em>This section is non-normative.</em></p>
<p>The JSON-LD Processing Algorithms and API specification [<cite><a class="bibref" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>] defines
@@ -2560,9 +2557,9 @@
}
]
}</pre></div>
-</section>
-
-<section class="informative" id="embedding-json-ld-in-html-documents">
+</div>
+
+<div class="informative section" id="embedding-json-ld-in-html-documents">
<h3><span class="secno">6.20 </span>Embedding JSON-LD in HTML Documents</h3><p><em>This section is non-normative.</em></p>
<p>HTML script tags can be used to embed blocks of data in documents.
@@ -2591,11 +2588,11 @@
<a class="tref externalDFN" title="rdf-dataset" href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-dataset">RDF dataset</a> using the
<cite><a href="../json-ld-api/#convert-to-rdf-algorithm">Convert to RDF Algorithm</a></cite>
[<cite><a class="bibref" href="#bib-JSON-LD-API">JSON-LD-API</a></cite>].</p>
-</section>
-
-</section>
-
-<section class="appendix normative" id="data-model">
+</div>
+
+</div>
+
+<div class="appendix normative section" id="data-model">
<!--OddPage-->
<h2><span class="secno">A. </span>Data Model</h2>
@@ -2676,11 +2673,11 @@
is being processed. This means, e.g., that properties which are not mapped to an
<a class="tref internalDFN" title="iri" href="#dfn-iri"><abbr title="Internationalized Resource Identifier">IRI</abbr></a> or <a class="tref internalDFN" title="blank-node" href="#dfn-blank-node">blank node</a> will be ignored.</p>
- <p style="text-align: center"><img src="linked-data-graph.png" title="An illustration of JSON-LD's data model" /></p>
+ <p style="text-align: center"><img src="linked-data-graph.png" title="An illustration of JSON-LD's data model" alt="An illustration of JSON-LD's data model" /></p>
<p style="text-align: center">Figure 1: An illustration of JSON-LD's data model.</p>
-</section>
-
-<section class="appendix normative" id="json-ld-grammar">
+</div>
+
+<div class="appendix normative section" id="json-ld-grammar">
<!--OddPage-->
<h2><span class="secno">B. </span>JSON-LD Grammar</h2>
@@ -2707,7 +2704,7 @@
Note that <a class="tref internalDFN" title="keyword" href="#dfn-keyword">keyword</a> aliases are not expanded during context
processing.</p></div>
- <section class="normative" id="terms">
+ <div class="normative section" id="terms">
<h3><span class="secno">B.1 </span>Terms</h3>
<p>A <dfn title="term" id="dfn-term">term</dfn> is a short-hand <a class="tref internalDFN" title="string" href="#dfn-string">string</a> that expands
@@ -2725,9 +2722,9 @@
<p>See <a class="sectionRef sec-ref" href="#the-context">section 5.1 The Context</a> and
<a class="sectionRef sec-ref" href="#iris">section 5.2 IRIs</a> for further discussion
on mapping <a class="tref internalDFN" title="term" href="#dfn-term">terms</a> to <a class="tref internalDFN" title="iri" href="#dfn-iri">IRIs</a>.</p>
- </section>
-
- <section class="normative" id="node-objects">
+ </div>
+
+ <div class="normative section" id="node-objects">
<h3><span class="secno">B.2 </span>Node Objects</h3>
<p>A <dfn title="node-object" id="dfn-node-object">node object</dfn> represents zero or more properties of a
@@ -2835,9 +2832,9 @@
<li>a <a class="tref internalDFN" title="language-map" href="#dfn-language-map">language map</a>, or </li>
<li>an <a class="tref internalDFN" title="index-map" href="#dfn-index-map">index map</a></li>
</ul>
- </section>
-
- <section class="normative" id="value-objects">
+ </div>
+
+ <div class="normative section" id="value-objects">
<h3><span class="secno">B.3 </span>Value Objects</h3>
<p>A <dfn title="value-object" id="dfn-value-object">value object</dfn> is used to explicitly associate a type or a
@@ -2868,9 +2865,9 @@
<p>See <a class="sectionRef sec-ref" href="#typed-values">section 6.4 Typed Values</a> and
<a class="sectionRef sec-ref" href="#string-internationalization">section 6.9 String Internationalization</a>
for more information on <a class="tref internalDFN" title="value-object" href="#dfn-value-object">value objects</a>.</p>
- </section>
-
- <section class="normative" id="lists-and-sets">
+ </div>
+
+ <div class="normative section" id="lists-and-sets">
<h3><span class="secno">B.4 </span>Lists and Sets</h3>
<p>A <a class="tref internalDFN" title="list" href="#dfn-list">list</a> represents an <em>ordered</em> set of values. A set
@@ -2909,9 +2906,9 @@
</ul>
<p>See <a class="sectionRef sec-ref" href="#sets-and-lists">section 6.11 Sets and Lists</a> for further discussion on sets and lists.</p>
- </section>
-
- <section class="normative" id="language-maps">
+ </div>
+
+ <div class="normative section" id="language-maps">
<h3><span class="secno">B.5 </span>Language Maps</h3>
<p>A <dfn title="language-map" id="dfn-language-map">language map</dfn> is used to associate a language with a value in a
@@ -2929,9 +2926,9 @@
<p>See <a class="sectionRef sec-ref" href="#string-internationalization">section 6.9 String Internationalization</a> for further discussion
on language maps.</p>
- </section>
-
- <section class="normative" id="index-maps">
+ </div>
+
+ <div class="normative section" id="index-maps">
<h3><span class="secno">B.6 </span>Index Maps</h3>
<p>An <dfn title="index-map" id="dfn-index-map">index map</dfn> allows keys that have no semantic meaning,
@@ -2956,9 +2953,9 @@
</ul>
<p>See <a class="sectionRef sec-ref" href="#data-indexing">section 6.16 Data Indexing</a> for further information on this topic.</p>
- </section>
-
-<section class="normative" id="context-definitions">
+ </div>
+
+<div class="normative section" id="context-definitions">
<h3><span class="secno">B.7 </span>Context Definitions</h3>
<p>A <dfn title="context-definition" id="dfn-context-definition">context definition</dfn> defines a <a class="tref internalDFN" title="local-context" href="#dfn-local-context">local context</a> in a
@@ -3046,11 +3043,11 @@
term also depends on the first term.</p>
<p>See <a class="sectionRef sec-ref" href="#the-context">section 5.1 The Context</a> for further discussion on contexts.</p>
-</section>
-
-</section>
-
-<section class="appendix normative" id="relationship-to-rdf">
+</div>
+
+</div>
+
+<div class="appendix normative section" id="relationship-to-rdf">
<!--OddPage-->
<h2><span class="secno">C. </span>Relationship to RDF</h2>
@@ -3102,7 +3099,7 @@
the primary data is stored in the default graph to enable consumers that do not support
datasets to process the information.</p></div>
- <section class="informative" id="transformation-from-json-ld-to-rdf">
+ <div class="informative section" id="transformation-from-json-ld-to-rdf">
<h3><span class="secno">C.1 </span>Transformation from JSON-LD to RDF</h3><p><em>This section is non-normative.</em></p>
<p>The process of turning a JSON-LD document depends on executing the
@@ -3185,10 +3182,10 @@
matching the triples from RDF, using a single <a class="tref internalDFN" title="node-object" href="#dfn-node-object">node object</a>
for all triples having a common subject, and a single <a class="tref internalDFN" title="property" href="#dfn-property">property</a>
for those triples also having a common predicate.</p>
- </section>
-</section>
-
-<section class="appendix informative" id="relationship-to-other-linked-data-formats">
+ </div>
+</div>
+
+<div class="appendix informative section" id="relationship-to-other-linked-data-formats">
<!--OddPage-->
<h2><span class="secno">D. </span>Relationship to Other Linked Data Formats</h2><p><em>This section is non-normative.</em></p>
@@ -3199,13 +3196,13 @@
evidence that JSON-LD is very flexible in what it can express across different
<a class="tref internalDFN" title="linked-data" href="#dfn-linked-data">Linked Data</a> approaches.</p>
- <section class="informative" id="turtle">
+ <div class="informative section" id="turtle">
<h3><span class="secno">D.1 </span>Turtle</h3><p><em>This section is non-normative.</em></p>
<p>The following are examples of converting RDF expressed in Turtle [<cite><a class="bibref" href="#bib-TURTLE">TURTLE</a></cite>]
into JSON-LD.</p>
- <section>
+ <div class="section">
<h4 id="prefix-definitions">Prefix definitions</h4><p><em>This section is non-normative.</em></p>
<p>The JSON-LD context has direct equivalents for the Turtle
@@ -3227,9 +3224,9 @@
"foaf:name": "Manu Sporny",
"foaf:homepage": { "@id": "http://manu.sporny.org/" }
}</pre></div>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="embedding-1">Embedding</h4>
<p>Both Turtle and JSON-LD allow embedding, although Turtle only allows embedding of
@@ -3256,9 +3253,9 @@
"foaf:name": "Gregg Kellogg"
}
}</pre></div>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="conversion-of-native-data-types">Conversion of native data types</h4>
<p>In JSON-LD numbers and boolean values are native data types. While Turtle
@@ -3289,9 +3286,9 @@
ex:numbers "14"^^xsd:integer, "2.78E0"^^xsd:double ;
ex:booleans "true"^^xsd:boolean, "false"^^xsd:boolean .</pre></div>
- </section>
-
- <section>
+ </div>
+
+ <div class="section">
<h4 id="lists">Lists</h4>
<p>Both JSON-LD and Turtle can represent sequential lists of values.</p>
@@ -3314,10 +3311,10 @@
"@list": [ "joe", "bob", "jaybee" ]
}
}</pre></div>
- </section>
- </section>
-
- <section class="informative" id="rdfa">
+ </div>
+ </div>
+
+ <div class="informative section" id="rdfa">
<h3><span class="secno">D.2 </span>RDFa</h3><p><em>This section is non-normative.</em></p>
<p>The following example describes three people with their respective names and
@@ -3364,9 +3361,9 @@
}
]
}</pre></div>
- </section>
-
- <section class="informative" id="microformats">
+ </div>
+
+ <div class="informative section" id="microformats">
<h3><span class="secno">D.3 </span>Microformats</h3><p><em>This section is non-normative.</em></p>
<p>The following example uses a simple Microformats hCard example to express
@@ -3396,9 +3393,9 @@
"url": "http://tantek.com/",
"fn": "Tantek Çelik"
}</pre></div>
- </section>
-
- <section class="informative" id="microdata">
+ </div>
+
+ <div class="informative section" id="microdata">
<h3><span class="secno">D.4 </span>Microdata</h3><p><em>This section is non-normative.</em></p>
<p>The HTML Microdata [<cite><a class="bibref" href="#bib-MICRODATA">MICRODATA</a></cite>] example below expresses book information as
@@ -3455,10 +3452,10 @@
"http://purl.org/dc/terms/type": "http://purl.oreilly.com/product-types/EBOOK"
}
]</pre></div>
- </section>
-</section>
-
-<section class="appendix normative" id="iana-considerations">
+ </div>
+</div>
+
+<div class="appendix normative section" id="iana-considerations">
<!--OddPage-->
<h2><span class="secno">E. </span>IANA Considerations</h2>
@@ -3560,9 +3557,9 @@
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>
[<cite><a class="bibref" href="#bib-RDF11-CONCEPTS">RDF11-CONCEPTS</a></cite>].</p>
-</section>
-
-<section class="appendix informative" id="acknowledgements">
+</div>
+
+<div class="appendix informative section" id="acknowledgements">
<!--OddPage-->
<h2><span class="secno">F. </span>Acknowledgements</h2><p><em>This section is non-normative.</em></p>
@@ -3598,18 +3595,18 @@
Richard Cyganiak, Roy T. Fielding, Sandro Hawke, Srecko Joksimovic,
Stephane Fellah, Steve Harris, Ted Thibodeau Jr., Thomas Steiner, Tim Bray,
Tom Morris, Tristan King, Sergio Fernández, Werner Wilms, and William Waites.</p>
-</section>
-
-
-
-<section id="references" class="appendix" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter">
+</div>
+
+
+
+<div id="references" class="appendix section" typeof="bibo:Chapter" resource="#references" rel="bibo:chapter">
<!--OddPage-->
-<h2><span class="secno">G. </span>References</h2><section id="normative-references" typeof="bibo:Chapter" resource="#normative-references" rel="bibo:chapter"><h3><span class="secno">G.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-BCP47">[BCP47]</dt><dd rel="dcterms:requires">A. Phillips; M. Davis. <a href="http://tools.ietf.org/html/bcp47"><cite>Tags for Identifying Languages</cite></a>. September 2009. IETF Best Current Practice. URL: <a href="http://tools.ietf.org/html/bcp47">http://tools.ietf.org/html/bcp47</a>
+<h2><span class="secno">G. </span>References</h2><div class="section" id="normative-references" typeof="bibo:Chapter" resource="#normative-references" rel="bibo:chapter"><h3><span class="secno">G.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-BCP47">[BCP47]</dt><dd rel="dcterms:requires">A. Phillips; M. Davis. <a href="http://tools.ietf.org/html/bcp47"><cite>Tags for Identifying Languages</cite></a>. September 2009. IETF Best Current Practice. URL: <a href="http://tools.ietf.org/html/bcp47">http://tools.ietf.org/html/bcp47</a>
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
</dd><dt id="bib-RFC3987">[RFC3987]</dt><dd rel="dcterms:requires">M. Dürst; M. Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt"><cite>Internationalized Resource Identifiers (IRIs) (RFC 3987)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3987.txt">http://www.ietf.org/rfc/rfc3987.txt</a>
</dd><dt id="bib-RFC4627">[RFC4627]</dt><dd rel="dcterms:requires">D. Crockford. <a href="http://www.ietf.org/rfc/rfc4627.txt"><cite>The application/json Media Type for JavaScript Object Notation (JSON) (RFC 4627)</cite></a>. July 2006. RFC. URL: <a href="http://www.ietf.org/rfc/rfc4627.txt">http://www.ietf.org/rfc/rfc4627.txt</a>
</dd><dt id="bib-RFC5988">[RFC5988]</dt><dd rel="dcterms:requires">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>
-</dd></dl></section><section id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:chapter"><h3><span class="secno">G.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-HTTP11">[HTTP11]</dt><dd rel="dcterms:references">R. Fielding et al. <a href="http://www.ietf.org/rfc/rfc2616.txt"><cite>Hypertext Transfer Protocol - HTTP/1.1</cite></a>. June 1999. RFC 2616. URL: <a href="http://www.ietf.org/rfc/rfc2616.txt">http://www.ietf.org/rfc/rfc2616.txt</a>
+</dd></dl></div><div class="section" id="informative-references" typeof="bibo:Chapter" resource="#informative-references" rel="bibo:chapter"><h3><span class="secno">G.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-HTTP11">[HTTP11]</dt><dd rel="dcterms:references">R. Fielding et al. <a href="http://www.ietf.org/rfc/rfc2616.txt"><cite>Hypertext Transfer Protocol - HTTP/1.1</cite></a>. June 1999. RFC 2616. URL: <a href="http://www.ietf.org/rfc/rfc2616.txt">http://www.ietf.org/rfc/rfc2616.txt</a>
</dd><dt id="bib-JSON-LD-API">[JSON-LD-API]</dt><dd rel="dcterms:references">Markus Lanthaler, Gregg Kellogg, Manu Sporny, Editors. <cite><a href="http://www.w3.org/TR/2013/WD-json-ld-api-20130411/">JSON-LD 1.0 Processing Algorithms and API</a>.</cite> W3C Working Draft (work in progress). URL: <a href="http://www.w3.org/TR/2013/WD-json-ld-api-20130411/">http://www.w3.org/TR/2013/WD-json-ld-api-20130411/</a>. The latest edition is available at <a href="http://www.w3.org/TR/json-ld-api/">http://www.w3.org/TR/json-ld-api/</a>
</dd><dt id="bib-JSON-LD-TESTS">[JSON-LD-TESTS]</dt><dd rel="dcterms:references"><cite><a href="http://www.w3.org/2013/json-ld-tests/">JSON-LD 1.0 Test Suite</a></cite>. W3C Test Suite (work in progress). URL: <a href="http://www.w3.org/2013/json-ld-tests/">http://www.w3.org/2013/json-ld-tests/</a>
</dd><dt id="bib-MICRODATA">[MICRODATA]</dt><dd rel="dcterms:references">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>
@@ -3620,4 +3617,4 @@
</dd><dt id="bib-RFC3986">[RFC3986]</dt><dd rel="dcterms:references">T. Berners-Lee; R. Fielding; L. Masinter. <a href="http://www.ietf.org/rfc/rfc3986.txt"><cite>Uniform Resource Identifier (URI): Generic Syntax (RFC 3986)</cite></a>. January 2005. RFC. URL: <a href="http://www.ietf.org/rfc/rfc3986.txt">http://www.ietf.org/rfc/rfc3986.txt</a>
</dd><dt id="bib-RFC6906">[RFC6906]</dt><dd rel="dcterms:references">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>
</dd><dt id="bib-TURTLE">[TURTLE]</dt><dd rel="dcterms:references">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>
-</dd></dl></section></section></body></html>
+</dd></dl></div></div></body></html>