[RFC][PATCH] recursive metadata and language & contry for metadata
Hi Patch below would add $subj comments and alternative suggestions are welcome! Index: nut.txt =================================================================== --- nut.txt (revision 660) +++ nut.txt (working copy) @@ -970,6 +970,29 @@ might be less pretty. Note: Nonstandard fields should be prefixed by "X-". + When there are multiple tags with the same name but different values, + then each except the first MUST have a sequential number starting at 2 + appended, for example + "Author", "Author2", "Author3", ... + This is required to avoid ambiguity when info packets are repeated. + + Subtypes, like the authors email address, MUST have a type that is made + of the refering type + '/' + the subtype, so for example 2 email + addresses of the second author would be: + "Author2/X-EMAIL" and "Author2/X-EMAIL2" + All subtags of a tag should be stored immediately after the tag with + no other fields in between, so that simple players can just display the + tags sequentially and have readable output. + + If the value of a tag is in a specific language, that should be indicated + by appending hyphen and the 3 letter ISO 639-2 language code optionally + followed by an ISO 3166-1 country code that is separated from the + language code by a hyphen as well. Examples would be + "Author2-deu" "Michael" + "Author2-eng" "Mike" + + names MUST not contain / - or end in numbers to avoid ambiguity. + value value of this name/type pair -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB While the State exists there can be no freedom; when there is freedom there will be no State. -- Vladimir Lenin
Hi, Michael Niedermayer wrote:
Hi
Patch below would add $subj
comments and alternative suggestions are welcome!
Index: nut.txt =================================================================== --- nut.txt (revision 660) +++ nut.txt (working copy) @@ -970,6 +970,29 @@ might be less pretty. Note: Nonstandard fields should be prefixed by "X-".
+ When there are multiple tags with the same name but different values, + then each except the first MUST have a sequential number starting at 2 + appended, for example + "Author", "Author2", "Author3", ... + This is required to avoid ambiguity when info packets are repeated.
Why not overwriting "Author" tag, it will be easier for demuxers, if info packet is a repeated one, it would be simpler to mark it as "repeated", no ?
[...]
+ + names MUST not contain / - or end in numbers to avoid ambiguity.
Escaping mechanism is needed and would be more flexible IMHO. [...] -- Baptiste COUDURIER GnuPG Key Id: 0x5C1ABAAA Smartjog USA Inc. http://www.smartjog.com Key fingerprint 8D77134D20CC9220201FC5DB0AC9325C5C1ABAAA
On Tue, Sep 23, 2008 at 12:53:25PM -0700, Baptiste Coudurier wrote:
Hi,
Michael Niedermayer wrote:
Hi
Patch below would add $subj
comments and alternative suggestions are welcome!
Index: nut.txt =================================================================== --- nut.txt (revision 660) +++ nut.txt (working copy) @@ -970,6 +970,29 @@ might be less pretty. Note: Nonstandard fields should be prefixed by "X-".
+ When there are multiple tags with the same name but different values, + then each except the first MUST have a sequential number starting at 2 + appended, for example + "Author", "Author2", "Author3", ... + This is required to avoid ambiguity when info packets are repeated.
Why not overwriting "Author" tag, it will be easier for demuxers, if info packet is a repeated one, it would be simpler to mark it as "repeated", no ?
I dont fully understand what you suggest, please elaborate. There can be multiple authors for one part or it may be that in real time streams, metadata is updated when new becomes available, packets can be lost and repeated ... Simply overwriting when a repeat flag is set doesnt work: "Author" "Michael Niedermayer" [this packet is lost, though even if not the case is still ambiguous] "Author" "Baptiste Coudurier" ... "Author" "Michael Niedermayer" repeated "Author" "Baptiste Coudurier" repeated With numbers the problem does not arise "Author" "Michael Niedermayer" "Author2" "Baptiste Coudurier" ... "Author" "Michael Niedermayer" "Author2" "Baptiste Coudurier" Also "Author" "Michael Niedermayer" "Author2/X-EMAIL" "foo@bar" "Author2" "Baptiste Coudurier" Is another case where droping the numbers would not work.
[...]
+ + names MUST not contain / - or end in numbers to avoid ambiguity.
Escaping mechanism is needed and would be more flexible IMHO.
IMHO escaping should not be needed, there should be no need to have arbitrary characters in identifers. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB There will always be a question for which you do not know the correct awnser.
Michael Niedermayer wrote:
Hi
Patch below would add $subj
comments and alternative suggestions are welcome!
Index: nut.txt =================================================================== --- nut.txt (revision 660) +++ nut.txt (working copy) @@ -970,6 +970,29 @@ might be less pretty. Note: Nonstandard fields should be prefixed by "X-".
+ When there are multiple tags with the same name but different values, + then each except the first MUST have a sequential number starting at 2 + appended, for example + "Author", "Author2", "Author3", ... + This is required to avoid ambiguity when info packets are repeated. +
I'm not sure if it's likely to have a field with $number-$text or $text$number. Since we have already the idea of prefixes I'd put the numbering as prefix so 1-Author 2-Author 1-X-Flavour 2-X-Flavour and so on. lu -- Luca Barbato Gentoo Council Member Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero
On Wed, Sep 24, 2008 at 12:03:59AM +0200, Luca Barbato wrote:
Michael Niedermayer wrote:
Hi
Patch below would add $subj
comments and alternative suggestions are welcome!
Index: nut.txt =================================================================== --- nut.txt (revision 660) +++ nut.txt (working copy) @@ -970,6 +970,29 @@ might be less pretty. Note: Nonstandard fields should be prefixed by "X-".
+ When there are multiple tags with the same name but different values, + then each except the first MUST have a sequential number starting at 2 + appended, for example + "Author", "Author2", "Author3", ... + This is required to avoid ambiguity when info packets are repeated. +
I'm not sure if it's likely to have a field with $number-$text or $text$number.
Since we have already the idea of prefixes I'd put the numbering as prefix so
1-Author 2-Author
1-X-Flavour 2-X-Flavour
I preffer Michael's idea, due to easy sorting. I'd rather not have escaping, it unnecessarily complicates... - ods15
participants (4)
-
Baptiste Coudurier -
Luca Barbato -
Michael Niedermayer -
ods15＠ods15.dyndns.org