[Bug 4045] scoping of wsdl1.1 identifiers spec

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





------- Comment #3 from Paul.Cotton@microsoft.com  2007-01-17 22:27 -------
In addition Change the Section 4 as follows:

This section describes a mechanism for associating policy expressions with Web 

service constructs in WSDL 1.1. The mechanism consists of:

- A model for attaching policies to WSDL 1.1 constructs. The model defines:

        - A partitioning of WSDL constructs into service, endpoint, operation
and 

message policy subjects.

        - The semantics of attaching a policy to each policy subject.

        - How to combine policies attached to more than one WSDL construct
within 

a single policy subject.

- An XML representation of policy expressions attached to WSDL 1.1 constructs. 

- The annotation of such policy expressions as required extensions using the 

WSDL-defined extensibility flag @wsdl:required.

<fix above sentence is the WSDL 2.0 section>

WSDL 1.1 disallows the use of extensibility elements on certain elements and
the 

use of extensibility attributes on others. However, the WS-I Basic Profile 1.1
[BP 

1.1] overrules this restriction and allows element extensibility everywhere. 

Therefore, when attaching a reference directly to the WSDL element the policy 

reference SHOULD be attached using wsp:PolicyReference as child element unless
it 

is absolutely necessary to maintain the original WSDL 1.1 restriction, in which 

case the @wsp:PolicyURIs attribute MAY be used for the following WSDL elements:

wsdl11:portType 

wsdl11:portType/wsdl11:operation/wsdl11:input 

wsdl11:portType/wsdl11:operation/wsdl11:output 

wsdl11:portType/wsdl11:operation/wsdl11:fault 

/paulc

Received on Wednesday, 17 January 2007 22:27:07 UTC