This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
3.3.1 Kinds of Errors "a static error (denoted by statError)" There's no need to introduce the symbol statError; it's never used. "Non-type static errors" If 'static error' and 'type error' are distinct, then the "Non-type" is unnecessary. "The [Functions and Operators] and [XQuery 1.0: A Query Language for XML] documents raise specific error conditions, but because these error conditions can be implemented in any way, we do not formalize them here." That doesn't sound very convincing. I mean, an XQuery processor can be "implemented in any way", but that doesn't stop you formalizing it. It seems plausible that you could write Dynamic Error rules that that raise specific errors, without over-constraining implementations. (E.g., 4.1.5 / DErr / rule 2 could raise err:XPTY0004 instead of just typeError.) I'm not saying you should do it, just that if you don't do it, you should have a better rationale.
Section 3.3.1 has been removed entirely. Section 3.3 refers to XQuery, F&O, and XPath documents for normative definitions of error conditions.