Dear Webapps WG, I am writing on behalf of the I18N Core WG who discussed the Selectors API WD in our call of 3 December [1].
We reviewed the Selectors API working draft. In reviewing this draft, we did not find any internationalization issues in the text of the document. However, we would like to point out that the CSS3 Selectors themselves have outstanding internationalization comments not addressed in the current version of that document [4] and which would (we think) impact anyone who were to implement the Selectors API. Our comments on CSS3 Selectors are located at [2]. We also note that Unicode Normalization is not treated anywhere in this draft or in CSS3 Selectors. Please note that members of the WG also found two minor editorial issues [3] We are concerned that changes in CSS3 might impact implementation of Selectors API and/or the text thereof and think our concerns probably should be addressed before Selectors API advances to the next level of maturity. Regards (for I18N Core), Addison [1] http://www.w3.org/2008/12/03-core-minutes.html [2] http://www.w3.org/International/reviews/0601-css3-selectors/ [3] http://lists.w3.org/Archives/Member/member-i18n-core/2008Dec/0006.html [4] http://www.w3.org/TR/css3-selectors/ aka http://www.w3.org/TR/2005/WD-css3-selectors-20051215 Addison Phillips Globalization Architect -- Lab126 Chair -- W3C Internationalization Core WG Internationalization is not a feature. It is an architecture.
