JSON-LD spec updates for September 2012

Richard, Sandro, and RDF WG members,

The editors for the JSON-LD specifications have prepared two
review-ready documents for the RDF Working Group here:

JSON-LD 1.0 Syntax


Diff-marked versions from the First Public Working Draft of both
documents can be found here:


These documents include the following updates since the release of the
First Public Working Draft:


They also include the following updates made during the last month:

JSON-LD 1.0 Syntax


The introduction of the document has been re-worked to flow better than
it had in the past. The following introductory portions of the document
have been re-written based on feedback from Richard Cyganiak and the
Community Group.

3 Basic Concepts
3.1 Benefits of JSON-LD
3.2 JSON-LD Data Model

We now start by providing reasons that a JSON developer may want to use
JSON-LD. We then explain the basic JSON-LD data model. There is no
longer a precise normative definition of Linked Data as the precise
definition we had was raising too many concerns around what did and did
not constitute Linked Data.

An illustration has been added to the JSON-LD data model section to
attempt to illustrate the model explanation.

Removal of N-Triples/N-Quads in examples

We were using N-Triples and N-Quads to illustrate the output of some of
the documents. We now just use a simple table to convey the same idea.
This removes the need to understand N-Triple and N-Quad syntax.

ISSUE status

There are 6 issues remaining:


4 of them have proposals that are being actively discussed at the moment.
1 of them is editorial and will be fixed as soon as we get more time.
1 of them is waiting on Richard to propose some spec edits.

We're in pretty good shape with this document.



The introduction was re-worked slightly to flow a bit better. It's still
rough and needs more work.

Error Behavior

A JSON-LD processor is capable of recovering from a wide range of
conformance errors by ignoring/dropping the current key-value that is
being processed. We wanted to give developers the ability to say which
conformance errors should stop the processor and which ones should cause
it to ignore the input and continue. There is now a conformance issue


Each method is now capable of dealing with errors. We use patterns that
are used heavily in the node.js community, passing the error as the
first parameter (null if there is no error), and the data as the second


We're still actively discussing this issue, so things may change over
the next month or two.


There is now a parameter that can be passed to .compact() and .expand()
to "flatten" the output. Flattening merges all predicate-value pairs
associated with a particular subject into one JSON object. It removes
deeply nested objects in JSON-LD and places all of them in one top-level

ISSUE status

There are currently 6 open JSON-LD API issues.

3 of them have proposals that are actively being discussed.
1 of them is waiting on Gregg to propose spec text.
1 of them is waiting on Dave Longley to propose spec text.
1 of them has a proposal, but has not been discussed yet.

The prose of the spec is not that great at the moment and needs some
heavy work over the next month or two in order to bring it up to our
standards. The algorithms also need to be gone over with a fine-toothed
comb to knock out any bugs that may be in there.

-- manu

Manu Sporny (skype: msporny, twitter: manusporny)
Founder/CEO - Digital Bazaar, Inc.
blog: HTML5 and RDFa 1.1

Received on Sunday, 30 September 2012 21:30:29 UTC