- From: <bugzilla@jessica.w3.org>
- Date: Tue, 04 Jan 2011 20:12:19 +0000
- To: public-ws-resource-access-notifications@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11667
Summary: Eventing: the optionalities of the wrapped and
unwrapped delivery formats are unclear
Product: WS-Resource Access
Version: LC
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Eventing
AssignedTo: public-ws-resource-access-notifications@w3.org
ReportedBy: gilbert.pilz@oracle.com
QAContact: public-ws-resource-access-notifications@w3.org
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).
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
Received on Tuesday, 4 January 2011 20:15:29 UTC