RE: Proposal from HbbTV

>If a text track never exposes any cues, we shouldn't expose its existence to browsers. That's like saying: hey, I have some data, but I won't give it to you. Or if we apply that logic to an audio or video stream: it's like announcing that a video stream exists, but not rendering it. Such tracks are not relevant to this specification.

What about text tracks that are rendered by the (native) media player and where HTML would like to be able to enable/disable them in the same way as video & audio?

Jon


________________________________________
From: Silvia Pfeiffer [silviapfeiffer1@gmail.com]
Sent: 24 September 2014 21:57
To: Jon Piesing
Cc: alexander.adolf@condition-alpha.com; public-inbandtracks@w3.org; Nigel Megitt
Subject: Re: Proposal from HbbTV

On Wed, Sep 24, 2014 at 10:51 PM, Jon Piesing <Jon.Piesing@tpvision.com> wrote:
>
>>Also: what's the purpose in not exposing any of the cue content for MPEG-2 TS ?
>
> HbbTV has no requirement for this and it seems like a lot of work. DVB has many, many different ways of carrying data in an MPEG-2 transport stream and there's no outright winner or lowest common denominator.


If a text track never exposes any cues, we shouldn't expose its
existence to browsers. That's like saying: hey, I have some data, but
I won't give it to you. Or if we apply that logic to an audio or video
stream: it's like announcing that a video stream exists, but not
rendering it. Such tracks are not relevant to this specification.

Regards,
Silvia.

Received on Wednesday, 24 September 2014 20:32:48 UTC