Export (0) Print
Expand All

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

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

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

archive policy: A feature that determines when items are moved into an alternate mailbox for archival purposes.

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

ASCII: The American Standard Code for Information Interchange (ASCII) is an 8-bit character-encoding scheme based on the English alphabet. ASCII codes represent text in computers, communications equipment, and other devices that work with text. ASCII refers to a single 8-bit ASCII character or an array of 8-bit ASCII characters with the high bit of each character set to zero.

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.

attachments table: A Table object whose rows represent the Attachment objects that are attached to a Message object.

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

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.

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.

character set: The range of characters used to represent textual data within a MIME body part, as described in [RFC2046].

clear-signed body: A message body that was promoted from a clear-signed S/MIME message, as described in [MS-OXOSMIME].

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.

contact: A presence entity (presentity) whose presence information can be tracked. 

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.

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

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

Draft Message object: A Message object that has not been sent.

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

Embedded Message object: A Message object that is stored as an Attachment object within another Message object.

EntryID: A sequence of bytes that is used to identify and access an 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.

header: A name-value pair that supplies structured data in an Internet email message or MIME entity.

header message object: A Message object that contains partial information about a message on a server, such as an identifier for the message, the display names of the recipients and the sender, the subject of the message, and the delivery time of the message. It allows a client to display enough information about a message to let a user choose whether to download the message.

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

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

language code identifier (LCID): A 32-bit number that identifies the user interface human language dialect or variation that is supported by an application or a client computer.

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 body: The content within an HTTP message, as described in [RFC2616] section 4.3.

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.

metafile: A file that stores an image as graphical objects, such as lines, circles, and polygons, instead of pixels. A metafile preserves an image more accurately than pixels when an image is resized.

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

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

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

Object Linking and Embedding (OLE): A technology for transferring and sharing information between applications by inserting a file or part of a file into a compound document. The inserted file can be either embedded or linked. See also embedded object and linked 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.

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

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

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.

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

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.

retention policy: A policy that specifies the length of time during which data, documents, and other records must be available for recovery.

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

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.

search key: A binary-comparable key that identifies related objects for a search.

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.

Store object: An object that is used to store mailboxes and public folder content.

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.

To recipient: See primary recipient.

transaction: The process of opening or creating an object on a server, and the subsequent committing of changes to the object by calling the required save function, at which time all changes to that instance of the object are either saved to the server, or discarded if a failure occurs before saving is finished successfully. Until successfully saved, changes are invisible to any other instances of the object.

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

undefined body: A body with no defined content.

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

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

Windows metafile format (WMF): A file format used by Windows that supports the definition of images, including a format for clip art in word-processing documents.

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.

© 2016 Microsoft