Re: URI/IRI concrete and abstract syntax

I have chnaged the grammar to use "IRIref" not "URI" as below.

	Andy

Dan Connolly wrote:
<snip/>

> 
> In the concrete syntax, i.e. the grammar, it's all IRI references.
> So this is pretty good...
> 
> [3]   BaseDecl   ::=   'base' QuotedURIref
> 
> probably better as QuotedIRIref.
> 
> But...
> 
> [12]   SourceSelector   ::=   URI
> 
> should be
> 
> [12]   SourceSelector   ::=   IRIref
> 
> and
> 
> [63]   URI   ::=   QuotedURIref | QName
> 
> should probably be
> 
> [63]   IRIref   ::=   QuotedIRIref | QName
> 
> likewise
> [41]   VarOrURI   ::=   Var | URI 
> should be
> [41]   VarOrIRIref   ::=   Var | IRIref
> 
> Also...
> 
> [69]   <Q_URIref>   ::=   '<' ([^> ])* '>' /* A URI relative reference :
> RFC 3869 */
> 
> should be...
> 
> [69]   <Q_IRIref>   ::=   '<' ([^> ])* '>' /* A IRI reference : RFC 3987
> */
> 
> and let's move that comment into the prose of the spec...
> how about under "Query Term Syntax".
> 
> 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.

<snip/>