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

[IndexedDB] Status

From: Nikunj Mehta <nikunj@o-micron.com>
Date: Mon, 7 Jun 2010 10:58:42 -0700
Message-Id: <74647805-9E55-4A68-BF05-549F39D3BEDC@o-micron.com>
Cc: Arthur Barstow <art.barstow@nokia.com>
To: public-webapps WG <public-webapps@w3.org>
Art asked for a status update on the IndexedDB spec. Here's my summary of the status:

1. Last published working draft: Jan 5, 2010
2. Bugzilla status: 15 issues logged
3. Editors: Nikunj Mehta (Invited Expert), Eliot Graf (Microsoft)
4. Spec document management: Currently W3C CVS, also using W3C's Distributed CVS (Mercurial) system

Major discussions since last working draft and their impact on the spec:

1. Asynchronous API proposal by Mozilla - to be assimilated in to the spec
2. Key data type changes proposal by Google - needs some coordination within WebApps with the WebIDL spec
3. Key path specification - no work done yet
4. Interaction between transactions - no work done yet
5. Version number discussion - no significant changes expected

Here's the sequence in which I will be working with Eliot to add bug fixes and the results of recent discussions to the spec:

1. 9561, 9563, 9768, 9769 - Mozilla Asynchronous API proposal
2. 9793: Key data type changes
3. 9832: Key path specification changes
4. 9789, 9791, 9790 - Naming changes
5. 9739 - editorial changes
6. 9653 - Null handling
7. 9786 - WebIDL bugs
8. 9652 - database open changes 
9. 9796 - async interface in workers

Here are some asks for additions to the spec, which also will need some amount of voting in order to be prioritized appropriately:

1. Nested transactions without durability of partially committed transaction trees
2. Inverted indexes for supporting full text searching
3. Enumeration of databases
4. Structured clone dependence
5. Encryption and expiration

Nikunj
Received on Monday, 7 June 2010 18:23:01 GMT

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