[Matroska-devel] EBML specification component for review - Structure

[Erik Piil]

This discussion relates to the “Structure” portion of the earlier EBML RFC
Draft for revision/incorporation into the final EBML specification.


>From the RFC Draft:


Structure

Syntactically an EBML document is a list of EBML elements. Each element has
three parts; an element ID, a size descriptor and the element data payload.
The element data payload is then either data, implicitly typed by the
element ID, or a list of EBML elements.

EBML = *ELEMENT

ELEMENT = ELEMENT_ID SIZE DATA

DATA = VALUE / *ELEMENT

ELEMENT_ID = VINT

SIZE = VINT

EBML uses big endian/network order byte order, i.e. most significant bit
first. All of the tokens above are byte aligned.


Any thoughts are most appreciated.


Best,


Erik
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.matroska.org/pipermail/matroska-devel/attachments/20150429/5c5928d3/attachment.html>