W3C home > Mailing lists > Public > public-qt-comments@w3.org > July 2005

[Bug 1637] New: [FS] collations can have a third, optional, mapping

From: <bugzilla@wiggum.w3.org>
Date: Fri, 15 Jul 2005 21:49:26 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DtY3i-0007Fx-5f@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1637

           Summary: [FS] collations can have a third, optional, mapping
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Platform: PC
        OS/Version: Windows 2000
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Formal Semantics
        AssignedTo: simeon@us.ibm.com
        ReportedBy: fred.zemke@oracle.com
         QAContact: public-qt-comments@w3.org


3.1.1 Static context
Under statEnv.collations, it says that a collation consists of
two functions: "the first function takes a set of strings and
returns a sequence containing those strings in sorted order;
and the second function takes two strings, returns true if they
are considered equal, and false if not."  This definition agrees
with the definition of collation found in Xquery 2.1.1 "Static
context" but not with the definition in
F&O 7.5 "Functions based on substring matching" paragraph 4,
which says "All collations support the capability of deciding 
whether two strings are considered equal, and if not, which of 
the strings should be regarded as preceding the other. For 
functions such as fn:compare(), this is all that is required. 
For other functions, such as fn:contains(), the collation needs 
to support an additional property: it must be able to decompose 
the string into a sequence of collation units...".  It 
seems that there must be a third (optional) function associated
with each collation, the function that maps to collation units.
Received on Friday, 15 July 2005 21:50:24 UTC

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