This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1652 - [FS] poor usage: "may not raise an error"
Summary: [FS] poor usage: "may not raise an error"
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Formal Semantics 1.0 (show other bugs)
Version: Last Call drafts
Hardware: PC Windows 2000
: P2 minor
Target Milestone: ---
Assignee: Jerome Simeon
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-16 00:28 UTC by Fred Zemke
Modified: 2007-01-16 17:31 UTC (History)
0 users

See Also:


Attachments

Description Fred Zemke 2005-07-16 00:28:36 UTC
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.
Comment 1 Jerome Simeon 2005-07-19 17:24:10 UTC
I believe this is editorial.
- Jerome
Comment 2 Jerome Simeon 2006-04-11 22:52:45 UTC
Taken over by events. The corresponding material about error handling has been removed in the CR draft.
- Jerome