RE: Rechartering the TV Control Working Group

Hi all,

Please see the draft liaison below. Your comments and feedback are very welcome. 

Best regards,

Chris (WG Chair)

--

This is a follow up to the previous liaisons between ATSC and the W3C Web and TV Interest Group in 2014, regarding the use of W3C specifications as part of the ATSC 3.0 runtime environment, and in particular your message to Chair of the TV Control Community Group on 22 October 2015.

On 14 April 2016, W3C created the TV Control Working Group, to continue the work done by the Community Group on the TV Control API, and to put this specification onto the W3C standards track.

The TV Control API aims to provide a way of sourcing broadcast and IPTV delivered media into the browser that is closely integrated with HTML5 and the web platform in general. Control of media playback is achieved through the familiar <video> and <audio> element interfaces. The API also provides access to program information (EPG), program recording and playback, parental control, emergency alert events, and triggered interactive overlays. For consistency with other web platform APIs, the TV Control API builds upon other W3C work, such as WebRTC MediaStream.

In response to feedback received from group participants, W3C members, and the W3C Technical Architecture Group (TAG), the TV Control Working Group has been working to align the API better with the rest of the web platform, and to bring a higher level of abstraction that is less coupled to specific device implementation details. This design is more flexible, and should ease integration of the TV Control API in regular web runtimes.

The Working Group is now starting rechartering discussions and, by end of January 2017 we expect to submit an updated charter and timelime for approval.

We would like to know whether the TV Control API still being considered to become part of ATSC 3.0. If so, we encourage more ATSC members to join the Working Group to further the standardisation of the API, and to support the re-chartering of the group after March 2017. If not, what would need to change to make the API suitable for your use cases?

Received on Monday, 12 December 2016 15:58:28 UTC