[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: XML spec and XSD
> > 2) Isn't it the case that some of the complexities of XSD > are that way > > to allow for that validation speed? > > > Do you have an example? (I imagine it causes some > simplifications as well as some complexities.) > Some of the restrictions are certainly there for that reason, like the subset of XPath permitted in identity constraints, the ban on backtracking (UPA etc), and the rules in conditional type assignment that restrict you to looking at attributes of the current element. I'm always suspicious of such rules: on the whole I think it's better to let users decide where to make the trade-off between performance and functionality; and I think writers of specifications are sometimes unimaginative when they consider implementation options. There's a classic in XSD, the rules for restriction of xs:all content models, where the spec explicitly says that a rule is there only for implementation convenience, and it actually causes my implementation a great deal of inconvenience to enforce it. As for streaming, I think we'll find in the fullness of time that a reasonably large subset of the assertions that people write (either in XSD 1.1 or in Schematron) can actually be evaluated in streaming mode. Regards, Michael Kay http://www.saxonica.com/ http://twitter.com/michaelhkay
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] |
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|