Bjoern Hoehrmann wrote: > * fantasai wrote: >> If there are multiple mechanisms, then the namespace prefix declared by >> a given mechanism is case-sensitive or case-insensitive as defined by that >> mechanism. If a case-sensitive mechanism declares FOO and a case-insensitive >> mechanism declares foo, then foo can only match the second declaration, and >> FOO will match the first or the second depending on which mechanism takes >> precedence, which is outside the scope of the Selectors spec since it does >> not specify a namespace declaration mechanism. Basically, a case-insensitive >> declaration declares all case variants of the prefix. > > The text with the changes you announced would be "The case sensitivity > of namespace prefixes in selectors is defined by the mechanism used to > declare them". > > Mechanism A: Namespace prefixes in selectors are case-sensitive. > Mechanism B: Namespace prefixes in selectors are case-insensitive. > > This is a conflict. You are avoiding the problem by speaking of the > case-sensitivity of the mechanism, while the draft text speaks of the > case-sensitivity of the prefix in the selector. Bjoern, if you've got better wording that still says what I mean, propose it. ~fantasaiReceived on Friday, 29 June 2007 14:08:11 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:51 GMT