Skip to content

Commit

Permalink
assume values not found in WebM have their default value
Browse files Browse the repository at this point in the history
WebM doesn't use all our elements but sometimes they are implied even though
they don't define it. For example ContentEncodingOrder.

The elements must not be in WebM files (for compliance) but a parser may need
the actual value (of ContentEncodingOrder) to make any sense. So we assume
elements have their default values if they are not found.

If this is too loose, we may have to list the elements not in WebM but which
default value should be used.
  • Loading branch information
robUx4 committed Oct 11, 2018
1 parent 20ebbd0 commit 2b0224c
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion matroska_schema_section_header.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ In addition to the EBML Schema definition provided by the EBML Specification, Ma

| attribute name | required | definition |
|:---------------|:---------|:-----------|
| webm | No | A boolean to express if the Matroska Element is also supported within version 2 of the `webm` specification. Please consider the [webm specification](http://www.webmproject.org/docs/container/) as the authoritative on `webm`. |
| webm | No | A boolean to express if the Matroska Element is also supported within version 2 of the `webm` specification. Please consider the [webm specification](http://www.webmproject.org/docs/container/) as the authoritative on `webm`. Elements with the webm boolean set to false MUST NOT be found in WebM. On the other end readers MAY assume these elements have their default value if they have one. |

# Matroska Schema

Expand Down

0 comments on commit 2b0224c

Please sign in to comment.