SOAP Version 1.2 Specification Assertions and Test Collection

Text from the specification

In particular, this document defines the following namespace names:

• The SOAP envelope has the namespace name "http://www.w3.org/2002/06/soap-envelope" (see 5. SOAP Message Construct).

• The SOAP Misunderstood element information item has the namespace name "http://www.w3.org/2002/06/soap-faults" (see 5.4.8 SOAP mustUnderstand Faults).

• The SOAP Upgrade element information item has the namespace name "http://www.w3.org/2002/06/soap-upgrade" (see 5.4.7 VersionMismatch Faults).

Normative XML Schema [4], [5] documents for these namespace names can be found by dereferencing the namespace names above.

Comments

This assertion will not be tested.

Text from the specification

SOAP does not require that XML Schema processing (assessment or validation) be performed to establish the correctness or 'schema implied' values of element and attribute information items defined by this specification. The values associated with element and attribute information items defined in this specification MUST be carried explicitly in the transmitted SOAP message except where stated otherwise (see 5. SOAP Message Construct).

Comments

This assertion will not be tested.

Text from the specification

SOAP attribute information items have types described by XML Schema: Datatypes [5]. Unless otherwise stated, all lexical forms are supported for each such attribute, and lexical forms representing the same value in the XML Schema value space are considered equivalent for purposes of SOAP processing.

Comments

This assertion will not be tested.

Text from the specification

An ultimate SOAP receiver cannot also be a SOAP intermediary for the same SOAP message (see 2. SOAP Processing Model).

Comments

This assertion will not be tested.

Text from the specification

A SOAP node receiving a SOAP message MUST perform processing according to the SOAP processing model as described in this section and in the remainder of this specification.

Comments

This assertion is tested by the entire test collection.

Text from the specification

A SOAP node MUST be identified by a URI.

Comments

This assertion will not be tested

Text from the specification

The roles assumed by a node MUST be invariant during the processing of an individual SOAP message.

Comments

This assertion cannot be fully tested, as a SOAP node is allowed to process and remove SOAP headers, reinsert them and send them upstream.

Tests

Text from the specification

"http://www.w3.org/2002/06/soap-envelope/role/next"

Each SOAP intermediary and ultimate SOAP receiver MUST act in this role and MAY additionally assume zero or more other SOAP roles.

Tests

Text from the specification

"http://www.w3.org/2002/06/soap-envelope/role/none"

SOAP nodes MUST NOT act in this role.

Tests

Text from the specification

"http://www.w3.org/2002/06/soap-envelope/role/ultimateReceiver"

To establish itself as an ultimate SOAP receiver a SOAP node MUST act in this role. SOAP intermediaries MUST NOT act in this role.

Tests

Text from the specification

While the purpose of a SOAP role name is to identify a SOAP node, there are no routing or message exchange semantics associated with the SOAP role name.

Comments

This assertion will not be tested.

Text from the specification

A SOAP header block MAY carry a role attribute information item (see 5.2.2 SOAP role Attribute) that is used to target the header block at SOAP nodes operating in the specified role. This specification refers to the value of the SOAP role attribute as the SOAP role for the corresponding SOAP header block.

Comments

All tests in the test collection that use the role attribute test this assertion.

Text from the specification

A SOAP header block is said to be targeted to a SOAP node if the SOAP role for the header block is the name of a role played by the SOAP node.

Comments

All tests in the test collection that use the role attribute test this assertion.

Text from the specification

Header blocks targeted to the special role "http://www.w3.org/2002/06/soap-envelope/role/none" are carried with the message to the ultimate SOAP receiver(s), but are never formally processed. Such blocks MAY carry data that is required for processing of other blocks.

Tests

Text from the specification

A SOAP header block is said to be understood by a SOAP node if the software at that SOAP node has been written to fully conform to and implement the semantics conveyed by the combination of local name and namespace name of the outer-most element information item of that header block.

Comments

All tests in the test collection that uses headers test this assertion.

