fix maxOccurs default value in the EBML Schema

[nerg4l]

A PR as promised.

Fixes #395

Feel free to add suggestion for the wording, or simply commit your changes on this PR (I allowed edits by maintainers).

[robUx4]

I think you should split the PR in 2. While the XSD fix is likely to make it, I'm less confident that a change of text will occur.

[robUx4]

The Matroska XML file still validates with the XSD change (phew).

[nerg4l]

Is it okay if I leave the change in the specification to you? In my opinion the change is needed because the following statement is now incorrect:

maxOccurs is a nonnegative integer expressing the maximum permitted number
of occurrences of this EBML Element within its Parent Element.

The rest can be kept as is. I just wanted to clarify the meaning of "unbounded".

[robUx4]

LGTM

[robUx4]

@mcr I sent an email to the mailing list so this can be handled through the proper channels
https://mailarchive.ietf.org/arch/msg/cellar/SwUeIWgHsf0ZZ8xDu6ehGT0ZcII/

[robUx4]

Is it okay if I leave the change in the specification to you? In my opinion the change is needed because the following statement is now incorrect:

maxOccurs is a nonnegative integer expressing the maximum permitted number
of occurrences of this EBML Element within its Parent Element.

The rest can be kept as is. I just wanted to clarify the meaning of "unbounded".

Just create a new PR with this other patch. It might be approved but I don't know how/if it will end up in the ERRATA.

[nerg4l]

Okay, thanks for the clarification

[robUx4]

Merge thanks !
Now we have to do the RFC errata.