Re: ISSUE-36: Specifying a default vocabulary via an RDFa Profile

I do not have a problem with it.

Ivan

On Jul 22, 2010, at 19:05 , Shane McCarron wrote:

> Earlier today we sorted out a solution for Issue 24 - case insensitive TERMs.  Part of that solution is permitting host languages to define default TERMs and prefix mappings via a default RDFa Profile.
> 
> The RDFa Core specification already also permits host languages to define a 'default vocabulary'.  In other words, a default value for @vocab to be used with CURIEs with no prefix are used (e.g., property='shanesFavoriteProperty').  For completeness, I think we should extend the definition of RDFa Profile to allow a declaration of a default vocabulary.  This would involve the following changes:
> 
>   * Define the term 'rdfa:vocabulary' in our term collection, and
>     rules for it in Section 9.
>   * Swap steps 2 and 3 in the processing sequence so that @profile is
>     evaluated before @vocab.
> 
> Note that I do NOT think that either XHTML+RDFa nor HTML+RDFa should define a default vocabulary.  This facility is there for other, future host languages.
> 
> Comments?  Objections?
> 
> -- 
> Shane P. McCarron                          Phone: +1 763 786-8160 x120
> Managing Director                            Fax: +1 763 786-8180
> ApTest Minnesota                            Inet: shane@aptest.com
> 
> 
> 


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