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 11667 - Eventing: the optionalities of the wrapped and unwrapped delivery formats are unclear
Summary: Eventing: the optionalities of the wrapped and unwrapped delivery formats ar...
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: LC
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: 2011-01-04 20:12 UTC by Gilbert Pilz
Modified: 2011-01-11 22:02 UTC (History)
1 user (show)

See Also:


Attachments

Description Gilbert Pilz 2011-01-04 20:12:18 UTC
I uncovered this one while working on the interop scenario for WS-Eventing. The spec defines two delivery formats, wrapped and unwrapped, and allows for the extensible definition of other formats. However, nothing in the spec says whether or not an Event Source or an Event Sink MAY/SHOULD/MUST implement either of these delivery formats. This creates a potential interop problem if a number of implementations support unwrapped but not wrapped and another set of implementations supports wrapped but not unwrapped (there is also a hole in which an impl may not choose to support either format - nothing in the spec says it has to - and instead only supports its own extension format).
Comment 1 Robert Freund 2011-01-04 20:49:28 UTC
2011-01-04 Agreed that event sources support both wrapped and unwrapped
Comment 2 Robert Freund 2011-01-04 20:53:29 UTC
Add the following sentence to the end of the 2nd paragraph of Section 2.3: Conformant Event Source implementations MUST support both wrapped and unwrapped notifications.