W3C home > Mailing lists > Public > public-rdf-dawg-comments@w3.org > December 2012

Re: possible bug in SPARQL syntax test suite

From: Andy Seaborne <andy.seaborne@epimorphics.com>
Date: Tue, 18 Dec 2012 09:46:16 +0000
Message-ID: <50D03B68.1020500@epimorphics.com>
To: public-rdf-dawg-comments@w3.org
Correct - this is :test_52 in the manifest and it's commented out of the 
list of tests in the manifest:

The manifest has:

[[
# :test_52	# obsoleted by decision to allow colons in prefixname local 
parts, but not allow them to be escaped
]]


Do you drive your test harness off the manifest or directly from the 
files in the directory?

(Personally, I wanted to remove tests that weren't active)

	Andy


On 18/12/12 01:36, Jeen Broekstra wrote:
> 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 09:47:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 18 December 2012 09:47:01 GMT