1.1 Glossary

This document uses the following terms:

8.3 name: A file name string restricted in length to 12 characters that includes a base name of up to eight characters, one character for a period, and up to three characters for a file name extension. For more information on 8.3 file names, see [MS-CIFS] section

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 container: An Address Book object that describes an address list.

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

address list: A collection of distinct Address Book objects.

address type: An identifier for the type of email address, such as SMTP and EX.

alias: An alternate name that can be used to reference an object or element.

ambiguous name resolution (ANR): A search algorithm that permits a client to search multiple naming-related attributes (2) on objects by way of a single clause of the form "(anr=value)" in a Lightweight Directory Access Protocol (LDAP) search filter. This permits a client to query for an object when the client possesses some identifying material related to the object but does not know which attribute of the object contains that identifying material.

Appointment object: A Calendar object that has an organizer but no attendees.

archive tag: An element that contains information about the archive policy of a Message object or folder.

Attachment object: A set of properties that represents a file, Message object, or structured storage that is attached to a Message object and is visible through the attachments table for a Message object.

Augmented Backus-Naur Form (ABNF): A modified version of Backus-Naur Form (BNF), commonly used by Internet specifications. ABNF notation balances compactness and simplicity with reasonable representational power. ABNF differs from standard BNF in its definitions and uses of naming rules, repetition, alternatives, order-independence, and value ranges. For more information, see [RFC5234].

blind carbon copy (Bcc) recipient: An addressee on a Message object that is not visible to recipients of the Message object.

body part: A part of an Internet message, as described in [RFC2045].

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

Calendar folder: A Folder object that contains Calendar objects.

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.

carbon copy (Cc) recipient: An address on a Message object that is visible to recipients of the Message object but is not necessarily expected to take any action.

class: User-defined binary data that is associated with a key.

common name (CN): A string attribute of a certificate (1) that is one component of a distinguished name (DN). In Microsoft Enterprise uses, a CN must be unique within the forest where it is defined and any forests that share trust with the defining forest. The website or email address of the certificate owner is often used as a common name. Client applications often refer to a certification authority (CA) by the CN of its signing certificate.

contact: A person, company, or other entity that is stored in a directory and is associated with one or more unique identifiers and attributes (2), such as an Internet message address or login name.

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

conversation: A single representation of a send/response series of email messages. A conversation appears in the Inbox as one unit and allows the user to view and read the series of related email messages in a single effort.

conversation action: A limited set of actions that a user applies to all Message objects that have the same PidTagConversationId value. The action is applied to all Message objects that are currently in the store or are delivered in the future.

Coordinated Universal Time (UTC): A high-precision atomic time standard that approximately tracks Universal Time (UT). It is the basis for legal, civil time all over the Earth. Time zones around the world are expressed as positive and negative offsets from UTC. In this role, it is also referred to as Zulu time (Z) and Greenwich Mean Time (GMT). In these specifications, all references to UTC refer to the time at UTC-0 (or GMT).

counter proposal: A request that an attendee sends to an organizer when requesting a change to the date or time of a meeting.

cyclic redundancy check (CRC): An algorithm used to produce a checksum (a small, fixed number of bits) against a block of data, such as a packet of network traffic or a block of a computer file. The CRC is a broad class of functions used to detect errors after transmission or storage. A CRC is designed to catch random errors, as opposed to intentional errors. If errors might be introduced by a motivated and intelligent adversary, a cryptographic hash function should be used instead.

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.

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

delivery receipt: A report message that is generated and sent by a client or server to the sender of a message or another designated recipient when an email message is received by an intended recipient.

Department object: An Address Book object that describes a department within an organization.

departmental group: A distribution list that describes a department within an organization.

display name: A text string that is used to identify a principal or other object in the user interface. Also referred to as title.

display template: A template that describes how to display or allow a user to modify information about an Address Book object.

distinguished name (DN): A name that uniquely identifies an object by using the relative distinguished name (RDN) for the object, and the names of container objects and domains that contain the object. The distinguished name (DN) identifies the object and its location in a tree.

distribution list: A collection of users, computers, contacts, or other groups that is used only for email distribution, and addressed as a single recipient.

Document object: A Message object that represents a single file, such as a document generated by a word-processing application. The Message object contains the file as an Attachment object and includes additional properties to describe the file.

domain: A set of users and computers sharing a common namespace and management infrastructure. At least one computer member of the set must act as a domain controller (DC) and host a member list that identifies all members of the domain, as well as optionally hosting the Active Directory service. The domain controller provides authentication (2) of members, creating a unit of trust for its members. Each domain has an identifier that is shared among its members. For more information, see [MS-AUTHSOD] section and [MS-ADTS].

double-byte character set (DBCS): A character set (1) that can use more than one byte to represent a single character. A DBCS includes some characters that consist of 1 byte and some characters that consist of 2 bytes. Languages such as Chinese, Japanese, and Korean use DBCS.

Email object: A Message object that represents an email message in a message store and adheres to the property descriptions that are described in in [MS-OXOMSG].

entry ID: See EntryID.

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

Exception Embedded Message object: An Embedded Message object that contains the changes for an Exception object.

Exception object: An instance of a recurring series that differs from the rest of the recurring series, for example by start time.

File Transfer Protocol (FTP): A member of the TCP/IP suite of protocols that is used to copy files between two computers on the Internet if both computers support their respective FTP roles. One computer is an FTP client and the other is an FTP server.

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.

free/busy status: A property of an appointment that indicates how an appointment on the calendar of an attendee or resource affects their availability.

Global Address List (GAL): An address list that conceptually represents the default address list for an address book.

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

group header: A navigation shortcut that groups other navigation shortcuts.

Hypertext Markup Language (HTML): An application of the Standard Generalized Markup Language (SGML) that uses tags to mark elements in a document, as described in [HTML].

Hypertext Transfer Protocol (HTTP): An application-level protocol for distributed, collaborative, hypermedia information systems (text, graphic images, sound, video, and other multimedia files) on the World Wide Web.

instance: A unique publication of data for a category (4). It enables a publisher to publish data for the same category multiple times. An example is a publisher who uses two different endpoints (5) to publish data. These endpoints can publish the same category. However, each endpoint requires a different instance number to be considered a distinct publication by the server (2). An instance number is provided by the publishing client.

Integrated Services Digital Network (ISDN): A high-speed digital technology that uses existing telephone lines to provide Internet access and digital network services.

Journal object: A Message object that represents an entry in a journal or log and adheres to the property descriptions that are described in in [MS-OXOJRNL].

locale: A collection of rules and data that are specific to a language and a geographical area. A locale can include information about sorting rules, date and time formatting, numeric and monetary conventions, and character classification.

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.

long ID (LID): A 32-bit quantity that, in combination with a GUID, defines a named property.

mail tip: A note that is presented to the author of a message when the author is composing the message. A mail tip provides information about the recipients of a message and issues that might impact delivery of the message, such as moderation or delivery restrictions.

mail user: An Address Book object that represents a person or entity that can receive deliverable messages.

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

meeting: An event with attendees.

Meeting object: A Calendar object that has both an organizer and attendees.

meeting request: An instance of a Meeting Request object.

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 Update object: A Message object that represents a meeting organizer's changes to a previously scheduled meeting. The update is categorized as either a full update or an informational update.

Meeting Workspace: A website that is created by using the Meetings Web Services protocol, as described in [MS-MEETS]. It can host documents, discussions, and other information about a 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 body: The main message text of an email message. A few properties of a Message object represent its message body, with one property containing the text itself and others defining its code page and its relationship to alternative body formats.

message class: A property that loosely defines the type of a message, contact, or other Personal Information Manager (PIM) object in a mailbox.

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.

Messaging Application Programming Interface (MAPI): A messaging architecture that enables multiple applications to interact with multiple messaging systems across a variety of hardware platforms.

messaging object: An object that exists in a mailbox. It can be only a Folder object or a Message object.

MIME message: A message that is as described in [RFC2045], [RFC2046], and [RFC2047].

MIME part: A message part that is as described in [RFC2045], [RFC2046], and [RFC2047].

Multipurpose Internet Mail Extensions (MIME): A set of extensions that redefines and expands support for various types of content in email messages, as described in [RFC2045], [RFC2046], and [RFC2047].

name service provider interface (NSPI): A method of performing address-book-related operations on Active Directory.

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

navigation shortcut: An object that contains identifying information to locate a folder in a message database or an object that groups other navigation shortcuts.

non-Unicode: A character set (1) that has a restricted set of glyphs, such as Shift_JIS or ISO-2022-JP.

Note object: A Message object that represents a simple text note in a messaging store and that adheres to the property descriptions that are described in [MS-OXONOTE]. A Note object functions as an electronic equivalent of a paper sticky note.

offline address book (OAB): A collection of address lists that are stored in a format that a client can save and use locally.

optional attendee: An attendee of an event whom the organizer lists as an optional participant.

organizer: The owner or creator of a meeting or appointment.

orphan instance: An instance of an event that is in a recurring series and is in a Calendar folder without the recurring series. For all practical purposes, this is a single instance.

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.

Permanent Entry ID: A property of an Address Book object that can be used to uniquely identify the object.

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.

