Pet Peeves - XML

By Sean McGrath  1 comment

We are teetering on the brink of a new edition of the XML standard: XML 1.0 5th Edition to be precise. This seems like an appropriate moment to look back at the XML roller-coaster and list off some personal peeves.

- My first peeve is the "L". "L" as in "Language". If I had a dollar for every time I have tried to explain that XML is not a language in the sense that most people understand the word, I would personally be able to fund the Emergency Ecomonic Stabilization Act of 2008.

Yes, I know that meta-languages are perfectly good languages with their own notations and syntax and all that good stuff but from the perspective of most senior C-level executives and IT managers, that is too close to intellectual self-gratification for comfort.

- My second peeve is the "X". "X" as in "Extensible". If I had a dollar for every time I have tried to explain that XML is not an extensible in the sense that most people understand the word, I would have a balance sheet to rival Berkshire Hathaway. The language itself is not extensible without considerable pain (see peeve 4). What you can do very easily, is create a language with it. The language you create is not an extension of XML in the same way that a Visual Basic program is not an extension of Visual Basic.

- My third peeve is that the world never decided that round-tripping XML was sufficiently important to make it very easy. I write lots of software that eats XML and spits XML out. I am very interested in the relationship between the XML I eat and the XML I spit. I need it to be really easy to write a "null" program that eats some XML and spits out the same XML - without changing it. To do that, I need to know what "the same" means in the XML world. We have a definition of that but... well...read it and decide for yourself.

- My fourth peeve relates to versioning and citation. I work a lot with legal and regulatory material and my antennae for citation problems are, perhaps, unusually sensitive. We started with XML 1.0. Okay, fine. There were some errata. That is only to be expected. Now we have "editions" of XML 1.0. Okay. Fine. Then along came XML 1.1. Not so fine. Much angst and debate.

XML 1.1 is/was, effectively ignored in many circles. Now we have XML 1.0 fifth edition which includes a revisitation of the same swampy grasslands as XML 1.1.

I know from plenty of personal experience that naming things is a real hard problem but it is terribly irksom that XML - which is all about naming things - appears to have deep problems naming itself.

1 comment

    Anonymous 3 years ago
    I need to start creating and using XML documents for a project. After reading this article I think I need sedation or some sort of medicine to help me through the coming quagmire.

      Add a comment

      Post a comment using one of these accounts
      Or join now
      At least 6 characters

      Note: Comment will appear soon after you have activated your account.
      Obscene/spam comments will be removed and accounts suspended.
      The information you submit is subject to our Privacy Policy and Terms of Service.

      ITworld LIVE

      SoftwareWhite Papers & Webcasts

      White Paper

      Best Practices Guide: Microsoft Exchange 2010 on VMware

      This guide provides best practice guidelines for deploying Exchange Server 2010 on vSphere.

      White Paper

      Free Trial: vRanger, the Powerful VMware Recovery Solution

      When disaster strikes, don't waste hours and dollars recovering critical data. vRanger delivers blazing-fast speed and granular recovery for your VMware applications and data. Get your free trial today.

      White Paper

      Executive Guide to Business and Software Requirements

      This paper is designed as an executive briefing on the issues surrounding business and software requirements. It features a wealth of statistics and tactics to help you get requirements right, and includes a tear-out single page summary.

      White Paper

      How to Launch a Successful IT Automation Initiative

      Corporations across all industries are under increasing pressure to cut costs and work more efficiently. In the race to meet both of these requirements, many organizations turn to technology, often purchasing and installing disparate pieces of software in hopes of achieving efficiencies not afforded by manual systems.

      White Paper

      Why Corporations Need to Automate IT Systems Management

      With corporate budgets being slashed and leaders expecting more out of their employees, companies are forced to do more with less, yet are still expected to provide the highest quality experience to customers. This is pushing them to make better use of their IT assets without breaking the budget. Companies are under more pressure than ever, thanks to data management regulations; increasingly complex security threats; and growing demand from management and end users for 24/7 uptime and high performance. These hurdles require a strategic investment in technologies that boost efficiency, save money and position IT as an integral part of the entire firm's operations. IT systems management is helping corporations fill these gaps.

      See more White Papers | Webcasts

      Ask a question

      Ask a Question