[tvcontrol-api] Interface to "applications" / data components

chrisn has just created a new issue for 
https://github.com/w3c/tvcontrol-api:

== Interface to "applications" / data components ==
The [radio API change](https://github.com/w3c/tvcontrol-api/pull/14) 
introduced a `TVApplication` interface, which can be used to access 
broadcast application specific data such as images (DAB Slideshow) and
 text messages (Dynamic Label).

Following on from a 
[comment](https://github.com/w3c/tvcontrol-api/pull/14#issuecomment-256897583)
 I made in the PR:

Accessing this data requires allocation of decoding resources in the 
implementation, so I think these should be exposed through interfaces 
more closely related to the `TVMediaStream` rather than the 
`TVChannel` (which is more about channel-level metadata)?

Since slideshow images and text labels are intended to be synchronised
 to the playing media, we could possibly expose these through 
[`HTMLTrackElement`](https://w3c.github.io/html/single-page.html#htmltrackelement-htmltrackelement)
 and 
[`TextTrackCue`](https://w3c.github.io/html/single-page.html#texttrackcue-texttrackcue).
 What interface should we use to support images? See [this 
discussion](https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/U06zrT2N-Xk)
 regarding 
[`DataCue`](https://w3c.github.io/html/single-page.html#datacue-datacue).

See also [Sourcing In-band Media Resource Tracks from Media Containers
 into HTML](https://dev.w3.org/html5/html-sourcing-inband-tracks/).

If we take this approach, would we still want to provide metadata 
about available applications through `TVChannel`? Another issue is 
that "application" is a quite overloaded term, so if we want to do 
this, we should find another name, e.g., Alex's suggestion 
`TVDataComponent`.

Please view or discuss this issue at 
https://github.com/w3c/tvcontrol-api/issues/29 using your GitHub 
account

Received on Tuesday, 15 November 2016 10:27:46 UTC