Text from the specification

SOAP header blocks MAY carry mustUnderstand attribute information items (see 5.2.3 SOAP mustUnderstand Attribute). When the value of such an attribute information item is "true", the SOAP block is said to be mandatory.

Mandatory SOAP header blocks are presumed to somehow modify the semantics of other headers or body elements. Therefore, for every mandatory SOAP header block targeted to a node, that node MUST either process the header block or not process the SOAP message at all, and instead generate a fault (see 2.6 Processing SOAP Messages and 5.4 SOAP Fault).

Comments

All tests in the test collection that use mustUnderstand attribute will test this assertion.

Text from the specification

This specification therefore does not require any fault to be generated based on the presence or value of the mustUnderstand attribute information item on a SOAP header block not targeted at the current processing node. In particular, it is not an error for an ultimate SOAP receiver to receive a message containing a mandatory header block that is targeted at a role other than the ones assumed by the ultimate SOAP receiver.

Tests

Text from the specification

An ultimate SOAP receiver MUST correctly process the immediate children of the SOAP body (see 5.3 SOAP Body).

Comments

All tests in the test collection that have body block(s) and do not generate a fault test this assertion.

Text from the specification

Unless otherwise stated, processing MUST be semantically equivalent to performing the following steps separately, and in the order given. Note however that nothing in this specification prevents the use of optimistic concurrency, roll back, or other techniques that might provide increased flexibility in processing order as long as all generated SOAP messages, SOAP faults and application-level side effects are equivalent to those that would be obtained by direct implementation of the following rules in the order shown below.

1. Determine the set of roles in which the node is to act. The contents of the SOAP envelope, including any header blocks and the body, MAY be inspected in making such determination.

2. Identify all header blocks targeted at the node that are mandatory.

3. If one or more of the header blocks identified in the preceding step are not understood by the node then generate a single SOAP fault with the Value of Code set to "env:MustUnderstand" (see 5.4.8 SOAP mustUnderstand Faults). If such a fault is generated, any further processing MUST NOT be done. Faults relating to the contents of the body MUST NOT be generated in this step.

4. Process all header blocks targeted at the node and, in the case of an ultimate SOAP receiver, the SOAP body. A SOAP node MUST process all SOAP header blocks targeted at it. A SOAP node MAY choose to ignore the application level processing specified by non-mandatory SOAP header blocks targeted at it.

5. In the case of a SOAP intermediary, and where the message is to be forwarded further along the message path, remove all SOAP header blocks targeted at the node, and possibly insert new SOAP header blocks.

Comments

All tests in the test collection test this assertion.

Text from the specification

In all cases where a SOAP header block is processed, the SOAP node MUST understand the SOAP block and MUST do such processing in a manner fully conformant with the specification for that block.

Comments

All tests in the test collection that process a soap header without generating a fault, test this assertion.

Text from the specification

An ultimate SOAP receiver MUST process the SOAP body, in a manner consistent with 2.5 Structure and Interpretation of SOAP Bodies.

Comments

All tests in the test collection that have body block(s) test this assertion.

Text from the specification

Failure is indicated by the generation of a fault (see 5.4 SOAP Fault). SOAP message processing MAY result in the generation of at-most one fault.

Comments

All tests in the test collection that generate a fault test this assertion.

Text from the specification

Header-related faults other than those related to understanding header blocks (see 2.4 Understanding SOAP Headers) MUST conform to the specification for the corresponding SOAP header block.

Tests

Text from the specification

Forwarding intermediaries MUST process the message according to the SOAP processing model defined in 2.6 Processing SOAP Messages. They MUST also remove from the message all SOAP header blocks targeted to them, prior to forwarding, regardless of whether these blocks were processed or ignored.

Comments

All tests in the test collection that use Node B.

Text from the specification

In addition, forwarding intermediaries MUST also obey the specification for the SOAP forwarding feature being used. The specification for such a feature MUST describe the required semantics, including the rules describing how the forwarded message is constructed.

