W3C home > Mailing lists > Public > public-qt-comments@w3.org > June 2008

[Bug 5819] New: [XQuery 1.1] "may not be identical"

From: <bugzilla@wiggum.w3.org>
Date: Fri, 27 Jun 2008 21:13:36 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-5819-523@http.www.w3.org/Bugs/Public/>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=5819

           Summary: [XQuery 1.1] "may not be identical"
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 1.1
        AssignedTo: jonathan.robie@redhat.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


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".


-- 
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, 27 June 2008 21:14:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:52 GMT