- From: Michael Probst via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Nov 2016 16:45:31 +0000
- To: public-tvcontrol@w3.org
mprobst-irt has just created a new issue for https://github.com/w3c/tvcontrol-api: == Component Discovery and Selection == There are various ways to discover available channel components and also to select them. The TVProgram interface has languages for audio and subtitles which I think refers to EPG data, e.g. languages signalled for components in EIT schedule. -> the current TVProgram interface is missing support for accessibility services like audio description. The MediaStream and its extension has tracks and allows to enable/disable them. The HTML5 media elements have tracks and allow to enable/disable them. -> Is it clear how both objects interact? Can either be used? -> See also my other issue on mapping service information to API. It should be defined which part of a service information is used to populate properties for tracks etc. -> There should be a defined relation between a component signalled in the EPG with tracks retrieved from MediaStream or HTML5 MEs. For example the EPG includes information that a program comes with Audio Description. When the program is running it should be possible to identify the proper audio track. Please view or discuss this issue at https://github.com/w3c/tvcontrol-api/issues/38 using your GitHub account
Received on Thursday, 17 November 2016 16:45:38 UTC