- From: <bugzilla@wiggum.w3.org>
- Date: Sat, 16 Jul 2005 00:28:36 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1652
Summary: [FS] poor usage: "may not raise an error"
Product: XPath / XQuery / XSLT
Version: Last Call drafts
Platform: PC
OS/Version: Windows 2000
Status: NEW
Severity: normal
Priority: P2
Component: Formal Semantics
AssignedTo: simeon@us.ibm.com
ReportedBy: fred.zemke@oracle.com
QAContact: public-qt-comments@w3.org
3.3.4 Errors and optimization
Penultimate para, last sentence: "An implementation, however, may
not raise an error...". This could be construed "an implementation
is not permitted to raise an error...". Of course, this
interpretation contradicts the rest of the passage, but it would
be better to reword this, perhaps "an implementation may fail to
raise an error..." or "an implementation is permitted not to raise
ane error..." or even "an implementation may, however, not raise
an error".
See also my comment #1603 that the term "may" has not been defined.
If "may" is given its usual definition "permitted but not
required" then your use of "may" in this sentence is actually
correct, although it still reads poorly in ordinary English.
Received on Saturday, 16 July 2005 00:28:38 UTC