Skip to content
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

add some text to define the basic Matroska concepts need to understand tags #956

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

add some text to define the basic Matroska concepts need to understand tags #956

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 2 additions & 0 deletions index_tags.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,8 @@ but also chapters and tags. The `Tag` elements add important metadata to identif
in a Matroska `Segment`. It can tag a whole `Segment`, separate `Tracks` elements, individual `Chapter` elements or `Attachments` elements.

Some details about tagging are already present in [@!RFC9559, section 24].
Readers of this document should be familiar with that section, the different high level parts of Matroska as defined in in [@!RFC9559, section 4.5]
and EBML Master Elements as defined in in [@!RFC8794, section 7.7].

While the Matroska tagging framework allows anyone to create their own custom tags, it's important to have a common
set of values for interoperability. This document intends to define a set of common tag names used in Matroska.
Expand Down