Monday 31 March 2008

When did XML become a good Idea?

It is so easy to list what is wrong with XML for EDI (Electronic Data Interchange).

  • It produces large files
  • It is very processor intensive to parse
  • Needs another new standard
  • Or can be used/abused without a standard
  • It isn't even very human readable (despite what some say)
And yet... a lot of people find it very compelling.

To understand why, imagine you are talking to a developer who knows nothing about EDI. Show them an EbizXML file, an EDIFACT file, a Tradacom file and a X12 file. All for the same document. The chances are they will immediately be able to tell you the first file is XML as they know what that is. They will probably even be able to begin to translate its contents.

Explain to this developer you want a subroutine / function / method, to extract and return certain elements from the document. They will not blink as they reach to the keyboard and fire up their perfered language tools. They will have a first draft ready in less time than it will take to explain the mere structure of any of the other files.

Any non-developer who has just read this is now scatching their head wondering why file structures would have to be explained. They are also wondering why the problems listed at the beginning are... problems?