Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


RE: [xml-dev] dynamically generated XML Schema?! Re: [xml-dev] R: [xml-dev] Number of active public XML schemas

From: "Michael Kay" <michael.h.kay@--------.--->
To: "'TAN Kuan Hui'" <kuanhui@---------.--->,"'Burak Emir'" <Burak.Emir@----.-->,"'Chizzolini Stefano'" <chist@---.-->
Date: 11/4/2004 9:56:00 AM
> Shouldn't it be the case that the validation process necessitates
> a 2-stage parsing ? What I mean is that XSD can only do a lexical
> validation, a second follow-up stage that validates against the
> application semantics is required.

That's actually four levels already: unicode encoding, XML well-formedness,
schema validity, and application validity. And yes, you often need multiple
levels.

But that doesn't stop you wanting individual levels to be configurable. A
very simple example, when I validate new documents I want to check that the
date is today. That kind of thing is very easily achieved by a configurable
schema. Equally, the application-level validation is often done using XSLT
stylesheets, and people often transform stylesheets for the same reason: you
need things to be configurable at that level too.

Michael Kay


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent