1.1 Glossary

This document uses the following terms:

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

Address Book object: An entity in an address book that contains a set of attributes, each attribute with a set of associated values.

calendar: A date range that shows availability, meetings, and appointments for one or more users or resources. See also Calendar object.

Calendar object: A Message object that represents an event, which can be a one-time event or a recurring event. The Calendar object includes properties that specify event details such as description, organizer, date and time, and status.

Calendar special folder: A Calendar folder that is in a user's mailbox and in which meetings are created by default.

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

delegate data folder: A special folder that contains the Delegate Information object.

Delegate Information object: A Message object that contains properties specifying delegate access settings for resources in a delegator's mailbox.

delegate rule: A server-side rule that is used to send mail to delegates on behalf of a delegator.

delegator: A user or resource for which another user or resource has permission to act on its behalf.

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

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

informational update: A Meeting Update object that includes a change that does not require attendees to respond again, such as additional agenda details.

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

Meeting Request object: A Message object that represents an invitation from the meeting organizer to an attendee.

Meeting Response object: A Message object that represents an attendee's response to a meeting organizer's invitation. The response indicates whether the attendee accepted, tentatively accepted, or declined the meeting request. The response can include a proposed new date or time for the meeting.

meeting-related object: A Message object that represents a relay of information between a meeting organizer and an attendee. It can be any of the following: Meeting Request object, Meeting Update object, Meeting Cancellation object, or Meeting Response object.

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.

multivalue property: A property that can contain multiple values of the same type.

permission: A rule that is associated with an object and that regulates which users can gain access to the object and in what manner. See also rights.

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].

remote user: A user who has a persistent identity within an enterprise and is connected from outside the enterprise network boundary.

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.

Root folder: The special folder that is the top-level folder in a message store hierarchy. It contains all other Folder objects in that message store.

ROP response: See ROP response buffer.

rule: 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.

send on behalf: A special permission that is granted to a delegate. It allows the delegate to send Message objects representing the delegator.

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

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

Task object: A Message object that represents an assignment to be completed.

task request: A Message object that is used to issue a task assignment.

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.