This document uses the following terms:
basic flag: A flag on a Message object that indicates that the object has an associated work item or shares a defining characteristic with other Message objects with such flags.
Contact object: A Message object that contains properties pertaining to a contact.
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).
Draft Message object: A Message object that has not been sent.
mailbox: A message store that contains email, calendar items, and other Message objects for a single recipient.
meeting-related object: A Message object that represents a relay of information between a meeting organizer and an attendee. It can be any of the following: Meeting Request object, Meeting Update object, Meeting Cancellation object, or Meeting Response object.
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.
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.
primary flag storage location: The typical location that is used to store flagging properties, as opposed to the secondary flag storage location.
recipient reminder: A collection of property values indicating that a Draft Message object is marked such that it will have an active reminder for the recipients of the Message Object.
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.
ROP request: See ROP request buffer.
ROP response: See ROP response buffer.
secondary flag storage location: A binary property that is used to encode a second set of flagging properties, which do not affect the flagged state of a Message object.
sender flag: A collection of property values that indicate that a Draft Message object has been marked such that the copy of the Message object that is saved in the sender's mailbox after the message is sent will appear flagged to the sender.
sender reminder: A collection of property values that indicate that a Draft Message object has been marked such that the copy of the Message object that is saved in the sender's mailbox after the message is sent will have an active reminder.
Task object: A Message object that represents an assignment to be completed.
time flag: A flag that extends the concept of a basic flag by associating time-related properties, such as start and due dates, with the flag information on a Message object. A time flagged Message object is also marked with a red color flag, but it is not considered to be color flagged by definition.
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).
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.