Set the EBML characteristics of the data to follow. Each EBML document has to start with this. The version of EBML parser used to create the file. The minimum EBML version a parser has to support to read this file. The maximum length of the IDs you'll find in this file (4 or less in Matroska). The maximum length of the sizes you'll find in this file (8 or less in Matroska). This does not override the element size indicated at the beginning of an element. Elements that have an indicated size which is larger than what is allowed by EBMLMaxSizeLength shall be considered invalid. A string that describes the type of document that follows this EBML header. 'mide' for Mide Instrumentation Data Exchange files. The version of DocType interpreter used to create the file. The minimum DocType version an interpreter has to support to read this file. Used to void damaged data, to avoid unexpected behaviors when using damaged data. The content is discarded. Also used to reserve space in a sub-element for later use. The CRC is computed on all the data of the Master element it's in. The CRC element should be the first in it's parent master for easier reading. All level 1 elements should include a CRC-32. The CRC in use is the IEEE CRC32 Little Endian Contain signature of some (coming) elements in the stream. Signature algorithm used (1=RSA, 2=elliptic). Hash algorithm used (1=SHA1-160, 2=MD5). The public key to use with the algorithm (in the case of a PKI-based signature). The signature of the data (until a new. Contains elements that will be used to compute the signature. A list consists of a number of consecutive elements that represent one case where data is used in signature. Ex: Cluster|Block|BlockAdditional means that the BlockAdditional of all Blocks in all Clusters is used for encryption. An element ID whose data will be used to compute the signature. A 'field' for config items without individual UI widgets (e.g. created from multiple other fields) For hidden fields, this determines if the config item will be written. Special-case widget that creates a resizable vertical spacer, placing the fields following it on the bottom of the dialog. Special-case control that compares device time to system time. Special-case control that resets all the siblings in its group or tab to their factory default values. Container For arbitrary name/value attributes, allowing additional data without revising (and bloating) the schema. All of these elements are level -1, allowing an AttributeList to occur at any level, but should always be used at the relative levels implied below. Attribute name. Should always be child of Atrribute. Integer Attribute. Should always be child of Atrribute. Unsigned integer Attribute. Should always be child of Atrribute. Floating point Attribute. Should always be child of Atrribute. ASCII String Attribute. Should always be child of Atrribute. Date Attribute. Should always be child of Atrribute. Binary Attribute. Should always be child of Atrribute. ASCII String Attribute. Should always be child of Atrribute.