1.  Incorrect example in Section 4.1 – The Framework does not allow new child elements from the policy namespace name as children of the policy operators.

Note: it is possible to add new names to the existing namespace, such as:

Example 4-5. Policy containing 1.5 and 1.6 Policies all in the 1.5 namespace

<wsp:Policy>

  <wsp:ExactlyOne>

    <wsp:Choice wsp:minOccurs="1" wsp:maxOccurs="2">

      ...

    </wsp:Choice>

    <wsp:All>

       ...

    </wsp:All>

  </wsp:ExactlyOne>

</wsp:Policy>

2.  Incorrect example in Section 4.2 – The Framework does not allow new child elements from the policy namespace name as children of the policy operators.

We show an example of a new version of policy that allows QName reference to Policies in the PolicyReference:

Example 4-9. WSDL containing 1.5 and 2.0 (compatible with 2.0) Policy References.

<wsdl11:binding name="StockQuoteSoapBinding" type="fab:Quote" >

       <wsoap12:binding style="document"

          transport="http://schemas.xmlsoap.org/soap/http" />

        <wsp:Policy>

          <wsp:ExactlyOne>

                <wsp:All>

                <wsp:PolicyReference URI="#RmPolicy"

wsdl11:required="true" />

              <wsp:PolicyReference URI="#X509EndpointPolicy"

wsdl11:required="true" />

                </wsp:All>

                <wsp:All>

                <wsp:PolicyReferenceByQName ref="rmp:RMAssertion"

wsdl11:required="true" />

              <wsp:PolicyReferenceByQName ref="sp:AsymmetricBinding"

wsdl11:required="true" />

                </wsp:All>

         </wsp:ExactlyOne>

        </wsp:Policy>

  <wsdl11:operation name="GetLastTradePrice" > ....

  ...