W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2013

Re: Call for Consensus to publish a First Public Working Draft of "MediaStream Recording API", deadline 31 Jan 2013 [resend adding DAP]

From: <Frederick.Hirsch@nokia.com>
Date: Thu, 24 Jan 2013 16:28:49 +0000
To: <Jim.Barnett@genesyslab.com>
CC: <Frederick.Hirsch@nokia.com>, <glenn@skynav.com>, <public-device-apis@w3.org>, <public-webrtc@w3.org>
Message-ID: <1CB2E0B458B211478C85E11A404A2B27018DEA28@008-AM1MPN1-034.mgdnok.nokia.com>
I think this discussion should be taken to the WebRTC TF list, public-media-capture at w3.org<http://w3.org>

 A FPWD is just that, a first draft, thus this discussion could lead to a subsequent WD being published if the TF agrees.

Glenn, I did not take your comment as an object to FPWD publication. Please confirm that you are not objecting to FPWD publication.


regards, Frederick

Frederick Hirsch, Nokia
Chair, W3C DAP Working Group

On Jan 24, 2013, at 10:23 AM, ext Jim Barnett wrote:

Iím not sure that I understand your first point.  The API is defined to work with any object of type MediaStream, whether local or remote.  If there is some other object that needs to be recorded, I would think that the question would be how to convert it into a MediaStream.  The getUserMedia spec would be the right place to do that, or possibly a separate spec, but the process should be transparent to the MediaRecorder class.  (Thereís a separate discussion going on about whether we want to taint certain MediaStreams to prevent recording for security reasons, but thatís orthogonal to this issue, I think.)

On the issue of where takePhoto() goes, it was originally a method on VideoTrack.  We moved it to the recorder class because it seemed to have a lot in common with recording.  I donít particularly care where it goes, though I wonder if a new interface is justified, given how limited the functionality is.  Iíll go with whatever the majority decides.

-          Jim

From: Glenn Adams [mailto:glenn@skynav.com]
Sent: Thursday, January 24, 2013 9:21 AM
To: Frederick.Hirsch@nokia.com<mailto:Frederick.Hirsch@nokia.com>
Cc: public-device-apis@w3.org<mailto:public-device-apis@w3.org>; public-webrtc@w3.org<mailto:public-webrtc@w3.org>
Subject: Re: Call for Consensus to publish a First Public Working Draft of "MediaStream Recording API", deadline 31 Jan 2013 [resend adding DAP]

>From my brief read of this draft, I have the following comments:

  *   Document should describe how it the mechanisms defined can be used to record media streams deriving from non-local devices, specifically, how to record media streams obtained from external servers, e.g., streams fetched and presented by HTMLMediaElement.
  *   The members takePhoto() and onphoto should be moved to a separate interface to make the MediaRecorder interface more generic, and not tied to specific types of media sources.


On Thu, Jan 24, 2013 at 6:31 AM, <Frederick.Hirsch@nokia.com<mailto:Frederick.Hirsch@nokia.com>> wrote:
DAP members:

The Media Capture Task Force [a] is a joint Task Force of the DAP and WebRTC working groups. This is a CfC to publish a FPWD of the  "MediaStream Recording API".

Below I include the mail sent to the WebRTC mailing list, consider this as a CfC for the Device APIs working group as well, and please respond on the DAP public mail list  as well as the public WebRTC mailing list with either +1 or concerns. (I've cross-posted this mail deliberately as CfC responses should be seen by all and I expect relatively low traffic).

regards, Frederick

Frederick Hirsch, Nokia
Chair, W3C DAP Working Group

[a] http://www.w3.org/2009/dap/#mediacapture

CfC sent to WebRTC list:

During the Media Capture Task Force call on 6 December 2012 [1] we agreed to start a CfC for a First Public Working Draft (FPWD) of the  "MediaStream Recording API" draft once Jim completed some additional
edits, which he has [2].

This is a Call for Consensus (CfC) for the WebRTC WG members to publish  of FPWD of this document.

A FPWD is a draft and can thus continue to be edited and evolve, but  gives visibility of the work to a broader community, and is thus useful.  It also starts the call-for-exclusion process under the W3C Patent Policy.

As with all of our CfCs, positive response is preferred and encouraged and silence will be considered as agreeing with the proposal. The deadline for comments is Thursday January 31st and all comments should
be sent to public-webrtc at w3.org<http://w3.org/>. We can then publish the week after,  assuming that works for the W3C team and editors.

Stefan, for the chairs

[1] Minutes:


[2] Draft:


Received on Thursday, 24 January 2013 16:29:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:39 UTC