W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > February 2011

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

From: Shane McCarron <shane@aptest.com>
Date: Wed, 09 Feb 2011 07:59:48 -0600
Message-ID: <4D529DD4.7080008@aptest.com>
To: Toby Inkster <tai@g5n.co.uk>
CC: RDFa Working Group WG <public-rdfa-wg@w3.org>, sysbot+tracker@w3.org
+1.  This is EXACTLY what I meant.  It was an (editorial) error to have 
@vocab set the default prefix.  I put that text in while we were 
experimenting with this feature and it somehow stayed there.

On 2/9/2011 6:05 AM, 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.

Shane P. McCarron                          Phone: +1 763 786-8160 x120
Managing Director                            Fax: +1 763 786-8180
ApTest Minnesota                            Inet: shane@aptest.com
Received on Wednesday, 9 February 2011 14:01:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:24 UTC