ACTION-11: Add Constraints API to API spec

Add Constraints API to API spec

State:

closed

Person:

Daniel Burnett

Due on:

January 12, 2012

Created on:

November 9, 2011

Related emails:

[minutes] June 11 F2F (from dom@w3.org on 2012-06-12)
Re: [minutes] April 10 teleconf (from adam.bergkvist@ericsson.com on 2012-04-11)
[minutes] April 10 teleconf (from dom@w3.org on 2012-04-11)
[minutes] March 13 Teleconf (from dom@w3.org on 2012-03-14)
Open actions on the action tracker (from harald@alvestrand.no on 2012-03-06)
Re: Housekeeping: Open actions in the WG tracker (from mmanig@gmail.com on 2011-12-09)
Housekeeping: Open actions in the WG tracker (from harald@alvestrand.no on 2011-12-09)

As proposed in SC meeting. Dan Burnett to lead, editing team to work.

Harald Alvestrand, 9 Nov 2011, 13:33:45

Delayed while it is investigated whether ROAP or JSEP model will be used.

Stefan Håkansson, 28 Nov 2011, 17:02:20

Seems to have the same hints for both JSEP and ROAP, so it's independent.

Harald Alvestrand, 5 Jan 2012, 16:20:36

Reassigning to Dan.

Relevant I-D: draft-burnett-rtcweb-constraints-registry-00.txt
This creates the registry.

Harald Alvestrand, 6 Mar 2012, 10:18:28

10 Apr 2012, 15:10:48

Constraints are part of the Media Capture and Streams as well as the webrtc document. ACTION done.

Stefan Håkansson, 17 Sep 2012, 13:43:48