Re: [rtcweb] WebRTC definition (Re: Consensus Call: RTCWeb Terminology)

How about:

WebRTC
     A technology and platform that enables real-time, interactive peer to peer audio, video and data communication between browsers on the Internet.  Components of WebRTC include a protocol profile, defined in the IETF, of which this document gives an overview, and an API, defined in the W3C, and specified in <reference>.

-hadriel

On Oct 26, 2011, at 10:20 PM, Jim McEachern wrote:

> How about this?
> 
> WebRTC
>      A collaborative standards effort between the IETF and W3C that specifies a JavaScript API and architectural context, to enable real-time peer to peer audio, video and data communication between browsers
>     on the Internet.
>     Components of WebRTC include a protocol profile, defined in the IETF, of which this document
>     gives an overview, and an API, defined in the W3C, and specified in <reference>
> 
> Jim
> 
>> -----Original Message-----
>> From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On
>> Behalf Of Harald Alvestrand
>> Sent: Wednesday, October 26, 2011 6:30 PM
>> To: rtcweb@ietf.org
>> Subject: [rtcweb] WebRTC definition (Re: Consensus Call: RTCWeb
>> Terminology)
>> 
>> On 10/26/2011 10:17 AM, Cullen Jennings wrote:
>>> With my chair hat on ...
>>> 
>>> I'd like to declare we currently have consensus for Hadriel's proposal that
>> the technology should be referred to as "WebRTC" and the API as the
>> "WebRTC API". The IETF WG name is still RTCWeb, the mailing list is still
>> rtcweb@ietf.org, the IETF drafts should still have "-rtcweb-" in them to
>> indicate the WG name.
>> 
>> As -overview editor, I'm happy to include this definition.
>> 
>> Just because I have to write it in a terminology list, I wonder how I should
>> define it.
>> 
>> Is it an effort? A technology? A project?
>> 
>> It should be something like:
>> 
>> WebRTC
>>      A <something> that <someting> to enable peer to peer audio and video
>> between browsers
>>     on the Internet.
>>     Components of WebRTC include a protocol profile, defined in the IETF, of
>> which this document
>>     gives an overview, and an API, defined in the W3C, and specified in
>> <reference>
>> 
>> Suggestions for the <something>s (or alternate formulations) would be most
>> welcome.
>> 
>>                  Harald
>> 
>> 
>> 
>>> Cullen<RTCWeb CoChair>
>>> 
>>> 
>>> On Oct 24, 2011, at 10:56 AM, Hadriel Kaplan wrote:
>>> 
>>>> For the API, the consensus was it would be confusing to people if we
>> weren't consistent with W3C docs.
>>>> 
>>>> So I propose the following:
>>>> 
>>>> WebRTC: the whole shebang
>>>> WebRTC API: the JS<->Browser API.
>>>> 
>>>> -hadriel
>>> _______________________________________________
>>> rtcweb mailing list
>>> rtcweb@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>> 
>> 
>> _______________________________________________
>> rtcweb mailing list
>> rtcweb@ietf.org
>> https://www.ietf.org/mailman/listinfo/rtcweb
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb