1.1 Glossary

This document uses the following terms:

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

address list: A collection of distinct Address Book objects.

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

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.

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

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.

Hypertext Transfer Protocol Secure (HTTPS): An extension of HTTP that securely encrypts and decrypts web page requests. In some older protocols, "Hypertext Transfer Protocol over Secure Sockets Layer" is still used (Secure Sockets Layer has been deprecated). For more information, see [SSL3] and [RFC5246].

OAB manifest: A file that contains information about data files in a version 4 OAB and has a fixed, well-known name "oab.xml". By discovering the Web Distribution Point (WDP) URI and downloading the manifest, a client application can receive all the information that is necessary to download any published data file in a specific WDP, as necessary.

OAB web distribution: A distribution mechanism that is specific to offline address book (OAB) version 4 and is used to publish OAB data files and an OAB manifest as a collection of files that a client application can download by using the HTTP/1.1 protocol, as described in [RFC2616].

OAL data sequence number: An integer that is associated with offline address list (OAL) data that represents the generation number of this data. The value of the initial sequence number is "1". Each subsequent data generation process that produces a data set that is not identical to the previous data set is incremented by one.

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

offline address book (OAB) data file: A file that contains offline address book (OAB) version 4–specific data, as described in [MS-OXOAB].

offline address list (OAL): A portion of data that is in an offline address book (OAB) and is related to a single address list.

recipient: An entity that is in an address list, can receive email messages, and contains a set of attributes. Each attribute has a set of associated values.

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 Distribution Point (WDP): A location on a server where offline address book (OAB) files are published for web distribution. A client can discover the URI of a WDP by using the Autodiscover Publishing and Lookup Protocol, as described in [MS-OXDSCLI].

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

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.