- From: Toby Inkster <tai@g5n.co.uk>
- Date: Wed, 9 Feb 2011 12:05:03 +0000
- To: RDFa Working Group WG <public-rdfa-wg@w3.org>
- Cc: sysbot+tracker@w3.org
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>
Received on Wednesday, 9 February 2011 12:05:06 UTC