OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] reasons why an XML instance must be validated with a XML schema

> why should we use XML schema to validate XML?

I'm interested to know how people decide what is a sufficient level of
checking in the schema, compared to the application...

Do you do as much as possible in the schema, which could be a lot in
1.1?  Where do you draw the line?

Do you do still write your application as though the XML isn't
validated, or do you rely on it?

For example, a startDate and endDate - do you check that the endDate
>= startDate in the schema, in the application or both?  Would you
bother with a decent error message "the end date must not be before
the start date" when that code is effectively unreachable if the XML
has been validated...?

If you are doing the check in the application, then do you still do
the check in the schema - making it more complex and slower?  A custom
application exception is a lot nicer than validation failure
message...  :)

However what's the point in partially processing XML, letting it get
to the application, when you could know that it would fail from the
validation level...

you get the idea :)

Andrew Welch
Kernow: http://kernowforsaxon.sf.net/

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS