email address: A string that identifies a user and enables the user to receive Internet messages.
email alias: A string which is the local-part of a mailbox as specified in [RFC2821].
email enabled list: A SharePoint list that is configured to accept incoming email messages.
Email Text Body: The textual portion of a message that is displayed, by convention, by industry standard email clients. The Internet mail format, as described in [RFC822], allowed only text messages to be transmitted. The concept of transmitting content other than text was not codified until MIME was standardized. Handling of entities other than the textual portion of a message, such as attachments, varies by implementation in email clients.
embedded object: (1) An object that is created by using one application and is hosted in a document that was created by using another application. Embedding an object, rather than inserting or pasting it, ensures that the object retains its original format. Users can double-click an embedded object and edit it with the toolbars and menus from the application that was used to create it. See also Object Linking and Embedding (OLE).
(2) Application data that is stored in documents from other applications.
encapsulating RTF writer: A Rich Text Format (RTF) writer, as described in [MSFT-RTF], that produces an RTF document as a result of format conversion from other formats, such as plain text or HTML, and also stores the original document in a form that allows for subsequent retrieval.
encapsulation: (1) A process of encoding one document in another document in a way that allows the first document to be re-created in a form that is nearly identical to its original form.
(2) See disk encapsulation.
encoding: (1) A process that specifies a Content-Transfer-Encoding for transforming character data from one form to another.
(3) The annotation of an object with metadata so that it can be sent to a client or server.
encrypted message: An Internet email message that is in the format described by [RFC5751] and uses the EnvelopedData CMS content type described in [RFC3852], or the Message object that represents such a message.
encryption: In cryptography, the process of obscuring information to make it unreadable without special knowledge.
endpoint: (1) A client that is on a network and is requesting access to a network access server (NAS).
(2) A network-specific address of a remote procedure call (RPC) server process for remote procedure calls. The actual name and type of the endpoint depends on the RPC protocol sequence that is being used. For example, for RPC over TCP (RPC Protocol Sequence ncacn_ip_tcp), an endpoint might be TCP port 1025. For RPC over Server Message Block (RPC Protocol Sequence ncacn_np), an endpoint might be the name of a named pipe. For more information, see [C706].
(3) A participant that uses the Microsoft Groove Dynamics Protocol, as described in [MS-GRVDYNM], to synchronize with a shared space. An endpoint is identified by the combination of an identity URL and a client device URL. Each endpoint maintains a copy of the data in a shared space.
(4) A communication port that is exposed by an application server for a specific shared service and to which messages can be addressed.
(5) A device that is connected to a computer network.
(7) A network-specific address of a remote procedure call (RPC) server process for remote procedure calls. The actual name and type of the endpoint depends on the RPC protocol sequence being used. For example, for RPC over TCP (RPC Protocol Sequence ncacn_ip_tcp), an endpoint might be TCP port 1025. For RPC over Server Message Block (SMB) (RPC Protocol Sequence ncacn_np), an endpoint might be the name of a named pipe. For more information, see [C706].
(9) An entity, processor, or resource that can be referenced where Web service messages are originated or targeted.
(10) A node that sends or receives a protocol stream.
(11) A tuple (composed of an IP address, port, and protocol number) that uniquely identifies a communication endpoint.
(13) A resource that can be addressed by an endpoint reference.
endpoint reference (EPR): (1) A resource that conveys the information that is needed to address an endpoint.
(2) As specified in section 2 of [WSA].
enterprise/site/server distinguished name (ESSDN): An X500 DN that identifies an entry in an abstract naming scheme that is separate from an address book. The naming scheme defines enterprises, which contain sites, and sites contain servers and users. There is no concrete data structure that embodies an ESSDN. Instead, an address book entry can contain an ESSDN as a property of the entry.
entity: (1) An instance of an EntityType element that has a unique identity and an independent existence. An entity is an operational unit of consistency.
(2) The payload of a transfer (by analogy to the definition in [RFC2616]).
(3) Any document on a server that is accessible by using a Hypertext Transfer Protocol (HTTP) URL.
(4) A unit that is part of the system such as a component or an element.
(5) A single business object about which data can be stored. It is the subject of a table in a relational database.
(6) Tabular data that is stored within the Master Data Services (MSD) system.
Entity: A type of DataClass that represents a type of business data object that is stored in a line-of-business (LOB) system and whose instances have a persistent EntityInstanceId.
Entity Data Model (EDM): A set of concepts that describes the structure of data, regardless of its stored form, as described in [MC-CSDL].
entry ID: See EntryID.
EntryID: A sequence of bytes that is used to identify and access an object.
Enum: A Primitive type whose members are constrained to a set of values. The Primitive type is considered to be an underlying Remoting Type of the Enum. Each value has a name associated with it. An Enum is part of the Remoting Data Model, and an abbreviation for "enumeration." For more information, see [MS-NRTP] section 3.1.1.
event: (1) Any significant occurrence in a system or an application that requires users to be notified or an entry to be added to a log.
(2) An action or occurrence to which an application might respond. Examples include state changes, data transfers, key presses, and mouse movements.
(3) A discrete unit of historical data that an application exposes that may be relevant to other applications. An example of an event would be a particular user logging on to the computer.
event class: (1) A collection of events that are grouped together based on criteria that the publishing application specifies.
(2) A collection of historical data grouped together using criteria specified by the publishing application.
event log: A collection of records, each of which corresponds to an event.
Exception Embedded Message object: An Embedded Message object that contains the changes for an Exception object.
Exception object: An instance of a recurring series that differs from the rest of the recurring series, for example by start time.
exclusion list: (1) A list of items to exclude from query results and to remove from a search index the next time that a crawl occurs.
(2) A list of processes that cannot be managed because of the negative system impact such management could create. Processes in an exclusion list are unmanaged and can consume resources freely. Both system-defined and user-defined exclusion lists are defined.
expression: (1) A combination of operators, symbols, constants, literal values, functions, names of fields or columns (2), controls, and properties that evaluates to a single value.
(2) A construct that serves two purposes: specifies the logical operator (AND/OR) to be used between 2 conditions of a policy; and specifies the index of the expressions that are parent to it. Taken together, conditions and expressions specify policy classification criteria.
(3) A combination of symbols (identifiers, literals, functions, and operators) that yields a single data value.
extended payload: An arbitrary BLOB of data associated with a Peer Name and published by an application.
extended rule: A rule that is added to, modified, and deleted from a server by using a mechanism other than standard rules, but is otherwise functionally identical to a standard rule.
external identifier: A globally unique identifier for an entity that represents either a foreign identifier or an internal identifier (2). It consists of a GUID that represents a namespace followed by one or more bytes that contain an identifier for an entity within that namespace. If an external identifier represents an internal identifier, it can be also called a global identifier.
external OOF message: An OOF message that is sent to external users.