ORTC API Editor’s Draft – Last Call & WebRTC WG
The W3C ORTC Community Group has published an Editor’s Draft update to the ORTC API and is also asking for last call comments on the draft…
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.
So what does that mean?
Well, likely the most important takeaway is the fact that this spec now looks to be in a form where it could be implemented. The ORTC Libs (https://github.com/openpeer/ortc-lib) have been in stasis while the CG worked on getting the spec further along. Now that the CG is very close to a public draft on the API spec, that work will resume.
Something else that may be of interest is the direct reference to the W3C WebRTC Working Group in this draft and the issue tracker. There are a few components that require progress in the WebRTC WG before the ORTC CG can implement them. Now there seems to be a direct correlation between the work being done in the ORTC CG and the WebRTC WG, which should really not come as any great surprise to anyone.
At the last meeting, the CG discussed “What is the ORTC CG end game?” The resulting conversation equated to an answer that sounded something like, “Let’s create an implementable API, then if the WebRTC WG is interested in seeing the work being done in the ORTC CG merged into the WG then we should be happy to explore that.” There was no definite objection apart from, “let’s make sure the timing is right and it makes sense to do that”.
So if you are fuzzy on where the ORTC CG is headed, you should really check out that video clip.
WebRTC.is 