When the pressure is on, getting the messages flowing seems to be everyone's priority. XML Security is a huge and important side topic examining the problems associated with ensuring XML messages can move untampered between clearly identified and fully authorised agents. Data Quality is the next most important issue: does the message contain valid, timely, meaningful and eventually useful data? How can we implement a data quality architecture to support these concepts?

Looking at the use of XML on both individual projects and also from the perspective of enterprise architecture, the topic of data quality will be discussed from business importance through to practical guidelines. Technical content is medium complexity - aimed at senior project or technical decision makers and architects.

Topics include:

> Data integration and the importance of Data Quality

> XML's advantages in the data quality battle

> How and where to validate XML:

- in the schema

- in schema extension languages

- in external validation modules (XSLT, etc)

- in validation frameworks use within a system

- within business rules within a program

- post-receipt using data quality tools

The advantages and restrictions imposed by each are discussed.

> Mistakes and lessons learned, in reasonable detail

> Project sizing guidelines and rules of thumb

> Architectural recommendations for implementing dq initiatives

> Presenting the 10-point scale of validation quality

> Discussing the concept of the Data Quality Firewall

> Conclusions

We will also look into the minor and major impacts of all of this on other XML issues: schema design, tool selection, etc. Schema management, ownership and control are also issues that will have a harsh light shone upon them by the technical and business requirements for data quality.

We will also address alternative thoughts and approaches

- "We already do testing. Why is this different?"

- "We use ETL tools. Why should I use XML?"