W3C home > Mailing lists > Public > public-linked-json@w3.org > July 2013

RE: Canonical JSON-LD format analogous to n-triples?

From: Markus Lanthaler <markus.lanthaler@gmx.net>
Date: Tue, 16 Jul 2013 19:50:16 +0200
To: "'Linked JSON'" <public-linked-json@w3.org>
Message-ID: <03a101ce824c$eeddc600$cc995200$@lanthaler@gmx.net>
On Tuesday, July 16, 2013 7:15 PM, David Booth wrote:
> I have a question about recommending a canonical JSON-LD profile to RDF
> users.  I would like to recommend a profile of JSON-LD that would be
> convenient for exchanging RDF data in JSON format, for use both by
> RDF-oriented processors and by JSON-oriented processors.  The ideal
> would probably be something analogous to n-triples: very simple (few or
> no options), very predictable, and very easy to generate and consume by
> machine.  Ease of human authoring is not a goal in this case.
> 
> I would like to be able to point both RDF and JSON developers at the
> appropriate sections of the JSON-LD spec, so that they don't have to
> learn all the ins and outs of the context and other features of JSON-LD
> that they won't need when they are simply using JSON-LD in this way as
> a JSON serialization of RDF data.
> 
> The goal would be something very simple, analogous to RDF/JSON
> https://dvcs.w3.org/hg/rdf/raw-file/default/rdf-json/index.html#
> though I don't care if the exact same conventions are used.
> 
> What JSON-LD profile should I recommend for this?  A combination of
> Expanded and Flattened document forms?

Exactly, expanded flattened document form. We have a profile media type
parameter and defined profile URIs so that you can signal and request it on
the HTTP level which means that you can use it directly in content
negotiation.


--
Markus Lanthaler
@markuslanthaler
Received on Tuesday, 16 July 2013 17:50:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:38 UTC