27.01.2014 Views

SOAP Version 1.2 Specification Assertions and Test Collection

SOAP Version 1.2 Specification Assertions and Test Collection

SOAP Version 1.2 Specification Assertions and Test Collection

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

provides a set of tests in order to show whether the assertions are implemented in a<br />

<strong>SOAP</strong> processor. The primary goal of this document is to foster interoperability between<br />

different <strong>SOAP</strong> <strong>1.2</strong> implementations. The document is intended to help implementors to<br />

write <strong>SOAP</strong> processors that comply with <strong>SOAP</strong> <strong>1.2</strong> specification, <strong>and</strong> interoperate with<br />

other <strong>SOAP</strong> processors that comply with <strong>SOAP</strong> <strong>1.2</strong> specification.<br />

A <strong>SOAP</strong> <strong>1.2</strong> implementation that passes all of the tests specified in this document may<br />

claim to conform to the <strong>SOAP</strong> <strong>1.2</strong> <strong>Test</strong> Suite $Date 2003/06/24 $.<br />

Even though the purpose of the <strong>SOAP</strong> <strong>1.2</strong> <strong>Test</strong> Suite is to facilitate the creation of<br />

interoperable implementations, conformance to the <strong>SOAP</strong> <strong>1.2</strong> <strong>Test</strong> Suite does not imply<br />

conformance to the <strong>SOAP</strong> <strong>1.2</strong> specifications; there are m<strong>and</strong>atory requirements of the<br />

specifications that are not tested by the suite (as a simple example, <strong>SOAP</strong> <strong>1.2</strong> requires<br />

that every legal value of a role name is accepted, <strong>and</strong> all illegal ones rejected). An<br />

implementation may be said to be <strong>SOAP</strong> <strong>1.2</strong> conformant if <strong>and</strong> only if it it satisfies the<br />

conformance requirements specified in <strong>SOAP</strong> <strong>1.2</strong> specifications. The W3C does not at<br />

this time provide for any comprehensive means of testing for such conformance.<br />

Similarly, an implementation may conform to the <strong>SOAP</strong> <strong>1.2</strong> specifications even if it does<br />

not support all capabilities tested by the <strong>SOAP</strong> <strong>1.2</strong> <strong>Test</strong> Suite. <strong>SOAP</strong> <strong>1.2</strong> specifications<br />

admits special purpose implementations, such as those in dedicated controllers, which<br />

may send <strong>and</strong> receive only a very limited suite of messages; the requirement is that<br />

whatever is done be done correctly. An implementation may conform to the <strong>SOAP</strong> <strong>1.2</strong><br />

specifications even if it does not support all capabilities tested by the <strong>SOAP</strong> <strong>1.2</strong> <strong>Test</strong><br />

Suite. The test suite defines higher level application semantics to enable testing <strong>and</strong><br />

facilitate interoperable implementations. It is not necessary for a <strong>SOAP</strong> processor to<br />

support these higher level semantics to be <strong>SOAP</strong> <strong>1.2</strong> compliant.<br />

<strong>Assertions</strong> for <strong>SOAP</strong> <strong>Version</strong> <strong>1.2</strong> Part 1 <strong>and</strong> Part 2 are numbered sequentially (1..n).<br />

"Location of the assertion" points the source of the assertion (section or subsection<br />

number) in Part 1 or Part 2. Hyperlinks are used to cross-reference to the original<br />

specification section/subsection.<br />

Some of the tests in this document use <strong>SOAP</strong>Builders interoperability tests as a started<br />

point, but have been modified to conform to the <strong>SOAP</strong> <strong>1.2</strong> specifications.<br />

2. <strong>SOAP</strong> <strong>1.2</strong> <strong>Assertions</strong><br />

2.1 <strong>SOAP</strong> <strong>1.2</strong>, Part 1 <strong>Assertions</strong><br />

Assertion x1-conformance-part1<br />

Location of the assertion<br />

<strong>SOAP</strong> <strong>1.2</strong> Part 1, Section <strong>1.2</strong><br />

Text from the specification<br />

For an implementation to claim conformance with the <strong>SOAP</strong> <strong>Version</strong> <strong>1.2</strong><br />

specification, it MUST correctly implement all m<strong>and</strong>atory ("MUST")<br />

From www.w3c.org 4 7/10/2003

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!