Chapter 5. XML Enabling the Enterprise

One of my favorite Monty Python sketches of all times is the so-called “Architect Sketch.” In this sketch John Cleese plays an architect who “hadn't fully divined” his client's attitude toward their tenants. Whereas his clients wanted a simple block of flats, he had designed a state-of-the-art abattoir. And although they were very appreciative of his wonderful slaughterhouse design, it didn't do them a bit of good in solving their actual problem, which was housing tenants.

As with any other technology, it is possible to grossly misuse XML if you don't have a solid understanding of its strengths and limitations. By studying the various ways to use XML within a large company, you can prevent misunderstandings like the one above from ever happening.

Few technologies can be applied to such a wide variety of problems as XML can. One of the most unusual aspects of the XML phenomenon is how well it is suited to both programming and documentation applications. The same XML editor could be used to view a company's annual report and verify an XML message stream between two servers.

There are so many compelling applications of XML that it is easy to lose focus on where it can provide the most value with the least effort. No system lives in a vacuum, and it is impossible to adopt XML in one place without impacting systems and users in another.

Deciding where and when to implement XML support within an organization requires a thorough knowledge of how XML can be applied to various business problems. Data storage, content publishing, and transmission are three major areas that can immediately benefit from XML solutions.