W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > December 2007

Re: what are you saying?

From: Shane McCarron <shane@aptest.com>
Date: Thu, 13 Dec 2007 10:01:11 -0600
Message-ID: <47615747.60102@aptest.com>
To: Manu Sporny <msporny@digitalbazaar.com>
CC: RDFa <public-rdf-in-xhtml-tf@w3.org>



Manu Sporny wrote:
> This is the crux of the argument, as far as I see it, and I have to
> strongly agree with Mark's position. RDFa is not a vocabulary, thus
> placing something in @profile doesn't make much sense as @profile is
> meant for specifying definitions of vocabularies[1].
>   
I concur.  However, *part* of RDFa is a vocabulary.  We define values 
for @rel/@rev.  So.... it *could* be argued that we the thing at the end 
of the profile URI should define that vocabulary.  And then RDFa parsers 
could use that vocabulary AND know that when that vocabulary is in use 
the document is definitely RDFa.
> One approach would be to create a vocabulary that specifies the type of
> metadata that is embedded in the document, so, we could have something like:
>
> <head profile="http://www.w3.org/profiles/html-metadata">
>    <meta name="metadata-flavor" content="xhtml+rdf">
>    <meta name="metadata-flavor" content="microformats">
> </head>
>   
Interesting idea - add a layer of abstraction.  Its a classic.  Also 
happens to work in HTML 4 and XHTML.
> Another approach could have us using @class to hint to the user agent
> that there is RDFa data in the document, something like:
>
> <div class="xhtml-rdf">... RDFa goes here ...</div>
>   
Can I say "ick"?  I really think this is an overloading of @class 
(despite the fact that @class can contain anything).  Plus, we are 
really talking about announcement, and that should happen in the head IMHO.

-- 
Shane P. McCarron                          Phone: +1 763 786-8160 x120
Managing Director                            Fax: +1 763 786-8180
ApTest Minnesota                            Inet: shane@aptest.com
Received on Thursday, 13 December 2007 16:01:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:15:19 GMT