Subject: [Cellar] ebml constraints on occurrences

From: Dave Rice <[email-masked]>
Date: Sun, 13 Mar 2016 11:41:20 -0400

The definition for min and maxOccurs which define how often the Element can occur didn’t work for Level 0 Elements. The definition was:
> An integer to express the minimal number of occurrences that the EBML Element MUST occur within its Parent Element if its Parent Element is used.
however, Level 0 Elements have no Parent Element. I added the line:
> If the Element has no Parent Level (as is the case with Elements at Level 0), then minOccurs refers to constaints on the Element's occurrence within the EBML Document.

This is in this PR: https://github.com/Matroska-Org/ebml-specification/pull/59

Dave Rice