- From: Sandro Hawke <sandro@w3.org>
- Date: Fri, 18 Mar 2011 19:35:32 -0400
- To: Lee Feigenbaum <lee@thefigtrees.net>
- Cc: David Wood <dpw@talis.com>, RDF WG <public-rdf-wg@w3.org>
On Fri, 2011-03-18 at 19:26 -0400, Lee Feigenbaum wrote:
> On 3/18/2011 7:10 PM, David Wood wrote:
> > Hi Lee,
> >
> >> On the wire, we serialize RDF in JSON, of course
> >
> > Why "of course"? Why not use Turtle or n-triples or something else?
>
> For a JavaScript client? Because I've got about a hundred JSON parsers
> to choose from (we use whatever comes with dojo). Why choose Turtle or
> n-triples?
Well, the reason to use Turtle would be so that you can read everyone
else's data, not just your own.
But the browser security policy prevents that, anyway. So until CORS
[1] is deployed in clients and servers, there's no real win, and you
might as well make up your own protocol/format.
The usual workaround for the browser security policy, jsonp, also
doesn't help here, since most people don't serve their Turtle in a jsonp
wrapper.
-- Sandro
[1] http://www.w3.org/TR/cors/
Received on Friday, 18 March 2011 23:35:41 UTC