Re: [rtcweb] RTCWeb Terminology

Harald Alvestrand <harald@alvestrand.no> Tue, 25 October 2011 01:13 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D6B211E81DF for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 18:13:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.599
X-Spam-Level:
X-Spam-Status: No, score=-109.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_BACKHAIR_27=1, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ah32sqr2GGFN for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 18:13:19 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by ietfa.amsl.com (Postfix) with ESMTP id DA84A21F8CF1 for <rtcweb@ietf.org>; Mon, 24 Oct 2011 18:13:18 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id D79C539E0F0; Tue, 25 Oct 2011 03:13:17 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at eikenes.alvestrand.no
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oYMsLmcqRNrp; Tue, 25 Oct 2011 03:13:17 +0200 (CEST)
Received: from [172.19.28.23] (216-239-45-4.google.com [216.239.45.4]) by eikenes.alvestrand.no (Postfix) with ESMTPS id 354F539E0A7; Tue, 25 Oct 2011 03:13:16 +0200 (CEST)
Message-ID: <4EA60D2A.9060101@alvestrand.no>
Date: Mon, 24 Oct 2011 18:13:14 -0700
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110921 Thunderbird/3.1.15
MIME-Version: 1.0
To: Cullen Jennings <fluffy@cisco.com>
References: <AAB480AA-8F03-4C25-8A7C-55B88D057C24@acmepacket.com> <42322A10-14A7-4600-820D-7612A1B12592@cisco.com> <3747C7CB-C039-4D15-A46C-8FDB9A47AF3A@acmepacket.com> <EB0F0985-66AC-4EF9-A5D9-862DD5C7443E@ag-projects.com> <1107BC89-1AB6-47F7-970A-BCF25955D1E0@cisco.com>
In-Reply-To: <1107BC89-1AB6-47F7-970A-BCF25955D1E0@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, Adrian Georgescu <ag@ag-projects.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] RTCWeb Terminology
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Oct 2011 01:13:20 -0000

Google's been using "WebRTC" (capitalized as such) for their opensource 
implementation of the technologies involved too.

On 10/24/2011 10:18 AM, Cullen Jennings wrote:
> +1
>
> On Oct 24, 2011, at 11:01 AM, Adrian Georgescu wrote:
>
>> WebRTC sounds great!
>>
>> Adrian
>>
>> On Oct 24, 2011, at 6:56 PM, Hadriel Kaplan wrote:
>>
>>> On Oct 24, 2011, at 11:03 AM, Cullen Jennings wrote:
>>>
>>>> I don't think there is an answer to this yet so I guess we need to figure it out.  I'm ore concerned about the long term explanation to people outside W3C or IETF. Hadriel, with you marketing hat on, you have any suggestions of what we should call the whole thing?
>>> Web 4.0.  ;)
>>>
>>> I asked a couple other folks and the consensus seems to be: "WebRTC" for the whole thing.
>>>
>>> The rationale is that it's still the Web but with native real-time-communication support, as opposed to real-time-communication but with web support.  For example if you wrote a book about how to write Web-apps for it, you would probably use the term "WebRTC" in the book title.  Another rationale was that it follows the naming scheme for WebM and WebP.
>>>
>>> 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
>>> p.s. personally I've gotten used to the term "RTCWeb", but it may be because of my IETF focus rather than W3C/Web focus.
>>>
>>>
>
>