- From: JPEvain via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Nov 2016 09:25:28 +0000
- To: public-tvcontrol@w3.org
The list of definitions is what we want to achieve to make sure we are all speaking the same language but there might be more work to be done. I'll share my comments soon. As I mentionned earlier in the thread, I believe mapping to DVB and ATSC is important in order to interoperate with these systems and the information they carry. I have been going back to the list of use cases to derive a few typical configurations. I was pleased to see that the use cases cover the configurations I had in mind when thinking about the definitions and associated data and some basic implementations. These configurations are important to remind us why we want to use the API for. Maybe we should open a separate issue to discuss / list configurations... 1. A device (not a TVSet) is equipped with a tuner and the proposal is to control/use this tuner to access content via an application 2. An (e.g. OTT) application like an EPG is used to select content of interest. The proposal is to play the content on the TVSet (with its own setup process), although it could equally be played on the application mentioned above. Is there anything else important missing? If not, we can look at the definitions again to: - refine what we associate with each term / object accessible through the API - verify the mapping between the data provided in line, which will be used to discover and access content through the API, and the data provided in applications like an EPG or why not a search engine. I'll look at the definitions again with these two configurations in mind and comment bearing in mind my original attempt to map to DVB (I know where to find DVB support) and ATSC (ATSC experts please help). -- GitHub Notification of comment by JPEvain Please view or discuss this issue at https://github.com/w3c/tvcontrol-api/issues/4#issuecomment-259641238 using your GitHub account
Received on Thursday, 10 November 2016 09:25:34 UTC