Skip to content

Remove normative text from IANA considerations #1075

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
robUx4 merged 2 commits into from
Feb 26, 2026
Merged

Remove normative text from IANA considerations #1075

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
df23b97
tags: remove normative text not found in the rest of the document
robUx4 Feb 25, 2026
e86a5dd
codec: add a text to mention the code
robUx4 Feb 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions cellar-tags/rfc_backmatter_tags.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,10 @@ description is clear and fits the purpose of this registry.

Moreover, criteria for `binary` tags include ensuring the data in the `TagBinary` element
are defined in a specification.
When possible, i.e., the binary format is not already in use elsewhere, the
data should not start with the size of the data to follow, as this size is already
When possible, i.e., the binary format is not already in use elsewhere, it is **RECOMMENDED** that the
data not start with the size of the data to follow, as this size is already
part of the `TagBinary` element.
The content of the binary data **MUST NOT** be a single UTF-8 string, in which case the tag should be `TagString`.

Criteria for `nested` tags include ensuring that the tag consists of one or more
child `SimpleTag` elements to describe the metadata corresponding to that tag.
Expand Down
6 changes: 1 addition & 5 deletions cellar-tags/tags_iana.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,10 +11,8 @@ a Change Controller, and
an optional Reference to a document describing the Element ID.

The Name corresponds to the value stored in the `TagName` element.
A Tag Name **MUST** only be found once in the IANA registry.
Two Tag Names **MUST NOT** have the same semantic meaning.
The Name is written in all latin capital letters, numbers and the underscore character '_'
as defined in (#tag-formatting). The Name **MUST NOT** start with the underscore character '_'.
as defined in (#tag-formatting). The Name must not start with the underscore character '_'.

The Type corresponds to which element will be stored the tag value.
There can be 3 values for the Type:
Expand All @@ -26,8 +24,6 @@ Matroska Tag Names for UTF-8 data are to be allocated according to the "First Co
* `binary`: the value of the Tag is stored in `TagBinary`,

Matroska Tag Names for binary data are to be allocated according to the "Specification Required" policy [@!RFC8126].
The content of the binary data **MUST NOT** be a single UTF-8 string, in which case the type should be `UTF-8`.
It is **RECOMMENDED** to not include the size of the binary data at the start of the data as the size is already handled by the element itself.

* `nested`: the tag doesn't contain a value, i.e., neither a `TagBinary` nor a `TagString` child element, only `SimpleTag` child elements inside.

Expand Down