This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section A.1.2 "Bindings for EventDescriptions" contains the following paragraph: "For any Notification Format it SHOULD be possible to determine how a given wse:eventType will appear on the wire as a notification in a subscription created with that format. The following sections define how wse:eventTypes bind to notifications for the two Notification Formats defined in this specification; Unwrapped and Wrapped. Specifications or profiles that define additional Notification Formats SHOULD define how wse:eventTypes bind to the notifications for those formats. In the absence of a mapping for a particular Notification Format, implementations MAY provide a Notification WSDL (see below) that explicitly describes the notification operations." This allows for the possibility of Notification Formats for which there is no well defined mapping from a wse:eventType to the on-the-wire notification. This completely undoes the entire purpose of EventDescriptions, which is to enable the event sink to determine how notifications will appear. Proposal: s/SHOULD/MUST/ in the above paragraph
applies to both SHOULDs s/SHOULD/MUST/g
resolved as proposed as amended by comment #1