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

[Bug 7986] New: Eventing: supported notification policy

From: <bugzilla@wiggum.w3.org>
Date: Tue, 20 Oct 2009 19:00:25 +0000
To: public-ws-resource-access-notifications@w3.org
Message-ID: <bug-7986-2780@http.www.w3.org/Bugs/Public/>

           Summary: Eventing: supported notification policy
           Product: WS-Resource Access
           Version: FPWD
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Eventing
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: dug@us.ibm.com
         QAContact: public-ws-resource-access-notifications@w3.org

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.


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().

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".

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, 20 October 2009 19:00:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:06:36 UTC