[ID3 Dev] 'Extending' ID3 V2.4

[Paul Grebenc]

>Another "problem" with XML is that it is so flexible when it comes to
>the text encoding of the actual document.  Having to support so many
>text encodings can be a big problem, especially in the embedded space.

The specification could dictate that the tag has to use UTF-8.  Or, it 
would be just as easy to not dictate that and let anyone use their 
preference.  As it stands, ID3v2 supports Unicode, but I doubt there are 
very many embedded devices that will correctly display anything outside 
the standard ASCII character set.  There are probably enough desktop 
applications that support ID3v2 that won't do the right thing with 
Unicode, as it is.

I don't want to argue this point forever.  I just want to express three 
opinions:

1. Parsing XML without a full-blown parser/DOM support does not have to be 
hard.

2. A new version should target the embedded devices that will be designed 
a few years from now as the minimum embedded platform.  Existing devices 
aren't going to retroactively support any new version, regardless of how 
simple it is, so there's no value in wondering whether a three year old 
32MB keychain player can 'handle it'.

3. XML has some disadvantages, but the one enormous advantage it has, 
considering that half the traffic on this list is moaning about bad ID3v2 
implementations, is the ability it provides to universally enforce 
validation.

Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org