Cart
[Home] [By Thread] [By Date] [Recent Entries]
[Jeff Lowery] > Inelegant as appinfo cardinality annotations may be, I have suggested three > alternatives, none of which are being accepted with open arms: > > 1) add a constraint to the data model that requires children to be ordered. > (I have sympathy for those who wish not to enforce artificial constraints on > their data model.) > 2) Use RELAX-NG + XSD datatypes. (Politically incorrect.) > 3) Fix the cardinality definitions in the XSD schema and use an XSLT > transform to order children prior to validation. (Seems simplest, but > what's the performance hit for a large document? Maybe Tom Passin can answer > that one.). > Aha, payback time, eh, Jeff? The smallest performance hit would be to use an xslt stylesheet to reorder the __schema__, not the data (after all, they want to allow any order, right?)! Cheers, Tom P
|
