Cart
[Home] [By Thread] [By Date] [Recent Entries]
> Schemas are only useful in some situations: many XML applications > built today already have data validation in them (in code). You've just pointed out an important reason to use schemas -- to minimize ad hoc validation by application code. Consider a scenario where you have multiple applications operating on a single document type. If there is a schema for that document, and all applications use the schema, there is uniform application of rules. Validation is consistent (at least for rules that are definable by a schema). On the other hand, if you do application-level validation, the logic must be duplicated across n programs. This presents a versioning problem. When there is a rule change, you must do n updates to source code, instead of updating a single schema. *************************************************************************** This is xml-dev, the mailing list for XML developers. To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev List archives are available at http://xml.org/archives/xml-dev/ ***************************************************************************
|
