--- a/spec/latest/json-ld-syntax/index.html Mon Dec 26 22:39:08 2011 -0800
+++ b/spec/latest/json-ld-syntax/index.html Tue Dec 27 09:42:49 2011 -0800
@@ -2,7 +2,7 @@
<html>
<head>
<title>JSON-LD Syntax 1.0</title>
-<meta http-equiv="content-type" content="text/html; charset=UTF-8">
+<meta http-equiv="content-type" content="text/html; charset=UTF-8"/>
<!--
=== NOTA BENE ===
For the three scripts below, if your spec resides on dev.w3 you can check them
@@ -12,7 +12,7 @@
src="http://dev.w3.org/2009/dap/ReSpec.js/js/respec.js" class="remove">
</script>
<script type="text/javascript" class="remove">
-
+//<![CDATA[
var preProc = {
apply: function(c) {
// extend the bibliography entries
@@ -255,6 +255,7 @@
content = content.replace(/@prefix/g, '<span class="sh_keyword">@prefix</span>');
return content;
}
+//]]>
</script>
<style>
.diff { font-weight:bold; color:#0a3; }
@@ -315,7 +316,7 @@
to be as simple as possible, utilizing the large number of JSON parsers
and libraries available today. It is designed to be able to
express key-value pairs, RDF data, RDFa [[RDFA-CORE]] data, Microformats
-[[MICROFORMATS]] data, and Microdata [[MICRODATA]]. That is, it supports
+[[MICROFORMATS]] data, and microdata [[MICRODATA]]. That is, it supports
every major Web-based structured data model in use today.
</p>
@@ -340,7 +341,7 @@
<ul>
<li>Web developers that want to understand the design decisions and
language syntax for JSON-LD.</li>
- <li>Software developers that want to encode Microformats, RDFa, or Microdata
+ <li>Software developers that want to encode Microformats, RDFa, or microdata
in a way that is cross-language compatible via JSON.</li>
<li>Software developers that want to implement processors and APIs for
JSON-LD.</li>
@@ -570,7 +571,7 @@
<section>
<h3>The Context</h3>
-<p>In JSON-LD, a <tdef>context</tdef> is used to map <tref>term</tref>s, i.e., keys and values
+<p>In JSON-LD, a <tdef>context</tdef> is used to map <tref>term</tref>s, i.e., keys with associated values
in an JSON document, to <tref>IRI</tref>s. A <tdef>term</tdef> is a short word that MAY be expanded to an
<tref>IRI</tref>. A <tref>term</tref> MUST have the lexical form of <cite><a
href="http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-NCName">NCName</a></cite> (see [[XML-NAMES]]), or
@@ -582,7 +583,7 @@
map directly to the IRI <code>http://xmlns.com/foaf/0.1/name</code>. This allows JSON-LD documents to be constructed
using the common JSON practice of simple name/value pairs while ensuring that the data is useful outside of the
page, API or database in which it resides. The value of a term mapping MUST be a simple string with the lexical form of an absolute <tref>IRI</tref>.
-</p></p>
+</p>
<p>These Linked Data <tref>term</tref>s are typically collected in a context document that would look something like this:</p>
@@ -689,7 +690,7 @@
would have to be declared in a single <tref>context</tref> could become quite large. To
reduce the number of different terms that must be defined, JSON-LD also allows
prefixes to be used to compact IRIs.
-<p>
+</p>
<p>For example, the <tref>IRI</tref> <code>http://xmlns.com/foaf/0.1/</code>
specifies a <tref>Web Vocabulary</tref> which may be represented using the
@@ -751,8 +752,6 @@
</section>
-</section>
-
<section>
<h1>Basic Concepts</h1>
@@ -775,8 +774,8 @@
<tref>active context</tref> are expanded to an IRI by JSON-LD processors.</li>
<li>An <tref>IRI</tref> is generated for the <tref>string</tref> value specified using
<code>@id</code> or <code>@type</code>.</li>
- <li>An <tref>IRI</tref> is generated for the value of any key if there are <tref>coercion</tref> rules in
- effect for that key that identify it as an <code>@id</code>.</li>
+ <li>An <tref>IRI</tref> is generated for the <tref>string</tref> value of any key for which there
+ are <tref>coercion</tref> rules in effect that identify the value as an <code>@id</code>.</li>
</ol>
<p>IRIs may be represented as an absolute IRI, a <tref>term</tref>, or a <tref>prefix</tref>:suffix construct.</p>
@@ -1765,7 +1764,7 @@
<p>The JSON-LD markup examples below demonstrate how JSON-LD can be used to
express semantic data marked up in other languages such as RDFa, Microformats,
- and Microdata. These sections are merely provided as proof that JSON-LD is
+ and microdata. These sections are merely provided as proof that JSON-LD is
very flexible in what it can express across different <tref>Linked Data</tref> approaches.</p>
<section>
@@ -1986,7 +1985,7 @@
<section>
<h3>Microdata</h3>
-<p>The Microdata example below expresses book information as a Microdata Work
+<p>The microdata example below expresses book information as a microdata Work
item.
</p>
@@ -2018,8 +2017,8 @@
-->
</pre>
-<p>Note that the JSON-LD representation of the Microdata information stays
-true to the desires of the Microdata community to avoid contexts and
+<p>Note that the JSON-LD representation of the microdata information stays
+true to the desires of the microdata community to avoid contexts and
instead refer to items by their full <tref>IRI</tref>.</p>
<pre class="example" data-transform="updateExample">
@@ -2112,7 +2111,7 @@
expand to "<code>http://example.org/myvocab#personality</code>".</p>
<p>This mechanism is a short-hand, called a <tref>Web Vocabulary</tref> <tref>prefix</tref>,
-and provides developers an unambiguous way to map any JSON value to RDF.<p>
+and provides developers an unambiguous way to map any JSON value to RDF.</p>
</section>