- From: Gregg Kellogg <greggkellogg@gmail.com>
- Date: Fri, 9 Mar 2012 21:59:00 -0700
- To: Iker Huerga <iker.huerga@gmail.com>
- Cc: Jeremy Carroll <jeremy@topquadrant.com>, "semantic-web@w3.org" <semantic-web@w3.org>
- Message-Id: <8AD630BB-5DF1-4A4D-83CD-15087DF36020@gmail.com>
My implementation looks at the accept header to determine the format to return. Gregg Kellogg Sent from my iPhone On Mar 9, 2012, at 9:49 PM, Iker Huerga <iker.huerga@gmail.com> wrote: > Hi, > > At least from my understanding this is endpoint dependent and is not standardized. I think there was some discussion about this a couple of years ago, you can take a look at [1]. > > Hope this helps > > [1] http://www.w3.org/2009/sparql/wiki/Feature:ReturnFormatKeyword > > 2012年3月9日 Jeremy Carroll <jeremy@topquadrant.com> > I am chasing through the standards trying to understand how to poke a SPARQL endpoint to give me JSON in a conformant fashion. > > So far I have that I can set my accept headers to ask for application/sparql-results+json > > I also note that different endpoints also seem to support additional query parameters to make this work e.g. > > http://dbpedia.org/sparql?query=select%20?book%20where%20{}&output=json > http://dbpedia.org/sparql?query=select%20?book%20where%20{}&format=json > > http://data.linkedmdb.org/sparql?query=select%20?book%20where%20{}&output=json > > http://lobid.org/sparql/?query=select ?b where {}&output=json > > I don't see where this output=json thing is documented .... > > thanks > > Jeremy > > > > > > > -- > Iker Huerga > http://www.ikerhuerga.com/ >
Received on Saturday, 10 March 2012 04:59:33 UTC