--- a/spec/latest/json-ld/index.html Tue Jun 11 19:17:43 2013 +0200
+++ b/spec/latest/json-ld/index.html Tue Jun 11 13:22:11 2013 -0400
@@ -180,7 +180,7 @@
sites across the Web.</p>
<p>JSON-LD is a lightweight syntax to serialize <tref>Linked Data</tref> in
- JSON [[!RFC4627]]. Its design allows existing JSON to be transformed to
+ JSON [[!RFC4627]]. Its design allows existing JSON to be interpreted as
Linked Data with minimal changes. JSON-LD 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. Since
@@ -217,14 +217,14 @@
<ul>
<li>Software developers who want to encode Linked Data in a variety of
- programming languages that can use JSON</li>
+ programming languages that can use JSON.</li>
<li>Software developers who want to convert existing JSON to JSON-LD.</li>
<li>Software developers who want to understand the design decisions and
- language syntax for JSON-LD</li>
+ language syntax for JSON-LD.</li>
<li>Software developers who want to implement processors and APIs for
- JSON-LD</li>
- <li>Software developers who want to generate or consume Linked Data, an
- RDF graph, or an RDF Dataset in a JSON syntax</li>
+ JSON-LD.</li>
+ <li>Software developers who want to generate or consume Linked Data,
+ an RDF graph, or an RDF Dataset in a JSON syntax.</li>
</ul>
<p>A companion document, the JSON-LD Processing Algorithms and API specification
@@ -270,13 +270,13 @@
esoteric use case, we chose not to support the use case. While Zero Edits is
a design goal, it is not always possible without adding great complexity
to the language. We should focus on simplicity when possible.</dd>
- <dt>Usable as RDF syntax</dt>
- <dd>JSON-LD was designed to be usable directly as JSON, with no knowledge of RDF,
- but was designed also to be usable as RDF for use with other Semantic Web
- technologies like SPARQL. People intending to use JSON-LD with RDF tools will
- find it can be used as another RDF syntax, like Turtle. Complete details of
- how JSON-LD relates to RDF can be found in
- <a class="sectionRef" href="#relationship-to-rdf"></a>.</dd>
+ <dt>Usable as RDF</dt>
+ <dd>JSON-LD was designed to be usable by developers as
+ idiomatic JSON, with no need to understand RDF [[RDF11-CONCEPTS]]. If
+ desired, it was also designed to be usable as RDF. People intending to use
+ JSON-LD with RDF tools will find it can be used like any other RDF syntax.
+ Complete details of how JSON-LD relates to RDF are in
+ <a href="#relationship-to-rdf"></a>.</dd>
</dl>
</section>
@@ -547,7 +547,7 @@
document. Information contained outside of the <code>@context</code> value
is ignored when the document is used as an external JSON-LD context document.</p>
- <p>JSON documents can be transformed to JSON-LD without having to be modified by
+ <p>JSON documents can be interpreted as JSON-LD without having to be modified by
referencing a <tref>context</tref> via an HTTP Link Header
as described in <a class="sectionRef" href="#interpreting-json-as-json-ld"></a>. It is also
possible to apply a custom context using the JSON-LD API [[JSON-LD-API]].</p>
@@ -2685,8 +2685,8 @@
to be escaped.</p>
<p>Defining how such data may be used is beyond the scope of this specification.
- The embedded JSON-LD document might be extracted as is or, e.g., be converted
- to RDF.</p>
+ The embedded JSON-LD document might be extracted as is or, e.g., be
+ interpreted as RDF.</p>
<p>If JSON-LD content is extracted as RDF [[RDF11-CONCEPTS]], it should be expanded into an
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-rdf-dataset">RDF Dataset</tref> using the
@@ -2759,11 +2759,11 @@
<a href="http://www.w3.org/2011/rdf-wg/wiki/JSON-LD_Features_at_Risk">features "at risk" in JSON-LD 1.0</a></p>
<p>RDF does not currently allow a <tref>blank node</tref> to be
used as <tref>graph name</tref> or <tref>property</tref>, while JSON-LD
- does. JSON-LD to RDF converters can work around this restriction, when converting
- JSON-LD to RDF, by converting such <tref title="blank node">blank nodes</tref> to
+ does. JSON-LD to RDF interpreters can work around this restriction, when interpreting
+ JSON-LD as RDF, by transforming such <tref title="blank node">blank nodes</tref> to
<tref title="IRI">IRIs</tref>, minting new "Skolem IRIs" as per
<cite><a href="http://www.w3.org/TR/rdf11-concepts/#section-skolemization">Replacing Blank Nodes with IRIs</a></cite>
- of [[RDF11-CONCEPTS]]. Based on feedback from implementors the
+ of [[RDF11-CONCEPTS]]. Based on feedback from implementors, the
Working Group may decide to disallow blank nodes as graph names and
properties in JSON-LD. If this change would affect you, be sure to
send in a comment.</p>
@@ -3168,10 +3168,10 @@
</ul>
- <p>Summarized these differences mean that JSON-LD is capable of serializing any RDF
+ <p>Summarized, these differences mean that JSON-LD is capable of serializing any RDF
graph or dataset and most, but not all, JSON-LD documents can be directly
- transformed to RDF. It is possible to work around this restriction, when
- converting JSON-LD to RDF, by converting <tref title="blank node">blank nodes</tref>
+ interpreted as RDF. It is possible to work around this restriction, when
+ interpreting JSON-LD as RDF, by transforming <tref title="blank node">blank nodes</tref>
used as <tref title="graph name">graph names</tref> or
<tref title="property">properties</tref> to <tref title="IRI">IRIs</tref>,
minting new "Skolem IRIs" as per
@@ -3304,7 +3304,7 @@
<section class="informative">
<h3>Turtle</h3>
- <p>The following are examples of converting RDF expressed in Turtle [[TURTLE]]
+ <p>The following are examples of transforming RDF expressed in Turtle [[TURTLE]]
into JSON-LD.</p>
<section>