|
If you face the prospect of exchanging 600,000 XML documents (or more) per year in as many as eight languages, normalization begins to look like a reasonable prophylactic (among others). When you enter into about 250,000 dialogs per year with customers, sending revisions of highly complex technical documents back and forth, even if it's always in English, normalization may help reduce the overall risk of change management. Building an effective and reliable search system of about 7,000,000 XML documents also adds some appeal to the idea of normalization. Even though we both generate and consume a large portion of this volume, a significant portion are not under our control, and, in the end, all of them are made available to value-added resellers; if only as good citizens of the information age, perhaps we should normalize everything that passes through our hands. |