Tuesday, June 03, 2008

XML: How to get the benefits without the heartache, part 1

    "For many applications of XML you will come across, there appears to be a better, more optimal non-XML based solution possible. For any given data representation requirement you as an application developer/designer might have, there is a "better" syntax than XML for representing it. XML is sub-optimal for everything, or so it sometimes seems." -- XML: How to get the benefits without the heartache, part 1

6 comments:

swheatley said...

Good article, Sean. Being a Python fan but not having done much with XML (and seeing this article on the UPP feed) how much XML work do you currently do with Python, if any?

Sean said...

swheatley,
Most of my XML work is done with Python/Jython.
Sean

swheatley said...

Is there a more up-to-date overview of Python XML capabilities? I picked up the Python & XML book from O'Reilly, but it hasn't been updated in 7 years. The Python XML SIG reference page has links to software, most of which hasn't been updated in 6-8 years. I'm not sure how much has changed in the interim, and was hoping as a heavy user maybe you could point me to some more current resources.

Gary Godfrey said...

Just curious - would you use Relax NG if you were starting a new project right now? The 2001/2003 dates that I see on the pages make it look like an orphan and that put me off.

Sean said...

Gary,

Yes I would but that statement needs to be interpreted w.r.t. my "dochead"/RESTian biass. If I primarily developed data-oriented apps (e.g. relational database stuff) or SOAPy Web Services I probably would use XSD.

Ali Umar said...

very Good