Comments

This assertion will not be tested.

Text from the specification

A SOAP node must determine whether it supports the version of a SOAP message on a per message basis.

Comments

This assertion will not be tested.

Text from the specification

A SOAP node MAY support multiple envelope versions. However, when processing a message, a SOAP node MUST use the semantics defined by the version of that message.

Tests

Text from the specification

If a SOAP node receives a message whose version is not supported it MUST generate a fault (see 5.4 SOAP Fault) with a Value of Code set to "env:VersionMismatch". Any other malformation of the message construct MUST result in the generation of a fault with a Value of Code set to "env:Sender".

Tests

Text from the specification

The specification of a feature MUST include the following:

1. The information (state) required at each node to implement the feature.

2. The processing required at each node in order to fulfill the obligations of the feature including any handling of communication failures that might occur in the underlying protocol (see also 4.2 Binding Framework).

3. The information to be transmitted from node to node.

4. In the case of MEPs:

   1. Any requirements to generate additional messages (such as responses to requests in a request/response MEP).

   2. Rules for the delivery or other disposition of SOAP faults generated during the operation of the MEP.

Comments

This assertion will not be tested. HTTP binding in SOAP 1.2 part 2 is a test for this assertion.

Text from the specification

A module specification follows the following rules. It:

1. MUST identify itself with a URI. This enables the module to be unambiguously referenced in description languages or during negotiation.

2. MUST clearly and completely specify the content and semantics of the header blocks used to implement the behavior in question, including if appropriate any modifications to the SOAP Processing model.

3. MAY utilize the property conventions defined in Part 2 [1], section A Convention for Describing Features and Bindings, in describing the functionality that the module provides. If these conventions are followed, the module specification MUST clearly describe the relationship between the abstract properties and their representations in the SOAP envelope. Note that it is possible to write a feature specification purely in terms of abstract properties, and then write a separate module specification which implements that feature, mapping the properties defined in the feature specification to SOAP header blocks in the module.

4. MUST clearly specify any known interactions with or changes to the interpretation of the SOAP body. Furthermore, it MUST clearly specify any known interactions with or changes to the interpretation of other SOAP features (whether or not those features are themselves modules).

Comments

This assertion will not be tested.

Text from the specification

A binding does not provide a separate processing model and does not constitute a SOAP node by itself.

Comments

This assertion will not be tested.

Text from the specification

A binding specification MUST enable one or more MEP.

Comments

HTTP binding specified in SOAP 1.2 part 2 enables an MEP. This assertion will not be tested.

Text from the specification

In cases where multiple features are supported by a binding specification the specifications for those features MUST provide any information necessary for their successful use in combination; this binding framework does not provide any explicit mechanism for ensuring such compatibility of multiple features.

Comments

HTTP binding specified in SOAP 1.2 part 2 enables an MEP. This assertion will not be tested.

Text from the specification

As described in 5. SOAP Message Construct, each SOAP message is modeled as an XML Infoset that consists of a document information item with exactly one child: the envelope element information item.

Comments

All tests in the test collection test this assertion.

Text from the specification

Therefore, the minimum responsibility of a binding in transmitting a message is to specify the means by which the SOAP XML Infoset is transferred to and reconstituted by the binding at the receiving SOAP node and to specify the manner in which the transmission of the envelope is effected using the facilities of the underlying protocol.

Comments

This assertion will not be tested.

Text from the specification

The binding framework does NOT require that every binding use the XML 1.0 [8] serialization as the "on the wire" representation of the Infoset; compressed, encrypted, fragmented representations and so on can be used if appropriate.

Comments

This assertion will not be tested.

Text from the specification

Section 5. SOAP Message Construct provides that the XML Infoset of a SOAP message MUST NOT include a DTD. Accordingly, a binding that uses the XML 1.0 serialization MUST NOT transmit a DTD; a binding that accepts XML 1.0 serializations MUST fault in a binding specific manner if an XML 1.0 serialization corresponding to a DTD for the SOAP message is received.

