ACTION-31: Add Data API to spec

Add Data API to spec

Adam Bergkvist
Due on:
March 12, 2012
Created on:
March 6, 2012
Related emails:
  1. [ACTION-31] Closed (from on 2012-03-24)
  2. Open actions on the action tracker (from on 2012-03-06)

Related notes:

As of March 5 call, it is clear that there's not agreement in the editing team how changes in the data channel state need to be signalled, but this doesn't affect the API much, if at all.

Adam to get the spec in, hewing as close to WebSockets API as he can, and leaving a token about the issue of inheriting from WebSockets API vs creating an abstract superclass in the IDL.

Harald Alvestrand, 6 Mar 2012, 10:55:33

Add Data API to spec: the latest version of the Editor's draft has a Data API proposal included ( It should be noted that there is some controversy regarding the API per se, but this ACTION can be closed. Updating/changing the API based on discussion and WG consensus is part of the common editing procedures.

Stefan Håkansson, 24 Mar 2012, 15:05:49

Display change log.

Harald Alvestrand <>, Bernard Aboba <>, Jan-Ivar Bruaroey <>, Chairs, Dominique Hazaël-Massieux <>, Carine Bournez <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $