search

w3c / dapt

Dubbing and Audio description Profiles of TTML2
https://w3c.github.io/dapt/
Other
7 stars 3 forks source link

Embedded data: Do we need to support all the permitted encodings? What about length? #117

Open nigelmegitt opened 1 year ago

nigelmegitt commented 1 year ago

In TTML2's <data> element, an encoding can be specified, being one of:

Do we need to require processor support for all of them, or will the default base64 be adequate?

Also, it is possible to specify a length attribute that provides some feasibility of error checking, since the decoded data must be the specified length in bytes. Is requiring support for this a net benefit? Would it be used?

cconcolato commented 1 year ago

Also, if supported at all, do we want to put a size limit on the actual data to be embedded?

nigelmegitt commented 1 year ago

If we are supporting embedded data then a size limit would be unhelpful for anyone who hits that limit. What would be the benefit of such a limit?

cconcolato commented 1 year ago

The benefit would be when allocating buffers, you know you'll never have a larger resources than the limit.

nigelmegitt commented 1 year ago

We could require that embedded data includes the length attribute so that implementations that do not have enough resource available can fail gracefully, before attempting to convert the resource to an internal audio object, rather than part way through. Would that address the concern?