Tests

Text from the specification

Although streaming SOAP receivers will acquire such Infosets incrementally, SOAP processing MUST yield results identical to those that would have been achieved if the entire SOAP envelope were available prior to the start of processing.

Comments

This assertion will not be tested.

Text from the specification

A SOAP message is specified as an XML Infoset that consists of a document information item with exactly one member in its [children] property, which MUST be the SOAP Envelope element information item (see 5.1 SOAP Envelope). This element information item is also the value of the [document element] property.

Comments

All tests in the test collection test this assertion.

Text from the specification

The [notations] and [unparsed entities] properties are both empty. The [base URI], [character encoding scheme] and [version] properties may have any legal value. The [standalone] property either has a value of "true" or has no value.

Tests

Text from the specification

The XML infoset of a SOAP message MUST NOT contain a document type declaration information item.

Tests

Text from the specification

A SOAP message SHOULD NOT contain processing instruction information items. A SOAP receiver MUST ignore processing instruction information items in SOAP messages that it receives.

Tests

Text from the specification

Element information items defined by this specification may have zero or more character information item children whose character code is amongst the whitespace characters as defined by [8]. Unless otherwise indicated, such character information items are considered insignificant. A SOAP receiver MUST ignore such insignificant character information items.

Tests

Text from the specification

The Envelope element information item has:

• A [local name] of Envelope .

• A [namespace name] of "http://www.w3.org/2002/06/soap-envelope".

• Zero or more namespace qualified attribute information items amongst its [attributes] property.

• One or two element information items in its [children] property in order as follows:

  1. An optional Header element information item (see 5.2 SOAP Header).

  2. A mandatory Body element information item (see 5.3 SOAP Body).

Comments

All the tests in the test collection test this assertion.

Text from the specification

The encodingStyle attribute information item has:

• A [local name] of encodingStyle .

• A [namespace name] of "http://www.w3.org/2002/06/soap-envelope".

Comments

All tests in the test collection that use encodingSytle attribute test this assertion.

Text from the specification

The encodingStyle attribute information item MAY only appear on:

1. A SOAP header block (see 5.2.1 SOAP header block).

2. A child element information item of the SOAP Body element information item (see 5.3.1 SOAP Body child Element).

3. A child element information item of the SOAP Detail element information item (see 5.4.5.1 SOAP detail entry).

4. Any descendent of 1, 2, and 3 above.

Comments

All tests in the test collection that use encodingSytle attribute test this assertion.

Text from the specification

The scope of the encodingStyle attribute information item is that of its owner element information item and that element information item's descendants, unless a descendant itself carries such an attribute information item.

Tests

Text from the specification

If no encodingStyle attribute information item is in scope for a particular element information item or the value of such an attribute information item is the zero-length URI ("") then no claims are made regarding the encoding style of that element information item and its descendants.

Tests

Text from the specification

The encodingStyle attribute information item is of type anyURI in the namespace http://www.w3.org/2001/XMLSchema

Comments

All the tests in the test collection that use encodingStyle, test this assertion.

Text from the specification

The Header element information item has:

• A local name of Header

• A namespace name of http://www.w3.org/2002/06/soap-envelope

• Zero or more namespace qualified attribute information item children.

• Zero or more namespace qualified element information item children.

Comments

All the tests in the test collection that use headers, test this assertion.

Text from the specification

Each SOAP header block element information item:

• MUST have a [namespace name] property which has a value, that is, MUST be namespace qualified.

• MAY have any number of character information item children. Child character information items whose character code is amongst the whitespace characters as defined by [8] are considered significant.

• MAY have an encodingStyle attribute information item in its [attributes] property.

• MAY have an role attribute information item in its [attributes] property.

• MAY have a mustUnderstand attribute information item in its [attributes] property.

Comments

All tests in the test collection that use headers, test this assertion.

Text from the specification

