This document uses the following terms:
attachments table: A Table object whose rows represent the Attachment objects that are attached to a Message object.
bookmark: A data structure that the server uses to point to a position in the Table object. There are three pre-defined bookmarks (beginning, end, and current). A custom bookmark is a server-specific data structure that can be stored by the client for easily navigating a Table object.
category: A grouping of rows in a Table object that all have the same value for a specified property.
handle array: An array of object handles that are sent to and received from a server as part of a remote procedure call (RPC) accompanying ROP request buffers and ROP response buffers, respectively. Also referred to as a Server object handle table or an HSOT table.
instance: A unique publication of data for a category. 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.
leaf row: A row that is in a category.
multivalue instance: A row that is in a table and corresponds to a single value in a multivalue property. There are multiple rows for each Message object in a table and each row corresponds to one value of the multivalue property. Each row has a single value for the property and the properties for the other columns are repeated.
property ID: A 16-bit numeric identifier of a specific attribute (1). A property ID does not include any property type information.
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 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.
ROP request: See ROP request buffer.
ROP response: See ROP response buffer.
search criteria: A criteria used to determine which messages are included in a folder with specific characteristics. It is composed of a restriction, which is the filter to be applied, and a search scope, which are the folders that contain the content to search.
sort order: A set of rules in a search query that defines the ordering of rows in the search result. Each rule consists of a managed property, such as modified date or size, and a direction for order, such as ascending or descending. Multiple rules are applied sequentially.
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.
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.