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

move the tag list in strings restriction in the string section #948

Merged
merged 1 commit into from
Feb 25, 2025
Merged

move the tag list in strings restriction in the string section #948

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
6 changes: 3 additions & 3 deletions tagging.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,9 +46,6 @@ This corresponds to this layout of EBML elements:

In this way, it becomes possible to store any `SimpleTag` as attributes of another `SimpleTag`.

Multiple items **SHOULD** never be stored as a list in a single `TagString`. If there is more
than one tag value with the same name to be stored, then more than one `SimpleTag` **SHOULD** be used.

## Why Official Tags Matter

There is a debate between people who think all tags **SHOULD** be free and those who think
Expand Down Expand Up @@ -89,6 +86,9 @@ Although tags are metadata mostly used for reading, there are cases where the st
be used for sorting, categorization, etc. For this reason, when possible, strict formatting
of the value should be used so everyone can agree on how to use the value.

Multiple items **SHOULD** never be stored as a list in a single `TagString`. If there is more
than one tag value with the same name to be stored, then more than one `SimpleTag` **SHOULD** be used.

Due to preexisting files where these formatting rules were not explicit, they are usually
presented as rules that **SHOULD** be applied when possible, rather than **MUST** be applied
at all times. It is **RECOMMENDED** to use strict formatting when writing new tag values.
Expand Down