Re: Call for API contributions to WEBRTC WG

We forgot the universal rule that all calls should include a deadline....
we'll start evaluating based on what's been proposed on July 27, 10 days 
from now.

                  Harald, for Harald and Stefan

On 06/15/11 17:14, Harald Alvestrand wrote:
> Team,
>
> as stated in our charter, our deliverables say:
>
> The working group will deliver specifications that cover at least the
> following functions, unless they are found to be fully specified
> within other working groups' finished results:
>
> Media Stream Functions - API functions to manipulate media streams for
> interactive real-time communications, connecting various processing
> functions to each other, and to media devices and network connections,
> including media manipulation functions for e.g. allowing to
> synchronize streams.
> Audio Stream Functions - An extension of the Media Stream Functions to
> process audio streams, to enable features such as automatic gain
> control, mute functions and echo cancellation.
> Video Stream Functions - An extension of the Media Stream Functions to
> process video streams, to enable features such as bandwidth limiting,
> image manipulation or "video mute".
> Functional Component Functions - API functions that allow to query for
> the components present in an implementation, instantiate them, and
> connect them to media streams.
> P2P Connection Functions - API functions to establish peer-to-peer
> connections between Web browsers, independent of the network protocols
> used to establish the connections between peers.
>
> The working group may decide to group the specified functions in one
> or more specifications.
>
> This is a call for contributions for API specifications that can be
> used as a starting point for an editor's draft for one or more of
> these functions - in
> particular, the Media Stream, Audio Stream, Video Stream and P2P
> Connection functions.
>
> If you have an API specification that you think is suitable as a basis
> for of this WG's deliverables, please send a note to the WG mailing
> list stating:
>
> - Where this document is to be found
> - An assertion that the submitter is ready to make the IPR statements
> required by W3C policy [1]
> - A statement on your belief in the status of the document (rough
> outline, complete-but-unstable specification,
> complete-and-unchangeable)
> - A description of any implementation work you know of that is ongoing
> to verify the API's suitability for these purposes
>
> The chairs expect to present a proposal for work based on incoming
> contributions before the July face-to-face meeting of the WG
>
> [1] The IPR statement required is an assertion that, as indicated in
> the 5 February 2004 W3C Patent Policy (section 3.1 [2]), you, as group
> participant, agree to make available under W3C RF licensing
> requirements any Essential Claims related to that document (noting the
> exceptions in section 4 of the W3C Patent Policy [3]).
>
> [2] 
> http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-W3C-RF-license
> [3] http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Exclusion
>
>

Received on Friday, 17 June 2011 06:29:19 UTC