This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
In the rules for case-insensitive matching: (a) the XPath expression used to define whether two characters are case-variants of each other is badly formatted (the 'or' between the two expressions should be part of the expression). (b) in the detailed rules, there is reference to the construct charRange. In XSD 1.1, this term strictly refers to the construct a-b, it no longer applies to a single character on its own. We need to make it clear to someone using the XSD 1.1 production rules that case-blindness applies to a singleChar as well as to a charRange.
I propose to handle this editorially as follows: (a) the markup has been fixed (b) change the relevant sentence to read: A character range (production <code>charRange</code> in the XSD 1.0 grammar, replaced by productions <code>charRange</code> and <code>singleChar</code> in XSD 1.1) represents the set containing all the characters that it would match in the absence of the "<code>i</code>" flag, together with their case-variants.
Fixed as suggested.