- From: Joshue O Connor <joconnor@w3.org>
- Date: Mon, 23 Sep 2019 10:54:47 +0100
- To: RQTF <public-rqtf@w3.org>
- Cc: Bernard Aboba <Bernard.Aboba@microsoft.com>, Dominique Hazael-Massieux <dom@w3.org>
Hi all, Just to update you all, we put the Real Time Text discussion on the agenda for WebRTC working group and had a very useful discussion at TPAC. Based on our discussion it seems that there are current implementations via polyfills that can be worked into WebRTC applications, or extensions that can be used if there are protocol requirements. Both may count as final implementations as they get closer to publishing their new spec. WebRTC will review their current implementation, e.g how it is exposed in the WebRTC stack and how interoperability is handled regarding RTT. Our Accessible RTC use cases document will also be helpful to them. FYI - we also asked the WebRTC group if they are happy for APA to publish our this document as a working group note.They were positively disposed towards the idea and expressed that it would be useful to have it as a separate doc. [2] They also stated that they will review our use cases and see what they can take to update their own use cases document with relevant items. A request was also made for APA to review the related IETF spec T.140 Real-time Text Conversation over WebRTC Data Channels. [3] This doc specifies how a WebRTC data channel can be used as a transport mechanism for Real-time text using the ITU-T Protocol for multimedia application text conversation (Recommendation ITU-T T.140), and how the SDP offer/answer mechanism can be used to negotiate such data channel, referred to as T.140 data channel. We can discuss this at our meeting on Weds. Thanks Josh [1] https://www.w3.org/2019/09/20-apa-minutes.html#item03 [2] https://www.w3.org/2019/09/20-apa-minutes.html#item04 [3] https://tools.ietf.org/html/draft-ietf-mmusic-t140-usage-data-channel -- Emerging Web Technology Specialist/Accessibility (WAI/W3C)
Received on Monday, 23 September 2019 09:54:51 UTC