>XMl is inherently not difficult to change -- personally I do not see
the need to take care of lyrics right this second.
DTDs can be extended easily (i.e. by adding containers and attributes
that weren't there before) but changing something that's already laid
down is Bad.
>> As it is, I'm happy to take what's in this DTD and write an API
around
>> it for submission and fetching. The lower levels of the API, for
>> parsing SCSI TOCs and launching web browsers (in case the CD player
>> doesn't want to present the UI) can be worked out later.
>
>I met with Marc in Cologe few days agao and he is also interested
>in writing this API. I remember last time you guys deadlocked
>on a few issues that were never resolved. I would very much
>like to see all of us work together to come up with an API
>that meets everyones needs.
That would be swell.
I can do a first pass and post it for discussion... this weekend, once
I've settled down for all the insane job hunting I'm doing. Next week,
I'm on a contract in the states but am unsure how much e-mail I'll be
picking up.
>I would like to offer my services as a moderator to settle any
differences
>that arise. I would prefer this over the standard 'the first person
with
>code wins' attitude. I think this will serve the community best.
No problem, sounds like a good idea.
/Steve