Export (0) Print
Expand All

1.1 Glossary

The following terms are defined in [MS-GLOS]:

Coordinated Universal Time (UTC)
handle
Unicode

The following terms are defined in [MS-OXGLOS]:

Appointment object
basic flag
color flag
Contact object
Draft Message object
Email object
Journal object
mailbox
meeting-related object
Message object
named property
Note object
property ID
recipient
reminder
reminder properties
remote operation (ROP)
ROP request
ROP request buffer
ROP response
ROP response buffer
Task object
time flag

The following terms are specific to this document:

complete flag: A flag on a messaging object that indicates that the associated work item has been completed.

consolidated to-do list: A list of all tasks and flagged Message objects that are in a user's mailbox.

primary flag storage location: The typical location that is used to store flagging properties, as opposed to the secondary flag storage location.

recipient flag: A collection of property values indicating that a draft Message object is marked such that it will appear as flagged with a basic flag to recipients.

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.

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.

MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as described in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.

Show:
© 2014 Microsoft