- From: Gregory Williams <greg@evilfunhouse.com>
- Date: Mon, 12 Oct 2015 09:12:45 -0400
- To: Karima Rafes <karima.rafes@gmail.com>
- Cc: public-rdf-tests@w3.org
>> Each of us may well think some choices are better than others, or that the >> specs should have said something else, but that's not the point when >> curating the W3C test suites. > > For the tests, I can use the Request Content Type (in the reference) > in the header HTTP but the basic developer JS uses the specific > parameter HTTP GET of triplestore and each triplestore implement a > different manner: > output=json > output=application/sparql-json... > format=jsonp > etc... > the reference of protocol SPARQL is again not enough… That sounds like a problem with how some developers are interacting with SPARQL endpoints, not with the SPARQL protocol spec. When staying within the spec, there are lots of conformant implementations that can all be used properly with content negotiation. In these cases, the SPARQL Protocol spec is “enough”. .greg
Received on Monday, 12 October 2015 13:13:14 UTC