This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The phrase "may not" is generally ambiguous. In the draft XQuery 1.1 document that is about to be published the phrase appears as: but these values may not be identical I think that in this case it means "might not" rather than "must not", but it takes a fairly careful reading to realise this. We also have the following, where (I think) in each case the intended reading is "must not": * Such a schema import may not bind a namespace prefix * however, the prefix xml may not be redeclared * The PITarget of a processing instruction may not consist of the characters "XML" * a processing instruction may not contain the string "?>" * The DirCommentContents of a comment may not contain two consecutive hyphens It is always possible and desirable to replace "may not" with either "might not" or "must not".
This has been fixed in the current internal editorial draft. (This draft also introduced one new instance of "may not", which now been fixed in my internal copy.)