--- a/local-biblio.js Tue Feb 18 09:53:56 2014 +0000
+++ b/local-biblio.js Tue Feb 18 09:54:08 2014 +0000
@@ -13,7 +13,7 @@
"RDF11-TESTCASES": "Gregg Kellogg, Markus Lanthaler. <cite><a href=\"http://www.w3.org/TR/2014/NOTE-rdf11-testcases-20140225/\">RDF 1.1 Test Cases</a></cite>. W3C Working Group Note, 25 February 2014. The latest published version is available at <a href=\"http://www.w3.org/TR/rdf11-testcases/\">http://www.w3.org/TR/rdf11-testcases/</a>.",
"RDF11-PRIMER": "Guus Schreiber, Yves Raimond. <cite><a href=\"http://www.w3.org/TR/2014/NOTE-rdf11-primer-20140225/\">RDF 1.1 Primer</a></cite>. W3C Working Group Note, 25 February 2014. The latest version is available at <a href=\"http://www.w3.org/TR/rdf11-primer/\">http://www.w3.org/TR/rdf11-primer/</a>.",
"RDF11-NEW": "David Wood. <cite><a href=\"http://www.w3.org/TR/2014/NOTE-rdf11-new-20140225/\">What’s New in RDF 1.1</a></cite>. W3C Working Group Note, 25 February 2014. The latest version is available at <a href=\"http://www.w3.org/TR/rdf11-new/\">http://www.w3.org/TR/rdf11-new/</a>.",
- "RDF11-DATASETS": "Antoine Zimmermann. <cite><a href=\"http://www.w3.org/TR/2014/NOTE-rdf11-datasets-20140225/\">RDF 1.1: On Semantics of Datasets</a></cite>. W3C Working Group Note, 25 February 2014. The latest version is available at <a href=\"http://www.w3.org/TR/rdf11-datasets/\">http://www.w3.org/TR/rdf11-datasets/</a>.",
+ "RDF11-DATASETS": "Antoine Zimmermann. <cite><a href=\"http://www.w3.org/TR/2014/NOTE-rdf11-datasets-20140225/\">RDF 1.1: On Semantics of RDF Datasets</a></cite>. W3C Working Group Note, 25 February 2014. The latest version is available at <a href=\"http://www.w3.org/TR/rdf11-datasets/\">http://www.w3.org/TR/rdf11-datasets/</a>.",
"RDFMS": "Ora Lassila; Ralph R. Swick. <cite><a href=\"http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/\">Resource Description Framework (RDF) Model and Syntax Specification</a></cite>. 22 February 1999. W3C Recommendation. URL: <a href=\"http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/\">http://www.w3.org/TR/1999/REC-rdf-syntax-19990222</a>.",
"LINKED-DATA": "Tim Berners-Lee. <cite><a href=\"http://www.w3.org/DesignIssues/LinkedData.html\">Linked Data</a></cite>. Personal View, imperfect but published. URL: <a href=\"http://www.w3.org/DesignIssues/LinkedData.html\">http://www.w3.org/DesignIssues/LinkedData.html</a>",
"BERNERS-LEE98": "Tim Berners-Lee. <cite><a href=\"http://www.w3.org/DesignIssues/RDFnot.html\">What the Semantic Web can represent</a></cite>. 1998. URI: <a href=\"http://www.w3.org/DesignIssues/RDFnot.html\">http://www.w3.org/DesignIssues/RDFnot.html</a>.",
@@ -34,6 +34,7 @@
"ANNOTATED-RDF" : "Octavian Udrea, Diego Reforgiato Recupero, V. S. Subrahmanian. <cite>Annotated RDF.</cite> In The Semantic Web: Research and Applications, 3rd European Semantic Web Conference, ESWC 2006, Budva, Montenegro, June 11-14, 2006, Proceedings. Springer, LNCS 4011, pp. 487-501",
"DELBRU-ET-AL-2008" : "Renaud Delbru, Axel Polleres, Giovanni Tummarello, Stefan Decker. <cite>Context Dependent Reasoning for Semantic Documents in Sindice.</cite> In Proceedings of the 4th International Workshop on Scalable Semantic Web Knowledge Base Systems (SSWS). Karlsruhe, Germany, 2008.",
"SPARQL11-OVERVIEW": { aliasOf: "sparql11-overview" },
+ "SPARQL11-QUERY": { aliasOf: "sparql11-query" },
"SPARQL11-ENTAILMENT": { aliasOf: "sparql11-entailment" },
"SPARQL11-SERVICE-DESCRIPTION": { aliasOf: "sparql11-service-description" },
"SPARQL11-TEST-CASE" : "Axel Polleres. <cite><a href=\"http://www.w3.org/2009/sparql/docs/tests/README.html\">SPARQL1.1: Test case structure</a></cite> Informal. URL: <a href=\"http://www.w3.org/2009/sparql/docs/tests/README.html\">http://www.w3.org/2009/sparql/docs/tests/README.html</a>",
--- a/rdf-primer/index.html Tue Feb 18 09:53:56 2014 +0000
+++ b/rdf-primer/index.html Tue Feb 18 09:54:08 2014 +0000
@@ -126,7 +126,7 @@
specification of RDF 1.1 the reader is referred to the RDF
1.1. Concepts and Abstract Syntax document [[RDF11-CONCEPTS]].</p>
</section>
-</div>
+
<section id="section-Introduction">
<h2>Introduction</h2>
@@ -157,7 +157,7 @@
For example, retrieving <code>http://www.example.org/bob#me</code>
could provide data about Bob, including the fact that he
knows Alice, as identified by her IRI (an IRI is an "International
- Resource Identifier"; see <a href="#subsection-IRI">Sec. 3.2</a> for details).
+ Resource Identifier"; see <a href="#section-IRI">Sec. 3.2</a> for details).
Retrieving Alice's IRI could then provide more data about her, including links
to other datasets for her friends, interests, etc. A person or
an automated process can then follow such links and aggregate data about these
@@ -228,13 +228,13 @@
<h2>RDF Data Model</h2>
- <section id="subsection-triple">
+ <section id="section-triple">
<h3>Triples</h3>
<p>RDF allows us to make statements about resources.
- The format of these statements is simple. It always
- has the following form:<p>
+ The format of these statements is simple. A statement always
+ has the following structure:<p>
<pre>
<subject> <predicate> <object>
</pre>
@@ -304,14 +304,14 @@
produce exactly the same graph from the perspective of the
abstract syntax. The semantics of RDF graphs [[RDF11-MT]] are defined in
terms of this abstract syntax. Concrete RDF syntax is introduced
- later in <a href="#section-graph-syntax">Sec. 5</a>.</p>
+ later in <a href="#section-graph-syntax">Sec. 5</a>.</p>
<p>In the next three subsections we discuss the three types of RDF data
that occur in triples: IRIs, literals and blank nodes. </p>
</section>
- <section id="subsection-IRI">
+ <section id="section-IRI">
<h3>IRIs</h3>
@@ -360,7 +360,7 @@
</section>
- <section id="subsection-literal">
+ <section id="section-literal">
<h3>Literals</h3>
@@ -395,7 +395,7 @@
</section>
- <section id="subsection-blank-node">
+ <section id="section-blank-node">
<h3>Blank nodes</h3>
@@ -429,7 +429,7 @@
</section>
- <section id="subsection-multiple-graphs">
+ <section id="section-multiple-graphs">
<h3>Multiple graphs</h3>
@@ -448,7 +448,7 @@
at most one unnamed ("default") graph. </p><p>
<p>For example, the
- statements in the <a href="#subsection-triple">first example</a>
+ statements in the <a href="#section-triple">first example</a>
could be grouped in two named
graphs. A first graph could be provided by a social networking
site and identified by <code>http://example.org/bob</code>:</p>
@@ -502,7 +502,7 @@
<figcaption>Informal graph of the sample dataset</figcaption>
</figure>
- <p><a href="#subsection-trig">Sec. 5.2</a> provides an example
+ <p><a href="#section-trig">Sec. 5.1.3</a> provides an example
of concrete syntax for this graph.</p>
</section>
@@ -592,7 +592,7 @@
<p class="note">The syntactic form (second column) is in a prefix
notation wich is discussed in more detail in
-<a href="#section-graph-syntax">Sec. 5</a>.
+<a href="#section-graph-syntax">Sec. 5</a>.
The fact that the constructs have two different prefixes
(<code>rdf:</code> and <code>rdfs:</code>) is a somewhat annoying
historical artefact, which is preserved for backward
@@ -667,46 +667,95 @@
to exactly the same triples, and are thus logically equivalent. </p>
<p>In this section we introduce the Turtle family of RDF languages
- (Turtle/N-Triples and TriG/N-Quads) and the JSON-based RDF syntax
- JSON-LD. Two other RDF syntaxes, RDFa (for HTML and XML embedding)
- and RDF/XML, are briefly described next two
- subsections we show RDF syntax examples using the Turtle and Trig
- language, because these two languages are best suited for human
- consumption. The final subsection lists the other RDF syntaxes,
- which include RDFa, JSON-LD (JSON-based syntax),
- N-Triples/N-Quads (line-based exchange formats) and RDF/XML. In
- <a href="#section-other-syntaxes">Appendix C</a> the
- reader can find, for each RDF syntax,
- corresponding examples of the ones in this section. </p>
+ (<a href="#section-n-triples">N-Triples</a>,
+ <a href="#section-turtle">Turtle</a>,
+ <a href="#section-trig">TriG</a> and
+ <a href="#section-n-quads">N-Quads</a>)
+ and the JSON-based RDF syntax <a href="#section-json-ld">JSON-LD</a>.
+ Two other RDF syntaxes,
+ <a href="#appendix-rdfa">RDFa</a> (for HTML and XML embedding)
+ and <a href="#appendix-rdfxml">RDF/XML</a>, are briefly described later on. </p>
<section>
-<h3>The Turtle family of RDF languages</h3>
-
- <section id="subsection-turtle">
-
- <h4>Turtle and N-Triples</h4>
-
- <p>Turtle [[TURTLE]] provides a syntax for RDF
- graphs, which is relatively convenient for humans.
- In its basic form a triple in Turtle looks this:<P>
+<h3>Turtle family of RDF languages</h3>
- <pre class="example">
-<http://example.org/bob#me> <http://xmlns.com/foaf/0.1/knows> <http://example.org/alice#me> .
- </pre>
+<p>In this subsection we introduce four concrete syntaxes for RDF
+which are closely related. We start with N-Triples, as it provides
+basic syntax for writing down RDF triples. The Turtle syntax
+extends this basic syntax with various forms of syntactic sugar to improve
+readability. Subsequently we discuss TriG and N-Quads, which are extensions of Turtle
+respectively N-Triples to encode multiple graphs. Together, these four are
+referred to as the "Turtle family of RDF languages".
- <p>In Turtle full IRIs are enclosed in angle brackets (<code><></code>);
- the period signals the
- end of the triple. This example represents concrete syntax for
- the second triple in <a href="#example-1">Example 1</a>.</p>
+<section id="section-n-triples">
+<h4>N-Triples</h4>
- <p>In addition to this basic syntax, Turtle
- introduces a number of syntax shortcuts, such as
- support for namespaces, lists and shorthands for datatyped
- literals. Turtle provides a trade-off between ease of
- writing, ease of parsing and readability. Our
- <a href="#example-1">first example</a> (in slightly
- extended form) can be
- represented in Turtle as follows:</p>
+<p>N-Triples [[N-TRIPLES]] provides a simple line-based, plain-text way for serializing RDF
+graphs. Each line represents an RDF triple. The informal graph in <a
+href="#fig1">Fig. 1</a> can be represented in N-Triples in the
+following way:</p>
+
+<pre class="example" id="n-triples-example">
+01 <http://example.org/bob#me> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://xmlns.com/foaf/0.1/Person> .
+02 <http://example.org/bob#me> <http://xmlns.com/foaf/0.1/knows> <http://example.org/alice#me> .
+03 <http://example.org/bob#me> <http://schema.org/birthDate> "1990-07-04"^^<http://www.w3.org/2001/XMLSchema#date> .
+04 <http://example.org/bob#me> <http://xmlns.com/foaf/0.1/topic_interest> <http://www.wikidata.org/entity/Q12418> .
+05 <http://www.wikidata.org/entity/Q12418> <http://purl.org/dc/terms/title> "Mona Lisa" .
+06 <http://www.wikidata.org/entity/Q12418> <http://purl.org/dc/terms/creator> <http://dbpedia.org/resource/Leonardo_da_Vinci> .
+07 <http://data.europeana.eu/item/04802/243FA8618938F4117025F17A8B813C5F9AA4D619> <http://purl.org/dc/terms/subject> <http://www.wikidata.org/entity/Q12418> .
+</pre>
+
+<p>In N-Triples each line represents a triple. Full IRIs are enclosed in angle brackets
+(<code><></code>). The period at the end of the line signals the
+end of the triple.</p>
+
+<p>In line 3 we see an example of a literal, in this case a date. The
+datatype is appended to the literal through a <code>^^</code> delimiter. The date
+representation follows the conventions of the XML Schema datatype
+<a href="http://www.w3.org/TR/xmlschema11-2/#date">date</a>.</p>
+
+<p>Because string literals are so ubiquitous N-Triples allows the user to
+omit the datatype when writing a string literal. Thus, <code>"Mona
+Lisa"</code> in line 5 is equivalent to
+<code>"Mona Lisa"^^xsd:string</code>.
+In case of language-tagged strings the tag
+appears directly after the string, separated by a <code>@</code>
+symbol, e.g. <code>"La Joconde"@fr</code> (the French name of the Mona
+Lisa).</p>
+
+<p class="note">For technical reasons the datatype of language-tagged
+strings is not <code>xsd:string</code> but
+<code>rdf:langString</code>. The
+datatype of language-tagged strings is never specified explicitly.</p>
+
+<p>The figure below shows the triples resulting from the example:</p>
+
+ <figure id="fig4">
+ <img class="graph" src="example-graph-iris.jpg"
+ alt="Graph of the sample triples">
+ <figcaption>RDF graph resulting from the N-Triples example</figcaption>
+ </figure>
+
+<p>Note that the seven lines in the N-Triples example correspond to the seven
+arcs in the diagram above.</p>
+
+<p>N-Triples is often used for exchanging large amounts of RDF and for
+processing large RDF graphs with line-oriented text processing
+tools. </p>
+
+</section>
+
+<section id="section-turtle">
+<h4>Turtle</h4>
+
+<p>Turtle [[TURTLE]] is an <strong>extension of N-Triples</strong>.
+In addition to the basic N-Triples syntax, Turtle
+introduces a number of syntax shortcuts, such as
+support for namespaces, lists and shorthands for datatyped
+literals. Turtle provides a trade-off between ease of
+writing, ease of parsing and readability. The graph shown in
+<a href="#fig4">Fig. 4</a> can be
+represented in Turtle as follows:</p>
<pre class="example" id="turtle-example">
01 BASE <http://example.org/>
@@ -730,7 +779,8 @@
19 dcterms:subject wd:Q12418 .
</pre>
-<p>Lines 1-6 contain a number of directives which provide shorthands for
+<p>The Turtle example is logically equivalent to the <a href="#n-triples-example">N-Triples</a>
+example. Lines 1-6 contain a number of directives which provide shorthands for
writing down IRIs. Relative IRIs (such as <code>bob#me</code> on line 8) are
resolved agains a base IRI, specified here in line 1.
Lines 2-6 define IRI prefixes (such as <code>foaf:</code>), which can
@@ -755,57 +805,6 @@
The <code>a</code> shorthand is intended to match the human
intuition about <code>rdf:type</code>. </p>
-<p>In line 11 we see an example of a literal, in this case a date. The
-datatype is appended to the literal through a <code>^^</code> delimiter. The date
-representation follows the conventions of the XML Schema datatype
-<a href="http://www.w3.org/TR/xmlschema11-2/#date">date</a>.</p>
-
-<p>Because string literals are so ubiquitous Turtle allows the user to
-omit the datatype when writing a string literal. Thus, <code>"Mona
-Lisa"</code> in line 15 is equivalent to
-<code>"Mona Lisa"^^xsd:string</code>.
-In case of language-tagged strings the tag
-appears directly after the string, separated by a <code>@</code>
-symbol, e.g. <code>"La Joconde"@fr</code> (the French name of the Mona
-Lisa).</p>
-
-<p class="note">For technical reasons the datatype of language-tagged
-strings is not <code>xsd:string</code> but
-<code>rdf:langString</code>. The
-datatype of language-tagged strings is never specified explicitly
-in Turtle.</p>
-
-<p>The figure below shows the triples resulting from this example:</p>
-
- <figure id="fig4">
- <img class="graph" src="example-graph-iris.jpg"
- alt="Graph of the sample triples">
- <figcaption>Graph of the Turtle example</figcaption>
- </figure>
-
-<h5>N-Triples</h5>
-
-<p>N-Triples [[N-TRIPLES]] is a subset of Turtle that
-provides a simple line-based, plain text way for serializing RDF
-graphs. Each line represents an RDF triple. The N-Triples version of
-the example above look like this:</p>
-
-<pre class="example" id="n-triples-example">
-01 <http://example.org/bob#me> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://xmlns.com/foaf/0.1/Person> .
-02 <http://example.org/bob#me> <http://xmlns.com/foaf/0.1/knows> <http://example.org/alice#me> .
-03 <http://example.org/bob#me> <http://schema.org/birthDate> "1990-07-04"^^<http://www.w3.org/2001/XMLSchema#date> .
-04 <http://example.org/bob#me> <http://xmlns.com/foaf/0.1/topic_interest> <http://www.wikidata.org/entity/Q12418> .
-05 <http://www.wikidata.org/entity/Q12418> <http://purl.org/dc/terms/title> "Mona Lisa" .
-06 <http://www.wikidata.org/entity/Q12418> <http://purl.org/dc/terms/creator> <http://dbpedia.org/resource/Leonardo_da_Vinci> .
-07 <http://data.europeana.eu/item/04802/243FA8618938F4117025F17A8B813C5F9AA4D619> <http://purl.org/dc/terms/subject> <http://www.wikidata.org/entity/Q12418> .
-</pre>
-
-<p>Note that the seven lines in the example correspond to the seven
-arcs in the diagram above.</p>
-
-<p>N-Triples is often used for exchanging large amounts of RDF and for
-processing large RDF graphs with line-oriented text processing tools. </p>
-
<h5>Representation of blank nodes</h5>
<p>Below is sample Turtle syntax for blank nodes, using the
@@ -820,28 +819,30 @@
<p>The term <code>_:x</code> is a blank node. It represents an
unnamed resource depicted in
-the Mona Lisa painting; the unnamed resource is an instance of the <code>Cypress</code> class. </p>
+the Mona Lisa painting; the unnamed resource is an instance of the
+<code>Cypress</code> class. The example above provides concrete syntax
+for the informal graph in <a href="#fig2">Fig. 2</a>.</p>
-<p>The above is by no means a full account of the Turtle syntax. For
+<p>This section gives by no means a full account of the Turtle syntax. For
more details about the syntax of Turtle please consult the Turtle specification [[TURTLE]].</p>
</section>
- <section id="subsection-trig">
-
- <h4>TriG and N-Quads</h4>
+<section id="section-trig">
- <p>The syntax of Turtle supports only the specification of single
- graphs without a means for "naming" them. TriG [[TRIG]] is an
- extension to the Turtle syntax enabling the specification of
- multiple graphs.</p>
+<h4>TriG</h4>
+
+<p>The syntax of Turtle supports only the specification of single
+graphs without a means for "naming" them. TriG [[TRIG]] is an
+<strong>extension of Turtle</strong> enabling the specification of
+multiple graphs in the form of an RDF dataset.</p>
<p class="note">In RDF 1.1 any legal Turtle document is a legal TriG
document. One could view it as one language. The names Turtle and TriG
still exist for historical reasons.</p>
- <p>The <a href="#subsection-multiple-graphs">multiple-graphs version of our example</a>
- can be specified in TriG as follows:</p>
+<p>The <a href="#section-multiple-graphs">multiple-graphs version of our example</a>
+can be specified in TriG as follows:</p>
<pre class="example" id="trig-example">
01 BASE <http://example.org/>
@@ -880,13 +881,13 @@
placed in between matching curly braces (lines 9 & 15, 18 &
28). Optionally you can precede the graph name with the keyword
<code>GRAPH</code>. This may improve readability, but it is mainly
- introduced for alignment with SPARQL Update [[SPARQL11-OVERVIEW]]. </p>
+ introduced for alignment with SPARQL Update [[SPARQL11-UPDATE]]. </p>
<p>The syntax of the triples and of the directives at the top conforms to
the Turtle syntax.</p>
<p>The two triples specified on lines 30-32 are not part of any
- named graph. Together they form the default graph of this RDF
+ named graph. Together they form the unnamed ("default") graph of this RDF
dataset.</p>
<p>The figure below shows the triples resulting from this example.</p>
@@ -896,8 +897,11 @@
alt="Triples resulting from the TriG example">
<figcaption>Triples resulting from the TriG example</figcaption>
</figure>
+</section>
-<h5>N-Quads</h5>
+<section id="section-n-quads">
+
+<h4>N-Quads</h4>
<p>N-Quads [[N-QUADS]] is a simple extension to N-Triples to enable the exchange of RDF
datasets. N-Quads allows one to add a fourth element to a line, capturing
@@ -917,7 +921,12 @@
</pre>
<p>The nine lines in the N-Quads example correspond to the nine
-arcs in the graph diagram above. </p>
+arcs in <a href="#fig5">Fig. 5</a>. Lines 1-7 represent quads, where the first
+element constitutes the graph IRI. The part of the quad after the
+graph IRI specifies the
+subject, predicate and object of the statement, following the syntactic
+conventions of N-Triples. Lines 8 and 9 represent the statements in the unnamed (default)
+graph, which lack a fourth element and thus constitute regular triples. </p>
<p><p>Like N-Triples, N-Quads is typically used for exchanging large RDF datasets and for
processing RDF with line-oriented text processing tools. </p>
@@ -927,7 +936,7 @@
</section>
</section>
-<section>
+<section id="section-json-ld">
<h3>JSON-LD</h3>
<p>JSON-LD [[JSON-LD]]
@@ -983,7 +992,7 @@
</section>
- <section id="subsection-other-syntaxes">
+ <section id="section-other-syntaxes">
<h3>Other concrete syntaxes for RDF</h3>
@@ -993,7 +1002,7 @@
<dl>
<dt>RDFa</dt>
- <dd>RDFa [[RDFA-PRIMER]] (<a href="#rdfa-example">single-graph example</a>)
+ <dd>RDFa [[RDFA-PRIMER]]
can be used to embed RDF data within
HTML documents. This enables, for example, search engines to aggregate
this data when crawling the Web and use it to enrich search
@@ -1006,8 +1015,7 @@
</dd>
<dt>RDF/XML</dt>
- <dd>RDF/XML [[RDF-SYNTAX-GRAMMAR]] (<a
- href="#rdf-xml-example">single-graph example</a>)
+ <dd>RDF/XML [[RDF-SYNTAX-GRAMMAR]]
provides an XML syntax for RDF
graphs. When RDF was original developed in the late 1990s, this was its
only syntax, and some people still call this syntax "RDF". In 2001, a
@@ -1172,7 +1180,8 @@
</pre>
<p>Such links can be deployed by RDF data-processing
- software. </p>
+ software, for example by merging or comparing RDF data of
+ IRIs that point to the same resource. </p>
</section>
@@ -1204,19 +1213,17 @@
<section class="appendix" id="changes">
<h2>Changes</h2>
- <dl>
- <dt>Changes compared to 2004 Primer [[RDF-PRIMER]]</dt>
- <dd>The introduction contains a number of sentences from the
- 2004 document. For the rest the RDF 1.1 Primer is a completely
- new document.</dd>
- </dl>
+ <p>The introduction contains a number of sentences from the
+ 2004 Primer [[RDF-PRIMER]]. For the rest the RDF 1.1 Primer is a completely
+ new document.</p>
+
</section>
-<section id="section-other-syntaxes" class="appendix">
+<section id="appendix-other-syntaxes" class="appendix">
<h2>More examples of RDF syntaxes</h2>
-<p>In <a href="#section-graph-syntax">Sec. 5</a> the
+<p>In <a href="#section-graph-syntax">Sec. 5</a> the
Turtle family of RDF languages and JSON-LD were introduced.
This appendix lists
corresponding examples for two other RDF syntaxes, namely RDFa and
@@ -1225,6 +1232,8 @@
<section id="appendix-rdfa">
<h3>RDFa</h3>
+ <p class="issue">Include comments/suggestions from Ivan</p>
+
<p>RDFa is an RDF syntax for encoding RDF
triples in an HTML document. The HTML example below encodes the
RDF graph depicted in <a href="#fig4">Fig. 4</a>:</p>
@@ -1364,8 +1373,8 @@
<section id="appendix-jsonld-1">
<p>In this section we describe several
- alternative serialisations for JSON-LD, adding to the example
- in the <a href="#json-ld">JSON-LD section above</a>.</p>
+ alternative serializations for JSON-LD, adding to the example
+ in the <a href="#section-json-ld">JSON-LD section</a> above.</p>
<p>In the following example we encode the
RDF graph depicted in <a href="#fig4">Fig. 4</a>, explicitly
@@ -1489,8 +1498,8 @@
<section id="appendix-jsonld-3">
<p>The <code>@context</code> of a JSON-LD document can be factored out
-and refered to by its IRI. The following is the context used in the example
-in the <a href="#json-ld">JSON-LD section above</a>.</p>
+and referred to by its IRI. The following is the context used in the example
+in the <a href="#section-json-ld">JSON-LD section</a> above.</p>
<pre class="example">
01 {
@@ -1525,6 +1534,8 @@
30 }
</pre>
+<p>For detailed information about JSON-LD please consult the JSON-LD
+ specification [[JSON-LD]]. </p>
</section>
</section>