W3C home > Mailing lists > Public > public-rdf-dawg@w3.org > October to December 2010

Re: Call for issues and comment on JSON result format

From: Sandro Hawke <sandro@w3.org>
Date: Tue, 21 Dec 2010 14:46:00 -0500
To: Gregory Williams <greg@evilfunhouse.com>
Cc: SPARQL Working Group <public-rdf-dawg@w3.org>
Message-ID: <1292960760.5553.235.camel@waldron>
On Tue, 2010-12-21 at 09:08 -0800, Gregory Williams wrote:
> On Dec 14, 2010, at 8:22 AM, Andy Seaborne wrote:
> 
> > This message is collect any issues and comments on the DAWG Note:
> > 
> > "Serializing SPARQL Query Results in JSON"
> > http://www.w3.org/TR/rdf-sparql-json-res/
> > 
> > Please reply to this message with any issues on this Note within one week so we can assess the practical implications of taking this through to REC as part of this working group.
> 
> I wanted to ask whether there'd be any support for adding JSONP[1] to the json results format. This would probably also involve the Protocol doc. It would allow easier use of sparql from within browsers. I'm not sure how prevalent support currently is, but I believe both ARC and Joseki currently implement JSONP.
> 
> .greg
> 
> [1] http://en.wikipedia.org/wiki/JSON#JSONP

I'm not an expert in this, but as I understand it, JSONP will be
obsolete when CORS is adopted by enough browsers.  I guess I lean toward
including it, but with some words about the security problems is raises
and its expected obsolescence.  As I understand it, the big problem with
JSONP is that you go from merely trusting that the endpoint is giving
you the data you want, to trusting it completely (within the sandbox of
the app itself).   Since there are lots of apps that don't really care
if they are subverted, and the alternatives are difficult or not yet
available, JSONP is quite useful.

     -- Sandro
Received on Tuesday, 21 December 2010 19:46:13 GMT

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