W3C home > Mailing lists > Public > public-webrtc@w3.org > October 2011

RE: RTCWeb Terminology

From: Cavigioli, Chris <chris.cavigioli@intel.com>
Date: Sun, 23 Oct 2011 21:10:00 -0700
To: Hadriel Kaplan <HKaplan@acmepacket.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1AA206FBD08B004C82025A41283CCE9EE55DCD91@orsmsx505.amr.corp.intel.com>
Very good question - been bugging me too.  -chris 

-----Original Message-----
From: public-webrtc-request@w3.org [mailto:public-webrtc-request@w3.org] On Behalf Of Hadriel Kaplan
Sent: Saturday, October 22, 2011 10:13 AM
To: rtcweb@ietf.org; public-webrtc@w3.org
Subject: RTCWeb Terminology

Howdy,
this may seem like a silly question, but what are the actual names and capitalization schemes for the overall architecture, mechanism/protocol, API and such?

I believe the Working Group names are "RTCWEB" in IETF and "WEBRTC" in W3C.  But in the W3C it appears the name of the API doc is "WebRTC".

Is the overall thing "RTCWEB", "RTCWeb", "RTCweb", or "rtcweb"?  I've seen all 4 uses in IETF drafts.  Meanwhile in W3C they call the overall architecture and protocol "WEBRTC" in the "WebRTC" document.  Which is it?

Is the Browser API itself an "RTCWeb API" or "WebRTC API" or what?

The draft-ietf-rtcweb-overview draft has a terminology section but does not cover this.

I know this is silly, but I've gotten the question several times from customers and marketing folks. (plus it would be nice to be consistent in both IETF and W3C docs)

I apologize if this question has already been asked and answered.  I googled but found conflicting terms and usage in those results as well.

-hadriel
Received on Monday, 24 October 2011 21:10:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:25 UTC