W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2012

[Bug 15463] New: [F+O3.0] [editorial] Rules for case-insensitive matching

From: <bugzilla@jessica.w3.org>
Date: Sun, 08 Jan 2012 22:01:51 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-15463-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15463

           Summary: [F+O3.0] [editorial] Rules for case-insensitive
                    matching
           Product: XPath / XQuery / XSLT
           Version: Member-only Editors Drafts
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: minor
          Priority: P2
         Component: Functions and Operators 3.0
        AssignedTo: mike@saxonica.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


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.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 8 January 2012 22:01:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:47 UTC