- From: Karima Rafes <karima.rafes@gmail.com>
- Date: Mon, 12 Oct 2015 15:54:34 +0200
- To: public-rdf-tests@w3.org
> 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”. >the protocol permits those variations for good reason. >it also provides means to discover the respective capabilities. >what is missing? Ok if I resume, if the developers have to use a different code for each triplestore... it's for a good reason... I thought the aim was to become interoperable. Sorry ;) When you will be agree on one clear protocol for SPARQL, I will be able to help you on the SPARQL test suite because for the moment, I have no the time to develop a new patch for all interpretations of each editor. Best regards Karima
Received on Monday, 12 October 2015 13:55:02 UTC