- From: Chris Needham via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Oct 2016 11:27:20 +0000
- To: public-tvcontrol@w3.org
A few more comments on these changes: Is application data only available for channels being presented, or can the data from any channel be accessed? I'm wondering whether the application data should be more closely related to the `TVMediaStream` rather than the `TVChannel` interface. Is the application data expected to be aligned temporally with the audio/video media? If so, we could look at using [TextTrackCue](https://w3c.github.io/html/single-page.html#texttrackcue-texttrackcue), as `TVMediaStream` has support for text tracks. Maybe we could use [DataCue](https://w3c.github.io/html/single-page.html#datacue-datacue) to support application-specific data types. I'm also worried that introducing an `Application` (or `TVApplication`) interface might be confusing, as elsewhere in the spec we use "application" to mean Web applications that use the TV Control API. Having said this, I think we should merge this PR (together with Francois' changes) and raise separate issues for these questions. -- GitHub Notification of comment by chrisn Please view or discuss this issue at https://github.com/w3c/tvcontrol-api/pull/14#issuecomment-256897583 using your GitHub account
Received on Friday, 28 October 2016 11:27:26 UTC