This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
One of the XML Query WG members is concerned about the default revalidation mode. I'll copy, in part, this person's comment: XQuery Update specifies that the default revalidation mode is "strict". Although this is implementation defined, I have two observations to make: 1) This has confused quite a few users who don't understand why they are getting revalidation errors about not being able to find a schema element. 2) The XQuery Update Test Suite doesn't pass without a default revalidation mode of "lax". Given that the experience we have with writing update queries suggests that "strict" is an unhelpful default value for revalidation mode, do we want to change the default mode to "lax"?
The XML Query WG considered your comment and agree to change the default revalidation mode to LAX. We note that the revalidation mode can be overwritten by an implementation and explicitly set by a user in the prolog. This allows us to choose either LAX, STRICT, or implementation-defined as the default value without greatly inconveniencing existing implementations. We felt that update operations on untyped data model instances should not, by default, raise an error, and so we have changed the default value to LAX.