The SOAP header block attribute information items defined later in 5.2.2 SOAP role Attribute and 5.2.3 SOAP mustUnderstand Attribute affect the processing of SOAP messages by SOAP receivers (see 2. SOAP Processing Model). A SOAP sender generating a SOAP message SHOULD use these attributes only on SOAP header block. A SOAP receiver MUST ignore these attribute information items if they appear on descendants of a SOAP header block or on a SOAP body child element information item (or its descendents).

Tests

Text from the specification

The role attribute information item has the following Infoset properties:

• A [local name] of role .

• A [namespace name] of "http://www.w3.org/2002/06/soap-envelope".

• A [specified] property with a value of "true".

The type of the role attribute information item is anyURI in the namespace named "http://www.w3.org/2001/XMLSchema". The value of the role attribute information item is a URI that names a role that a SOAP node may assume.

Comments

All tests in the test collection that use roles, will test this assertion.

Text from the specification

Omitting the SOAP role attribute information item is equivalent to supplying that attribute with a value of "http://www.w3.org/2002/06/soap-envelope/role/ultimateReceiver".

Tests

Text from the specification

An empty value for this attribute is equivalent to omitting the attribute completely, i.e. targeting the block at an ultimate SOAP receiver.

Comments

'this' in the specification text refers to the role attribute information item.

Tests

Text from the specification

SOAP senders SHOULD NOT generate, but SOAP receivers MUST accept the SOAP role attribute information item with a value of "http://www.w3.org/2002/06/soap-envelope/role/ultimateReceiver" (see 1.2.2 Robustness Principle).

Tests

Text from the specification

The mustUnderstand attribute information item has the following Infoset properties:

• A [local name] of mustUnderstand .

• A [namespace name] of "http://www.w3.org/2002/06/soap-envelope".

• A [specified] property with a value of "true".

The type of the mustUnderstand attribute information item is boolean in the namespace "http://www.w3.org/2001/XMLSchema".

Comments

All tests in the test collection that use mustUnderstand attribute, test this assertion.

Text from the specification

Omitting this attribute information item is defined as being semantically equivalent to including it with a value of "false" or "0".

Comments

'this' in the specification text refers to the mustUnderstand attribute information item.

Tests

Text from the specification

SOAP senders SHOULD NOT generate, but SOAP receivers MUST accept the SOAP mustUnderstand attribute information item with a value of "false" or "0" (see section 1.2.2 Robustness Principle).

Tests

Text from the specification

A SOAP receiver MUST accept any valid lexical representation of the attribute value.

Comments

The attribute mentioned in the spec text refers to env:mustUnderstand.

Tests

Text from the specification

The Body element information item has:

• A [local name] of Body .

• A [namespace name] of "http://www.w3.org/2002/06/soap-envelope".

• Zero or more namespace qualified attribute information items in its [attributes] property.

• Zero or more namespace qualified element information items in its [children] property.

Comments

All tests in the test collection that have the Body element, test this assertion.

Text from the specification

All child element information items of the SOAP Body element information item:

• MUST have a [namespace name] property which has a value, that is, be namespace qualified.

• MAY have an encodingStyle attribute information item in their [attributes] property.

Comments

All tests in the test collection that have the body blocks, test this

Text from the specification

The Fault element information item has:

• A [local name] of Fault .

• A [namespace name] of "http://www.w3.org/2002/06/soap-envelope".

• Two or more child element information items in its [children] property in order as follows:

  1. A mandatory Code element information item (see 5.4.1 SOAP Code Element).

  2. A mandatory Reason element information item (see 5.4.2 SOAP Reason Element).

  3. An optional Node element information item (see 5.4.3 SOAP Node Element).

  4. An optional Role element information item (see 5.4.4 SOAP Role Element).

  5. An optional Detail element information item (see 5.4.5 SOAP Detail Element).

Comments

All tests in the test collection that generate fault, test this assertion.

Text from the specification

