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

Re: [rtcweb] RTCWeb Terminology

From: Cullen Jennings <fluffy@cisco.com>
Date: Mon, 24 Oct 2011 09:03:38 -0600
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-Id: <42322A10-14A7-4600-820D-7612A1B12592@cisco.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>

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?

On Oct 22, 2011, at 11:13 AM, Hadriel Kaplan wrote:

> 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
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
Received on Monday, 24 October 2011 15:04:19 UTC

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