[Matroska-devel] EBML

[Steve Lhomme]

Martin Nilsson wrote:

> http://pike.ida.liu.se/generated/ebml.txt

In Chapter 2

"The default value can also be a symbol referring back to a previously 
seen symbol. If however no such symbol has been seen, i.e. it has not 
been encoded into the EBML data and has no default value, the element 
will not be added as a child on the semantic level."

This has not been firmly defined yet. Even though in Matroska we already 
use this. The problem is in what scope the 'other' element should be. 
Especially since there is no order in EBML (as in XML). Even though we 
always assume there is one... I really have no idea on how to define 
this clearly. So for now your formulation is best.

"2.7.  Child order property"

This is not yet supported. But the idea to have some elements that need 
ordering and some not is good.


There are 2 chapter 4



Otherwise the rest is OK.
IMPRESSIVE WORK !!!

Do you plan to submit this to the IETF ? That would be great to have 
EBML become a wide standard. Because I'm sure it can be used in many 
cases : small XML that can store binary data and use default values.