- From: Steve Morris via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Nov 2016 09:04:05 +0000
- To: public-tvcontrol@w3.org
@JPEvain thanks for your comments > Introducing the notion of IP multicast may lead to different APIs to resolve the list of TVChannels available from these different types of sources? I would hope that the API is the same in each case. We have getChannels() on the TVSource, although I do wonder whether this per-source separation of channels is really a good thing: many devices only present a unified channel list to the user, regardless of the source. I'm not sure if that's something we need to consider now, or leave it until we've defined the basic shape of the API > I would keep the definitions as generic as possible. The penultimate sentence looks like a repeat of what's being said in the second sentence. I would keep the last sentence of the definition of TVSource out. Re-reading this, I agree. > The definition of TVChannel -> DVB Service, ATSC?? It would be an ATSC Channel > Mediastream (if we want to reuse definitions) Yes, I think the area you highlight probably does need further discussion, although what is there is based on discussions from TPAC and is similar to the WebRTC model. > TVProgram -> DVB Event -> ATSC?? It would be an ATSC Event. -- GitHub Notification of comment by stevem-tw Please view or discuss this issue at https://github.com/w3c/tvcontrol-api/issues/4#issuecomment-260282392 using your GitHub account
Received on Monday, 14 November 2016 09:04:11 UTC