- From: Axel Polleres <axel.polleres@deri.org>
- Date: Tue, 22 Apr 2008 10:18:06 +0100
- To: Jos de Bruijn <debruijn@inf.unibz.it>
- CC: "Public-Rif-Wg (E-mail)" <public-rif-wg@w3.org>
Jos de Bruijn wrote: > I think we should have a shortcut mechanism for IRIs in the presentation > syntax, since they are the most common kind of identifier used in the > language. > I also think that we only need to have *one* mechanism for that. > We do not need to define a completely new parsable presentation syntax. > I also do not think we need to have a general shortcut mechanism in the > presentation syntax. For one thing, we don't have much time. > > Therefore, I would suggest to adopt the following suggestions by Axel: > >> 1) We use UNQUOTED prefix:ncname to denote CURIEs which expand to >> QUOTED IRIs > > 4) For symbol space IRIs (i.e. IRIs after the ^^) we only allow eithr > > the unquoted prefix:ncname writing or the angle bracketted name. that is basically the current status. And I was only suggesting some slight syntactic sugar to make things more readable. a) a prefix definition mechanism (adopted 1:1 from SPARQL, i.e. nothing new) b) (unquoted) curies are also allowed for the first part c) a stand-alone CURIE a:b is a shortcut for a:b^^rif:iri, i.e. a shortcut for "the expanded IRI for a:b"^^rif:iri d) angle brackets ( <iri> )serve as shortcut for "iri"^^rif:iri or if you want to write a full iri as symspace ("iri"^^<http://www.w3.org/2007/rif#iri>) > i.e., > mailto:chris = "http://....#chris"^^rif:iri = > "http://....#chris"^^http://.....#iri > > CURIES should *not* be allowed as the first part of a constant name, > i.e., my:curie^^rif:iri should not be allowed. why? if unquoted, I don't see any problem with allowing curies there, although I can live without b) if you buy in c) Axel -- Dr. Axel Polleres, Digital Enterprise Research Institute (DERI) email: axel.polleres@deri.org url: http://www.polleres.net/ rdfs:Resource owl:differentFrom xsd:anyURI .
Received on Tuesday, 22 April 2008 09:18:53 UTC