w3c / tvcontrol-api

TV Control API specification - https://w3c.github.io/tvcontrol-api/
10 stars 11 forks source link

Component Discovery and Selection #38

Open mprobst-irt opened 7 years ago

mprobst-irt commented 7 years ago

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.