[Bug 8198] New: Eventing: A mechanism to relate the portType(s) of an event source Web Service to the abstract description of the events it can produce

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

           Summary: Eventing:  A mechanism to relate the portType(s) of an
                    event source Web Service to the abstract description of
                    the events it can produce
           Product: WS-Resource Access
           Version: FPWD
          Platform: PC
               URL: http://lists.w3.org/Archives/Public/public-ws-resource-
                    access-comments/2009Oct/0001.html
        OS/Version: All
            Status: NEW
          Keywords: externalComments
          Severity: normal
          Priority: P2
         Component: Eventing
        AssignedTo: public-ws-resource-access-notifications@w3.org
        ReportedBy: bob@freunds.com
         QAContact: public-ws-resource-access-notifications@w3.org


A mechanism to relate the portType(s) of an event source Web Service to the
abstract description of the events it can produce is needed. 
This mechanism cannot be solely based on WS-MetadataExchange, as this
information may be needed by clients at design time, before any service
endpoints are available. 
The draft replaces the previous mechanism for advertising events produced by a
source, based on a portType extension (using both the wse:EventSource attribute
and notification and solicit/response operations), by two new mechanisms, one
introducing a new language (Event Descriptions), the second one using a WSDL
definition for the sink. 
Both mechanisms provide an abstract description of the events, but no
mechanisms to relate them to the portType of the event source. Rather, it is
suggested to use new WS-Eventing dialects in conjunction with
WS-MetadataExchange to retrieve the descriptions at runtime.


-- 
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 Thursday, 5 November 2009 13:37:44 UTC