Re: abbreviated IRIs - ISSUE-14 (was Re: owl minutes)

> I'm not sure what the motivation was for slightly expanding on  
> QNames in
> the abbreviated IRI syntax, but not going all the way to CURIES.  Does
> anyone know?

The weren't going to move towards CURIES at all, but for a last  
minute complaint by your truly. They agreed to modify to accommodate  
abbreviations like: pmid:123004002, i.e. leading numerals, but did  
not want to go further in order to reserve the possibility that other  
characters that CURIES might have permitted, specifically, I believe,  
"/" could be used for other purposes, such as "path" delimiting  
characters.

-Alan

On Nov 12, 2007, at 7:17 AM, Peter F. Patel-Schneider wrote:

>
> I wanted to wait until I had a chance to look at the SPARQL spec,
> http://www.w3.org/TR/rdf-sparql-query/ before approving the resolution
> of ISSUE-14.
>
> The relevant part of the SPARQL spec appears to be Section 4.1.1.  I
> read this normative section fully, and came up with the following
> conclusions:
>
> 1/ The syntax for IRI_REF does not match the syntax for IRI  
> references.
> 2/ The abbreviated syntax for IRIs does not match CURIES, nor anything
>    else that I can tell, and will not generate all IRIs.
>
> However, this section, although it is marked as normative, is not
> complete.  (I seem to remember a comment by me on this before -  
> very bad
> document design - LET'S NOT DO THIS!)  To get a complete answer one  
> has
> to go to Appendix A, where deficiency 1 is alleviated.  However, I
> believe that deficiency 2 not alleviated.
>
> I'm not sure what the motivation was for slightly expanding on  
> QNames in
> the abbreviated IRI syntax, but not going all the way to CURIES.  Does
> anyone know?
>
> I don't view it as an acceptable solution - if we are
> going to generalize QNames, then we should go all the way to CURIES.
>
> peter
>