W3C home > Mailing lists > Public > semantic-web@w3.org > October 2006

Re: Why JSON?

From: Ben Adida <ben@adida.net>
Date: Sat, 07 Oct 2006 12:10:49 -0400
Message-ID: <4527D189.2040502@adida.net>
To: Richard Newman <r.newman@reading.ac.uk>
CC: Hans Teijgeler <hans.teijgeler@quicknet.nl>, SW-forum <semantic-web@w3.org>, "Paap, Onno" <onno.paap@gmail.com>


In addition, because you can request Javascript SCRIPTs in HTML from
third-party domains, an HTML page can combine JSON objects from
different sources in any JS-compatible browser (with a little bit of
extra manipulation to notify the calling page that the JSON object has
been loaded.)

http://ajaxian.com/archives/jsonp-json-with-padding

Ideally, the browser security model will evolve to be a bit more
consistent regarding third-party data access, though great care is
required, of course. In the meantime, JSON and JSONP are the only way.

-Ben

Richard Newman wrote:
> Because RDF/XML, SPARQL-XML, and turtle are great, but nothing beats
> 
> var mine = eval ("(" + input + ")");
> 
> in Javascript.
> 
> That's a big deal.
> 
> Also, a JSON serialiser is trivial to write.
> 
Received on Saturday, 7 October 2006 16:30:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 07:41:53 UTC