15463 2012-01-08 22:01:50 +0000 [FO30] [editorial] Rules for case-insensitive matching 2012-07-23 03:34:38 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Functions and Operators 3.0 Member-only Editors Drafts PC All CLOSED FIXED P2 minor --- 1 mike mike public-qt-comments oldest_to_newest 62400 0 mike 2012-01-08 22:01:50 +0000 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. 65814 1 mike 2012-03-20 11:20:20 +0000 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. 71285 2 mike 2012-07-23 03:34:38 +0000 Fixed as suggested.