- From: JC Verdié <jicheu@yahoo.fr>
- Date: Tue, 3 Dec 2013 10:24:24 +0100
- To: "Mandyam, Giridhar" <mandyam@quicinc.com>
- Cc: public-web-and-tv <public-web-and-tv@w3.org>
- Message-Id: <423806D9-A2A0-43DB-806C-EEC6EF7B87C3@yahoo.fr>
Hi Giri On 30Nov 2013, at 23:04, Mandyam, Giridhar <mandyam@quicinc.com> wrote: > Hello JC, > Thanks. I agree. > > I have made edits to the requirements wiki with the clarification. Please modify/correct as you see fit. > http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Content_Streaming > Looks good to me :) Rgds JC > -Giri > > From: JC Verdié [mailto:jicheu@yahoo.fr] > Sent: Thursday, November 28, 2013 1:40 AM > To: Mandyam, Giridhar > Cc: public-web-and-tv > Subject: Re: [apis] Clarification on Requirement for Content Streaming > > Hi Giri, > > On 27Nov 2013, at 22:38, Mandyam, Giridhar <mandyam@quicinc.com> wrote: > > > Re: http://www.w3.org/2011/webtv/wiki/Media_APIs/Requirements#Content_Streaming > > The requirement currently reads: > “There SHALL be a mechanism to stream TV’s content to HTML player in set-top box.” > > I had originally interpreted “TV’s content” to really be TV content (i.e. broadcast content), but in retrospect I am not sure if that is the correct interpretation. What was “TV’s content” intended to cover? > > > My opinion is that TV Content != broadcast. It could be: > - a broadcast emitted content > - a broadband emitted content (over broadcast such as DVB-IPI, or a multicast ip stream) > - a local content (PVR, …) > - a local network content (accessed through DLNA, airplay, miracast, dial... or other local network streaming protocol). > > JC > > > > My apologies if this issue has been addressed before. > > -Giri Mandyam, Qualcomm Innovation Center
Received on Tuesday, 3 December 2013 09:24:55 UTC