If anyone could show me a format that isn't based on a relational database,
and has a significatly lower byte count that the corresponding XML, I might be
swayed. If I was a CD-player developer, I would love for an extensible format
to arise, because I could use it to differentiate my player from the other
players.
> If you're going to go with XML, be prepared to offer precoded engines
> to everyone that they can just link in to their player code with a
> simple set of API's.
lib-dmi. Cool. (that's digital media index, for those who missed it)
> On second thought, that's not too bad of an idea. You could supply a
> reference library (for _everyone_, not just the unix-heads in the
> crowd) that used a standardized API and provided a precoded parser.
Well, for us unix-heads, there is a nice lib-xml. The GNOME project is using
it successfully.
As for driving away developers, we could offer our core service of XML via
HTTP for new, sexy clients. Requests that come in for the CDDB protocol could
be handled by an XML-CDDB parser. That would allow us to transition the CDDB
clients to the new service immediately.
Later,
-jwb