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.
archive policy: A feature that determines when items are moved into an alternate mailbox for archival purposes.
attachments table: A Table object whose rows represent the Attachment objects that are attached to a Message object.
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.
calendar options dictionary: A dictionary that contains calendar configuration data. It is stored in a folder associated information (FAI) message that is in a Calendar special folder.
Calendar special folder: A Calendar folder that is in a user's mailbox and in which meetings are created by default.
category: A subdivision of items into useful groups such as geographical regions. For example, categories that represent geographical regions could be North, South, East, and West.
code page: An ordered set of characters of a specific script in which a numerical index (code-point value) is associated with each character. Code pages are a means of providing support for character sets and keyboard layouts used in different countries. Devices such as the display and keyboard can be configured to use a specific code page and to switch from one code page (such as the United States) to another (such as Portugal) at the user's request.
Common Views folder: A special folder that contains the data for default views that are standard for a message store and can be used by any user of a client that accesses the message store.
Contact object: A Message object that contains properties pertaining to a contact.
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.
conversation ID: A unique value that is associated with a conversation. It is assigned to each Message object that is part of a conversation and it is used to identify the conversation to which the message belongs.
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).
dictionary: A collection of key/value pairs. Each pair consists of a unique key and an associated value. Values in the dictionary are retrieved by providing a key for which the dictionary returns the associated value.
display name: A text string that is used to identify a principal or other object in the user interface. Also referred to as title.
distribution list: A collection of users, computers, contacts, or other groups that is used only for email distribution, and addressed as a single recipient.
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].
EntryID: A sequence of bytes that is used to identify and access an object.
FAI contents table: A table of folder associated information (FAI) Message objects that are stored in a Folder object.
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.
free/busy status: A property of an appointment that indicates how an appointment on the calendar of an attendee or resource affects their availability.
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] have to be used for generating the GUID. See also universally unique identifier (UUID).
group header: A navigation shortcut that groups other navigation shortcuts.
handle: Any token that can be used to identify and access an object such as a device, file, or a window.
Inbox folder: A special folder that is the default location for Message objects received by a user or resource.
Internet Message Access Protocol - Version 4 (IMAP4): A protocol that is used for accessing email and news items from mail servers, as described in [RFC3501].
interpersonal messaging subtree: The root of the hierarchy of folders commonly visible in a messaging client. This includes mailbox folders (such as the Inbox folder and Outbox folder) and user-created folders, including user-created public folders.
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].
little-endian: Multiple-byte values that are byte-ordered with the least significant byte stored in the memory location with the lowest address.
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.
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.
named property: A property that is identified by both a GUID and either a string name or a 32-bit identifier.
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.
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.
property ID: A 16-bit numeric identifier of a specific attribute. 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.
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.
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.
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.
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.
restriction: A set of conditions that an item meets to be included in the search results that are returned by a query server in response to a search query.
retention policy: A policy that specifies the length of time during which data, documents, and other records have to be available for recovery.
root folder: The folder at the top of a hierarchy of folders in a list.
ROP request: See ROP request buffer.
ROP request buffer: A ROP buffer that a client sends to a server to be processed.
rule: A condition or action, or a set of conditions or actions, that performs tasks automatically based on events and values.
search folder: A Folder object that provides a means of querying for items that match certain criteria. The search folder includes the search folder definition message and the search folder container.
sort order: The order in which the rows in a Table object are requested to appear. This can involve sorting on multiple properties and sorting of categories.
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.
Stream object: A Server object that is used to read and write large string and binary properties.
subproperty: A binary stream property that is embedded in another property, possibly in addition to other subproperties.
Task object: A Message object that represents an assignment to be completed.
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).
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.
Web Distributed Authoring and Versioning Protocol (WebDAV): The Web Distributed Authoring and Versioning Protocol, as described in [RFC2518] or [RFC4918].
working hours: Times of the day that are valid for meetings to be considered for an attendee.
XML: The Extensible Markup Language, as described in [XML1.0].
XML namespace: A collection of names that is used to identify elements, types, and attributes in XML documents identified in a URI reference [RFC3986]. A combination of XML namespace and local name allows XML documents to use elements, types, and attributes that have the same names but come from different sources. For more information, see [XMLNS-2ED].
XML namespace prefix: An abbreviated form of an XML namespace, as described in [XML].
XML schema: A description of a type of XML document that is typically expressed in terms of constraints on the structure and content of documents of that type, in addition to the basic syntax constraints that are imposed by XML itself. An XML schema provides a view of a document type at a relatively high level of abstraction.
XML schema definition (XSD): The World Wide Web Consortium (W3C) standard language that is used in defining XML schemas. Schemas are useful for enforcing structure and constraining the types of data that can be used validly within other XML documents. XML schema definition refers to the fully specified and currently recommended standard for use in authoring XML schemas.
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.