The group which is defining the #WebRTC #JavaScript APIs is proposing a new charter to map its work for the next couple of years. w3.org/2018/04/webrtc-charte…
#WebRTC enables audio-video communication and #P2P data in browsers.
This tweet is unavailable
1
5
1
3
“The highest priority of the group in this charter period will be to get the core recommendations progressed towards Recommendation status”
1
This means in particular finishing the #WebRTC 1.0 APIs, incl 99 open issues github.com/w3c/webrtc-pc/iss… and getting more implementation convergence dontcallmedom.github.io/webr…
1
1
3
But this also includes new work on extensions to WebRTC 1.0, to cover new use cases, possibly new protocols for data transfer (#QUIC?), new modes of operations (in workers? service workers?), and less SDP
Right now, the draft new charter is setting the group to finish its ongoing work, look at bringing low-level APIs to get rid of the dependency on SDP (if you don't know what that is, DO NOT ASK, DO NOT LOOK IT UP 🙈🙉🙊), and explore new foundations for P2P data channels.
Apr 24, 2018 · 2:34 PM UTC
1