W3C home > Mailing lists > Public > public-ws-resource-access@w3.org > November 2009

RE: [Bug 7986] New: Eventing: supported notification policy

From: Li, Li (Li) <lli5@avaya.com>
Date: Thu, 5 Nov 2009 11:32:31 -0500
Message-ID: <7DC6C0F0E8D7C74FB4E1E73CC371280A01345A6A@300813ANEX2.global.avaya.com>
To: <public-ws-resource-access@w3.org>
Cc: "Chou, Wu (Wu)" <wuchou@avaya.com>
Hi Doug,

I'd like to get some clarification on this issue [1]. You stated two

1) Right now there doesn't appear to be a way for an event source
to advertise how it can send Notifications.  By this I mean,
how does a Subscribe know what policy assertions it can put into
the NotifyTo EPR?  The QoS for the Event Source ops, meaning the
Subscribe operations, could be very different from the QoS that's
supported when it comes to sending Notifications.

2) Add to ws-eventing (new section 9.3) the notion of using MEX to
retrieve the
Notification Policy.  So sending a mex.GetMetadata like this:

      <mex:Dialect URI="http://www.w3.org/ns/ws-policy"
         Identifier= "http://www.w3.org/2009/02/ws-evt/Notifications" />

will return the Policy assertion that the Subscriber can use during
a Subscribe().

For point 1), if I understood correctly, an event source can attach
policy assertions to the notification WSDL specified in A.2 of WS-E. 

For point 2), if I understood correctly, a subscriber can use MEX to
retrieve this notification WSDL and obtain the policy in it as specified
in A.2.1 of WS-E. 

Could you clarify what is the relation of this new proposed mechanism
and those available in A.2? 



[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=7986

Received on Thursday, 5 November 2009 16:33:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:34:53 UTC