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

Re: [IndexDB] Collation Algorithm?

From: Jeremy Orlow <jorlow@chromium.org>
Date: Fri, 11 Jun 2010 12:43:35 +0100
Message-ID: <AANLkTikAxQQWFFtaDgqVQlReIjjRKQd2K0PXpNJq-d5J@mail.gmail.com>
To: Mikeal Rogers <mikeal.rogers@gmail.com>
Cc: Webapps WG <public-webapps@w3.org>
P.S.  Please use "[IndexedDB]" as that's the convention we've been using so
far and many people have filters set up for this.

On Wed, Jun 9, 2010 at 10:42 PM, Mikeal Rogers <mikeal.rogers@gmail.com>wrote:

> One of the things I noticed that seems to be missing from the IndexDB
> specification is the collation algorithm used for sorting the index
> keys.
>
> 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.
>
> http://wiki.apache.org/couchdb/View_collation#Collation_Specification
>
> http://www.unicode.org/reports/tr10/
>
> -Mikeal
>
>
>
Received on Friday, 11 June 2010 11:44:24 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:39 GMT