[Bug 8288] New: requirements on Notification Bindings for EventDescriptions too lax

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8288

           Summary: requirements on Notification Bindings for
                    EventDescriptions too lax
           Product: WS-Resource Access
           Version: PR
          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


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


-- 
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 Friday, 13 November 2009 21:57:35 UTC