W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > July 2010

Re: ISSUE-36 (Default vocab specification): Should Profile documents allow the specification of a default vocabulary? [RDFa 1.1 Core]

From: Shane McCarron <shane@aptest.com>
Date: Fri, 16 Jul 2010 09:36:42 -0500
Message-ID: <4C406E7A.2070503@aptest.com>
To: Toby Inkster <tai@g5n.co.uk>
CC: Manu Sporny <msporny@digitalbazaar.com>, public-rdfa-wg@w3.org
+1.  However, since @profile cascades, an imported profile that defines 
a default vocab would override any definition of @vocab in a parent.  
@vocab on the same element or on a child would override anything defined 
in the imported profile.  This is entirely consistent with how the rest 
of the spec works.

On 7/16/2010 9:27 AM, Toby Inkster wrote:
> On Fri, 2010-07-16 at 10:17 -0400, Manu Sporny wrote:
>    
>> Good point - so that's an argument for @vocab overriding any default
>> vocabulary specified in the @profile document.
>>      
> @vocab overriding @profile is consistent with @prefix overriding it
> (which is what currently happens).
>
>    

-- 
Shane P. McCarron                          Phone: +1 763 786-8160 x120
Managing Director                            Fax: +1 763 786-8180
ApTest Minnesota                            Inet: shane@aptest.com
Received on Friday, 16 July 2010 14:37:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:55:07 GMT