Re: EBML specification component for review - Structure

Sounds ok to me as VINT is described in another email.

On Thu, Apr 30, 2015 at 5:52 AM, Erik Piil <[email protected]> wrote:

> 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
>



-- 
Steve Lhomme
Matroska association Chairman

_______________________________________________
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