Is there any chance that there could be a v2 of the Ogg Vorbis Tag Standard on the horizon? The thing is that I get used to the extra fields in MediaMonkey & then that's it. If MediaMonkey falls to a better program/database in the future, then how do I port all those extra bits of info from the database since they're NOT in the tag. Well, this just happened to me since I decided to leave NI's Traktor. All that extra info is still in that damn database & I really don't fell like hand jamming it all into MediaMonkey.

I know it's been discussed before, but it just makes total sense to me to have the artwork embedded in the tag. Otherwise, that's just one more bit of info left to the old database.


Just look at how many Tag Fields are in the ID3v4 standard:

4. Declared ID3v2 frames

The following frames are declared in this draft.

4.19 AENC Audio encryption
4.14 APIC Attached picture
4.30 ASPI Audio seek point index

4.10 COMM Comments
4.24 COMR Commercial frame

4.25 ENCR Encryption method registration
4.12 EQU2 Equalisation (2)
4.5 ETCO Event timing codes

4.15 GEOB General encapsulated object
4.26 GRID Group identification registration

4.20 LINK Linked information

4.4 MCDI Music CD identifier
4.6 MLLT MPEG location lookup table

4.23 OWNE Ownership frame

4.27 PRIV Private frame
4.16 PCNT Play counter
4.17 POPM Popularimeter
4.21 POSS Position synchronisation frame

4.18 RBUF Recommended buffer size
4.11 RVA2 Relative volume adjustment (2)
4.13 RVRB Reverb

4.29 SEEK Seek frame
4.28 SIGN Signature frame
4.9 SYLT Synchronised lyric/text
4.7 SYTC Synchronised tempo codes

4.2.1 TALB Album/Movie/Show title
4.2.3 TBPM BPM (beats per minute)
4.2.2 TCOM Composer
4.2.3 TCON Content type
4.2.4 TCOP Copyright message
4.2.5 TDEN Encoding time
4.2.5 TDLY Playlist delay
4.2.5 TDOR Original release time
4.2.5 TDRC Recording time
4.2.5 TDRL Release time
4.2.5 TDTG Tagging time
4.2.2 TENC Encoded by
4.2.2 TEXT Lyricist/Text writer
4.2.3 TFLT File type
4.2.2 TIPL Involved people list
4.2.1 TIT1 Content group description
4.2.1 TIT2 Title/songname/content description
4.2.1 TIT3 Subtitle/Description refinement
4.2.3 TKEY Initial key
4.2.3 TLAN Language(s)
4.2.3 TLEN Length
4.2.2 TMCL Musician credits list
4.2.3 TMED Media type
4.2.3 TMOO Mood
4.2.1 TOAL Original album/movie/show title
4.2.5 TOFN Original filename
4.2.2 TOLY Original lyricist(s)/text writer(s)
4.2.2 TOPE Original artist(s)/performer(s)
4.2.4 TOWN File owner/licensee
4.2.2 TPE1 Lead performer(s)/Soloist(s)
4.2.2 TPE2 Band/orchestra/accompaniment
4.2.2 TPE3 Conductor/performer refinement
4.2.2 TPE4 Interpreted, remixed, or otherwise modified by
4.2.1 TPOS Part of a set
4.2.4 TPRO Produced notice
4.2.4 TPUB Publisher
4.2.1 TRCK Track number/Position in set
4.2.4 TRSN Internet radio station name
4.2.4 TRSO Internet radio station owner
4.2.5 TSOA Album sort order
4.2.5 TSOP Performer sort order
4.2.5 TSOT Title sort order
4.2.1 TSRC ISRC (international standard recording code)
4.2.5 TSSE Software/Hardware and settings used for encoding
4.2.1 TSST Set subtitle
4.2.2 TXXX User defined text information frame

4.1 UFID Unique file identifier
4.22 USER Terms of use
4.8 USLT Unsynchronised lyric/text transcription

4.3.1 WCOM Commercial information
4.3.1 WCOP Copyright/Legal information
4.3.1 WOAF Official audio file webpage
4.3.1 WOAR Official artist/performer webpage
4.3.1 WOAS Official audio source webpage
4.3.1 WORS Official Internet radio station homepage
4.3.1 WPAY Payment
4.3.1 WPUB Publishers official webpage
4.3.2 WXXX User defined URL link frame

From the same site:

From what I understand, it's not an exhaustive list. A complete application should support all possible fields (see foobar2000, Winamp plug-in, MP3Tag, etc...). An incomplete one could only support a few of them and still being complient with Vorbis format.
In your case, it would be better to request from one developer to implement a better tag reader than asking for a revised version of suggested fields.

I keep on reading that the ONLY taggins standard for FLAC is Ogg Vorbis, so I'm just trying to keep with standards, otherwise....I'll be stuck with tagged info that another program/database can't read.

Some software won't even exploit "standard" fields like LICENSE, LOCATION, VERSION... I guess it's more a kind of recommendation than a real "standard", but I may be wrong. Anyway, updating the list of "standard" field won't necessary change the way some software are working. The most complete ones don't care with official list and can handle personal fields, and the most uncomplete won't go beyond ARTIST-ALBUM-TITLE-TRACK-DATE-GENRE even if an official list contains much more possibilities.

That list of fields is not really a standard; it's just a recommendation.

I always say, feel free to come up with your own.

Thanks! Already posted on the MediaMonkey forums for them to support more tag fields.