11667 2011-01-04 20:12:18 +0000 Eventing: the optionalities of the wrapped and unwrapped delivery formats are unclear 2011-01-11 22:02:20 +0000 1 1 1 Unclassified WS-Resource Access Eventing LC All All CLOSED REMIND P2 normal --- 1 gilbert.pilz public-ws-resource-access-notifications dug public-ws-resource-access-notifications oldest_to_newest 43811 0 gilbert.pilz 2011-01-04 20:12:18 +0000 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). 43812 1 bob 2011-01-04 20:49:28 +0000 2011-01-04 Agreed that event sources support both wrapped and unwrapped 43813 2 bob 2011-01-04 20:53:29 +0000 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.