Skip to content

Commit 5807465

Browse files
committed
move the tag list in strings restriction in the string section
1 parent 5ed5c43 commit 5807465

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

tagging.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -46,9 +46,6 @@ This corresponds to this layout of EBML elements:
4646

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

49-
Multiple items **SHOULD** never be stored as a list in a single `TagString`. If there is more
50-
than one tag value with the same name to be stored, then more than one `SimpleTag` **SHOULD** be used.
51-
5249
## Why Official Tags Matter
5350

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

89+
Multiple items **SHOULD** never be stored as a list in a single `TagString`. If there is more
90+
than one tag value with the same name to be stored, then more than one `SimpleTag` **SHOULD** be used.
91+
9292
Due to preexisting files where these formatting rules were not explicit, they are usually
9393
presented as rules that **SHOULD** be applied when possible, rather than **MUST** be applied
9494
at all times. It is **RECOMMENDED** to use strict formatting when writing new tag values.

0 commit comments

Comments
 (0)