To be recognized as carrying SOAP error information, a SOAP message MUST contain a single SOAP Fault element information item as the only child of the SOAP Body .

Comments

All tests in the test collection that generate fault, test this assertion.

Text from the specification

When generating a fault, SOAP senders MUST NOT include additional element information items in the SOAP Body. A message whose Body contains a Fault plus additional element information items has no SOAP-defined semantics.

Comments

All tests in the test collection that generate fault, test this assertion.

Text from the specification

The Code element information item has:

• A [local name] of Code .

• A [namespace name] of http://www.w3.org/2002/06/soap-envelope .

• One or two child element information items in its [children] property, in order, as follows:

  1. A mandatory Value element information item as described below (see 5.4.1.1 SOAP Value element (with Code parent))

  2. An optional Subcode element information item as described below (see 5.4.1.2 SOAP Subcode element).

Comments

All tests in the test collection that generate fault, test this assertion.

Text from the specification

The Value element information item has;

• A [local name] of Value .

• A [namespace name] of http://www.w3.org/2002/06/soap-envelope .

The type of the Value element information item is faultCodeEnum in the "http://www.w3.org/2002/06/soap-envelope" namespace.

Comments

All tests in the test collection that generate fault, test this assertion.

Text from the specification

The Subcode element information item has:

• A [local name] of Subcode .

• A [namespace name] of http://www.w3.org/2002/06/soap-envelope .

• One or two child element information items in its [children] property, in order, as follows:

  1. A mandatory Value element information item as described below (see 5.4.1.3 SOAP Value element (with Subcode parent)).

  2. An optional Subcode element information item (see 5.4.1.2 SOAP Subcode element).

Tests

Text from the specification

The Value element information item has:

• A [local name] of Value .

• A [namespace name] of http://www.w3.org/2002/06/soap-envelope .

The type of the Value element information item is XML qualified name in the "http://www.w3.org/2001/XMLSchema" namespace.

Tests

Text from the specification

The Reason element information item has:

• A [local name] of Reason .

• A [namespace name] of http://www.w3.org/2002/06/soap-envelope .

• An optional attribute information item with a [local name] of lang and [namespace name] of "http://www.w3.org/XML/1998/namespace" (see [8], Language Identification).

Comments

All tests in the test collection that generate fault, test this assertion.

Text from the specification

The type of the Reason element information item is string in the "http://www.w3.org/2001/XMLSchema" namespace.

Comments

All tests in the test collection that generate fault, test this assertion.

Text from the specification

The Node element information item has:

• A [local name] of Node .

• A [namespace name] of http://www.w3.org/2002/06/soap-envelope .

Tests

Text from the specification

SOAP nodes that do not act as the ultimate SOAP receiver MUST include this element information item.

Comments

The element information item in the specification text refers to the 'Node' element.

Tests

Text from the specification

The Role element information item has:

• A [local name] of Role .

• A [namespace name] of http://www.w3.org/2002/06/soap-envelope .

The type of the Role element information item is anyURI in the "http://www.w3.org/2001/XMLSchema" namespace.

Tests

Text from the specification

The Detail element information item has:

• A [local name] of Detail .

• A [namespace name] of http://www.w3.org/2002/06/soap-envelope .

• Zero or more attribute information items in its [attributes] property.

• Zero or more child element information items in its [children] property.

Tests

Text from the specification

The Detail element information item MUST be present when the contents of the SOAP Body could not be processed successfully. It MUST NOT be used to carry error information about any SOAP header blocks.

Tests

Text from the specification

Detailed error information for SOAP header blocks MUST be carried within the SOAP header blocks themselves.

Tests

Text from the specification

The values of the Value child element information item of the Code element information item are restricted to those in Table 2. Additional fault subcodes MAY be created for use by applications or features. Such subcodes are carried in the Value child element information item of the Subcode element information item.

Comments

All tests in the test collection that generate fault, test this assertion.

Text from the specification

The Upgrade element information item has:

• A [local name] of Upgrade .

