The "Perl end" of XML

grantm on 2007-07-26T08:21:15

In theory XML allows two parties to agree on an unambiguous definition of a format for data exchange. Low level rules define what is and what is not XML. Optional layers on top of that define some sort of schema for the elements in the XML document and once again it is relatively easy to take an XML document and confirm whether or not it complies with the agreed schema.

In practise things are quite different to theory.

In my experience, there's always politics. There's always one party which is either unwilling or unable to comply with the rules or in extreme cases even acknowledge that rules exist. The other party inevitably has to bend over and take it. This has led me to postulate the following 'law':

Where XML data must be exchanged between two parties, the party at the "Perl end" of the pipe will inevitably have to adapt to whatever non-compliant tag-soup gunk the other party emits or expects.


I've never had this problem

Alias on 2007-07-27T01:33:09

I may have gotten lucky then, because in all the cases where I've implemented an XML transport, I've been able to have an XML schema, and both parties have agreed to enforce those XML Schemas from day 1.

Of course, this just moves the politics out of the XML and into the schema definition process.

But this is already a source of politics, and it means that the movement of functionality from concept to implementation is somewhat controlled.

Truth

Lecar_red on 2007-08-03T15:15:50

I laughed so hard when I read this. I couldn't agree more since I have been at the end of the pipe waving the Perl wand to clean up the XML tag mess.