|
[XQuery Talk Mailing List Archive Home] [By Date] [By Thread] [By Subject] [By Author] [Recent Entries] [Reply To This Message] How to copy in-scope namespace bindingsMartin Probst mail at martin-probst.comTue Dec 15 19:00:10 PST 2009
> specification explicitly doesn't say that a conforming implementation must > reject any construct that isn't defined in (or "supported by") the spec: and > as far as I have been able to determine, that is a deliberate omission. The > cultural background of XQuery is in the database world, where vendors > routinely expect to implement their own enhancements to standards and users > typically don't complain. That is a tough decision in my opinion. For example, the standard mandates that "5div 3" must be treated as an error, at least that's the way I read it. Our parser actually contains several special case statements that check for such conditions - normally, we'd be able to properly parse that (and I don't quite understand why it should be a problem), but we need special logic to prevent that. The same thing applies to casting strings to QNames at run time, and other similar things. I'm actually thinking about implementing a more rigid standards compliancy mode that enforces these things, and a more lenient mode. Preventing things like the run time case to QName is quite a pain for users, and it's entirely gratuitous in my opinion. Regards, Martin
|
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
|






