W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2010

[Bug 9903] New: Need to define specification and use of collations for string sorting

From: <bugzilla@jessica.w3.org>
Date: Thu, 10 Jun 2010 19:00:13 +0000
To: public-webapps@w3.org
Message-ID: <bug-9903-2927@http.www.w3.org/Bugs/Public/>

           Summary: Need to define specification and use of collations for
                    string sorting
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Indexed Database API
        AssignedTo: nikunj.mehta@oracle.com
        ReportedBy: pablo.castro@microsoft.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org

Currently the spec does not define what collation algorithm should be used for
string sorting. In order to properly support international applications we need
to define both how implementations should use collations and how the API
exposes options for the developer to choose a collation for a certain scope
(database, index, etc.)

Original WG message for context:

From: public-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On
Behalf Of Mikeal Rogers
Sent: Wednesday, June 09, 2010 2:42 PM
To: Webapps WG
Subject: [IndexDB] Collation Algorithm?

One of the things I noticed that seems to be missing from the IndexDB
specification is the collation algorithm used for sorting the index

There are lots of collation differences between databases, if left
unspecified I'm afraid this would negatively affect interoperability
between IndexDB implementations.

CouchDB has a good collation specification for rich keys (any JSON
type) and defers to the Unicode Collation Algorithm once it hits
string comparisons. This might be a good starting point.




Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 10 June 2010 19:00:15 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:25 UTC