This is Table 4, originally part of the SOAP Implementation Summary Page. It lists features that were once in Table 2 of the Summary Page but have subsequently been superseded, modified or deleted. The Notes on Table 2 should apply to all entries in Table 4.
| ID Number | Spec Part | Spec Section | Category | Implementation Feature | Assertions | Implementations | Test(s) | Feature Notes | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 60 | 2 | 4.2.2 | Support of RPC Fault Handling mechanism and fault generation. | 107, 110 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0037.html; includes 56 per [1]; minor rewording per [2]; split into 60.1. and 60.2 per [4] | |||||||
| 38 | 2 | 7.5.1.2, 7.5.2.2 | Supports all specified HTTP status codes. | 133, 134, 135 | Y (partial) | Y' | Y | N (planned) | Y | Suggest that we limit this to the fault codes that are tied to SOAP faults as described in part 2, table 19 as this would otherwise be a test for which much is not relevant to SOAP (see also 41) | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; includes 39 per [1]. Split into 38.1 .2 .3 .4 .5 per [3] | |
| 52 | 2 | 4 | Supports the use of SOAP RPC Representation with other MEPs | -- | Y (in principle, untested) | N | N (awaiting WSD support) | Y | N (unsure about feature defn) | missing | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0037.html; subsumed by 31.* and 32.* per [3] | |
| 31 | 2 | 6.2 | Message Exchange Patterns | Supports Request-Response Message Exchange Pattern | 32, 33, 114, 115, 116, 117, 118, 130 | Y | Y' | Y | Y | Y | R* | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; split into features 31.1 and 31.2 per [3] |
| 32 | 6.3 | Supports SOAP Response Message Exchange Pattern | 121, 122, 123, 124 | Y | N | N | Y | N | missing | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; split into features 32.1 and 32.2 per [3] | ||
| 77 | 2 | 3.2 | Implementation supports decoding faults | N | Y | Y | Y | Y | created in [1]; superseded by 77.1 per [2] | |||
| 76 | 2 | 3.1.4, 3.1.5 | Implementation supports encoding references | Y | Y' | Y | Y | N | created in [1]; duplicate of 27.5 per [2] | |||
| 29 | 2 | 3 | Supports multiple encoding schemes | -- | Y (difficult) | Y' (if literal is a scheme) | Y (SOAP Enc and Literal) | Y (SOAP Enc and Literal) | Y | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; replaced by 29.1 per [2] | ||
| 25 | 2 | 3.1.1 | Allows the inline (embedded) serialization of multiref values | 88 | Y | Y' | Y | Y | Y | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; duplicate of 27.5, per [2] | ||
| 24 | 2 |
3.1.1 3.1.3 |
Supports the SOAP Encoding | 87, 90 | Y (partial) | Y' | Y | Y | Y | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, modified per [1]; duplicate of 27.1, per [2] | ||
| 6 | 1 | 2.4 | Supports mustUnderstand attribute information item in the header block | 16 | Y | Y' | Y | Y | Y | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; removed per [2], duplicate of 19 | ||
| 1.3 | 1 | 2.7 | Relaying SOAP messages - intermediary. | Y (possible) | Y | N | Y | N (yes with user written handler) | derived from 1, per [1]; removed per [2] | |||
| 53.2 | 2 | 4.2.1 | Supports RPC invocation as arrays where parameter access is by position | 104 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0037.html; derived from 53 per [1]. Arrays removed from RPC. | |||||||
| 27.4 | 2 | Supports generics | 91, 92, 93 | derived from 27 per [1]. Generics removed from SOAP 1.2. | ||||||||
| 61 | 1 | 1.2 | >Specifications for the processing of application-defined data carried in a SOAP message but not defined by this specification MAY call for additional validation of the SOAP message in conjunction with application-level processing. | -- | filtered version of http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html, deleted per [1] | |||||||
| 62 | 1 | 1.2 | The media type "application/soap+xml" [13] SHOULD be used for XML 1.0 serializations of the SOAP message infoset. | -- | filtered version of http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html, dupe of #34 per [1] | |||||||
| 1 | 1 |
2.1 2.5 2.6 |
Messaging Framework – Processing SOAP Messages | Supports SOAP nodes to transmit, receive, process and/or relay a SOAP message – initial SOAP sender, ultimate SOAP receiver, or a SOAP intermediary | 5, 6, 18, 21 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, split into 1.1, 1.2, 1.3 per [1] | ||||||
| 3 | 1 | 2.2 | Routing single message over multiple hops | -- | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, deleted per [1] | |||||||
| 4 | 1 | 2.3 | Supports SOAP header block targeted at a SOAP node operating in specified role | 12, 13 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, dupe of 2 per [1] | |||||||
| 5 | 1 | 2.3 | Supports SOAP header block targeted at a special role | 14 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, split into 5.1, 5.2, 5.3 per [1] | |||||||
| 63 | 1 | 2.6 | SOAP nodes MAY make reference to any information in the SOAP envelope when processing a SOAP body or SOAP header block. | -- | filtered version of http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html, deleted per [1] | |||||||
| 64 | 1 | 2.6 | The processing of one or more SOAP header blocks MAY control or determine the order of processing for other SOAP header blocks and/or the SOAP body. | -- | filtered version of http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html, deleted per [1] | |||||||
| 65 | 1 | 2.6 | Header blocks MAY be processed in arbitrary order. Header block processing MAY precede, MAY be interleaved with, or MAY follow processing of the body. | -- | filtered version of http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html, deleted per [1] | |||||||
| 66 | 1 | 2.7.1 | The semantics of one or more SOAP header blocks in a SOAP message, or the SOAP MEP used MAY require that the SOAP message be forwarded to another SOAP node on behalf of the initiator of the inbound SOAP message. | -- | filtered version of http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html, deleted per [1] | |||||||
| 67 | 1 | 2.7.2 | In addition to the processing performed by forwarding intermediaries, active intermediaries undertake additional processing that can modify the outbound message in ways not described in the inbound message. That is, they can undertake processing not described by SOAP header blocks in the incoming message. | -- | filtered version of http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html, deleted per [1] | |||||||
| 10 | 1 | 5 | Supports zero or more character information item children in an element information items | 43 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, deleted per [1] | |||||||
| 68 | 1 | 5 | A SOAP intermediary MAY ignore such insignificant character information items when forwarding (see 2.7 Relaying SOAP Messages) a message. | -- | filtered version of http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html; duplicate of 11 and deleted per [1]. | |||||||
| 12 | 1 | 5.1 | Supports SOAP Envelope element information item: Envelope, [namespace name], zero or more namespace qualified attribute information items, and one or two element information item (optional Header and/or mandatory Body element information items) | 44 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, obsoleted by 9 per [1] | |||||||
| 14 | 1 | 5.1.1 | Scope of encodingStyle attribute information item | 47, 48 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, merged into 13 per [1] | |||||||
| 15 | 1 | 5.2 | Supports SOAP Header element information item: Header, [namespace name], zero or more namespace qualified attribute information items, and zero or more namespace qualified element information items | 50 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, obsoleted by 9 per [1] | |||||||
| 16 | 1 | 5.2.1 | Supports SOAP header block (child element information item of the SOAP Header): qualified namespace, may have any number of character information item children, may have an encodingStyle attribute information item, may have a role attribute information item, and may have a mustUnderstand attribute information item | 51 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, obsoleted by 9 per [1] | |||||||
| 17 | 1 | 5.1.1 | Use of role and mustUnderstand attributes in SOAP header blocks and descendants | 52 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, obsoleted by 2 and 9 per [1] | |||||||
| 18 | 1 | 5.2.2 |
Supports SOAP role attribute information item
|
53, 54, 55, 56 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; merged into 2 per [1]. | |||||||
| 69 | 1 | 5.2.2 | If relaying a SOAP message, a SOAP intermediary MAY discard the SOAP role attribute information item for SOAP header blocks when the value of the role attribute information item is "http://www.w3.org/2002/06/soap-envelope/role/ultimateReceiver" (see 2.7 Relaying SOAP Messages). | -- | filtered version of http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html; duplicated by other features and deleted per [1]. | |||||||
| 70 | 1 | 5.2.3 | If relaying the message, a SOAP intermediary MAY substitute "true" for the value "1", or "false" for "0". The SOAP mustUnderstand attribute information item MAY be omitted if its value would have been "false" or "0". | -- | filtered version of http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0033.html; duplicates other features and deleted per [1]. | |||||||
| 20 | 1 | 5.3 | Supports SOAP Body element information item: Body, [namespace name], zero or more namespace qualified attribute information items, and zero or more namespace qualified element information items | 61 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, obsoleted by 9 per [1] | |||||||
| 21 | 1 | 5.3.1 | Supports SOAP Body child element: qualified namespace, may have an encodingStyle attribute information item, and may have any number of character information item children. | 62 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, obsoleted by 9 per [1] | |||||||
| 22 | 2 | 2 | Data Model | Supports representation of application-defined data structures and values including mapping of non-XML-based data | -- | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, deleted per [1] | ||||||
| 23 | 2 | 3.1 | SOAP Encoding | Supports multiple serialized graph-based representations at all nodes | 86 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, obsoleted by 29 per [1] | ||||||
| 26 | 2 | 3.1.3 | Support of global and locally scoped namespaces | 91 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, deleted per [1] (no longer in SOAP spec) | |||||||
| 27 | 2 |
3.1.3 3.1.5.1 3.1.5.2 3.1.5.3 3.1.6 |
Supports encoding/decoding of simple and compound data types and values | 92, 93, 97, 98, 99, 100, 101 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, split into 27.1, 27.2, 27.3, 27.4, 27.5 per [1] | |||||||
| 28 | 2 |
3.1.3 3.1.4 3.1.4.1 |
Supports itemType attribute information item and properties | 94, 95, 96 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; obsoleted by 27.3 and deleted per [1]. | |||||||
| 30 | 2 | 4 | RPC | TBD | TBD | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, see features 51-60 | ||||||
| 35 |
1 2 |
4.2 7.3 |
Supports Message Exchange Patterns:
|
32, 33 130 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, duplicate of 31 and 32 per [1] | |||||||
| 36 | 2 | 7.4 | Supports of Web Method Feature | 131 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; duplicate of 33 per [1]. | |||||||
| 37 | 2 | 7.5.1 | Supports streaming and prevention of deadlocks | 132 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html, deleted per [1] (not in SOAP spec) | |||||||
| 39 | 2 | 7.5.2.2 | State description of responding SOAP node and HTTP statues code | 135 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; merged into 38 per [1]. | |||||||
| 40 | 1 | 4.2 | Binding using XML 1.0 serialization | 36, 37 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; deleted per [1]. | |||||||
| 42 | 1 |
5.4.1 5.4.1.1 5.4.1.2 5.4.1.3 |
Supports SOAP Code element information item: Code, [namespace name], one or two child element information items in its [children] property with mandatory Value element information item, and optional Subcode element information item | 66, 67, 68, 69 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html | |||||||
| 43 | 1 | 5.4.2 | Supports SOAP Reason element information item | 70, 71 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html | |||||||
| 44 | 1 | 5.4.3 | Supports SOAP Node element information item | 72, 73 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html | |||||||
| 45 | 1 | 5.4.4 | Supports SOAP Role element information item | 74 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html | |||||||
| 46 | 1 | 5.4.5 | Supports SOAP Detail element information item and detail child element information items | 75, 76 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html | |||||||
| 50 | 1, 2 |
Various 3.2 |
Supports error handling mechanism and fault generation for SOAP messaging processing, serialization, RPC, and binding | 102, 110 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0012.html; deleted per [1]. | |||||||
| 53 | 2 | 4.2.1 | Supports RPC invocation via struct where parameter access is by name or arrays where parameter access is by position | 104 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0037.html; split into 53.1 and 53.2 per [1]. | |||||||
| 55 | 2 | 4.2.2 | Supports RPC response via struct where parameter access is by name or arrays where parameter access is by position. | 106 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0037.html; duplicate of 53 and deleted per [1]. | |||||||
| 56 | 2 | 4.2.2 | RPC response must not contain both a result and a fault | 107 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0037.html; appended to 60 per [1]. | |||||||
| 57 | 2 | 4 | Supports all encoding styles of the RPC representation | -- | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0037.html; deleted per [1]. | |||||||
| 58 | 2 | 4.2.3 | SOAP encoding and RPC: SOAP Body must contain only a single child element information item, that child being the serialized RPC invocation or response struct or array. | 108 | origin http://lists.w3.org/Archives/Member/w3c-xml-protocol-wg/2002Jul/0037.html; covered by 53 and deleted per [1]. | |||||||
David
Fallside, Yves Lafon