This page describes the profile of SOAP that CategoryTools are expected to support to use a WellFormedEntry. For a counter-argument, see JakeSavin's Use XML-RPC.
This profile (Message Exchange Pattern?) is based on SOAP Version 1.2 Part 1: Messaging Framework
-
Tools must support a SOAP Envelope.
-
WellFormedEntry does not, at this time, define any of its own SOAP header blocks.
-
Implementations may define SOAP header blocks for their own use. See BloggerProposals for an example.
-
The body of a SOAP envelope is a DocumentLiteral, effectively containing the XML that would be sent if a SOAP profile had not been used.
-
WellFormedEntry will use SOAP in the REST Architectural Style, that is to say, "actions to be performed" are not defined in SOAP headers but are based on the URIs used and the body content. (still in discussion)
-
SOAP RPC Representation and SOAP Encoding are not used.
-
XML Base is supported for determining a base URI for relative URI references used as values in information items. Same as if a SOAP profile were not used.
-
SOAP receivers (both requestors and providers in a request/response interaction) must process the SOAP message as in Processing SOAP Messages:
-
Determine the set of roles in which the node is to act. The contents of the SOAP envelope, including any SOAP header blocks and the SOAP body, MAY be inspected in making such determination.
-
Identify all header blocks targeted at the node that are mandatory [have an env:MustUnderstand='true' attribute].
-
If one or more of the SOAP 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 SOAP body MUST NOT be generated in this step.
-
Process all mandatory SOAP header blocks targeted at the node and, in the case of an ultimate SOAP receiver, the SOAP body. A SOAP node MAY also choose to process non-mandatory SOAP header blocks targeted at it.
-
SOAP receivers must return a SOAP message or SOAP fault in response to a SOAP request.
-
HTTP is the reference transfer protocol for WellFormedEntry SOAP messages, but implementations are not restricted to HTTP.
-
It is not clear that this profile adopts the SOAP HTTP Binding.
-
It is not clear that this profile adopts the SOAP Request-Response Message Exchange Pattern.
[DeveloperDude] PSSAPI You can start using this API now with RSS and I'll mold it into Pie/Echo as it progresses.