XML Protocol Working Group - Publications

Recommendations

- history

SOAP Version 1.2 Part 0: Primer (Second Edition) is a non-normative document intended to provide an easily understandable tutorial on the features of SOAP Version 1.2. In particular, it describes the features through various usage scenarios, and is intended to complement the normative text contained in Part 1 and Part 2 of the SOAP 1.2 specifications. This second edition includes additional material on the SOAP Message Transmission Optimization Mechanism (MTOM), the XML-binary Optimized Packaging (XOP) and the Resource Representation SOAP Header Block (RRSHB) specifications.

- history

SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. "Part 1: Messaging Framework" defines, using XML technologies, an extensible messaging framework containing a message construct that can be exchanged over a variety of underlying protocols.

- history

SOAP Version 1.2 is a lightweight protocol intended for exchanging structured information in a decentralized, distributed environment. SOAP Version 1.2 Part 2: Adjuncts defines a set of adjuncts that may be used with SOAP Version 1.2 Part 1: Messaging Framework. This specification depends on SOAP Version 1.2 Part 1: Messaging Framework [SOAP Part 1].

- history

This document draws on assertions found in the SOAP Version 1.2 specifications [SOAP Part 1], [SOAP Part 2], and provides a set of tests in order to show whether the assertions are implemented in a SOAP processor.

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, 2007 04 27. It is incorrect to claim to be compliant with the SOAP Version 1.2 specifications merely by passing successfully all the tests provided in this test suite. It is also incorrect to claim that an implementation is non compliant with the SOAP Version 1.2 specifications based on its failure to pass one or more of the tests in this test suite.

- history

This document describes the semantics and serialization of a SOAP header block for carrying resource representations in SOAP messages.

- history

This document describes an abstract feature and a concrete implementation of it for optimizing the transmission and/or wire format of SOAP messages. The concrete implementation relies on the [XML-binary Optimized Packaging] format for carrying SOAP messages.

- history
1 translation for XML-binary Optimized Packaging
português

This document defines the XML-binary Optimized Packaging (XOP) convention, a means of more efficiently serializing XML Infosets that have certain types of content.

Notes

- history

SOAP Version 1.2 Part 2 provides a request-response MEP and a response-only MEP. This, the SOAP 1.2 Part 3, provides a one-way MEP.

- history

This document addresses the need to indicate the content-type associated with binary element content in an XML document and the need to specify, in XML Schema, the expected content-type(s) associated with binary element content. It is expected that the additional information about the content-type will be used for optimizing the handling of binary data that is part of a Web services message.

- history

This document defines a SOAP feature that represents an abstract model for SOAP attachments. It provides the basis for the creation of SOAP bindings that transmit such attachments along with a SOAP envelope, and provides for reference of those attachments from the envelope. SOAP attachments are described using the notion of a compound document structure consisting of a primary SOAP message part and zero or more related documents parts known as attachments.

- history

This document lists and provides answers to some frequently asked questions about the design decisions behind the choice of include mechanism by the XML Protocol Working Group during construction of XML-binary Optimized Packaging (XOP). For more information about XOP, see the Working Group Home Page.

- history

SOAP 1.2 intermediaries have some license when reserializing messages that pass through them. This document defines a transformation algorithm that renders all semantically equivalent SOAP messages identically. The transformation may be used in conjunction with an XML canonicalization algorithm prior to the generation of a message digest in producing XML digital signatures that are sufficiently robust to survive passage through one or more SOAP intermediaries.

- history

This document describes the SOAP Usage Scenarios and how they may be implemented using the SOAP 1.2 specification.

- history

This document describes the XML Protocol Working Group's requirements for the XML Protocol (XMLP) specification.

- history

This document is meant to be an illustration of the SOAP 1.2 Protocol Binding Framework applied to a well known internet transport mechanism, Email, specifically rfc2822.

Retired specifications