--- a/spec/latest/json-ld-syntax/index.html Wed Mar 27 11:16:10 2013 +0100
+++ b/spec/latest/json-ld-syntax/index.html Wed Mar 27 11:47:56 2013 +0100
@@ -197,7 +197,7 @@
to reshape documents into a deterministic structure which simplifies their
processing.</p>
- <section>
+ <section class="informative">
<h2>How to Read this Document</h2>
<p>This document is a detailed specification for a serialization of Linked
@@ -264,7 +264,7 @@
<section class="normative">
<h1>Terminology</h1>
- <section>
+ <section class="normative">
<h2>General Terminology</h2>
<p>This document uses the following terms as defined in JSON [[!RFC4627]]. Refer
@@ -307,7 +307,7 @@
</dl>
</section>
- <section>
+ <section class="normative">
<h2>Syntax Tokens and Keywords</h2>
<p>JSON-LD specifies a number of syntax tokens and <tdef title="keyword">keywords</tdef>
@@ -374,7 +374,10 @@
<h1>Conformance</h1>
<p>This specification describes the conformance criteria for JSON-LD documents.
- This criteria is relevant to authors and authoring tool implementers.</p>
+ This criteria is relevant to authors and authoring tool implementers. As well
+ as sections marked as non-normative, all authoring guidelines, diagrams, examples,
+ and notes in this specification are non-normative. Everything else in this
+ specification is normative.</p>
<p>A <tref>JSON-LD document</tref> complies with this specification if it follows
the normative statements in appendix <a href="#json-ld-grammar"></a>. JSON documents
@@ -387,7 +390,7 @@
meaning defined in [[!RFC2119]].</p>
</section>
-<section class="normative">
+<section class="informative">
<h1>Basic Concepts</h1>
<p>JSON [[RFC4627]] is a lightweight, language-independent data-interchange format.
@@ -444,7 +447,7 @@
to work with for human developers. To address this issue, JSON-LD introduces the notion
of a <tref>context</tref> as described in the next section.</p>
- <section>
+ <section class="informative">
<h2>The Context</h2>
<p>Simply speaking, a <tdef>context</tdef> is used to map <tref title="term">terms</tref>, to
@@ -556,7 +559,7 @@
</pre>
</section>
-<section>
+<section class="informative">
<h2>IRIs</h2>
<p><tref title="IRI">IRIs</tref> (Internationalized Resource Identifiers
@@ -688,7 +691,7 @@
</ol>
</section>
-<section>
+<section class="informative">
<h2>Node Identifiers</h2>
<p>To be able to externally reference <tref title="node">nodes</tref>
@@ -723,7 +726,7 @@
<code>http://me.markus-lanthaler.com/</code>.</p>
</section>
-<section>
+<section class="informative">
<h2>Specifying the Type</h2>
<p>The type of a particular node can be specified using the <code>@type</code>
@@ -775,16 +778,14 @@
</section>
</section>
-<section>
+<section class="normative">
<h1>Advanced Concepts</h1>
-<em>This section is normative.</em>
-
<p>JSON-LD has a number of features that provide functionality above and beyond
the core functionality described above. The following section describes this
advanced functionality in more detail.</p>
-<section>
+<section class="informative">
<h2>Base IRI</h2>
<p class="issue atrisk" data-number="223" title="Feature at risk">This feature is
@@ -835,7 +836,7 @@
</pre>
</section>
-<section>
+<section class="informative">
<h2>Default Vocabulary</h2>
<p>At times, all properties and types may come from the same vocabulary. JSON-LD's
@@ -884,7 +885,7 @@
</pre>
</section>
-<section>
+<section class="informative">
<h2>Compact IRIs</h2>
<p>A <tdef>compact IRI</tdef> is a way of expressing an <tref>IRI</tref>
@@ -957,7 +958,7 @@
</pre>
</section>
-<section>
+<section class="informative">
<h2>Typed Values</h2>
<p>
@@ -1113,7 +1114,7 @@
</section>
-<section>
+<section class="informative">
<h2>Type Coercion</h2>
<p>JSON-LD supports the coercion of values to particular data types.
@@ -1266,7 +1267,7 @@
</section>
-<section>
+<section class="informative">
<h2>Embedding</h2>
<p><tdef>Embedding</tdef> is a JSON-LD feature that allows an author to
@@ -1297,7 +1298,7 @@
any value position in the body of a JSON-LD document.</p>
</section>
-<section>
+<section class="informative">
<h2>Advanced Context Usage</h2>
<p>Section <a href="#the-context"></a> introduced the basics of what makes
@@ -1412,7 +1413,7 @@
not all programming languages are able to handle empty property names.</p>
</section>
-<section>
+<section class="normative">
<h2>Interpreting JSON as JSON-LD</h2>
<p>Ordinary JSON documents can be interpreted as JSON-LD by referencing a JSON-LD
@@ -1468,7 +1469,7 @@
ignored for such documents.</p>
</section>
-<section>
+<section class="informative">
<h2>String Internationalization</h2>
<p>At times, it is important to annotate a <tref>string</tref>
@@ -1636,7 +1637,7 @@
</section>
-<section>
+<section class="informative">
<h2>IRI Expansion within a Context</h2>
<p>In general, normal IRI expansion rules apply
anywhere an IRI is expected (see <a class="sectionRef" href="#iris"></a>). Within
@@ -1803,7 +1804,7 @@
</pre>
</section>
-<section>
+<section class="informative">
<h2>Sets and Lists</h2>
<p>A JSON-LD author can express multiple values in a compact way by using
@@ -1963,7 +1964,7 @@
</section>
-<section>
+<section class="informative">
<h2>Reverse Properties</h2>
<p class="issue atrisk">This feature is at risk.</p>
@@ -2056,7 +2057,7 @@
</section>
-<section>
+<section class="informative">
<h2>Named Graphs</h2>
<p>At times, it is necessary to make statements about a <tref>JSON-LD graph</tref>
@@ -2234,7 +2235,7 @@
</section>
-<section>
+<section class="informative">
<h2>Identifying Blank Nodes</h2>
<p>At times, it becomes necessary to be able to express information without
@@ -2276,7 +2277,7 @@
it can also be referenced from other documents.</p>
</section>
-<section>
+<section class="informative">
<h2>Aliasing Keywords</h2>
<p>Each of the JSON-LD <tref title="keyword">keywords</tref>,
@@ -2311,7 +2312,7 @@
other keywords.</p>
</section>
-<section>
+<section class="informative">
<h2>Data Indexing</h2>
<p>Databases are typically used to make access to
@@ -2619,7 +2620,7 @@
</pre>
</section>
-<section>
+<section class="informative">
<h2>Embedding JSON-LD in HTML Documents</h2>
<p>HTML script tags can be used to embed blocks of data in documents.
@@ -2729,7 +2730,6 @@
<section class="appendix normative">
<h1>JSON-LD Grammar</h1>
- <em>This section is normative</em>
<p>This appendix restates the syntactic conventions described in the
previous sections more formally.</p>
@@ -2753,7 +2753,7 @@
Note that <tref>keyword</tref> aliases are not expanded during context
processing.</p>
- <section>
+ <section class="normative">
<h2>Terms</h2>
<p>A <tdef>term</tdef> is a short-hand <tref>string</tref> that expands
@@ -2773,7 +2773,7 @@
on mapping <tref title="term">terms</tref> to <tref title="IRI">IRIs</tref>.</p>
</section>
- <section>
+ <section class="normative">
<h2>Node Objects</h2>
<p>A <tdef>node object</tdef> represents zero or more properties of a
@@ -2883,7 +2883,7 @@
</ul>
</section>
- <section>
+ <section class="normative">
<h2>Value Objects</h2>
<p>A <tdef>value object</tdef> is used to explicitly associate a type or a
@@ -2916,7 +2916,7 @@
for more information on <tref title="value object">value objects</tref>.</p>
</section>
- <section>
+ <section class="normative">
<h2>Lists and Sets</h2>
<p>A <tref>list</tref> represents an <em>ordered</em> set of values. A set
@@ -2957,7 +2957,7 @@
<p>See <a class="sectionRef" href="#sets-and-lists"></a> for further discussion on sets and lists.</p>
</section>
- <section>
+ <section class="normative">
<h2>Language Maps</h2>
<p>A <tdef>language map</tdef> is used to associate a language with a value in a
@@ -2977,7 +2977,7 @@
on language maps.</p>
</section>
- <section>
+ <section class="normative">
<h2>Index Maps</h2>
<p>An <tdef>index map</tdef> allows keys that have no semantic meaning,
@@ -3004,7 +3004,7 @@
<p>See <a class="sectionRef" href="#data-indexing"></a> for further information on this topic.</p>
</section>
-<section>
+<section class="normative">
<h2>Context Definitions</h2>
<p>A <tdef>context definition</tdef> defines a <tref>local context</tref> in a
@@ -3133,7 +3133,7 @@
the primary data is stored in the default graph to enable consumers that do not support
datasets to process the information.</p>
- <section>
+ <section class="informative">
<h3>Transformation from JSON-LD to RDF</h3>
<p>The process of turning a JSON-LD document depends on executing the
@@ -3243,7 +3243,7 @@
evidence that JSON-LD is very flexible in what it can express across different
<tref>Linked Data</tref> approaches.</p>
- <section>
+ <section class="informative">
<h3>Turtle</h3>
<p>The following are examples of converting RDF expressed in Turtle [[TURTLE-TR]]
@@ -3401,7 +3401,7 @@
</section>
</section>
- <section>
+ <section class="informative">
<h3>RDFa</h3>
<p>The following example describes three people with their respective names and
@@ -3460,7 +3460,7 @@
</pre>
</section>
- <section>
+ <section class="informative">
<h3>Microformats</h3>
<p>The following example uses a simple Microformats hCard example to express
@@ -3502,7 +3502,7 @@
</pre>
</section>
- <section>
+ <section class="informative">
<h3>Microdata</h3>
<p>The HTML Microdata [[MICRODATA]] example below expresses book information as
@@ -3574,7 +3574,6 @@
<section class="appendix normative">
<h2>IANA Considerations</h2>
- <em>This section is normative</em>
<p>This section is included for community review and will be submitted to the
Internet Engineering Steering Group (IESG) as part of the Last Call announcement