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 6916 - Event and Enum: change MAY generate to MUST generate
Summary: Event and Enum: change MAY generate to MUST generate
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: All (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-18 19:56 UTC by Doug Davis
Modified: 2015-06-20 16:35 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2009-05-18 19:56:20 UTC 
In Eventing and Enum there are several places where it talks about the
request message failing and how the service MAY then generate a certain
type of fault.
To increase interop, these MAYs should be MUSTs.  A service is always
free to transmit the fault, but if it does transmit a fault we need to
ensure that everyone agrees on which fault it is.
Comment 1 Doug Davis 2009-05-18 19:56:46 UTC 
Proposal:
s/MAY generate/MUST generate/g
Comment 2 Robert Freund 2009-05-26 20:51:29 UTC 
discussed on 2009-05-26, folks requested 1 more week
Comment 4 Robert Freund 2009-06-03 06:00:43 UTC 
2009-06-02 resolved with comment #3
Comment 5 Jackie 2015-06-20 16:34:29 UTC 
Please make my changes
Comment 6 Jackie 2015-06-20 16:35:18 UTC 
Please make my changes