Re: Media Capture TF Update

On Mon, Apr 1, 2013 at 10:24 AM, Mandyam, Giridhar <mandyam@quicinc.com>wrote:

> As per my action item from the last call, I will call the group's
> attention to ongoing specification work in the Media Capture Task Force
> (jointly run by the DAP and WebRTC Working Groups).  I strongly encourage
> DAP members to review and provide feedback to the Media Capture TF mailing
> list (http://lists.w3.org/Archives/Public/public-media-capture/) on these
> specifications.
>
> The group originally was chartered to develop the primary Media Capture
> and Streams specification, with the primary JS method known as
> getUserMedia().  Since that time, the group has also developed the
> Recording API (which is in FPWD status) and the Image Capture API (which is
> now a group Editor's Draft and I am the editor).
>
> 1. Media Capture and Streams:
> http://dev.w3.org/2011/webrtc/editor/archives/20130320/getusermedia.html.
> 2. Recording API:
> https://dvcs.w3.org/hg/dap/raw-file/default/media-stream-capture/MediaRecorder.html
> 3. Image Capture API:  http://gmandyam.github.com/image-capture/
>         Note that I plan on checking this into Mercurial soon, after I
> reverify with the latest version of respec.js
>

Is the Recording API intended to be use to record externally sourced media
being played back through HTMLMediaElement? If it is not, then I would like
to see the following changes:

   - rename the specification to a name that qualifies its usage to local
   device captured media content
   - add language to abstract and overview sections that qualifies the
   intended usage

If it is intended to support recording of externally sourced media, then
the group needs to widen the participation in the spec process to bring in
people from the HTML Media TF and the Web & TV IG.

Regards,
Glenn Adams (for CoxCom)