Cart
[Home] [By Thread] [By Date] [Recent Entries]
> Even in a case like that, somewhere you or software would have to decide
> what to do in case there were more records than the form could hold. That
> cannot be done with the information in the schema anyway. So why bother
> putting the constraint into the schema in the first case? It doesn't really
> solve the problem it is there to handle.
I am in awe of the hubris of folks who can make such generalizations.
"Trust me, if you try to strictly define your data, then your software
will [expletive deleted]."
Wow.
Perhaps folks really mean "this is the final straw, making XSD so
complex that as validation-implementors we cannot stand for it."
But that is not what they've been saying.
/r$
--
Rich Salz Chief Security Architect
DataPower Technology http://www.datapower.com
XS40 XML Security Gateway http://www.datapower.com/products/xs40.html
XML Security Overview http://www.datapower.com/xmldev/xmlsecurity.html
|
