W3C home > Mailing lists > Public > public-media-capture@w3.org > November 2011

Media Capture TF Goals

From: Travis Leithead <travis.leithead@microsoft.com>
Date: Wed, 30 Nov 2011 18:18:25 +0000
To: "public-media-capture@w3.org" <public-media-capture@w3.org>, Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, Harald Alvestrand <harald@alvestrand.no>
Message-ID: <9768D477C67135458BF978A45BCF9B38381BE869@TK5EX14MBXW602.wingroup.windeploy.ntdev.microsoft.com>
Hi Harald and Stefan!

Thanks for jump-starting this task force.

Before we start nit-picking the recently-submitted first draft, I think it's important to set up some goals for this task force. Goals will help us all align on a common direction, and provide the measurement by which we will know when we are "done".

I would like to suggest some of the goals that I have for this TF. Perhaps other members can submit theirs and we can build consensus on the goals.

1. Build a set of shared requirements derived from both the WebRTC scenarios as well as local media capture scenarios. My current perspective is slanted in the direction of local media capture scenarios (as I don't have much RTC in-depth knowledge). Both myself (Microsoft) and Rich (Opera) have action items to provide a set of scenarios to this TF.

2. Clearly split out the "media capture" scenarios from the current WebRTC spec in a way that doesn't de-stabilize the WebRTC spec's dependencies on MediaStreams. Capture these requirements in a separate spec-the final deliverable of the task force. The task force should take the best of both local capture scenarios and WebRTC streaming scenarios and build a capture API that can equally serve both.

3. Explore and possibly integrate and align the TF deliverable with other current W3C technologies, notably Microsoft's recent Streams API proposal [1], and the HTMLMediaElement (video tag) from HTML5 (which has a lot of similarities to WebRTC's MediaStream).

4. Discuss and possibly incorporate some of the feedback previously provide via the DAP working group related to media capture [2].

5. Provide a clear scope of the work so that essential requirements can be met, and other future requirements can be integrated into a V2 spec in a way that doesn't require re-working the V1 API.

[1] http://dvcs.w3.org/hg/webapps/raw-file/tip/StreamAPI/Overview.htm 
[2] http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/att-0177/minutes-2011-11-03.html#item05
Received on Wednesday, 30 November 2011 18:20:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:24:34 UTC