- From: Ruben Verborgh <ruben.verborgh@ugent.be>
- Date: Sun, 28 Dec 2014 20:43:46 +0100
- To: Gregg Kellogg <gregg@greggkellogg.net>
- Cc: public-rdf-comments@w3.org, Markus Lanthaler <markus.lanthaler@gmx.net>
Hi Gregg, > Is following redirection a problem for your test harness? The redirection itself does not pose a problem. The problem is it makes the test incorrect—and that's a serious issue. Below is the transaction that happens with cURL (truncated for clarity): $ curl -ivL 'http://www.w3.org/2013/TriGTests/trig-subm-27.trig' > GET /2013/TriGTests/trig-subm-27.trig HTTP/1.1 HTTP/1.1 301 Moved Permanently Location: http://www.w3.org/2013/TrigTests/trig-subm-27.trig > GET /2013/TrigTests/trig-subm-27.trig HTTP/1.1 HTTP/1.1 200 OK Content-Type: application/trig < # In-scope base URI is <http://www.w3.org/2013/TriGTests/trig-subm-27.trig> at this point However, the only correct way to parse this document is with <http://www.w3.org/2013/TrigTests/trig-subm-27.trig> as base IRI, since this is the URL with which the document has been requested. > Probably the cleanest is to change the README and .nq result files. I'm concerned that changing this actually invalidates tests Another option is to change the direction of the redirect, so that TrigTests => TriGTests instead of the other way round. This should keep compatibility with all existing tests (if they handle redirects), while providing the correct parsing of all documents. Best, Ruben
Received on Sunday, 28 December 2014 19:44:22 UTC