WS-I Basic Profile 1.2

The following changes were made in BP 1.2.:

SOAP Changes

• XML Envelope Serialization:
  .
  • An ENVELOPE MUST be serialized as XML 1.0.
    .
• Unicode BOMs:
  .
  • A RECEIVER MUST accept envelopes that include the Unicode Byte Order Mark (BOM).
    .
• XML declarations:
  .
  • A RECEIVER MUST accept messages with envelopes that contain an XML Declaration.
    .
• Character Encodings:
  .
  • A RECEIVER MUST ignore the encoding pseudo-attribute of the envelope's XML declaration.
    .
• SOAP Envelope Structure:
  .
  • An ENVELOPE MUST conform to the structure specifi ed in SOAP 1.1 Section 4, "SOAP Envelope".
    .
  • An ENVELOPE MUST have exactly zero or one child elements of the soap:Body element.
    .
• SOAP Defined Faults Action URI:
  .
  • An ENVELOPE MUST use the http://www. w3.org/2005/08/addressing/soap/fault URI as the value for the wsa:Action element when present, for either of the SOAP1.1 defined VersionMismatch and MustUnderstand faults.
    .
• SOAP MustUnderstand or VersionMismatch fault Transmission:
  .
  • A RECEIVER that receives a SOAP envelope that generates either a SOAP MustUnderstand or VersionMismatchfault SHOULD transmit such a fault on the HTTP response message, regardless of the value of the wsa:ReplyTo or wsa: FaultTo SOAP headers present in the message.
    .
• Use of wsa:Action and WS-Addressing WSDL Binding:
  .
  • An ENVELOPE that includes a wsa:Action SOAP header block and which is described using WSDL 1.1 description MUST conform to WS-Addressing WSDL Binding, Section 5.1.
    .
• Understanding WS-Addressing SOAP Header Blocks:
  .
  • When a message contains multiple WS-Addressing SOAP header blocks with at least one of those header blocks containing a soap:mustUnderstand='1'attribute, then a RECEIVER MUST understand all the WS-Addressing SOAP header blocks or none of them.
    .
• Valid Range of Values for SOAPAction when WS-Addressing is used:
  .
  • When wsa:Action MAP is present in an envelope, the containing MESSAGE MUST specify a SOAPAction HTTP header with either a value that is an absolute URI that has the same value as the value of the wsa:ActionMAP, or a value of "" (empty string).
    .
• Use of Non-Anonymous Response EPR in a Request-Response Operation:
  .
  • If an INSTANCE sends a MustUnderstandor VersionMismatch fault generated as a result of an invocation of a Request-Response WSDL operation, it MUST send that fault in the entity body of HTTP response using the same HTTP connection as the request message of that operation.
    .
  • If an INSTANCE sends a response, which is neither a MustUnderstand nor VersionMismatch fault, as a result of an invocation of a Request-Response WSDL operation and the response EPR has a non-anonymous wsa:Address value, then the response MUST be sent in the entity body of an HTTP request in a separate HTTP connection specified by the response EPR using the SOAP 1.1 Request Optional Response HTTP binding.

WSDL Changes

• WSDL and Schema Import:
  .
  • In a DESCRIPTION, the namespace attribute of the wsdl:import MUST NOT be a relative URI.
    .
• WSDL documentation Element:
  .
  • In a DESCRIPTION the wsdl:documentation element MAY be present as the first child element of wsdl:import, wsdl: partand wsdl:definitions in addition to the elements cited in the WSDL1.1 specification.
    .
• Multiple GED Definitions with the same QName:
  .
  • A DESCRIPTION SHOULD NOT contain multiple global element declarations that share the same qualified name.
    .
• Multiple Type Definitions with the same QName:
  .
  • A DESCRIPTION SHOULD NOT contain multiple type definitions that share the same qualified name.

First Page: SOA Web Services - WS-I Specifications