Guiding Principles

1. Schemas and data have a mutual obligation to the simplest structure possible, achievable by continual reassessment of the two by their creators and rigorous justification for every modification.
2. Efficient XML development produces the necessary functionality and benefits with the minimum investment.
3. Design of a data model focuses on all stakeholders' requirements for the data.
4. Requirements are prioritized to guide design and development and address known issues and requirements, not hypothetical possibilities.
5. Effective sampling and analysis upfront reduces risk and improves implementation schedules.
6. Designs or components are not reinvented, but rather are leveraged where possible.
7. Consistency and clarity of practices remove ambiguity and enable designs, applications, and data to be leveraged to reduce investment.
8. Manageable iterative releases done over time focus on most important benefits first.
9. Documentation of design and components is always done but must be simple yet efficient and feasible to produce and maintain.
10. A clearly articulated methodology improves developers understanding and participation, accelerates development and reduces risk.