W3C home > Mailing lists > Public > public-i18n-core@w3.org > April to June 2011

RE: I18N-ACTION-40: CSS Selectors and Normalization (new response)

From: Phillips, Addison <addison@lab126.com>
Date: Tue, 24 May 2011 23:03:02 -0700
To: fantasai <fantasai.lists@inkedblade.net>, "public-i18n-core@w3.org" <public-i18n-core@w3.org>
Message-ID: <131F80DEA635F044946897AFDA9AC3476A931F0046@EX-SEA31-D.ant.amazon.com>
> > ---
> > This is a personal summary meant
> 
> This is all very interesting, and of course should be taken as feedback for
> Selectors Level 4, but selector matching is completely out-of-scope for CSS
> Namespaces, which is the topic currently at hand.
> 

Fair enough, although I note that this is the *second* note on this topic and you replied to the earlier one as well. 

That said, the Namespaces problem and the Selectors problem are similar problems (from opposite sides). As a result, we can either:

1. Require normalization of the namespace prefix in the document (i.e. EUN). Since the rest of CSS doesn't have this requirement, it seems futile or problematic to impose it on the namespace prefix.

2. Require namespace prefix matching to use normalization. See selector text in previous email for reasons why the WG is likely to prefer this. I rather doubt the WG will come to a different conclusion for namespaces.

I do note that XML Namespaces (on which this is based) relies on RFC 3986 (i.e. URI rather than IRI). It might be a good idea to talk about IRIs and IRI equivalence in this document. While normalization is part of this discussion, the IRI problem goes beyond this.

Addison

Addison Phillips
Globalization Architect (Lab126)
Chair (W3C I18N WG)

Internationalization is not a feature.
It is an architecture.



Received on Wednesday, 25 May 2011 06:03:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 25 May 2011 06:03:41 GMT