W3C home > Mailing lists > Public > public-rdf-wg@w3.org > August 2011

Re: Can JSON-LD cater for Talis' RDF/JSON design goals?

From: Richard Cyganiak <richard@cyganiak.de>
Date: Fri, 26 Aug 2011 11:54:08 +0100
Cc: Ian Davis <ian.davis@talis.com>, RDF WG <public-rdf-wg@w3.org>, public-linked-json@w3.org
Message-Id: <18DDB70D-A33A-474C-9EF9-AC936B3B2235@cyganiak.de>
To: Thomas Steiner <tomac@google.com>
On 26 Aug 2011, at 10:32, Thomas Steiner wrote:
>> This gives me hope that there could be a way forward to produce only a
>> single JSON spec.
> 
> I think this is the most important part of your email :-) Me too, I
> strongly believe in the fact that both needs (RDF geek's, Web
> developer's) can be addressed by one spec.

The way to do this might be to define in the spec some sort of “RDF geek compatibility context” that could be used by anyone who wants a very regular and direct representation of RDF triples in JSON-LD. For example, my SPARQL store could use that context when serializing a CONSTRUCT result to JSON-LD.

I'd expect to be able to do something like this with the resulting JSON-LD:

  my_jsonld_data = …    // load JSON-LD file
  subject = "http://data.example.com/people/123";
  predicate = "http://xmlns.com/foaf/0.1/name";
  object = my_jsonld_data[subject][predicate][0];
  alert(object.string); // "Bob"

If that would be possible, then I'd consider JSON-LD as addressing the use cases that motivate RDF/JSON [1].

Best,
Richard


[1] http://www.w3.org/2011/rdf-wg/wiki/TF-JSON-UC#Use_JSON_syntax_to_interact_with_a_SPARQL_store_.28or_other_RDF_backend.29
Received on Friday, 26 August 2011 10:55:08 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 16:25:44 GMT