In spite of its many benefits, Extensible Markup Language (XML) still has a variety of problems that can either slow down an integration project, or worse, cause the integration project to collapse. Although XML is meant to be a flexible, easy to use, and fully portable solution for Web applications and integration projects, it is not the cure all that many believe it to be. Preventing the use of poorly written XML is more complicated than most developers realize. The key to successfully using XML in an integration project is to first understand the inefficiencies that may cause poorly written XML, then apply a rule-based system that establishes policies that can be adhered to. This article will outline the many drawbacks of XML, and will address how a rule-based system can prevent the use of poorly written XML in integration projects.