From d8e820b3516580834cf84521e438ed7b69f74632 Mon Sep 17 00:00:00 2001 From: Steve Lhomme Date: Sun, 23 Feb 2025 08:08:16 +0100 Subject: [PATCH] move the tag list in strings restriction in the string section --- tagging.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tagging.md b/tagging.md index 0a13d3f1d..faef25aa9 100644 --- a/tagging.md +++ b/tagging.md @@ -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 @@ -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.