As software developers, we grew tired of dealing with configuration files. We would often find that the addition of a new configuration option meant that we needed to modify source code, man pages, example configuration files, etc. We decided it would be nice to maintain a single XML document which described the configurable values and then use various translators to generate the necessary files.

While using XML to describe a application's configuration has many benefits, it makes setting up a software development environment more difficult. However, we (the "we" being Paul and Bill) are convinced that the extra headaches in preparing the development system will be worth the benefit of having a single XML file that the developer needs to maintain. As an added bonus, the slow speed of processing XML files will give you plenty of time to appreciate all of these new found benefits.

In making the assumption that the xml-keyval package will only the first of many XML based packages, Paul decided it was worth the extra effort to create a "common" set of shared files which will be useful in the creation of the xml-keyval, package, but will also be useful as more XML based packages are designed.

So, we've stuck you, the developer, with the chore of installing extra packages in order to make use of this stategic new technology that will carry us to a new paradigm (sorry, I've been reading too many Dilbert cartoons).

Be forwarned, there is a steep learning curve to making use of XML and this document goes over the issues encountered by a amatuer to the XML world. If you are not well versed in XML, you should find yourself a real book to gain some background to the XML world before diving into the development process.