[Matroska-devel] Re: Re: Re: Tag names

[Age Bosma]

Age Bosma wrote:

> I updated my document again. Your changes so far are included and I'll 
> mark the nested id3 fields later on today.
> 
> I would like to suggest to move the "Titles" section to the to pof the 
> page or maybe underneath the "General" section. This would be a more 
> logical position because it's more important compared to the rest of the 
> tag fields. Also AMOUNT should maybe be placed above CURRENCY.
> 
> As for the consistent and logical naming of fields I would like to 
> propose to change the following in the current specs:
> - FILE -> ORIGINAL_FILE
>   FILE itself doesn't say anything about the content and because 
> ORIGINAL_.... is used in multiple places...
> - FRAMESPS -> FRAMES_PER_SECOND
>   Like BITS_PER_SECOND and BEATS_PER_MINUTE
> - MOOD -> MOOD_DESCRIPTION
>   I'm not a 100% sure about changing this one but desided to mention it 
> anyway
> - PRODUCT -> ORIGINAL_PRODUCT or maybe even ORIGINAL_PRODUCT_NAME
> - INSTRUMENT -> INSTRUMENTS
> - DATE_RELEASE_ORIGINAL -> DATE_ORIGINAL_RELEASE
> - DATE_TAGGING -> DATE_TAGGED
> - DATE_DIGITIZING -> DATE_DIGITIZED
> - DATE -> DATE_START
>   Because it's used in together with DATE_END
> - LEAD_PERFORMER -> ARTIST
>   ARTIST is used in all other tag types and means the same thing, imo it 
> would be unwise to do something completely different in this case.
> - ORIGINAL_TITLE
>   This description is to vague and open. Maybe ORIGINAL_x shold be 
> included in the specs meaning "ORIGINAL_ can be placed infront of every 
> field to indicate it's origin, e.g. ORIGINAL_ALBUM, ORIGINAL_ARTIST, 
> etc." it might not make sence in all cases but it can be used in almost 
> all cases.
> - INVOLVED_PERSON -> CREDITS
>   Not sure again if this would be wise to change though.
> - EDITION -> VERSION
> 
> I know, it does look a bit drastic and I may have overlooked some as 
> well but I figured while we are at changing the specs we might as well 
> do it right ;-)

As an update about the "ORIGINAL" suggestion: what about introducing a 
new level for the "ORIGINAL_x" information?
This makes it all grouped nicely and you're again capable of specifying 
the "ORIGINAL" info of almost anything people see fit.

Age