NETCONF Over SOAP [PDF]

"Regardless of the protocol to which SOAP is bound, messages are routed along a so-called 'message path', which allows for processing at one or more intermediate nodes in addition to the ultimate destination".

The SOAP Digest Authentication Proposal offers a means to control access to SOAP services using a Digest Authentication scheme similar to that specified in RFC2617 . It is implemented as a SOAP extension, embodied in a collection of SOAP Header blocks.

This specification outlines a (proposed) SOAP service interface that can be implemented by SOAP implementations as part of an interoperability testing process. It introduces standard headers for use in testing header processing.

The SOAP Specification defines SOAP attachments as a way to include MIME data in or associated with SOAP messages. Some web service designs use SOAP attachments to pass typed files between a client and a web service. This topic describes how WebLogic Workshop web services can send and receive MIME messages as SOAP attachments.

Since the SOAP specification left security issues open, several proposals evolved to bridge the security gaps. Recently the SOAP Security Extension [SOAP-SEC] was published as a W3C Note, specifically addressing the XML Digital Signature.

As you may know by now, SOAP 1.2 has reached Proposed Recommendation (PR) status, which means that the XML Protocol Working Group believes that it's done.

XML-RPC is a simple request/reply protocol that runs over HTTP. It is simple, easy to implement and supported by most programming languages. Twisted's XML-RPC support is implemented using the xmlrpclib library that is included with Python 2.2 and later.

Simple Object Access Protocol or SOAP, is the protocol for accessing a Web Service. It is an open standard being maintained by the W3C. SOAP is based on XML so the advantages of data transfer that XML has pertain to SOAP as well such as platform independence, language independent, extensible, and a W3C standard.

The desire to integrate XML with pre-existing data formats has been a long-standing and persistent issue for the XML community. Users often want to leverage the structured, extensible markup conventions of XML without abandoning existing data formats that do not readily adhere to XML 1.0 syntax. Often, users want to leave their existing non-XML formats as is, to be treated as opaque sequences of octets by XML tools and infrastructure.

How can we effectively make the treasures contained in TPF systems available to the clients and agents on the World Wide Web? [PDF]

For a variety of reasons, it is desirable that some web services, compliant with the SOAP HTTP Binding, can also be accessed via HTTP GET. This requirement mandates that the information necessary to access the resource can be expressed in an HTTUP URI.

This object is passed as a parameter to the handler function for SOAP requests. These handlers are specified by the onComplete property of the SOAP request object. Response objects contain either s response payload or error information.

The HTTP transport specifies how to route a SOAP request using the HyperText Transfer Protocol. This transport is the default for new SOAP requests.

SOAP messages require a body so the traditional HTTP GET message insufficient to convey a SOAP request. The solution is to use POST.

If the SOAP node is a SOAP intermediary, the SOAP message pattern and results of processing (e.g. no fault generated) MAY require that the SOAP message be sent further along the SOAP message path.

Building Blocks of Web Services: SOAP, WSDL, UDDI, and ebXML. [PDF]

This paper describes some of the properties expected of a SOAP based message path model and proposes that such a model expressed as a SOAP header entry would be within the realm of a W3C standardization initiative.

These are intended to allow testing of the "relay" attribute information item defined in SOAP 1.2 REC and supplement the tests found in the SOAP 1.2 Assertions and Test Collection.

By default, a WebLogic Web Service uses SOAP 1.1 as the message format when a client application invokes one of its operations.