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.
backup event log: An event log that cannot be written to, only read from. Backup event logs are typically used for archival purposes, or for copying to another computer for use by support personnel.
category: A grouping of rows in a Table object that all have the same value for a specified property.
category message file: A binary resource file defining category strings for event categories.
category string: A localizable human-readable string corresponding to the event category of a record.
event: 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 category: An application-specific value used for grouping events. For example, an application might use one category for all events that occur during startup, and use another category for events that occur during shutdown. Other applications might use categories to identify the part of the application that raised the event.
event description string: A localizable human-readable string corresponding to the record.
event log: A collection of records, each of which corresponds to an event.
event message file: A binary resource file defining unexpanded description strings for an event source.
event source: An application or component that writes to an event log.
EventID: An integer indicating the type of event. For example, a user logging on to the computer could be one type of event while a user logging off would be another type; and these events could be indicated by using distinct EventIDs.
fully qualified domain name (FQDN): An unambiguous domain name that gives an absolute location in the Domain Name System's (DNS) hierarchy tree, as defined in [RFC1035] section 3.1 and [RFC2181] section 11.
globally unique identifier (GUID): A term used interchangeably with universally unique identifier (UUID) in Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the value. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the GUID. See also universally unique identifier (UUID).
live event log: An event log that can be written to and read from.
localizable: A condition of a data value or element that allows it to be modified, translated, or output for different languages or regional formats.
named pipe: A named, one-way, or duplex pipe for communication between a pipe server and one or more pipe clients.
Network Data Representation (NDR): A specification that defines a mapping from Interface Definition Language (IDL) data types onto octet streams. NDR also refers to the runtime environment that implements the mapping facilities (for example, data provided to NDR). For more information, see [MS-RPCE] and [C706] section 14.
opnum: An operation number or numeric identifier that is used to identify a specific remote procedure call (RPC) method or a method in an interface. For more information, see [C706] section 12.5.2.12 or [MS-RPCE].
parameter message file: A binary resource file that defines parameter strings for an event source.
parameter string: A localizable human-readable string inserted into an event description string using the string rendering algorithm defined in section 3.2.4.1.5.2.
record: The data structure that contains an event that is currently represented in an event log.
record ID: An unsigned int64 numeric value. The record ID is the identifier of the records in the event log file.
registry: A local system-defined database in which applications and system components store and retrieve configuration data. It is a hierarchical data store with lightly typed elements that are logically stored in tree format. Applications use the registry API to retrieve, modify, or delete registry data. The data stored in the registry varies according to the version of the operating system.
registry key or registry subkey: A node in the logical tree of the Windows registry data store. For more information, see [MSWINREG]. The term subkey specifies that a key has a parent in the logical tree; for example, "A is a subkey of B".
remote procedure call (RPC): A communication protocol used primarily between client and server. The term has three definitions that are often used interchangeably: a runtime environment providing for communication facilities between computers (the RPC runtime); a set of request-and-response message exchanges between computers (the RPC exchange); and the single message from an RPC exchange (the RPC message). For more information, see [C706].
RPC protocol sequence: A character string that represents a valid combination of a remote procedure call (RPC) protocol, a network layer protocol, and a transport layer protocol, as described in [C706] and [MS-RPCE].
synchronization object: A data structure that is used to synchronize client requests to prevent data corruption from the execution of multiple threads. In Windows-based servers, the CRITICAL_SECTION object (as described in [MSDN-CSO]) is used as the synchronization object.
unexpanded description string: A localizable string containing replaceable insertion patterns that are expanded by using a string-rendering algorithm, defined in section 3.2.4.1.5, to produce an event description string.
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).
Universal Naming Convention (UNC): A string format that specifies the location of a resource. For more information, see [MS-DTYP] section 2.2.57.
universally unique identifier (UUID): A 128-bit value. UUIDs can be used for multiple purposes, from tagging objects with an extremely short lifetime, to reliably identifying very persistent objects in cross-process communication such as client and server interfaces, manager entry-point vectors, and RPC objects. UUIDs are highly likely to be unique. UUIDs are also known as globally unique identifiers (GUIDs) and these terms are used interchangeably in the Microsoft protocol technical documents (TDs). Interchanging the usage of these terms does not imply or require a specific algorithm or mechanism to generate the UUID. Specifically, the use of this term does not imply or require that the algorithms described in [RFC4122] or [C706] must be used for generating the UUID.
well-known endpoint: A preassigned, network-specific, stable address for a particular client/server instance. For more information, see [C706].
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.