IETF Logo Mail Archive

Re: [rtcweb] RTCWeb Terminology

Hadriel Kaplan <HKaplan@acmepacket.com> Mon, 24 October 2011 16:56 UTC

Return-Path: <HKaplan@acmepacket.com>
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 4FE4921F8ABC for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 09:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level:
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[AWL=-0.326, BAYES_00=-2.599, J_BACKHAIR_27=1]
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 bMVAGSbj5Ftg for <rtcweb@ietfa.amsl.com>; Mon, 24 Oct 2011 09:56:20 -0700 (PDT)
Received: from etmail.acmepacket.com (etmail.acmepacket.com [216.41.24.6]) by ietfa.amsl.com (Postfix) with ESMTP id B5EA621F84A5 for <rtcweb@ietf.org>; Mon, 24 Oct 2011 09:56:20 -0700 (PDT)
Received: from MAIL2.acmepacket.com (10.0.0.22) by etmail.acmepacket.com (216.41.24.6) with Microsoft SMTP Server (TLS) id 8.2.254.0; Mon, 24 Oct 2011 12:56:18 -0400
Received: from MAIL1.acmepacket.com ([169.254.1.230]) by Mail2.acmepacket.com ([169.254.2.157]) with mapi id 14.01.0270.001; Mon, 24 Oct 2011 12:56:19 -0400
From: Hadriel Kaplan <HKaplan@acmepacket.com>
To: Cullen Jennings <fluffy@cisco.com>
Thread-Topic: [rtcweb] RTCWeb Terminology
Thread-Index: AQHMkm3ZWlVgOvN8GUaOFts2KjZpww==
Date: Mon, 24 Oct 2011 16:56:18 +0000
Message-ID: <3747C7CB-C039-4D15-A46C-8FDB9A47AF3A@acmepacket.com>
References: <AAB480AA-8F03-4C25-8A7C-55B88D057C24@acmepacket.com> <42322A10-14A7-4600-820D-7612A1B12592@cisco.com>
In-Reply-To: <42322A10-14A7-4600-820D-7612A1B12592@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.0.0.30]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <253ECA8D6EE0164E853BAA260F257524@acmepacket.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAQAAAWE=
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "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: Mon, 24 Oct 2011 16:56:21 -0000

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.

v2.23.0 | Report a Bug | By Email