Extension Handling 101: Example 5

It turns out that the authors of the "pauseable Subscription" extension 
outlined in Example 3 are nothing if not thorough. To allow 
implementations that support their extension to advertise this fact to 
potential Subscribers they have created the devm:Pauseable policy 
assertion. devm:Pauseable has the following attributes:

    * Its presence indicates support for the pauseable Subscription
      extension; Subscribers MAY include the dev:Pauseable extension in
      their Subscribe requests with the expectation that the Event
      Source will process it according the specification at
      http://www.smalldevices.org/evt-ext. There is no mechanism to
      force Subscribers to include the dev:Pauseable extension.
    * It appears as a nested sub-assertion of wsem:Eventing, the policy
      assertion that indicates support for WS-Eventing (play along with
      me here). As such it has the same policy subject, scope, and
      allowable attachment points as wsem:Eventing.

The following is a WSDL snippet that illustrates the use of this policy 
assertion:

<wsdl:service name="eventSource">
  <wsdl:port name="soap12port" binding="tns:eventSOAP12Binding">
    <wsdl:documentation>
      This port serves as a WS-Eventing Event Source and supports the use of
      pauseable Subscriptions (see http://www.smalldevices.org/evt-ext)
    </wsdl:documentation>
    <soap:address location="http://www.wstf.org/sc00X/sc00XSOAP12"/>
*    <wsp:Policy>
      <wsem:Eventing>
        <wsp:Policy>
          <devm:Pauseable/>
        </wsp:Policy>
      </wsem:Eventing>
    </wsp:Policy>
*  </wsdl:port>
</wsdl:service>

This concludes Example 5.

- gp