1.1 Glossary

This document uses the following terms:

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.

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

character set: A mapping between the characters of a written language and the values that are used to represent those characters to a computer.

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.

de-encapsulating RTF reader: A Rich Text Format (RTF) reader, as described in [MSFT-RTF], that recognizes if an input RTF document contains encapsulated HTML or plain text, and extracts and renders the original HTML or plain text instead of the encapsulating RTF content.

encapsulating RTF writer: A Rich Text Format (RTF) writer, as described in [MSFT-RTF], that produces an RTF document as a result of format conversion from other formats, such as plain text or HTML, and also stores the original document in a form that allows for subsequent retrieval.

encapsulation: A process of encoding one document in another document in a way that allows the first document to be re-created in a form that is nearly identical to its original form.

format conversion: A process that converts a text document from one text format, such as Rich Text Format (RTF), HTML, or plain text, to another text format. The result of text conversion is typically a new document that is an approximate rendering of the same information.

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

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

MIME Encapsulation of Aggregate HTML Documents (MHTML): A MIME-encapsulated HTML document, as described in [RFC2557].

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

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.

rendering position: A location in a Rich Text Format (RTF) document where an attachment is placed visually.

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

ROP request: See ROP request buffer.

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

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.