1.1 Glossary

  • Article

This document uses the following terms:

node: An endpoint in the computer network that can receive, send, or process a SOAP message, as specified in [SOAP1.2-2/2007].

packet routing: A routing algorithm that directs a message from a source to an ultimate destination through intermediate routers without guaranteeing that subsequent messages between the source and destination will take the same path.

router: An endpoint that receives messages from a node and forwards those messages to the next node based on a routing algorithm.

routing algorithm: An algorithm used to determine the next destination node for a specific message.

SOAP header: A mechanism for implementing extensions to a SOAP message in a decentralized manner without prior agreement between the communicating parties. See [SOAP1.2-1/2007] section 5.2 for more information.

SOAP message: An XML document consisting of a mandatory SOAP envelope, an optional SOAP header, and a mandatory SOAP body. See [SOAP1.2-1/2007] section 5 for more information.

SOAP mustUnderstand attribute: A global, Boolean attribute that is used to indicate whether a header entry is mandatory or optional for the recipient to process. See [SOAP1.2-1/2007] section 5.2.3 for more information.

SOAP packet: A SOAP message that does not have a behavioral dependency on the path taken to deliver the message from the source to the destination.

MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.