This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Issue: When Qnames are used for delivery mode extension, there is a critical need for the event source to specify and publish the supported delivery mode Qname expressions for the subscriber to negotiate with its own capabilities and compose an event subscription message to reach an agreement with the event source. Moreover, when optional event delivery behaviors are involved in the negotiation, there is a need for the event source to inform the event subscriber exactly which options will be used for the event subscriber to prepare the matching event sink. Proposal: We propose to use delivery policy to decorate the delivery mode extensions in the WSDL and using the policy negotiation based on WS-Policy for delivery extension negotiation. Moreover, we propose to include the exact delivery extension in the form of delivery policy as part of the positive response message to the event subscribe for subscriber to prepare the matching event sink. Detailed description is provided in (Section B.3, B.4) http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Jul/0050.html.
2009-08-05 directional decision: we put in the appropriate place (where we talk about extensions - 3.2) "extension authors are delegated the task of extending response message to indicate the understanding of and acceptance of the extension in the request" action on Gilbert Pilz to write detailed text proposal
proposal at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/0034.html
proposed re-wording at http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Aug/0036.html
comment #3 accepted, resolved
resolved also that this extend to all of the specs
Please make my changes