1.1 Glossary

This document uses the following terms:

base64 encoding: A binary-to-text encoding scheme whereby an arbitrary sequence of bytes is converted to a sequence of printable ASCII characters, as described in [RFC4648].

callback context: The context that is required for a server to make callbacks to a client. A callback context consists of an endpoint reference for a client endpoint with an optional context identifier.

client: A computer on which the remote procedure call (RPC) client is executing.

Client Context Initiating Message: A client message that requests a server to establish a context.

client message: A message that is sent from a client to a server.

connection: A time-bounded association between two endpoints that allows the two endpoints to exchange messages.

context: An abstract concept that represents an association between a resource and a set of messages that are exchanged between a client and a server. A context is uniquely identified by a context identifier.

context identifier: A GUID that identifies a context.

Context Participating Message: A client message or a server message that is one of a set of messages associated with a context.

endpoint: A communication port that is exposed by an application server for a specific shared service and to which messages can be addressed.

endpoint reference (EPR): A resource that conveys the information that is needed to address an endpoint.

server: A computer on which the remote procedure call (RPC) server is executing.

Server Context Establishing Message: A server message that establishes a new context and is correlated to a Client Context Initiating Message.

server message: A message that is sent from a server to a client.

SOAP: A lightweight protocol for exchanging structured information in a decentralized, distributed environment. SOAP uses XML technologies to define an extensible messaging framework, which provides a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation-specific semantics. SOAP 1.2 supersedes SOAP 1.1. See [SOAP1.2-1/2003].

SOAP envelope: A container for SOAP message information and the root element of a SOAP document. See [SOAP1.2-1/2007] section 5.1 for more information.

SOAP fault: A container for error and status information within a SOAP message. See [SOAP1.2-1/2007] section 5.4 for more information.

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.

UTF-8: A byte-oriented standard for encoding Unicode characters, defined in the Unicode standard. Unless specified otherwise, this term refers to the UTF-8 encoding form specified in [UNICODE5.0.0/2007] section 3.9.

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.