Gregory Williams wrote:
Hello,

Hopefully this is the correct list to be sending to, but if not, hopefully someone can point me in the right direction.

I've been playing around with the DBPedia SPARQL endpoint at http://dbpedia.org/sparql , and have run across what seems like a bug. When I modify the http Accept header in the request, the endpoint seems to return an error if the header contains "text/turtle" (in addition to the expected results format of "application/sparql-results+xml"). This appears to be the case even though text/turtle is not the expected result mime type. Changing the turtle mime type to "text/x-turtle" returns a proper result.

Here are two simple requests that hopefully demonstrate the problem:

curl -I -H "Accept: application/sparql-results+xml,text/x-turtle" "http://dbpedia.org/sparql?query=PREFIX%20foaf%3A%20%3Chttp%3A%2F%2Fxmlns.com%2Ffoaf%2F0.1%2F%3E%0ASELECT%20*%20WHERE%20%7B%0A%09%3Fp%20a%20%3Chttp%3A%2F%2Fxmlns.com%2Ffoaf%2F0.1%2FPerson%3E%20.%0A%09%3Fp%20%3Chttp%3A%2F%2Fxmlns.com%2Ffoaf%2F0.1%2Fname%3E%20%3Fname%20.%0A%7D "

curl -I -H "Accept: application/sparql-results+xml,text/turtle" "http://dbpedia.org/sparql?query=PREFIX%20foaf%3A%20%3Chttp%3A%2F%2Fxmlns.com%2Ffoaf%2F0.1%2F%3E%0ASELECT%20*%20WHERE%20%7B%0A%09%3Fp%20a%20%3Chttp%3A%2F%2Fxmlns.com%2Ffoaf%2F0.1%2FPerson%3E%20.%0A%09%3Fp%20%3Chttp%3A%2F%2Fxmlns.com%2Ffoaf%2F0.1%2Fname%3E%20%3Fname%20.%0A%7D "

The first returns 200 OK, while the second returns 406 Unacceptable. The only difference is "text/x-turtle" versus "text/turtle".

Any thoughts as to why this might be happening?

thanks,
gregory williams


------------------------------------------------------------------------------
_______________________________________________
Virtuoso-users mailing list
Virtuoso-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtuoso-users


Mitko,

Please fix this.


--


Regards,

Kingsley Idehen       Weblog: http://www.openlinksw.com/blog/~kidehen
President & CEO OpenLink Software Web: http://www.openlinksw.com





Reply via email to