- From: JPEvain via GitHub <sysbot+gh@w3.org>
- Date: Sat, 05 Nov 2016 08:03:25 +0000
- To: public-tvcontrol@w3.org
Hi all, I am probably joining the discussion late but I am starting to dive into this as my problem is to look at a better use of metadata for selecting a programme of interest to be eventually displayed. Reading the specification, independently from implementation details (i.e. what function should do what), I can live with a TVManager that identifies available TVTuners (yes, tv sets on the market do have more than one tuner) as physical devices, through which information can be collected to list tvsources/channels. Question: do we mean using inline metadata from embedded service information? Then either a tvsource/channel is selected and the mediaStream in consumed displaying the programme available at that time, or the inline metadata such as present/following data allows selecting a tvsource/channel for the particular programme it offers. Question: I do not see how the current APIs would exploit the data to select a tvsource/channel for its content/programme. Actually, in this context, I am more confused with "tvsources vs. channels" than "tvtuner vs tvsource". General comment: we have clear focus on TV but these could be Radio as well -- GitHub Notification of comment by JPEvain Please view or discuss this issue at https://github.com/w3c/tvcontrol-api/issues/4#issuecomment-258597434 using your GitHub account
Received on Saturday, 5 November 2016 08:03:47 UTC