Copyright (c)2012, Cable Television Laboratories, Inc. ESAM Signal XML Schema, Release Version I01 Real-time Event Signaling and Management API This schema is a normative component of CableLabs® Real-time Event Signaling and Management API Specification, OC-SP-ESAM-API-I01-120910

Note the imports below normatively reference the latest Metadata 3.0 EC's. The latest EC versions of the referenced Metadata 3.0 schemas as of the time of publication of ESAM are included with ESAM 1.0 for convenience, but the normative versions apply if there is any subsequent EC or any other discrepancy.

Container for forwarding one or more signals to a confirmation endpoint. Container for passing signal processing instructions to a conditioning end point. Typically, such instructions are sent in response to a SignalProcessingEvent set a confirmation endpoint. Conditioning Into Type - Conditioning information communicated to an acquisition point. For example, communicate ABR (Adaptive Bit Rate) information. A globally unique ID for the point referenced. Specifies a desired off-set start time for the scheduled signal. Signal Processing Event Type - Type to carry one or more acquired signals across an interface Container for passing a signal from an acquisition point. In addition to the attributes defined, Signal Processing Event may include additional, custom attributes as needed by the application. Event Schedule Type - support insertion of a signal on a repetitive and/or scheduled basis. Defines a time range, either absolute or relative. Specifies the time to start broadcasting the data as a UTC date and time. Optional time to stop broadcasting the data as a UTC date and time. Specifies the time to start broadcasting the data as a duration from the associated/related signal. Optional time to stop broadcasting the data as a duration from the associated/related signal. Specifies a desired repetition interval for the scheduled signal. An Event Schedule may include additional, custom attributes as needed by the application. Signal Processing Notification Type - message to acquisition point to direct processing of signals Container to carry one or more signal processing instructions. Provide conditioning information. For example, adptive bit rate processing rules. Provides return status information to the caller and is returned for all errors. May optionally be included in a response payload to provide warning or informational details. A unique identity of the acquisition point. In addition to the attributes defined, signal processing notification may include additional, custom attributes as needed by the application. Response Signal Type - extension of AcquisitionPointInfoType from the signaling schema to support actions to take Optional insertion schedule to support delayed insertion and repetition. create - add a signal replace - replace the existing signal delete - delete the signal noop - do nothing, pass through the signal as is private: - support private actions If omitted the default action against an existing signal is a replace. For new signals the default action is create. For existing signals if create is specified, it will insert an additional signal. For new signals delete is invalid and the implementation will perform a create action.