--- a/spec/latest/json-ld-api/index.html Fri Aug 16 16:39:52 2013 +0200
+++ b/spec/latest/json-ld-api/index.html Fri Aug 16 18:34:21 2013 +0200
@@ -13,8 +13,8 @@
doRDFa: "1.1",
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "CR",
- publishDate: "2013-08-22",
+ specStatus: "ED",
+ // publishDate: "2013-08-22",
// if you wish the publication date to be other than today, set this
//publishDate: "2012-12-25",
copyrightStart: "2010",
--- a/spec/latest/json-ld/index.html Fri Aug 16 16:39:52 2013 +0200
+++ b/spec/latest/json-ld/index.html Fri Aug 16 18:34:21 2013 +0200
@@ -13,9 +13,9 @@
doRDFa: "1.1",
// specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
- specStatus: "CR",
+ specStatus: "ED",
// if you wish the publication date to be other than today, set this
- publishDate: "2013-08-22",
+ // publishDate: "2013-08-22",
copyrightStart: "2010",
// the specification's short name, as in http://www.w3.org/TR/short-name/
@@ -175,11 +175,11 @@
</ul>
<p>
- Before this specification may exit the Candidate Recommendation phase,
- at least two independent implementations must pass each test,
- although no single implementation must pass every test. The
- working group will decide when
- the test suite is of sufficient quality to test interoperability and
+ Before this specification may exit the Candidate Recommendation phase,
+ at least two independent implementations must pass each test,
+ although no single implementation must pass every test. The
+ working group will decide when
+ the test suite is of sufficient quality to test interoperability and
will produce an implementation report hosted together with the test suite.
</p>
@@ -616,7 +616,7 @@
</pre>
<p>The referenced context not only specifies how the terms map to
- <tref title="IRI">IRIs</tref> in the Schema.org vocabulary but also
+ <tref title="IRI">IRIs</tref> in the Schema.org vocabulary but also
specifies that string values associated with
the <code>homepage</code> and <code>image</code> property
can be interpreted as an <tref>IRI</tref> (<code>"@type": "@id"</code>,
@@ -1387,7 +1387,7 @@
For the current status see
<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>A number of JSON-LD document authors have been confused with the context
- sensitivity of @type. When used in the context, it means
+ sensitivity of @type. When used in the context, it means
"coerce the string value associated with the term to the following datatype."
When used in the body of a document in a JSON-LD object that represents a
node in the graph, it means "the rdf:type of the subject identified by @id
@@ -1397,7 +1397,7 @@
has led to confusion that may be easily remedied by reading a tutorial or
the specification. It may also be that further modifications for declaring a
datatype may be required, such as introducing a "@coerce" or "@literalType"
- keyword. Implementors are asked to pay particular attention to the
+ keyword. Implementors are asked to pay particular attention to the
feature and provide feedback on alternative ways to express the functionality
described above. The feature may remain in the specification as-is, or it may
be modified heavily after further implementation experience has been gathered.
@@ -3311,7 +3311,7 @@
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-concrete-rdf-syntax">concrete RDF syntax</tref>
as described in [[RDF11-CONCEPTS]]. Hence, a JSON-LD document is both an
RDF document <em>and</em> a JSON document and correspondingly represents an
- instance of an RDF data model. However, JSON-LD also extends the RDF data
+ instance of an RDF data model. However, JSON-LD also extends the RDF data
model to optionally allow JSON-LD to serialize
<tref href="http://www.w3.org/TR/rdf11-concepts/#dfn-generalized-rdf-dataset">Generalized RDF Datasets</tref>.
The JSON-LD extensions to the RDF data model are:</p>