Re: [Fwd: SPARQL: QuotedIRIref too lax]

On Mon, 2005-08-01 at 13:38 +0100, Seaborne, Andy wrote:
> Bjoern Hoehrmann wrote:
>  > Dear RDF Data Access Working Group,
>  >
>  >   http://www.w3.org/TR/2005/WD-rdf-sparql-query-20050721/ section 10.1
>  > notes "IRIs are ordered by comparing the character strings making up
>  > each IRI" it's however not clear how character strings are compared,
>  > I would have expected that a `string < string` operator is defined, but
>  > section 11.1 only defines such an operator for numeric and dateTime
>  > types. Please change the draft such that ordering of IRIs is clear.
>  >
>  > regards,
> 
> 
> The current grammar does have a rather open production for QuotedIRIref 
> (anything except space and >).

Right. I think that's what the grammar should say.

To reiterate what I originally said in
  http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0156
and quoted last week in...
http://lists.w3.org/Archives/Public/public-rdf-dawg/2005JulSep/0103.html

[[ 
We should probably be more clear about whether this
is a sparql query or not:

  SELECT ?x WHERE { <foo###bar> dc:title ?x }.

REQUEST FOR TESTCASE.

I suggest that yes, it's a SPARQL query as defined by the
grammar, but it's erroneous; i.e. it's in the same category
as queries that don't obey the limitations on where variables
can go when using OPTIONAL.

So we probably need a new kinda of test case.
]]
 -- http://lists.w3.org/Archives/Public/public-rdf-dawg/2005AprJun/0156


> and the rq23 grammar becomes:
> 
> QuotedIRIref  	  ::= '<' IRICHAR* '>'     /* An IRI reference : RFC 3987 */

That won't address this issue; <foo###bar> matches but
isn't an IRI reference.


-- 
Dan Connolly, W3C http://www.w3.org/People/Connolly/
D3C2 887B 0F92 6005 C541  0875 0F91 96DE 6E52 C29E

Received on Monday, 1 August 2005 17:04:31 UTC