This document uses the following terms:
Calendar object: A Message object that represents an event, which can be a one-time event or a recurring event. The Calendar object includes properties that specify event details such as description, organizer, date and time, and status.
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).
dismiss: A process that disables an overdue reminder. After a reminder is dismissed, it is not considered overdue anymore and is not signaled or displayed to a user or any agents who are acting on behalf of that user.
Draft Message object: A Message object that has not been sent.
Exception Attachment object: An Attachment object on a Recurring Calendar object that contains the data for an exception, including an Exception Embedded Message object.
full reminder domain: The maximum scope that a client is allowed to use when searching for objects that have reminders enabled. The full reminder domain includes all folders except the following: Deleted Items, Junk Email, Drafts, Outbox, Conflicts, Local Failures, Server Failures, and Sync Issues.
instance: A unique publication of data for a category (4). 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.
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.
minimal reminder domain: The smallest scope that a client is allowed to use when searching for objects that have an active reminder. The minimal reminder domain includes the following folders: Inbox, primary Contacts, primary Calendar, and primary Tasks. It does not include sub-folders.
object: A set of attributes (1), each with its associated values. Two attributes of an object have special significance: an identifying attribute and a parent-identifying attribute. An identifying attribute is a designated single-valued attribute that appears on every object; the value of this attribute identifies the object. For the set of objects in a replica, the values of the identifying attribute are distinct. A parent-identifying attribute is a designated single-valued attribute that appears on every object; the value of this attribute identifies the object's parent. That is, this attribute contains the value of the parent's identifying attribute, or a reserved value identifying no object. For the set of objects in a replica, the values of this parent-identifying attribute define a tree with objects as vertices and child-parent references as directed edges with the child as an edge's tail and the parent as an edge's head. Note that an object is a value, not a variable; a replica is a variable. The process of adding, modifying, or deleting an object in a replica replaces the entire value of the replica with a new value. As the word replica suggests, it is often the case that two replicas contain "the same objects". In this usage, objects in two replicas are considered the same if they have the same value of the identifying attribute and if there is a process in place (replication) to converge the values of the remaining attributes. When the members of a set of replicas are considered to be the same, it is common to say "an object" as shorthand referring to the set of corresponding objects in the replicas.
Recurring Calendar object: A Calendar object that describes an event that repeats according to a recurrence pattern.
recurring task: A series of Task objects that are described by a recurrence pattern.
Recurring Task object: A Task object that represents a recurring task.
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.
reminder domain: A set of folders that are searched for objects that have an active reminder.
reminder queue: A sorted list of objects that are in a reminder domain and have been stamped with properties implying that they could have an active reminder.
(2) A Folder object that provides a means of querying for items that match certain criteria. The search folder includes the search folder definition message and the search folder container.
signal time: The time at which a reminder has been specified to notify the user or an agent acting on behalf of the user. For example, the signal time for a meeting that starts at 11:00 A.M. can be 10:45 A.M., thus allowing the user 15 minutes to prepare for or travel to the meeting upon receiving the notification.
snooze: A process that delays an overdue reminder by a specified time interval. At the end of the time interval, the reminder becomes overdue again.
special folder: One of a default set of Folder objects that can be used by an implementation to store and retrieve user data objects.
Task object: A Message object that represents an assignment to be completed.
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.