[Ogg a11y] Fwd: Codec specific information in BOS header

Ralph Giles giles at xiph.org
Fri Nov 21 12:03:24 PST 2008


On Fri, Nov 21, 2008 at 4:09 AM, ogg.k.ogg.k at googlemail.com wrote:

> That, to allow a codec to place its specific information in this space,
> we would need a second offset. Otherwise, when/if you want to revise
> the generic part of the BOS and add a generic field, you cannot add
> it without breaking those codec specific parts.

Is the version field not sufficient to flag this? I'd suggest we use a
fixed offset now, and encode this second offset, or an offset to
additional OggText fields in the reserved area if we need to revise
the BOS structure.

There are also additional header packets, of course.

Silvia said:

> Yes, that's exactly what it was meant for. And for future version of
> the BOS page, to make it easy for a decode to get to the right pages.

If this is intentional, I think you should mark 'zero or more bytes of
codec-specific data' on the packet diagram, so it is obvious this
should be supported.

 -r


More information about the Accessibility mailing list