Re: HTML5 Polyglot spec and RDFa

Toby,

just to make it clear:

- #1-2bis: I think Manu+Gregg had a sub-option to #1-#2: first try a case sensitive search among the terms being defined, and then a case insensitive one

- Your #4 of course subsumes #3: host languages, conceptually, defined a host profile (that is already the case) and they can then make use of that possibility. In some ways, I would not like to see #3 only due to that.

My personal preference goes to #4 or #1.

Ivan



On Oct 10, 2010, at 17:32 , Toby Inkster wrote:

> On Sun, 10 Oct 2010 10:15:07 +0200
> Ivan Herman <ivan@w3.org> wrote:
> 
>> I am still not 100% sure that the issue raised by Gregg is, in
>> practice, such a show stopper that it would warrant to change the
>> current (clearly simplistic) solution.
> 
> As far as I'm concerned there are four possible paths that we could go
> down which are all quite sensible. (And probably dozens of silly paths
> we could take.)
> 
> 	#1. How RDFa Core 1.1 is currently specified: all terms are
> 	case-insensitive.
> 
> 	#2. All terms are case-sensitive.
> 
> 	#3. Terms are case-sensitive generally, but a host language's
> 	default profile MAY be case-insensitive if the host language's
> 	specification states that it is (and XHTML+RDFa 1.1 would).
> 
> 	#4. Profiles may indicate which terms are case-sensitive and
> 	which are not.
> 
> Currently I've implemented #3 in my parser, though will obviously
> switch to whatever the WG has resolved as RDFa 1.1 approaches stability.
> 
> #3 or #4 are my preferred solutions, because they seem to offer
> profile designers a bit of control while taking into account
> grandfathered case-insensitive terms. 
> 
> -- 
> 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