XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
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] What does "optional" mean?


An XSD wrapper document to parameterize the validation: what would that look
like?

len

From: Michael Kay [mailto:mike@saxonica.com] 


I've seen people getting into a real mess by deciding that fields were 
mandatory because the data model says there must be a value, but the 
fact that there is a value doesn't mean the value has to appear in every 
message.

<snip />

One solution to that might be to allow an XSD wrapper document 
to supply the parameters, so when you name a schema document to use for 
validation, it has the parameter values already bound.

Michael Kay
Saxonica




[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