- From: Jonathan Rees <jar@creativecommons.org>
- Date: Sun, 29 May 2011 16:34:14 -0700
- To: Andy Seaborne <andy.seaborne@epimorphics.com>
- Cc: www-tag@w3.org
Thanks for the comments on the IR note. I should mention that I didn't mean for comments to be sent to just me, but should be sent to www-tag. The request to send to me was left over from earlier drafts that were not out for wider review. On Mon, May 23, 2011 at 7:43 AM, Andy Seaborne <andy.seaborne@epimorphics.com> wrote: > Jonathan, > > I didn't understand the sentence: > > [[ > However, SPARQL, Turtle, and RDFa are being extended to admit CURIEs that > include #, making this a newly attractive option. > ]] > > I can read that as CURIE syntax that can include a # as the output of the > CURIE-to-IRI process, or that the CURIE syntax in SPARQL can include a hash. I meant the latter... > In the first case > > PREFIX ex <http://example/ns#> > ... > { ?s ex: ?o } > .... You'd need a different prefix for each member of the big namespace, which is not what anyone would want, I think. > and in the second case > > PREFIX ex <http://example/> > ... > { ?s ex:ns#frag ?o } > .... > > SPARQL 1.1, Last Call, is not changing from the SPARQL 1.0 syntax where the > second use is not allowed. Oh well, too bad. I was being optimistically sloppy. Thanks for catching this. > # is the comment character in SPARQL. Ah, this puts an even bigger hole in my plan. Turtle would have the same problem. That just leaves RDFa, where a:b# is a valid CURIE. Will repair the document. Thanks Jonathan (tracker: ISSUE-57) > (CURIEs post-date the SPARQL syntax which has lead to a bit of confusion - > SPARQL talks about "prefixed names") > > Andy
Received on Sunday, 29 May 2011 23:34:42 UTC