W3C home > Mailing lists > Public > public-lod@w3.org > January 2010

Re: Creating JSON from RDF

From: Jeni Tennison <jeni@jenitennison.com>
Date: Thu, 7 Jan 2010 21:52:14 +0000
Cc: Mike Bergman <mike@mkbergman.com>, Dave Reynolds <dave.e.reynolds@googlemail.com>, public-lod@w3.org, Mark Birbeck <mark.birbeck@webbackplane.com>, John Sheridan <John.Sheridan@nationalarchives.gsi.gov.uk>
Message-Id: <2D77ED73-B84C-4701-B71B-7F0602EC09F6@jenitennison.com>
To: Niklas Lindström <lindstream@gmail.com>
Hi Niklas,

On 4 Jan 2010, at 22:32, Niklas Lindström wrote:
> "Gluon is a JSON format for RDF. It has a full syntax covering
> properties, resource references, bnodes and literals with optional
> datatype or language. With profiles, more more succinct forms are
> possible."

Thanks for the pointer! The compact (natural) example that you give at  
[1] is pretty much what I'd like to see as the JSON generated by  
default by a linked data API. Have you used this in anger anywhere?

What we're trying to do in the linked-data-api project [2] is thrash  
out not only what that JSON looks like but also how it might be  
generated automatically by a server sitting on top of a triplestore.  
But you say that you're working on a profiling mechanism? Perhaps we  
can join forces to work out what that might look like?



[1]: http://code.google.com/p/oort/source/browse/trunk/lab/gluon/etc/examples/lcsh/sh95000541-compact.json
[2]: http://code.google.com/p/linked-data-api/
Jeni Tennison
Received on Thursday, 7 January 2010 21:52:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:16:02 UTC