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

Re: ISSUE-24: Proposal for dealing with case-insensitive terms in the XHTML vocabulary

From: Ivan Herman <ivan@w3.org>
Date: Wed, 14 Jul 2010 12:28:20 +0200
Cc: Shane McCarron <shane@aptest.com>, RDFa WG <public-rdfa-wg@w3.org>
Message-Id: <6C1BA57E-41E1-4047-AB8D-2080BBF65C81@w3.org>
To: Toby Inkster <tai@g5n.co.uk>

On Jul 14, 2010, at 11:03 , Toby Inkster wrote:
[snip]
> 
> Ivan wrote:
> 
>> 2. in RDFa+XHTML (and I presume in RDFa+HTML5) there is a a default
>> @vocab, namely http://www.w3.org/1999/xhtml/vocab# and, if this is the
>> one in effect, then terms are interpreted in a case insensitive way,
>> ie, terms must be mapped on lower case.
> 
> Personally I'd ditch that too -- you get too many junk results. Better
> to say that the default vocabulary in (X)HTML+RDFa is null.
> 
> Otherwise you'll end up with having to deal with rel values from
> Microformats, etc. The problem with that it that Microformats have
> their own ways of determining what the "subject" is for a rel; applying
> RDF's @about/@src/chaining rules doesn't work well.
> 
> To handle the case of rel="next", rel="prev", etc define a default
> *profile* for XHTML+RDFa, and have that profile define those terms
> case-insensitively. (The profile SHOULD be hard-coded in XHTML+RDFa
> parsers; authors MAY include an explicit @profile attribute referencing
> the default profile.)
> 

If we can specify that cleanly, I do not have any problem with that approach. But I remember Ralph had some technical issues with that (let us consider him as a honorary Working Group member:-) but I do not remember what that was. Worth asking him if we go down that route.


> This means that parsers need to internally allow profiles to define
> both case-sensitive and case-insensitive terms,

Yeah, that is what I do already, I just never put that into the rdfa vocabulary to avoid overcomplication...

Ivan

> though we may decide
> not that profiles other than the XHTML vocab are not privileged to
> declare case-insensitive terms.
> 
> This solution allows us to pick up "our" @rel terms but skim safely
> over the @rel terms used by Microformats, Javascript libraries, etc.
> 
> -- 
> Toby A Inkster
> <mailto:mail@tobyinkster.co.uk>
> <http://tobyinkster.co.uk>
> 


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







Received on Wednesday, 14 July 2010 10:28:23 GMT

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