[whatwg] Thoughts on video accessibility
silviapfeiffer1 at gmail.com
Tue Dec 9 12:30:29 PST 2008
Also, for those interested, metavid and mv_embed are examples of use of ROE:
for clean remote embedding of multiple text/video/audio tracks in a
single xml encapsulation.
An example of such embeds is here: http://metavid-mike.blogspot.com/
On Wed, Dec 10, 2008 at 3:49 AM, Silvia Pfeiffer
<silviapfeiffer1 at gmail.com> wrote:
> I heard some complaints about there not being any implementation of
> the suggestions I made.
> So here goes:
> 1. out-of-band
> There is an example of using srt with ogg in a out-of-band approach here:
> You will need Firefox3.1 to play it.
> The syntax of what Jan implemented is different to what I proposed,
> but I wanted to take it forward and make it more generic.
> 2. in-band
> There is also a draft implementation of srt inside Ogg through the
> OggText specification, but I it's not released yet. It is also not as
> relevant to this group as the out-of-band example.
> On Tue, Dec 9, 2008 at 7:33 PM, Robert O'Callahan <robert at ocallahan.org> wrote:
>> On Tue, Dec 9, 2008 at 6:20 PM, Martin Atkins <mart at degeneration.co.uk>
>>> Silvia Pfeiffer wrote:
>>>> I'm interested to hear people's opinions on these ideas. I agree with
>>>> Ralph and think having a simple, explicit mechanism at the html level
>>>> is worthwhile - and very open and explicit to a web author. Having a
>>>> redirection through a ROE-type file on the server is more opaque, but
>>>> maybe more consistent with existing similar approaches as taken by
>>>> RealNetworks in rm files and WindowsMedia files in asx files.
>>> This (having a separate document that references other streams) is what I
>>> was thinking of. I guess which is more natural depends on who is doing the
>>> assembling. If it is the HTML author that takes the individual pieces and
>>> links them together then doing it in the HTML is probably easiest.
>> For what it's worth, loading an intermediate document of some new type which
>> references other streams to be loaded adds a lot of complexity to the
>> browser implementation. It creates new states that the decoder can be in,
>> and introduces new failure modes. It creates new timing issues and possibly
>> new security issues.
>> "He was pierced for our transgressions, he was crushed for our iniquities;
>> the punishment that brought us peace was upon him, and by his wounds we are
>> healed. We all, like sheep, have gone astray, each of us has turned to his
>> own way; and the LORD has laid on him the iniquity of us all." [Isaiah
More information about the whatwg