[ID3 Dev] 'Extending' ID3 V2.4

Ion Todirel iontodirel at yahoo.co.uk
Sat Feb 11 12:14:33 PST 2006


.....
   
  <Song ... Encoding="UTF-8" ... >
      <Name>...</Name>
  </Song>
   
  What i wont to say is that we can use encoding, different with the entire xml encoding to atribute level. We put the standard Unicode, for XML document, but some atributes we can interpret as ASCII or other encoding.

Robert Manson <rmanson at gracenote.com> wrote:
  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.

Some things I would like to see in a new ID3 version:

1. Tags at the end of the file, perhaps directly above an IDv1 tag
2. No binary data, thus avoiding the need for an unsyncronization
scheme
3. One UTF* text encoding format, perhaps one that does not require
unsyncronization, UTF-7?
4. Simple key-value pairing whereby ID3 recognizes a set of standard
keys but allows room for custom keys (ie TXXX).

-Rob


-----Original Message-----
From: Paul Grebenc [mailto:jid3 at blinkenlights.org] 
Sent: Friday, February 10, 2006 3:24 PM
To: id3v2 at id3.org
Subject: Re: [ID3 Dev] 'Extending' ID3 V2.4


>- This would require implementers to include an XML parsing engine.
...

>- XML is hierarchical rather than linear. All tagging formats that ...

This is not entirely true. Granted, an XML document is hierarchical,
and 
you can load it into a DOM and pull what you need from it, but you can 
also read it sequentially, in the same manner in which a V2 tag is read.

This would leave it up to the implementation whether it wants to load a 
DOM or not. In fact, a legitimate XML parsing engine would not even be 
necessary, so long as tag names were recognizable, and the content
within 
them was known.

As far as reading, an XML document has the potential to be as easy to
read 
as an ID3 v2 tag. What XML would offer is the possibility to use a full

parser with DOM in tag editing applications. With a formal schema,
there 
would be no need for a 'reference implementation'. If your document 
validates against the public schema for that version, it is valid. If
it 
doesn't, it is not.

Paul

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




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



		
---------------------------------
Yahoo! Photos – NEW, now offering a quality print service from just 8p a photo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.id3.org/pipermail/id3v2/attachments/20060211/244cba2e/attachment.html>


More information about the ID3v2 mailing list