- From: Bob Lund <B.Lund@CableLabs.com>
- Date: Tue, 31 May 2011 09:44:44 -0600
- To: Web and TV Interest Group WG <public-web-and-tv@w3.org>
While there may be <video> tag requirements imposed by MPEG-2 TS, it doesn't seem to fit within the scope of the HNTF, which is addressing how home network services get discovered and used by Web content. There has been some discussion about starting a new TF to address how adaptive bit-rate delivery should be accommodated in HTML5. This would seem to be the place to also examine the MPEG-2 TS issue raised. Thanks, Bob Lund > -----Original Message----- > From: public-web-and-tv-request@w3.org [mailto:public-web-and-tv- > request@w3.org] On Behalf Of Web and TV Interest Group Issue Tracker > Sent: Monday, May 30, 2011 2:27 AM > To: public-web-and-tv@w3.org > Subject: webtv-ISSUE-18 (JanL): Video tag support of MPEG2-TS > [HOME_NETWORK_TF] > > > webtv-ISSUE-18 (JanL): Video tag support of MPEG2-TS [HOME_NETWORK_TF] > > http://www.w3.org/2011/webtv/track/issues/18 > > Raised by: Jan Lindquist > On product: HOME_NETWORK_TF > > The support of MPEG2-Transport Stream is fundamental to viewing content > in the home (ex. TV). Applications require an API to have control and > access of MPEG2-TS components. > > This use case puts explicit requirements of what the the application may > requires support from the video tag (HTML5). While video tag support > many of the indicated implementation requirements not all are supported. > This use case may not explicitly indicate the missing portions but > highlights the full set of implementation requirements. > >
Received on Tuesday, 31 May 2011 15:45:14 UTC