phishing: The luring of sensitive information, such as passwords or other personal information, from a recipient by masquerading as someone who is trustworthy and has a real need for such information.

plain text: Text that does not have markup. See also plain text message body.

primary recipient: A person for whom a message is directly intended.

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

property name: A string that, in combination with a property set, identifies a named property.

property set: A set of attributes (1), identified by a GUID. Granting access to a property set grants access to all the attributes in the set.

property type: A 16-bit quantity that specifies the data type of a property value.

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

read receipt: An email message that is sent to the sender of a message to indicate that a message recipient received the message.

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

recipient table: The part of a Message object that represents users to whom a message is addressed. Each row of the table is a set of properties that represents one recipient.

recurrence pattern: Information for a repeating event, such as the start and end time, the number of occurrences, and how occurrences are spaced, such as daily, weekly, or monthly.

Recurring Calendar object: A Calendar object that describes an event that repeats according to a recurrence pattern.

recurring series: An event that repeats at specific intervals of time according to a recurrence pattern.

recurring task: A series of Task objects that are described by a recurrence pattern.

reminder: A generally user-visible notification that a specified time has been reached. A reminder is most commonly related to the beginning of a meeting or the due time of a task but it can be applied to any object type.

resource: Any component that a computer can access where data can be read, written, or processed. This resource could be an internal component such as a disk drive, or another computer on a network that is used to access a file.

Resource object: An Address Book object that represents an asset that can be reserved, such as a room or equipment.

retention tag: An element that contains information about the retention policy of a Message object or folder.

Rich Text Format (RTF): Text with formatting as described in [MSFT-RTF].

rights-managed email message: An email message that specifies permissions that are designed to protect its content from inappropriate access, use, and distribution.

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 buffer: A structure containing an array of bytes that encode a remote operation (ROP). The first byte in the buffer identifies the ROP. This byte is followed by ROP-specific fields. Multiple ROP buffers can be packed into a single remote procedure call (RPC) request or response.

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.

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.

Sent Items folder: A special folder that is the default location for storing copies of Message objects after they are submitted or sent.

Server object: An object on a server that is used as input or created as output for remote operations (ROPs).

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

signal time: The time at which a reminder has been specified to notify the user or an agent acting on behalf of the user. For example, the signal time for a meeting that starts at 11:00 A.M. can be 10:45 A.M., thus allowing the user 15 minutes to prepare for or travel to the meeting upon receiving the notification.

Simple Mail Transfer Protocol (SMTP): A member of the TCP/IP suite of protocols that is used to transport Internet messages, as described in [RFC5321].

site mailbox: A repository comprised of a mailbox and a web-based collaboration environment that is presented to users as a mailbox in an email client. A site mailbox uses team membership to determine which users have access to the repository.

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

spam: An unsolicited email message.

spam filter: A filter that checks certain conditions in a message to determine a spam confidence level.

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

stream: A flow of data from one host to another host, or the data that flows between two hosts.

tagged property: A property that is defined by a 16-bit property ID and a 16-bit property type. The property ID for a tagged property is in the range 0x001 – 0x7FFF. Property IDs in the range 0x8000 – 0x8FFF are reserved for assignment to named properties.

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.

Transmission Control Protocol (TCP): A protocol used with the Internet Protocol (IP) to send data in the form of message units between computers over the Internet. TCP handles keeping track of the individual units of data (called packets) that a message is divided into for efficient routing through the Internet.

Transport Neutral Encapsulation Format (TNEF): A binary type-length-value encoding that is used to encode properties for transport, as described in [MS-OXTNEF].

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

Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].

Uniform Resource Locator (URL): A string of characters in a standardized format that identifies a document or resource on the World Wide Web. The format is as specified in [RFC1738].

unsendable attendee: An attendee to whom a meeting request or meeting update is not sent.

Use License: An XrML 1.2 license that authorizes a user to gain access to a protected content file and describes the applicable usage policies. Also referred to as "End-User License (EUL)."

Web Distributed Authoring and Versioning Protocol (WebDAV): The Web Distributed Authoring and Versioning Protocol, as described in [RFC2518] or [RFC4918].

X500 DN: A distinguished name (DN), in Teletex form, of an object that is in an address book. An X500 DN can be more limited in the size and number of relative distinguished names (RDNs) than a full DN.

XML: The Extensible Markup Language, as described in [XML1.0].

XML document: A document object that is well formed, as described in [XML10/5], and might be valid. An XML document has a logical structure that is composed of declarations, elements, comments, character references, and processing instructions. It also has a physical structure that is composed of entities, starting with the root, or document, entity.

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.