A schema is a set of rules that can be personal or standard. I started with a W3C Standard schema (DocBook 5.0) and got rid of all the stuff I didn't need. When it became manageable for me, I stopped and just used what was left. It then became the personal schema upon which I based Quantum Publications. This was an effective approach for me because of the relatively small scale of this web site.

Enterprise class professionals, obviously, have more sophisticated and immediate business requirements. A standard schema produces a starting point used to solve simple issues first. As more complex solutions present themselves, a customized schema can be re-generated to include new developments.

1. Validate the process in practice by testing appropriately for your needs.

2. Evaluate performance and only add more complexity when needed.

3. Then do it again.

Each revision refines the efficiency of your schema and the effectiveness of your process.

Fortunately, a standard schema comes with the logic and experience of some very helpful allies: