- From: Ivan Herman <ivan@w3.org>
- Date: Mon, 16 Nov 2009 14:17:25 +0100
- To: Niklas Lindström <lindstream@gmail.com>
- CC: Ben Adida <ben@adida.net>, RDFa <public-rdf-in-xhtml-tf@w3.org>
- Message-ID: <4B0150E5.9070402@w3.org>
Hi Niklas, Niklas Lindström wrote: >> >> So is there an elephant?:-) > > I haven't followed this discussion to closely, so I want to check if > this the following is considered: > > This usage will "muddle the waters" in cases when the relative URI:s > contain colon, and there is a prefix with the same name as the leading > part before that, right? Concrete (but contrieved) example: > > Given: > - base URI: <http://en.wikipedia.org/wiki/> > - prefix Talk: <http://example.org/schema/talk#> > > When: > @resource="Talk:Linked_Data" > > Then: > - URI becomes < http://example.org/schema/talk#Linked_Data>, > instead of <http://en.wikipedia.org/wiki/Talk:Linked_Data>, which is > might be expected? > Hm. You may found the elephant:-) Yes, in this case one would indeed get the example.org URI. The question is: is this use case so strong as to nullify the advantages of using CURIE-s in @about? Indeed, wikipedia uses such URI-s with ':' quite a lot but the user can of course put full URI-s into the value of @about... Thanks! Ivan > (Don't mind the malpractise of using a "Title-cased" prefix here, I > just picked the first real-word relative URL with colon in it I > found..) > > Best regards, > Niklas -- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Monday, 16 November 2009 13:18:02 UTC