W3C home > Mailing lists > Public > www-tag@w3.org > June 2010

Re: RDF and JSON

From: Reto Bachmann-Gmür <reto@gmuer.ch>
Date: Thu, 17 Jun 2010 23:15:51 +0200
Message-ID: <AANLkTinne4KdEVp7fBgL7Q4IbPrOWCJj-ah6Ra-NgW0h@mail.gmail.com>
To: nathan@webr3.org
Cc: Graham Klyne <GK@ninebynine.org>, "www-tag@w3.org" <www-tag@w3.org>
FYI: Apache Clerezza provides an rdf/json parser and serilaizer
compliant with the talis spec, the sources are here:
http://svn.apache.org/viewvc/incubator/clerezza/trunk/org.apache.clerezza.parent/org.apache.clerezza.rdf.rdfjson/

On Thu, Jun 17, 2010 at 9:53 AM, Nathan <nathan@webr3.org> wrote:
> Graham Klyne wrote:
>>>
>>>   timbl: If people are moving data around, the direction to go is to
>>>   standardize some way to map JSON to/from RDF
>>
>> You're probably aware, but just in case...
>>
>> http://n2.talis.com/wiki/RDF_JSON_Specification
>>
>> FWIW, this discussion relates to an issue w.r.t. a Javascript app I'm
>> working on; the intent was to use RDF but initially I used JSON for speed of
>> deployment (ala agile philosophy) [2].  Now I'm looking at migration to use
>> RDF [1], but despite original intentions it's not looking quite as clean as
>> I originally hoped:
>>
>> [1] http://code.google.com/p/shuffl/wiki/Alternative_serialization_notes
>> [2]
>> http://code.google.com/p/shuffl/wiki/TechnicalNotes#Representing_card_data
>
> Also, JSON-LD [1] from the RDFa guys
>
> [1] http://rdfa.digitalbazaar.com/specs/source/json-ld/
>
> Best,
>
> Nathan
>
>
Received on Thursday, 17 June 2010 21:16:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:33:06 UTC