- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Thu, 26 May 2011 15:48:33 +0200
- To: public-device-apis@w3.org
- Cc: public-webrtc@w3.org
Hi, As many of you know, W3C started a Working Group dedicated to building APIs for real-time communications a few weeks ago: http://www.w3.org/2011/04/webrtc/ (I'm copying their public mailing list on this report) There is some possible overlap between our two groups, since both are interested in interactions with cameras and microphones. To avoid duplication of work and clarify who is in charge of what, the co-chairs and staff contacts of the two groups met briefly today. It was proposed that as a line of separation: * Web RTC would be working on media streams APIs — I understand that the group is currently evaluating the getUserMedia [1] API defined in the WhatWG HTML document to that end * if there is still interest in it, there is still room for an API to capture media records that DAP would be in charge of (continuing its work for instance on the Media Capture API [2]) * WebRTC might need an API to control camera/microphone settings; this might be something for DAP to start looking at, provided we have interests/relevant requirements * the audio volume reading API that is proposed in the next charter of DAP [3] is not directly relevant to Web RTC (or at least not as much as the APIs that the Audio WG [4] would be developing) Dom 1. http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#obtaining-local-multimedia-content 2. http://dev.w3.org/2009/dap/camera/Overview-API.html 3. http://www.w3.org/2010/11/DeviceAPICharter.html 4. http://www.w3.org/2011/audio/
Received on Thursday, 26 May 2011 13:48:50 UTC