This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section 2.2 "Delivery" contains the following paragraph: "When the wse:NotifyTo element is used within the Delivery element it specifies the endpoint to which notifications are sent. For delivery to addressable endpoints this is sufficient. However, for non-addressable endpoints some additional mechanisms are needed. A subscription manager MAY choose to support mechanisms, such as the [WS-MakeConnection] specification, to enable delivery of notifications to non-addressable endpoints. See the [WS-MakeConnection] specification for more information, and an example, of how this would work." The "MAY choose to support" clause in the above means that the set of event source implementations that support non-addressable sinks will be fractured into those that support WS-MakeConnection and those that support some other polling mechanism. The has obvious impacts on interoperability. Proposal: rephrase the above to "When the wse:NotifyTo element is used within the Delivery element it specifies the endpoint to which notifications are sent. For delivery to addressable endpoints this is sufficient. However, for non-addressable endpoints some additional mechanisms are needed. Event sources and subscription managers that support non-addressable event sinks MUST support the [WS-MakeConnection] specification."