• A [namespace name] of "http://www.w3.org/2002/06/soap-upgrade".

• One or more envelope element information items in its [children] property as described below:

The envelope element information item has:

• A [local name] of envelope .

• A [namespace name] which has no value.

• An unqualified attribute information item with a local name of qname and a type of QName in the "http://www.w3.org/2001/XMLSchema" namespace.

Tests

Text from the specification

A SOAP node MAY generate a SOAP fault for any one or more SOAP header blocks that were not understood in a SOAP message. It is NOT a requirement that the fault contain the qualified names of ALL such header blocks.

Each such header block element information item has:

• A [local name] of Misunderstood .

• A [namespace name] of "http://www.w3.org/2002/06/soap-faults".

• A qname attribute information item in its [attributes] property as described below.

The qname attribute information item has the following Infoset properties:

• A [local name] of qname .

• A [namespace name] which has no value.

• A [specified] property with a value of "true".

The type of the qname attribute information item is QName in the "http://www.w3.org/2001/XMLSchema" namespace. Its value is the XML qualified name of a header block which the faulting node failed to understand.

Tests

Text from the specification

SOAP does not define a base URI but relies on the mechanisms defined in XML Base[11] and RFC 2396[6] for establishing a base URI against which relative URIs can be made absolute.

Tests

Text from the specification

