1.1 Glossary
This document uses the following terms:
access control list (ACL): A list of access control entries (ACEs) that collectively describe the security rules for authorizing access to some resource; for example, an object or set of objects.
alias: An alternate name that can be used to reference an object or element.
ASCII: The American Standard Code for Information Interchange (ASCII) is an 8-bit character-encoding scheme based on the English alphabet. ASCII codes represent text in computers, communications equipment, and other devices that work with text. ASCII refers to a single 8-bit ASCII character or an array of 8-bit ASCII characters with the high bit of each character set to zero.
calendar: A date range that shows availability, meetings, and appointments for one or more users or resources. See also Calendar object.
Calendar folder: A Folder object that contains Calendar objects.
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.
class: User-defined binary data that is associated with a key.
contact: A presence entity (presentity) whose presence information can be tracked.
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).
delegate: A user or resource that has permissions to act on behalf of another user or resource.
discretionary access control list (DACL): An access control list (ACL) that is controlled by the owner of an object and that specifies the access particular users or groups can have to the object.
Exception Embedded Message object: An Embedded Message object that contains the changes for an Exception object.
Folder object: A messaging construct that is typically used to organize data into a hierarchy of objects containing Message objects and folder associated information (FAI) Message objects.
free/busy status: A property of an appointment that indicates how an appointment on the calendar of an attendee or resource affects their availability.
header field: A component of a Session Initiation Protocol (SIP) message header, as described in [RFC3261].
Hypertext Markup Language (HTML): An application of the Standard Generalized Markup Language (SGML) that uses tags to mark elements in a document, as described in [HTML].
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].
Inbox folder: A special folder that is the default location for Message objects received by a user or resource.
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 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. 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: An event with attendees.
Meeting object: A Calendar object that has both an organizer and attendees.
meeting request: An instance of a Meeting Request object.
Meeting Request object: A Message object that represents an invitation from the meeting organizer to an attendee.
Meeting Response object: A Message object that represents an attendee's response to a meeting organizer's invitation. The response indicates whether the attendee accepted, tentatively accepted, or declined the meeting request. The response can include a proposed new date or time for the meeting.
Meeting Update object: A Message object that represents a meeting organizer's changes to a previously scheduled meeting. The update is categorized as either a full update or an informational update.
Meeting Workspace: A website that is created by using the Meetings Web Services protocol, as described in [MS-MEETS]. It can host documents, discussions, and other information about a meeting.
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 store: A unit of containment for a single hierarchy of Folder objects, such as a mailbox or public folders.
optional attendee: An attendee of an event whom the organizer lists as an optional participant.
organizer: The owner or creator of a meeting or appointment.
orphan instance: An instance of an event that is in a recurring series and is in a Calendar folder without the recurring series. For all practical purposes, this is a single instance.
Out of Office (OOF): One of the possible values for the free/busy status on an appointment. It indicates that the user will not be in the office during the appointment.
permission: A rule that is associated with an object and that regulates which users can gain access to the object and in what manner. See also rights.
plain text: Text that does not have markup. See also plain text message body.
property set: A set of attributes, identified by a GUID. Granting access to a property set grants access to all the attributes in the set.
public folder: A Folder object that is stored in a location that is publicly available.
recurrence pattern: Information for a repeating event, such as the start and end time, the number of occurrences, and how occurrences are spaced, such as daily, weekly, or monthly.
recurring series: An event that repeats at specific intervals of time according to a recurrence pattern.
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.
required attendee: An attendee of an event whom the organizer lists as a mandatory participant.
resource: Any component that a computer can access that can read, write, and process data. This includes internal components (such as a disk drive), a service, or an application running on and managed by the cluster on a network that is used to access a file.
restriction: A set of conditions that an item meets to be included in the search results that are returned by a query server in response to a search query.
root folder: The folder at the top of a hierarchy of folders in a list.
security descriptor: A data structure containing the security information associated with a securable object. A security descriptor identifies an object's owner by its security identifier (SID). If access control is configured for the object, its security descriptor contains a discretionary access control list (DACL) with SIDs for the security principals who are allowed or denied access. Applications use this structure to set and query an object's security status. The security descriptor is used to guard access to an object as well as to control which type of auditing takes place when the object is accessed. The security descriptor format is specified in [MS-DTYP] section 2.4.6; a string representation of security descriptors, called SDDL, is specified in [MS-DTYP] section 2.5.1.
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.
Simple Mail Transfer Protocol (SMTP): A member of the TCP/IP suite of protocols that is used to transport Internet messages, as described in [RFC5321].
structured document: A document that is internally composed of multiple streams that specify data for individual pieces of the document, such as style information, images, or embedded objects. The streams allow pieces of the document to be addressed and manipulated individually.
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).
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].
Uniform Resource Locator (URL): A string of characters in a standardized format that identifies a document or resource on the World Wide Web. The format is as specified in [RFC1738].
unsendable attendee: An attendee to whom a meeting request or meeting update is not sent.
Web Distributed Authoring and Versioning Protocol (WebDAV): The Web Distributed Authoring and Versioning Protocol, as described in [RFC2518] or [RFC4918].
WebDAV client: A computer that uses WebDAV, as described in [RFC2518] or [RFC4918], to retrieve data from a WebDAV server.
WebDAV server: A computer that supports WebDAV, as described in [RFC2518] or [RFC4918], and responds to requests from WebDAV clients.
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.