- From: <bugzilla@jessica.w3.org>
- Date: Fri, 30 Sep 2011 08:11:51 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13674 --- Comment #9 from Michael Kay <mike@saxonica.com> 2011-09-30 08:11:51 UTC --- (In reply to comment #8) > With Mike's text in place, is it therefore a static error if these conditions > are not met? No, the intro to section 2.2.5 explains it: In order for XQuery 3.0 to be well defined, the input XDM instance, the static context, and the dynamic context must be mutually consistent. The consistency constraints listed below are prerequisites for correct functioning of an XQuery 3.0 implementation. Enforcement of these consistency constraints is beyond the scope of this specification. This specification does not define the result of a query under any condition in which one or more of these constraints is not satisfied. In other words, if the consistency constraints aren't satisfied, anything might happen. In practice I think you have several options: (a) design your product so inconsistencies can't happen, (b) detect the inconsistencies and report them nicely as static (or perhaps link-time) errors, (c) tell the user it's their job to get it right, and if they don't, you're not answerable for the consequences, (d) ensure that your product can give some kind of reasonable result even if inconsistencies are present (e.g. by merging substitution groups at query link time, and avoiding pessimistic static type checking). -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 30 September 2011 08:12:00 UTC