garlik/4store — Issue #51: Unencoded unicode character in SPARQL XML result
Author: RinkeHoekstra
Created: 2012-01-03 12:00:12+00:00
State: open

My 4store database contains a literal with a unicode 0x1 character in it. When one of my SPARQL results contains this literal, the character is returned as is, i.e. it is not encoded as an XML entity. This means that the SPARQL XML is invalid, as 0x1 is not allowed in XML documents, and my XML parser falls over.

See (line 2186):

http://eculture2.cs.vu.nl:5020/sparql/?query=SELECT+%3Fb+%3Fv0%0AWHERE+%7B%0A%3Fb+%3Chttp%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23type%3E+%3Chttp%3A%2F%2Fwww4.wiwiss.fu-berlin.de%2Fsider%2Fresource%2Fsider%2Fdrugs%3E+.%0AOPTIONAL+%7B%0A%3Fb+%3Chttp%3A%2F%2Fwww4.wiwiss.fu-berlin.de%2Fsider%2Fresource%2Fsider%2FdrugName%3E+%3Fv0+.%0A%7D%0A%7D+OFFSET+8000+LIMIT+1000