This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Current WS-Eventing defines the concept of Event Source, but does not specify how to address it in the Subscribe message. The sample Subscribe messages suggest that WS-Addressing [destination] EPR is used to address the Event Source, but this mechanism is not mandated. It is also not clear how to address individual event sources, such as a port type or dynamic event sources, in the Subscribe request. We propose to mandate using WS-Addressing [destination] EPR to address any event sources. For example, a port type event source is addressed in SOAP as: <s12:Header> <wsa:To>http://www.example.org/oceanwatch/EventSource</wsa:To> <wsdl:portType wsa:IsReferenceParameter='true' name='eventPortType' /> </s12:Header> A CSTA monitor is addressed as: <s12:Header> <wsa:To>http://www.example.org/csta/CallControl</wsa:To> <csta:MonitorCrossRefID wsa:IsReferenceParameter='true'> 12345 </csta:MonitorCrossRefID> </s12:Header>
2009-01-15: action to Li assigned for a before/after text
Proposal from http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Feb/0024.html see http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Feb/att-0024/wse_6425_2.pdf
Discussion points in http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Feb/att-0112/00-part
Resolved 2009-03-10 with "All messages defined by this specification are sent to a Web service that is addressable by an EPR [WS-Addressing 1.0 Core]" to be added at an appropriate place, this change to be extended to all of the specs.
in specs
on 2009-03-12 The editor asked if there was an inadvertent lack of normative language It as suggested to change "are sent" to "MUST be sent" members agreed