Added section outlining the focus on Linked Data and not RDF.
authorManu Sporny <msporny@digitalbazaar.com>
Sun, 19 Aug 2012 13:40:23 -0400
changeset 829 1fb5c742dd97
parent 828 d2ad17452b11
child 830 d4883ca1028f
Added section outlining the focus on Linked Data and not RDF.
spec/latest/json-ld-syntax/index.html
--- a/spec/latest/json-ld-syntax/index.html	Sun Aug 19 12:27:22 2012 -0400
+++ b/spec/latest/json-ld-syntax/index.html	Sun Aug 19 13:40:23 2012 -0400
@@ -471,13 +471,28 @@
  a graph representation can become difficult. In these instances, rather than
  having JSON-LD support an esoteric use case, we chose not to support the
  use case and support a simplified syntax instead. So, while Zero Edits is
- a goal, it is not always possible without adding great complexity to
+ a design goal, it is not always possible without adding great complexity to
  the language.
  </dd>
  <dt>One-pass Processing</dt>
  <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>
+ <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 
+ (RDF [[RDF-CONCEPTS]], TURTLE [[TURTLE-TR]], triple stores, and 
+ SPARQL [[RDF-SPARQL-QUERY]]). 
+ While this may be off-putting to proponents of the Semantic Web, the audience 
+ for this specification are Web developers that want a gentler introduction
+ 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-rdf-formats"></a> 
+ for more information about how JSON-LD integrates into the more traditional 
+ Semantic Web stack.
+ </dd>
 </dl>
 </section>
 
@@ -2618,7 +2633,7 @@
 
 <p>A JSON-LD processor SHOULD attempt to process non-conforming
   JSON-LD documents. Conformance variations MUST be reported through a
-  callback mechanism defined in [[!JSON-LD-API]].</p>
+  callback mechanism defined in [[JSON-LD-API]].</p>
 
 <p>The JSON-LD syntax is a subset of the JSON syntax. For a JSON-LD document
   to be conforming, it MUST be a valid JSON document as described in
@@ -3048,7 +3063,7 @@
   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.
+  [[JSON-LD-API]] specification.
   </p>
 
 </section>