1.1 Glossary
This document uses the following terms:
Application object: A CEP metadata object that defines a containing namespace for all child objects, which can be any of the following: Entity, EventType, InputAdapter, OutputAdapter, Query, or QueryTemplate.
CEP metadata object: An object that the CEP server allows an implementer to name and define. A metadata object can be any of the following types: Application, Entity, EventType, InputAdapter, OutputAdapter, Query, or QueryTemplate.
complex event processing (CEP): The continuous and incremental processing of event streams from multiple sources, based on declarative query and pattern specifications with near-zero latency.
CountByStartTime window: A segmentation of the timeline based on the count of distinct event start times. If every event has a unique timestamp, the window spans the specified number of events, starting at the first event's start time and spanning up to the last event's start time plus one tick. If multiple events carry the same timestamp, they count as one unit with respect to the specified window count.
current time increment (CTI): A "heartbeat" event type that does not carry any payload, only a single timestamp. CTIs advance application time in the CEP engine.
Entity object: A CEP metadata object that is represented by an expression that is deployed to the server.
event sink: A destination for an event stream within the CEP platform. In the current version, only output adapters can be event sinks.
EventType object: A CEP metadata object that is used to define the structure of the payload of an event, including the associated fields.
hopping window: A segmentation of the timeline according to a specific fixed window size and a specific fixed hopsize. The hopsize specifies the offset of one window to the next. If the hopsize equals the window size, the windows are non-overlapping and without gaps.
InputAdapter object: A CEP metadata object that is the registration of the binary file compiled from user-written code, which makes the input adapter available to the CEP system so that it can be used in query definitions. This object represents an input stream source and converts proprietary event data into CEP event format.
insert: An event type that declares that a payload is valid for the actual observed duration of the specified event's lifetime (start time–end time).
OutputAdapter object: A CEP metadata object that is the registration of the binary file compiled from user-written code, which makes the output adapter available to the CEP system so that it can be used in query definitions. This object represents an output stream source and receives events that are produced by the CEP engine for further processing.
Query object: A CEP metadata object that represents the binding of input and output adapters and a QueryTemplate object within an application.
QueryTemplate object: A CEP metadata object that defines how to compute an output stream from one or more input streams.
retract: An event type that shortens the lifetime of an event. To be associated with an event, the retract must match the specified event's start time, end time, and entire set of payload field values.
snapshot window: A division of the timeline that is created when the timeline is divided into segments along every event start and every event end. A snapshot window, by definition, does not contain any start or end of an event except at its boundaries.
SOAP body: A container for the payload data being delivered by a SOAP message to its recipient. See [SOAP1.2-1/2007] section 5.3 for more information.
SOAP fault: A container for error and status information within a SOAP message. See [SOAP1.2-1/2007] section 5.4 for more information.
SOAP header: A mechanism for implementing extensions to a SOAP message in a decentralized manner without prior agreement between the communicating parties. See [SOAP1.2-1/2007] section 5.2 for more information.
Web Services Description Language (WSDL): An XML format for describing network services as a set of endpoints that operate on messages that contain either document-oriented or procedure-oriented information. The operations and messages are described abstractly and are bound to a concrete network protocol and message format in order to define an endpoint. Related concrete endpoints are combined into abstract endpoints, which describe a network service. WSDL is extensible, which allows the description of endpoints and their messages regardless of the message formats or network protocols that are used.
XML namespace: A collection of names that is used to identify elements, types, and attributes in XML documents identified in a URI reference [RFC3986]. A combination of XML namespace and local name allows XML documents to use elements, types, and attributes that have the same names but come from different sources. For more information, see [XMLNS-2ED].
XML Schema (XSD): A language that defines the elements, attributes, namespaces, and data types for XML documents as defined by [XMLSCHEMA1/2] and [XMLSCHEMA2/2] standards. An XML schema uses XML syntax for its language.
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.