EBML specification component for review - Structure
Erik Piil <[email protected]>
| Newsgroups | gmane.comp.multimedia.matroska.devel |
|---|---|
| Message-ID | <CAKNa7H_AGau9h=QaG2xf35z=GBjB64ofnYgOAN7r-Fj=qa7prw@mail.gmail.com> |
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 _______________________________________________ Matroska-devel mailing list [email protected] http://lists.matroska.org/cgi-bin/mailman/listinfo/matroska-devel Read Matroska-Devel on GMane: http://dir.gmane.org/gmane.comp.multimedia.matroska.devel