RDFLib/rdflib — Issue #72: JSON serialization/parsing
Author: gjhiggins
Created: 2012-02-20 08:32:00+00:00
State: open

azarot...@gmail.com, 2009-07-15T17:41:44.000Z

Attached JSON serializer and parser, for consideration.

Comment 1 by eik...@gmail.com

Comment 2 by ed.summers

Comment 3 by lindstr...@gmail.com
Given the current plethora of JSON formats for RDF, can we really endorse this one? It's
a nice take (seems based on the Google JSON format for Atom/GData), but see also e.g.:

(my own, experimental, works with
rdflib)

(Furthermore, Google seems to be moving away from their current format to a
simplified/compact version
().)

Although I'd very much like to see JSON support in RDFLib, we should take care to
support only things with a wide adoption, or wait until more consensus (there is interest
within W3C for this as well).

Comment 4 by azarot...@gmail.com
Why pick and choose? So long as each format has an identifier, then they can be used
or not as the developer desires. Some better naming system could be used to make the
distinctions easier: json-(name) for example.

Comment 5 by ed.summers
Since eikeon is leaning towards bundling additional non-core functionality as 3rd
party extensions perhaps json serialization/deserialization can be left out of the
core and distributed separately somehow?

Comment 6 by eik...@gmail.com
Yeah, let's focus on getting the core bits back in order first for Milestone-Release2.5.

Comment 7 by ed.summers
Rob, would you be open to me working with you to bundle this as an extension? I'm
thinking of putting the code on github/bitbucket or in an extensions svn directory
here in rdflib svn, adding setup.py, docs, pushing to pypi, and adding an extensions
page to the rdflib wiki?

Comment 8 by azarot...@gmail.com
@edsu: Yep, no problem :)

Comment 9 by eik...@gmail.com
Sounds like a great plan guys; thank you. I think we'll all benefit from more distributed development and keeping
rdflib a little leaner.

Comment 10 by ed.summers
hmm I didn't get much time to spend on packaging up this as an extension. As lindstream said, there are some other more "standard" json formats that would make sense to bundle in rdflib. There's nothing that prevents azaroth42 from distributing his rdflib plugin himself. So I'm going to close this one.

Comment 11 by lindstr...@gmail.com
I agree, as expected. ;) There's a lot going on right now on this front, and we should wait to see how the dust settles standardization-wise. Specifically for RDFLib, I've included the Gluon mechanics in the Oort trunk proper for anyone interested (just one of many ways to do it, and gluon *will* get updated as consensus is hopefully approached).

Comment 12 by lindstr...@gmail.com
I should also say that if there's a convergence in the plethora of formats, I expect Gluon to merge with that. If so, I think my parsing and serializing code should be moved from "Oort" to rdfextras (considering that for "incubation" for possible inclusion in RDFLib once the format is finalized/standardized/"defacto"-ized).