ORTC (Object Real-time Communications) Community Group
The mission of the Object Real-Time Communications Community Group, is to define Object-centric APIs (client-side at first) to enable Real-Time Communications in Web browsers, Mobile endpoints and Servers.
Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.
Since there is quite a bit of overlap between members in the IETF RTCWEB WG and the ORTC CG we thought it would serve us well if we had the next CG meeting on the Sunday July 20, prior to the IETF 90 meeting in Toronto.
We would need some help with room sponsorship at the hotel for the CG meeting room. We will also provide remote attendance as well for those who are not able to make it in person.
I would like to get this nailed down this week so we can announce the meeting as far in advance as possible. If you plan on coming or If you are interested in helping with room sponsorship please let me know via email directly asap: email@example.com
We are nearing completion of the ORTC specification for our initial ORTC community group draft. We are asking for last call feedback at this time. Some comments to explain some of the changes are still pending but all issues are tracked here and on github. If you would like to make comment, please have a read through and make comment either on this list or as part of our next CG meeting coming up.
There are a few outstanding areas which are “pending” synchronization with WebRTC, e.g. stats, data channel, and IdP. As these have dependencies on WebRTC 1.0, we will attempt to complete the our specification as best we can but those areas will be subject to synchronization should updates come out of the WebRTC community group.
Now is the time to have a read through for final review as the next stage will be to build implementations for implementation feedback.