The use of IP addresses in URIs SHOULD be avoided whenever possible (see RFC 1900 [18]. However, when used, the literal format for IPv6 addresses in URIs as described by RFC 2732 [12] SHOULD be supported.

Tests

Text from the specification

SOAP does not place any a priori limit on the length of a URI. Any SOAP node MUST be able to handle the length of any URI that it publishes and both SOAP senders and SOAP receivers SHOULD be able to deal with URIs of at least 2048 characters in length.

Tests

Text from the specification

A SOAP/1.1 node receiving a SOAP Version 1.2 message will according to SOAP/1.1 generate a version mismatch SOAP fault based on a SOAP/1.1 message construct. That is, the envelope will have a local name of Envelope and a namespace name of "http://schemas.xmlsoap.org/soap/envelope/".

Comments

Since this assertion is about the behavior of SOAP 1.1 compliant SOAP node, the test collection does not test this assertion.

Text from the specification

A SOAP Version 1.2 node receiving a SOAP/1.1 message either:

• MAY process the message as a SOAP/1.1 message (if supported), or

• MUST generate a version mismatch SOAP fault based on a SOAP/1.1 message construct following SOAP/1.1 semantics. The SOAP fault SHOULD include an Upgrade header block as defined in this specification (see 5.4.7 VersionMismatch Faults) indicating support for SOAP Version 1.2. This allows a receiving SOAP/1.1 node to correctly interpret the SOAP fault generated by the SOAP Version 1.2 node.

Tests

Text from the specification

When serializing a graph for transmission inside a SOAP message any representation that deserializes to the identical graph MAY be used; when receiving an encoded SOAP message, all representations MUST be accepted.

Tests

Text from the specification

Each graph edge is encoded as an element information item and each element information item represents a graph edge.

Comments

All tests in the test collection that use soap encoding, will test this assertion.

Text from the specification

The graph node at which an edge terminates is determined as follows:

1. If the element information item representing the edge does not have a ref attribute information item (see 3.1.5.2 ref Attribute Information Item) amongst its attributes then that element information item is said to represent a node in the graph and the edge terminates at that node.

2. If the element information item representing the edge does have a ref attribute information item (see 3.1.5.2 ref Attribute Information Item) among its attributes, then the value of that attribute information item MUST be identical to the value of exactly one id attribute information item ( see 3.1.5.1 id Attribute Information Item ) in the same envelope. In this case the edge terminates at the graph node represented by the element information item on which the id attribute information item appears. That element information item MUST be in the scope of an encodingStyle attribute with a value of "http://www.w3.org/2002/06/soap-encoding".

All nodes in the graph are encoded as described in 1 above. Additional inbound edges for multi reference graph nodes are encoded as described in 2 above.

Comments

All tests in the test collection that use soap encoding and do not return a fault, test this assertion.

Text from the specification

The "lexical value" of a terminal graph node is the sequence of Unicode characters identified by the character information item children of the element information item representing that node.

Tests

Text from the specification

An outbound edge of a graph node is encoded as an element information item child of the element information item that represents the node (see 3.1.1 Encoding graph edges and nodes).

Tests

Text from the specification

For a graph edge which is distinguished by label ( "struct" or "generic" ), the namespace name property of the element information item determines whether the edge label is globally or locally scoped:

• If the namespace name is empty then the edge label is locally scoped.

• If the namespace name is not empty then the edge label is globally scoped. The namespace name is the URI part of the edge label.

The interpretation of the local name property of the element information item with respect to the edge label is as follows:

• If the edge label is locally scoped, the edge label is the same as the local name. (see A. Mapping Application Defined Names to XML Names).

• If the edge label is globally scoped, the non-URI part of the edge label is the local name. (see A. Mapping Application Defined Names to XML Names).

Tests

Text from the specification

For a graph edge which is distinguished by position ( "array" or "generic" ):

• The ordinal position of the graph edge corresponds to the position of the element information item relative to its siblings

• If outbound edges are distinguished only by position ("array") then the local name and namespace name properties of the element information item are not significant.

Tests

Text from the specification

The following rules apply to the encoding of a graph node that represents an "array":

• The element information item representing an array node MAY have amongst its attributes an itemType attribute information item (see 3.1.4.1 itemType Attribute Information Item).

• The element information item representing an array node MAY have amongst its attributes an arraySize attribute information item (see 3.1.6 arraySize Attribute Information Item).

Comments

All tests in the test collection that use arrays, will test this assertion

Text from the specification

If a graph edge does not terminate in a graph node then it can either be omitted from the serialization or it can be encoded as an element information item with an xsi:nil attribute information item.

Tests

Text from the specification

The type name property of a graph node is a {namespace name, local name} pair computed as follows:

1. If the element information item representing the graph node has an xsi:type attribute information item amongst its attributes then the type name property of the graph node is the value of the xsi:type attribute information item.

2. Otherwise if the parent element information item of the element information item representing the graph node has a "enc:itemType" attribute information item (see 3.1.4.1 itemType Attribute Information Item) amongst its attributes then the type name property of the graph node is the value of the "enc:itemType" attribute information item

3. Otherwise the value of the type name property of the graph node is unspecified.

Comments

All encoding tests in the test collection, test this assertion.

Text from the specification

The itemType attribute information item has the following Infoset properties:

• A local name of itemType ;

• A namespace name of "http://www.w3.org/2002/06/soap-encoding".

• A specified property with a value of true.

The type of the itemType attribute information item is QName in the namespace named "http://www.w3.org/2001/XMLSchema". The value of the itemType attribute information item is used to compute the type name property (see 3.1.4 Computing the Type Name property) of members of an array.

Tests

Text from the specification

The id attribute information item has the following Infoset properties:

• A local name of id ;

• A namespace name which is empty

• A specified property with a value of "true".

The type of the id attribute information item is ID in the namespace named "http://www.w3.org/2001/XMLSchema". The value of the id attribute information item is a unique identifier that can be referred to by a ref attribute information item (see 3.1.5.2 ref Attribute Information Item).

Tests

Text from the specification

The ref attribute information item has the following Infoset properties:

• A local name of ref ;

• A namespace name which is empty

• A specified property with a value of true.

The type of the ref attribute information item is IDREF in the namespace named "http://www.w3.org/2001/XMLSchema". The value of the ref attribute information item is a reference to a unique identifier defined by an id attribute information item (see 3.1.5.1 id Attribute Information Item).

Tests

Text from the specification

The value of a ref attribute information item MUST also be the value of exactly one id attribute information item.

Tests