Re: ISSUE-83 (CURIEs must require colon): CURIEs are dangerous when used in combination with @vocab and @about [LC Comment - RDFa Core 1.1]

To see if I understand: @vocab does not affect CURIE production only terms, right? 

Ivan




On Feb 9, 2011, at 13:05 , Toby Inkster wrote:

> On Sat, 05 Feb 2011 23:27:42 +0000
> RDFa Working Group Issue Tracker <sysbot+tracker@w3.org> wrote:
> 
>> The solution to this problem must not create backward
>> incompatibilities and must allow the usage of @vocab.
> 
> Proposed solution - which is probably the same as what Shane
> suggested...
> 
> 1. @vocab no longer sets the default prefix mapping.
> 
> 2. @vocab sets some other concept called something like the "wildcard
> profile".
> 
> 3. The wildcard profile URI is used as a prefix for any terms which are
> discovered but have not been defined by any of the active profiles.
> 
> Imagine the CURIE/Term mapping for about="#me" now:
> 
> 	- it does not match the Term production, so we don't check to
> 	  see if "#me" is a term in any of the defined profiles.
> 	  Further, it is not subject to the wildcard profile. 
> 
> 	- it *does* match the CURIE production, however, only with the
> 	  default prefix. The default prefix is undefined by default,
> 	  and people can no longer use @vocab to define it (because
> 	  that's not what @vocab does any more!)
> 
> 	- so it falls back to a relative URI reference.
> 
> That should mean that Nathan's example gets parsed correctly.
> 
> -- 
> Toby A Inkster
> <mailto:mail@tobyinkster.co.uk>
> <http://tobyinkster.co.uk>
> 


----
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