WS-I Basic Profile Version 1.1 - instructional media + magic

The following specifications (or sections thereof) are referred to in this section of the
Profile:
• WSDL 1.1, Section 3.0
WSDL 1.1 defines a binding for SOAP 1.1 endpoints. The Profile mandates the use of
SOAP binding as defined in WSDL 1.1, and places the following constraints on its use:
4.7.1 Specifying the transport Attribute
There is an inconsistency between the WSDL 1.1 specification and the WSDL 1.1
schema regarding the transport attribute. The WSDL 1.1 specification requires it;
however, the schema shows it to be optional.
R2701 The wsdl:binding element in a DESCRIPTION MUST be constructed so that its
soapbind:binding child element specifies the transport attribute.
4.7.2 HTTP Transport
The profile limits the underlying transport protocol to HTTP.
R2702 A wsdl:binding element in a DESCRIPTION MUST specify the HTTP transport
protocol with SOAP binding. Specifically, the transport attribute of its soapbind:binding child
MUST have the value "http://schemas.xmlsoap.org/soap/http".
Note that this requirement does not prohibit the use of HTTPS; See R5000.
4.7.3 Consistency of style Attribute
The style, "document" or "rpc", of an interaction is specified at the wsdl:operation level,
permitting wsdl:bindings whose wsdl:operations have different styles. This has led to
interoperability problems.
R2705 A wsdl:binding in a DESCRIPTION MUST either be a rpc-literal binding or a
document-literal binding.
4.7.4 Encodings and the use Attribute
The Profile prohibits the use of encodings, including the SOAP encoding.
R2706 A wsdl:binding in a DESCRIPTION MUST use the value of "literal" for the use
attribute in all soapbind:body, soapbind:fault, soapbind:header and soapbind:headerfault elements.
4.7.5 Multiple Bindings for portType Elements
The Profile explicitly permits multiple bindings for the same portType.
From www.ws-i.org/Profiles/BasicProfile-1.1.html 40 8 February 2008