[Matroska-devel] EBML data type constraints

Moritz Bunkus moritz at bunkus.org
Wed Jul 1 19:31:24 CEST 2015


> Is a 0 sized (un)signed integer allowed?

Als Ralph Giles has said: that'd be a change to existing practice, so
yes, they're allowed and represent value 0.

> Additionally, the EBML spec says that Floats may be either 4 or 8
> bytes, while the RFC Draft says 0, 4, 8, or 10. Are 0 or 10 byte
> length floats allowed?

Only floats of 4 and 8 bytes are allowed.

> The RFC Draft says that a "string can be zero length" while the EBML
> spec doesn't say. Is a 0 sized string element allowed?

They are and represent an empty string. Note that an empty string is not
the same as the element not being present (which might mean a default
value would come into play); therefore allowing zero-length strings is
pretty clearly a requirement.

Kind regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.matroska.org/pipermail/matroska-devel/attachments/20150701/657e1698/attachment.sig>

More information about the Matroska-devel mailing list