--- a/spec/latest/json-ld-syntax/index.html	Mon Oct 22 18:09:25 2012 +0200
+++ b/spec/latest/json-ld-syntax/index.html	Mon Oct 22 20:31:40 2012 +0200
@@ -430,7 +430,7 @@
  <dd>JSON-LD supports one-pass processing, which results in a very small memory
  footprint when processing documents. For example, to expand a JSON-LD document
  from a compacted form, only one pass is required over the data.</dd>
- <dt>Linked Data-centric</dt>
+ <!--<dt>Linked Data-centric</dt>
  <dd>The focus on Linked Data is placed at a much higher priority than the
  focus on the Semantic Web. One outcome of this ordering of
  priorities is an aggressively reduced focus on the Semantic Web stack.
@@ -439,10 +439,10 @@
  and a simpler technology stack for using Linked Data in their Web applications.
  Semantic Web concepts, such as conversion to and from RDF, are fully supported
  by JSON-LD, but the implementation of these features are not elaborated upon
- in this specification. See <a href="#relationship-to-other-linked-data-formats-and-data-models"></a>
+ in this specification. See <a href="#relationship-to-other-linked-data-formats"></a>
  for more information about how JSON-LD integrates into the more traditional
  Semantic Web stack.
- </dd>
+ </dd>-->
 </dl>
 </section>
 
@@ -3041,61 +3041,46 @@
 </pre>
 </section>
 
-<section class="appendix informative">
-<h2>Relationship to Other Linked Data Formats and Data Models</h2>
+<section class="appendix normative">
+<h2>Relationship to RDF</h2>
 
 <p class="issue" data-number="157">
-The intent of the Working Group and the Editors of this specification is to
-eventually align terminology used in this document with the terminology used
-in the RDF Concepts document [[!RDF-CONCEPTS]] to the extent to which it makes sense to do so.
-In general, if there is an analogue to terminology used in this document in
-the RDF Concepts document, the preference is to use the terminology in the
-RDF Concepts document.
+  The intent of the Working Group and the Editors of this specification is to
+  eventually align terminology used in this document with the terminology used
+  in the RDF Concepts document [[!RDF-CONCEPTS]] to the extent to which it makes sense to do so.
+  In general, if there is an analogue to terminology used in this document in
+  the RDF Concepts document, the preference is to use the terminology in the
+  RDF Concepts document.
 </p>
 
-<p>JSON-LD is a specification for representing <tref>Linked Data</tref> in JSON. A common
-  way of working with Linked Data is through <tdef>RDF</tdef>, the Resource Description Framework.
-  RDF can be expressed using JSON-LD by associating JSON-LD concepts such as <code>@id</code>
-  and <code>@type</code> with the equivalent <tref>IRI</tref>s in RDF. Further information about
-  RDF may be found in the [[RDF-PRIMER]].</p>
+<p>The RDF data model, as outlined in [[!RDF-CONCEPTS]], is an abstract
+  syntax for representing a directed graph of information. JSON-LD is
+  capable of serializing any RDF graph, and performing full RDF to
+  JSON-LD to RDF round-tripping. A complete description the algorithms to
+  convert from RDF to JSON-LD and from JSON-LD to RDF are included in the
+  JSON-LD API [[JSON-LD-API]] specification.</p>
+
+<p>JSON-LD allows properties to be <tref title="blank node">blank nodes</tref>,
+  while RDF does not. Expressing properties as
+  <tref title="blank node">blank nodes</tref> in JSON-LD only becomes an issue
+  (and could raise an exception) when it is transformed to RDF.</p>
+
+</section>
+
+<section class="appendix informative">
+<h2>Relationship to Other Linked Data Formats</h2>
 
 <p>The JSON-LD markup examples below demonstrate how JSON-LD can be used to
-  express semantic data marked up in other languages and data models
-  such as RDF, Turtle, RDFa, Microformats,
-  and Microdata. These sections are merely provided as evidence that JSON-LD is
-  very flexible in what it can express across different <tref>Linked Data</tref> approaches.
-  Further information on transforming JSON-LD into RDF are detailed in the
-  [[JSON-LD-API]].</p>
-
-<section>
-  <h3>RDF</h3>
-
-  <p>The RDF data model, as outlined in [[RDF-CONCEPTS]], is an abstract
-  syntax for representing a directed graph of information. JSON-LD is
-  capable of serializing any RDF graph, and performing full RDF to
-  JSON-LD to RDF round-tripping. A complete description of how JSON-LD maps
-  to RDF and algorithms detailing how one can convert from RDF to
-  JSON-LD and from JSON-LD to RDF are included in the JSON-LD API
-  [[JSON-LD-API]] specification.
-  </p>
-
-  <p>JSON-LD allows properties to be BNodes, while RDF does
-  not. Expressing properties as BNodes in JSON-LD only becomes an issue
-  (and could raise an exception) when it is transformed to RDF.</p>
-
-  <p>Note that the <tref>JSON-LD data model</tref> is silent on the topic of
-  <tref title="unlabeled node">unlabeled nodes</tref>. Nevertheless,
-  this specification allows for the expression of
-  <tref title="unlabeled node">unlabeled nodes</tref>, as most graph-based data
-  sets on the Web contain a number of associated nodes that are not named and
-  thus are not directly de-referenceable.
-  </p>
+  express semantic data marked up in other linked data formats such as Turtle,
+  RDFa, Microformats, and Microdata. These sections are merely provided as
+  evidence that JSON-LD is very flexible in what it can express across different
+  <tref>Linked Data</tref> approaches.</p>
 
 <section>
   <h3>Turtle</h3>
 
-  <p>The following are examples of converting <tref>RDF</tref>
-  expressed in [[TURTLE-TR]] into JSON-LD.</p>
+  <p>The following are examples of converting RDF expressed in [[TURTLE-TR]]
+    into JSON-LD.</p>
 
 <section>
 <h4>Prefix definitions</h4>