This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7986 - Eventing: supported notification policy
Summary: Eventing: supported notification policy
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: Eventing (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Doug Davis
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-20 19:00 UTC by Doug Davis
Modified: 2010-03-17 11:31 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2009-10-20 19:00:25 UTC 
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.

Proposal:

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:GetMetadata>
      <mex:Dialect URI="http://www.w3.org/ns/ws-policy"
         Identifier= "http://www.w3.org/2009/02/ws-evt/Notifications" />
   </mex:GetMetadata>

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

9.3 Notification Policy

An Event Source SHOULD advertise the features that are supported when sending
Notifications by making available a WS-Policy document containing the
policy assertions that a Subscriber MAY include in a Subscribe request.
This WS-Policy document SHOULD be made available through the use of
WS-MetadataExchange's GetMetadata operation by specifying a Dialect 
IRI of "../Policy" and an Identifier IRI of ".../ws-evt/Notifications".
Comment 1 Robert Freund 2009-12-02 17:38:50 UTC 
Connected possibly with 8031 any may be simultaneously resolved
Comment 2 Robert Freund 2010-01-26 19:21:14 UTC 
Consider under the "Mob of Angry Peasants"
Comment 4 Robert Freund 2010-01-27 23:34:21 UTC 
Resolved as proposed with the following text amending...

When present, this OPTIONAL parameter includes the Endpoint Subject Policy that the event source supports for sending notifications. This element MUST have one child element - typically a wsp:Policy element or a wsp:PolicyReference element. A subscriber can use this information to discover the valid set of Policy Alternatives that MAY be used within a wse:NotifyTo EPR which will be used for any Notification message sent from the event source to the event sink. Any policy alternatives included within this parameter SHOULD be compatible with those Policy Alternatives available of the Notification WSDLs that the event source advertises.