Mulgara Project: Issueshttps://code.mulgara.org/https://code.mulgara.org/favicon.ico?15861924492009-09-19T16:55:39ZMulgara Project
Redmine Mulgara - Bug #205 (Closed): IRI parsing flakinesshttps://code.mulgara.org/issues/2052009-09-19T16:55:39ZGregg -gar@foo.bar
<pre>
<pre>
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix test: <http://example.org/test#> .
test:Test-comma test:uri test:U,062F .
</pre>
and the result is:
<pre>
0000: HTTP/1.1 500 Unable to load
file:///Users/gar/work/mulligan/test/iri/comma-U.062F.n3
into http://example.org/test/iri/: unexpected char: 'F'
</pre>
<pre></pre> Mulgara - Bug #202 (New): SPARQL queries with non-ascii chars failhttps://code.mulgara.org/issues/2022009-09-06T14:49:10ZGregg -gar@foo.bar
<p>I'm able to successfully load UTF-8 data with non-ascii characters, both in URIs and in literals (Mulgara 2.1.3). SPARQL queries against the data succeed so long as such non-ascii values match variables. However, if the query itself contains non-ascii chars it fails.</p>
<p>For example, if my data includes something like<br /><pre>
eg:Foo a eg:Füß
</pre><br />then a query like<br /><pre>
SELECT ?z WHERE { <eg:Foo> a ?z .}
</pre><br />will succeed, but one like<br /><pre>
SELECT ?x WHERE { ?x a <eg:füß> . }
</pre></p>
<p>will fail.</p>
<p>This is a show-stopper for me, since I need non-ascii Unicode in both my data and my queries.</p> Mulgara - Bug #201 (New): Accept-Charset HTTP header not honoredhttps://code.mulgara.org/issues/2012009-09-06T14:39:02ZGregg -gar@foo.bar
<p>(This ticket obsoletes <a class="issue tracker-3 status-3 priority-33 priority-high2" title="Bug: SPARQL results char encoding (New)" href="https://code.mulgara.org/issues/197">#197</a>)</p>
<p>Currently there doesn't seem to be a way to request a specific character encoding for query results. I think the way to do this is via content negotiation; at least I haven't seen any way to make such a request in SPARQL, but I might be wrong about that. In any case, I need a way to definitely indicate that I want utf-8 for the results.</p>
<p>The Mulgara HTTP interfaces (version 2.1.3) don't seem to honor the Accept-Charset header. Ideally it should be possible to use the header to stipulate any encoding for XML results. For JSON results, it should be possible to stipulate any UTF (utf-8, utf-16, utf-32) or UCS (UCS-4; I understand UCS-2 is obsolete.)</p> Mulgara - Bug #200 (Closed): JSON results encodinghttps://code.mulgara.org/issues/2002009-09-06T14:29:16ZGregg -gar@foo.bar
<p>(This ticket obsoletes <a class="issue tracker-3 status-3 priority-33 priority-high2" title="Bug: SPARQL results char encoding (New)" href="https://code.mulgara.org/issues/197">#197</a>.)</p>
<p>According section 3 of <a href="http://www.ietf.org/rfc/rfc4627.txt" class="external">RFC 4627</a>, <em>The application/json Media Type for <a class="wiki-page new" href="https://code.mulgara.org/projects/mulgara/wiki/JavaScript">JavaScript</a> Object Notation (JSON)</em>,</p>
<pre>
JSON text SHALL be encoded in Unicode. The default encoding is UTF-8.
</pre>
<p>Currently json output for sparql queries is not utf-8. This is for Mulgara 2.1.3.<br />To verify, load some triples with non-ascii chars in the URIs and also non-ascii string objects. Then run a query and the result will not be utf-8. I can supply test data if needed.</p>
<p>My data is for linguistics research, and requires the full range of unicode, so this is a show-stopper.</p> Mulgara - Bug #199 (New): TQL Load data encodinghttps://code.mulgara.org/issues/1992009-09-06T14:14:16ZGregg -gar@foo.bar
<pre>
To see this, take any ascii file, save it in emacs with latin-1 encoding, try to load it, get the error message. Then save it as utf-8 and it loads fine.
Ideally one should be able to specify any input encoding, but at a minimum I would suggest support for any form of Unicode, the (16?) ISO Latin encodings, one or two of the standard Japanese encodings, maybe a Chinese and Russian (KOI-8?).
I'm not sure how one would specify this; it should probably be specified in an HTTP header. I looked at the "SPARQL 2":http://www.w3.org/TR/sparql-features/#sparql-update new features draft and the "SPARUL":http://www.w3.org/Submission/2008/SUBM-SPARQL-Update-20080715/ stuff but I don't see any mention of charset stuff.</pre> Mulgara - Feature #198 (New): SPARQL XML results encodinghttps://code.mulgara.org/issues/1982009-09-01T20:02:05ZGregg -gar@foo.bar
<p>Currently the XML response to SPARQL queries does not specify an encoding in the XML header. The SPARQL Protocol definition doesn't seem to address this, and the examples omit it; but the SOAP example includes it. As a matter of "best practice" I think Mulgara should always explicitly indicate the encoding.</p> Mulgara - Bug #197 (New): SPARQL results char encodinghttps://code.mulgara.org/issues/1972009-09-01T19:59:32ZGregg -gar@foo.bar
<p>The SPARQL Protocol definition says that for the HTTP binding "the whttp:outputSerialization is application/sparql-results+xml with UTF-8 encoding, application/rdf+xml with<br />UTF-8 encoding." (<a href="http://www.w3.org/TR/rdf-sparql-protocol/#query-bindings-http" class="external">Section 2.2</a>) That's for XML results; I haven't found the equivalent requirement for JSON output, but for my application in any case full utf-8 support for json and xml is essential.</p>
<p>As a general matter (principle of least surprise), I think the expected behavior would be "encoding-in equals encoding-out", so if I populate a graph with utf-8 data, query results should be utf-8, no matter the output serialization. Alternatively, one could argue that the standard HTTP 1.1 Accept-Charset header should govern; since it is an HTTP binding, HTTP rules should apply.</p>
<p>The SPARQL Protocol definition doesn't explicitly address character encoding for the SOAP binding, but since SOAP is an HTTP protocol it should probably do utf-8 or honor the Accept-Charset header.</p> Mulgara - Bug #196 (New): N3 parser fails on colonhttps://code.mulgara.org/issues/1962009-08-30T11:41:03ZGregg -gar@foo.bar
<p>The TQL load command fails on: <br /><pre>
@prefix eg: <http://example.org/ns#> .
eg:foo
a eg:FooDad;
eg:long:tag eg:Oops
.
</pre><br />returning: <br /><pre>
Error 500 Unable to load file:///tmp/test.n3 into http://example.org/data: No @prefix for :tag</title>
</pre></p>
<p>But I believe colons are allowed here; in any case this n3 validates fine at <a class="external" href="http://www.rdfabout.com/demo/validator/validate.xpd">http://www.rdfabout.com/demo/validator/validate.xpd</a></p>
<p>I'm running 2.1.3; the issue tracker's version dropdown needs updating.</p> Mulgara - Bug #195 (New): Server IO Exceptionhttps://code.mulgara.org/issues/1952009-08-29T16:45:42ZGregg -gar@foo.bar
<p>I'm see the server dump a stack frame when I run a query using curl. I'm trying to query the system graph, on a freshly installed server with no loaded graphs. I don't know if I'm doing this right, but I don't think the server should barf. The curl file is:<br /><pre>
--url = "http://localhost:8080/sparql/"
--include
--header "Accept: application/sparql-results+xml"
--get
--data-urlencode "query=select ?x ?y ?z where {?x ?y ?z}"
--data-urlencode "default-graph-uri=http://localhost:8080/#"
</pre></p>
<p>mulgara.log says:<br /><pre>
2009-08-29 11:37:56,505 WARN [btpool0-17 - /sparql/?query=select%20%3Fx%20%3Fy%20%3Fz%20where%20%7B%3Fx%20%3Fy%20%3Fz%7D&default-graph-uri=http%3A%2F%2Flocalhost%3A8080%2F%23] http.HttpContent - Ignoring bad parameters in ' charset=iso-8859-1' from the content type for http://localhost:8080/#
2009-08-29 11:37:56,512 WARN [btpool0-17 - /sparql/?query=select%20%3Fx%20%3Fy%20%3Fz%20where%20%7B%3Fx%20%3Fy%20%3Fz%7D&default-graph-uri=http%3A%2F%2Flocalhost%3A8080%2F%23] http.HttpContent - Ignoring bad parameters in ' charset=iso-8859-1' from the content type for http://localhost:8080/#
2009-08-29 11:37:56,863 WARN [Thread-46] rdfxml.Parser - Recoverable error, line 1, column 122: {E213} Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
at com.hp.hpl.jena.rdf.arp.impl.XMLHandler.generalError(XMLHandler.java:197)
at com.hp.hpl.jena.rdf.arp.impl.RDFXMLParser.parse(RDFXMLParser.java:113)
at com.hp.hpl.jena.rdf.arp.ARP.load(ARP.java:143)
at org.mulgara.content.rdfxml.Parser.run(Parser.java:297)
Caused by: java.io.IOException: Server returned HTTP response code: 503 for URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1305)
at org.apache.xerces.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startEntity(Unknown Source)
at org.apache.xerces.impl.XMLEntityManager.startDTDEntity(Unknown Source)
at org.apache.xerces.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
at org.apache.xerces.impl.XMLDocumentScannerImpl$DTDDispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.DTDConfiguration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at com.hp.hpl.jena.rdf.arp.impl.RDFXMLParser.parse(RDFXMLParser.java:106)
... 2 more
</pre></p> Mulgara - Bug #194 (Closed): SPARQL endpoint returns 302 Found intead of 303 See Otherhttps://code.mulgara.org/issues/1942009-08-29T03:04:52ZGregg -gar@foo.bar
<p>Accessing the sparql endpoint without the final '/':<br /><pre>
~/work/mulgara/examples $ curl -I http://localhost:8080/sparql
HTTP/1.1 302 Found
Location: http://localhost:8080/sparql/
Content-Length: 0
Server: Jetty(6.1.x)
</pre><br />Shouldn't it return "303 See other"?</p>