- initial SOAP sender
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
The SOAP sender that originates a SOAP message at the starting point of a SOAP message path.
- SOAP
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
The formal set of conventions governing the format and processing rules of a SOAP message. These conventions include the interactions among SOAP nodes generating and accepting SOAP messages for the purpose of exchanging information along a SOAP message path.The embodiment of the processing logic necessary to transmit, receive, process and/or relay a SOAP message, according to the set of conventions defined by this recommendation. A SOAP node is responsible for enforcing the rules that govern the exchange of SOAP messages (see 2. SOAP Processing Model). It accesses the services provided by the underlying protocols through one or more SOAP bindings.A SOAP receiver's expected function in processing a message. A SOAP receiver can act in multiple roles.The formal set of rules for carrying a SOAP message within or on top of another protocol (underlying protocol) for the purpose of exchange (see 4. SOAP Protocol Binding Framework). Examples of SOAP bindings include carrying a SOAP message within an HTTP entity-body, or over a TCP stream.An extension of the SOAP messaging framework (see 3. SOAP Extensibility Model). Examples of features include "reliability", "security", "correlation", "routing", and "Message Exchange Patterns" (MEPs).A SOAP Module is a specification that contains the combined syntax and semantics of SOAP header blocks specified according to the rules in 3.3 SOAP Modules. A SOAP module realizes zero or more SOAP features.A template for the exchange of SOAP messages between SOAP nodes enabled by one or more underlying SOAP protocol bindings (see 4. SOAP Protocol Binding Framework). A SOAP MEP is an example of a SOAP feature (see 3.2 SOAP Message Exchange Patterns (MEPs)).An entity, typically software, that produces, consumes or otherwise acts upon SOAP messages in a manner conforming to the SOAP processing model (see 2. SOAP Processing Model).
- SOAP application
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
An entity, typically software, that produces, consumes or otherwise acts upon SOAP messages in a manner conforming to the SOAP processing model (see 2. SOAP Processing Model).
- SOAP binding
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
The formal set of rules for carrying a SOAP message within or on top of another protocol (underlying protocol) for the purpose of exchange (see 4. SOAP Protocol Binding Framework). Examples of SOAP bindings include carrying a SOAP message within an HTTP entity-body, or over a TCP stream.
- SOAP body
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
A collection of zero or more element information items targeted at an ultimate SOAP receiver in the SOAP message path (see 5.3 SOAP Body).
- SOAP envelope
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
The outermost element information item of a SOAP message.
- SOAP fault
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
A SOAP element information item which contains fault information generated by a SOAP node.
- SOAP feature
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
An extension of the SOAP messaging framework (see 3. SOAP Extensibility Model). Examples of features include "reliability", "security", "correlation", "routing", and "Message Exchange Patterns" (MEPs).
- SOAP header
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
A collection of zero or more SOAP header blocks each of which might be targeted at any SOAP receiver within the SOAP message path.An element information item used to delimit data that logically constitutes a single computational unit within the SOAP header. The type of a SOAP header block is identified by the XML expanded name of the header block element information item.
- SOAP header block
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
An element information item used to delimit data that logically constitutes a single computational unit within the SOAP header. The type of a SOAP header block is identified by the XML expanded name of the header block element information item.
- SOAP intermediary
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
A SOAP intermediary is both a SOAP receiver and a SOAP sender and is targetable from within a SOAP message. It processes the SOAP header blocks targeted at it and acts to forward a SOAP message towards an ultimate SOAP receiver.
- SOAP message
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
The basic unit of communication between SOAP nodes.
- SOAP message exchange pattern (MEP)
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
A template for the exchange of SOAP messages between SOAP nodes enabled by one or more underlying SOAP protocol bindings (see 4. SOAP Protocol Binding Framework). A SOAP MEP is an example of a SOAP feature (see 3.2 SOAP Message Exchange Patterns (MEPs)).
- SOAP message path
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
The set of SOAP nodes through which a single SOAP message passes. This includes the initial SOAP sender, zero or more SOAP intermediaries, and an ultimate SOAP receiver.
- SOAP module
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
A SOAP Module is a specification that contains the combined syntax and semantics of SOAP header blocks specified according to the rules in 3.3 SOAP Modules. A SOAP module realizes zero or more SOAP features.
- SOAP node
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
The embodiment of the processing logic necessary to transmit, receive, process and/or relay a SOAP message, according to the set of conventions defined by this recommendation. A SOAP node is responsible for enforcing the rules that govern the exchange of SOAP messages (see 2. SOAP Processing Model). It accesses the services provided by the underlying protocols through one or more SOAP bindings.
- SOAP receiver
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
A SOAP node that accepts a SOAP message.
- SOAP role
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
A SOAP receiver's expected function in processing a message. A SOAP receiver can act in multiple roles.
- SOAP sender
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
A SOAP node that transmits a SOAP message.
- ultimate SOAP receiver
-
From SOAP Version 1.2 Part 1: Messaging Framework (2003-06-24)
The SOAP receiver that is a final destination of a SOAP message. It is responsible for processing the contents of the SOAP body and any SOAP header blocks targeted at it. In some circumstances, a SOAP message might not reach an ultimate SOAP receiver, for example because of a problem at a SOAP intermediary. An ultimate SOAP receiver cannot also be a SOAP intermediary for the same SOAP message (see 2. SOAP Processing Model).