Technically WebRTC and SyntaxNet have nothing in common. What they do have in common is that Google again makes it easy to add capabilities, once in the hands of the rich and experts, as a feature into applications. Once this is possible, Natural Language Understanding (NLU) can be added also into WebRTC applications. How can WebRTC applications benefit from it?
Learning from the SIP standard, implementations by vendors are in many cases diverted from the pure standard to proprietary versions of SIP thus requiring mediation between vendor environments. Which areas of WebRTC should be covered by the standards and which areas should be left for the vendors to decide on? What level of interoperability and compatibility do we want to have?
RingCentral is a cloud PBX and contact center provider that also offers Glimp, a team collaboration platform. Lately they decided to open up their WebRTC APIs. RingCentral already had integration APIs in their platform. Is there anything significant in the RingCentral WebRTC API announcement and what does it mean to the existing PaaS WebRTC services (e.g. TokBox).
ORTC is a pretty hot topic on the technology side of WebRTC. Many still see it as a competing technology to WebRTC and therefore are worried it will delay adoption of WebRTC. On the other hand, some are not clear technically what new capabilities ORTC brings and what are the challenges associated with it. In a very high level, it is not correct to compare ORTC with WebRTC but rather to compare it to SDP.