Abstract

This document draws a list of testable assertions found in the SOAP Version 1.2 specification, and provides a set of tests in order to show whether the assertion is implemented in a SOAP processor.

The goal of this document is to get a list of features whose implementation can be tested in order to satisfy the entrance criteria of the Proposed Recommendation stage.

 It is incorrect to claim to be compliant with the SOAP Version 1.2 specification by passing successfully all the tests provided in this test suite. It is also incorrect to claim to be non-complaint with the SOAP Version 1.2 specification by failing any test provided in this test suite.  A SOAP 1.2 implementation that passes all of the tests specified in this document may claim to conform to the SOAP 1.2 Test Suite $Date: 2002/04/16 $.

Status

This document has been produced by the W3C XML Protocol Working Group. All information in this document is to be considered as work in progress.

This version is based on the Mar 23 2002 snapshot of the SOAP Version 1.2 Part 1 and Part 2 specification. Please refer to the latest SOAP Version 1.2 Working Draft for any current normative information.

 References to the Mar 23 2002 snapshot document will gradually go away, and the document will be updated with the text and assertions from the latest version of the draft.

 Please send comments on this document to w3c-xml-protocol-wg@w3.org (member archive), especially if something is missing from this list of assertions.

Editorial Note: The mailing list has been restricted on the basis of the fact that the specification documents referenced from here are the WG-private versions.

Introduction

This document draws a list of testable assertions found in the SOAP Version 1.2 specification, and provides a set of tests in order to show whether the assertion is implemented in a SOAP processor. The primary goal of this document is to foster interoperability between different SOAP 1.2 implementations. The document is intended to help implementors to write SOAP processors that comply with SOAP 1.2 specification, and interoperate with other SOAP processors that comply with SOAP 1.2 specification.

A SOAP 1.2 implementation that passes all of the tests specified in this document may claim to conform to the SOAP 1.2 Test Suite (insert version number).

Even though the purpose of the SOAP 1.2 Test Suite is to facilitate the creation of interoperable implementations, conformance to the SOAP 1.2 Test Suite does not imply conformance to the SOAP 1.2 specification; there are mandatory requirements of the specification that are not tested by the suite (as a simple example, SOAP 1.2 requires that every legal value of a role name is accepted, and all illegal ones rejected).  An implementation may be said to be SOAP 1.2 conformant if and only if all messages it sends, and all processing it does, are correct with respect to the normative requirements of  the SOAP 1.2 specification. The W3C does not at this time provide for any comprehensive means of testing for such conformance.

Similarly, an implementation may conform to the SOAP 1.2 specification even if it does not support all capabilities tested by the SOAP 1.2 Test Suite. SOAP 1.2 specification admits special purpose implementations, such as those in dedicated controllers, which may send and receive only a very limited suite of messages; the requirement is that whatever is done be done correctly. An implementation may conform to the SOAP 1.2 specification even if it does not support all capabilities tested by the SOAP 1.2 Test Suite. SOAP 1.2 specifies a protocol and a processing model and not a SOAP processor or an API, therefore the test suite defines higher level application semantics to enable testing and facilitate interoperability implementations. It is not necessary for a SOAP processor to support these higher level semantics to be SOAP 1.2 compliant.