1.1 Glossary

This document uses the following terms:

action: (1) The smallest unit of work in a workflow system. An action can contain one or more tasks that define work that actors need to do. Actions are deployed and registered in the workflow system to be activated by protocol client users.

(2) A discrete operation that is executed on an incoming Message object when all conditions in the same rule (2) are TRUE. A rule contains one or more actions.

address book: A collection of Address Book objects, each of which are contained in any number of address lists.

binary large object (BLOB): A discrete packet of data that is stored in a database and is treated as a sequence of uninterpreted bytes.

client-side rule: A rule that has at least one action that is executed by a client because it cannot be executed by a server.

condition: A logical expression comparing one or more properties in all incoming Message objects against a set of clauses. This logical expression can evaluate to TRUE or FALSE.

contents table: A Table object whose rows represent the Message objects that are contained in a Folder object.

Deferred Action Folder (DAF): A special folder where a server places all Deferred Action Messages and Deferred Error Messages to be acted on by a client. The Deferred Action Folder is not visible to a user.

Deferred Action Message (DAM): A hidden message indicating to a client that it needs to execute one or more rules on another user-visible message in the store.

Deferred Error Message (DEM): A hidden message indicating to a client that it needs to present the user with an error indicating that a server-side rule failed to execute.

delegate: A user or resource that has permissions to act on behalf of another user or resource.

entry ID: See EntryID.

EntryID: A sequence of bytes that is used to identify and access an object.

extended rule: A rule that is added to, modified, and deleted from a server by using a mechanism other than standard rules, but is otherwise functionally identical to a standard rule.

FAI contents table: A table of folder associated information (FAI) Message objects that are stored in a Folder object.

flags: A set of values used to configure or report options or settings.

folder associated information (FAI): A collection of Message objects that are stored in a Folder object and are typically hidden from view by email applications. An FAI Message object is used to store a variety of settings and auxiliary data, including forms, views, calendar options, favorites, and category lists.

Folder object: A messaging construct that is typically used to organize data into a hierarchy of objects containing Message objects and folder associated information (FAI) Message objects.

globally unique identifier (GUID): A term used interchangeably with universally unique identifier (UUID) in Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the value. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the GUID. See also universally unique identifier (UUID).

handle: Any token that can be used to identify and access an object such as a device, file, or a window.

hard delete: A process that removes an item permanently from the system. If an item is hard deleted, a server does not retain a back-up copy of the item and a client cannot access or restore the item. See also soft delete.

Inbox folder: A special folder that is the default location for Message objects received by a user or resource.

little-endian: Multiple-byte values that are byte-ordered with the least significant byte stored in the memory location with the lowest address.

Logon object: A Server object that provides access to a private mailbox or a public folder. A client obtains a Logon object by issuing a RopLogon remote operation (ROP) to a server.

mailbox: A message store that contains email, calendar items, and other Message objects for a single recipient.

Message object: A set of properties that represents an email message, appointment, contact, or other type of personal-information-management object. In addition to its own properties, a Message object contains recipient properties that represent the addressees to which it is addressed, and an attachments table that represents any files and other Message objects that are attached to it.

message store: A unit of containment for a single hierarchy of Folder objects, such as a mailbox or public folders.

named property: A property that is identified by both a GUID and either a string name or a 32-bit identifier.

Out of Office (OOF): One of the possible values for the free/busy status on an appointment. It indicates that the user will not be in the office during the appointment.

Out of Office rule: A rule that is only evaluated when the mailbox is in an Out of Office state.

property ID: A 16-bit numeric identifier of a specific attribute (1). A property ID does not include any property type information.

property tag: A 32-bit value that contains a property type and a property ID. The low-order 16 bits represent the property type. The high-order 16 bits represent the property ID.

public folder: A Folder object that is stored in a location that is publicly available.

recipient: (1) An entity that can receive email messages. 

(2) An entity that is in an address list, can receive email messages, and contains a set of attributes (1). Each attribute has a set of associated values.

remote operation (ROP): An operation that is invoked against a server. Each ROP represents an action, such as delete, send, or query. A ROP is contained in a ROP buffer for transmission over the wire.

remote procedure call (RPC): A context-dependent term commonly overloaded with three meanings. Note that much of the industry literature concerning RPC technologies uses this term interchangeably for any of the three meanings. Following are the three definitions: (*) The runtime environment providing remote procedure call facilities. The preferred usage for this meaning is "RPC runtime". (*) The pattern of request and response message exchange between two parties (typically, a client and a server). The preferred usage for this meaning is "RPC exchange". (*) A single message from an exchange as defined in the previous definition. The preferred usage for this term is "RPC message". For more information about RPC, see [C706].

restriction: A filter used to map some domain into a subset of itself, by passing only those items from the domain that match the filter. Restrictions can be used to filter existing Table objects or to define new ones, such as search folder (2) or rule criteria.

ROP request: See ROP request buffer.

ROP request buffer: A ROP buffer that a client sends to a server to be processed.

ROP response: See ROP response buffer.

ROP response buffer: A ROP buffer that a server sends to a client to be processed.

rule: (1) A condition or action, or a set of conditions or actions, that performs tasks automatically based on events and values.

(2) An item that defines a condition and an action. The condition is evaluated for each Message object as it is delivered, and the action is executed if the new Message object matches the condition.

Rule FAI message: A folder associated information (FAI) message stored in the Inbox special folder where the client can store extra rule-related information that is opaque to the server.

rule provider: A client application that creates and maintains a specific rule. The application is identified by a unique, well-known string, which is saved as a property on the rule.

rules table: A Table object whose rows represent the rules that are contained in a Folder object.

server-side rule: A rule for which all actions are executed by a server.

Short Message Service (SMS): A communications protocol that is designed for sending text messages between mobile phones.

special folder: One of a default set of Folder objects that can be used by an implementation to store and retrieve user data objects.

standard rule: A rule that is created, modified, or deleted by using the RopModifyRules remote operation.

Table object: An object that is used to view properties for a collection of objects of a specific type, such as a Message object or a Folder object. A Table object is structured in a row and column format with each row representing an object and each column representing a property of the object.

Unicode: A character encoding standard developed by the Unicode Consortium that represents almost all of the written languages of the world. The Unicode standard [UNICODE5.0.0/2007] provides three forms (UTF-8, UTF-16, and UTF-32) and seven schemes (UTF-8, UTF-16, UTF-16 BE, UTF-16 LE, UTF-32, UTF-32 LE, and UTF-32 BE).

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.