RE: possible bug in SPARQL syntax test suite

How about - for now - commenting them out in the
turtle (with a comment why it was removed)?

Axel

> -----Original Message-----
> From: Andy Seaborne [mailto:andy.seaborne@epimorphics.com]
> Sent: Dienstag, 18. Dezember 2012 10:54
> To: SPARQL Working Group
> Subject: Fwd: possible bug in SPARQL syntax test suite
>
> We ought to remove inactive tests!
>
>       Andy
>
> -------- Original Message --------
> Subject: possible bug in SPARQL syntax test suite
> Resent-Date: Tue, 18 Dec 2012 01:36:52 +0000
> Resent-From: public-rdf-dawg-comments@w3.org
> Date: Tue, 18 Dec 2012 14:36:14 +1300
> From: Jeen Broekstra <jeen.broekstra@gmail.com>
> To: public-rdf-dawg-comments@w3.org
>
> In running the syntax tests over the latest update of the SPARQL test suite, I
> encountered the following positive test, which fails for me:
>
> http://www.w3.org/2009/sparql/docs/tests/data-sparql11/syntax-query/qname-
> escape-01.rq
>
> The query is the following:
>
> PREFIX og: <http://ogp.me/ns#>
> SELECT * WHERE {
>       ?page og:audio\:title ?title
> }
>
> As far as I can tell, this test case is out of date: colons in prefixed
> localnames are no longer to be escaped, and grammar production PN_LOCAL_ESC
> (see http://www.w3.org/TR/sparql11-query/#rPN_LOCAL_ESC)
> does no longer contain the ':' character as a legal value for escaping.
>
> There is a negative syntax test which covers exactly the same issue:
>
> http://www.w3.org/2009/sparql/docs/tests/data-sparql11/syntax-query/syn-bad-
> pname-06.rq
>
> Query:
>
> PREFIX : <http://example/>
> SELECT *
> {
>    :a :b :c\:z .
> }
>
> Clearly, these two tests are contradicting each other, and I suspect that the
> first one should be removed.
>
> Regards,
>
> Jeen
>
>
>

Received on Tuesday, 18 December 2012 10:11:23 UTC