Thanks for clarification, Wook. The point I'm raising now may already have been discussed (and resolved) previously in the Term Cap TF. I think when both STB (possibly multiple of these) are connected to a TV, and the web app is trying to control them, there needs to be a way for the web app to know how the devices are connected, or at least how a TV may switch from displaying one STB output to another, as well as to its (TV's) own tuner output. This is almost the same problem faced by home theatre installers. Once we have that resolved, we can in fact "free" the web app to execute anywhere, on any device. Seems to me these are, at the minimum, the assumptions needed to define the use case. ---- Sheau Ng | NBCUniversal | P: +1.609.759.0819 From: 현욱 <whyun@etri.re.kr<mailto:whyun@etri.re.kr>> Date: Monday, June 10, 2013 11:24 AM To: Sheau Ng <sheau.ng@nbcuni.com<mailto:sheau.ng@nbcuni.com>> Cc: 김성혜 <shkim@etri.re.kr<mailto:shkim@etri.re.kr>>, JC Verdié <jc.verdie@mstarsemi.com<mailto:jc.verdie@mstarsemi.com>>, "public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>" <public-web-and-tv@w3.org<mailto:public-web-and-tv@w3.org>>, 허미영 <myhuh@etri.re.kr<mailto:myhuh@etri.re.kr>>, 강신각 <sgkang@etri.re.kr<mailto:sgkang@etri.re.kr>> Subject: Re: [apis] propose two use cases regarding tunner control and channel bounded applications 2013. 6. 10., 오후 10:29, "Ng, Sheau (NBCUniversal)" <Sheau.Ng@nbcuni.com<mailto:Sheau.Ng@nbcuni.com>> 작성: In the use case 6, is the TV web application controlling the "TV tuner" in the TV or in the STB? Yes, it is. I think that some kinds of APIs for handling TV tuner such as 'channelUp, channelDown, setChannel, etc' is needed to be defined. BTW, It is also possible to use declarative approach without defining channel-related apis. http://www.w3.org/2011/09/webtv/papers/channel_xml.pdf You may check further details in http://www.w3.org/2011/webtv/wiki/Terminal Regards, --
Received on Monday, 10 June 2013 17:42:24 UTC