- From: Mandyam, Giridhar <mandyam@quicinc.com>
- Date: Sat, 30 Nov 2013 22:04:58 +0000
- To: JC Verdié <jicheu@yahoo.fr>
- CC: public-web-and-tv <public-web-and-tv@w3.org>
- Message-ID: <CAC8DBE4E9704C41BCB290C2F3CC921A166B7D8D@nasanexd01h.na.qualcomm.com>
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 -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<mailto: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 Saturday, 30 November 2013 22:05:28 UTC