SignalGroupAssetType is an extension of the CableLabs 3 AssetType. Implementers which do not deal with CableLabs Assets may safely ignore this type. One or more SignalPoint elements that exist in an asset. One or more SignalRegion elements that exist in an asset. Container for a collection of signals. Signal Group can contain one or more Signal Points and/or Signal Regions Container for passing a signal from an acquisition point Define a point of interest in an asset. Defube a region of interest in an asset Specifies the type of signal contained in this element. Specify information about a signaled point in a stream. The information may specfy information about an anticipated signal or be populated after the signal arrives. Specify the time range the signal will be considered valid. For example, an SCTE 35 cue message may only be considered valid during a defined time range. Authoritative StreamTimes contains one or more time values that are generated and interpreted by the underlying subsystem. While implementation specific, this data is intended to be passed as is through intervening systems unaltered. One or more AcquisitionPointInfo items can be passed in the structure. One use of this structure is in the case where signals for the same point are acquired from multiple acquisiiton points. Typically only one of the signals will be applied while multiple signals are actually received and communicated between subsystems. This structure allows a system to pass the data for all acquisition points. A diagnostic system is one consumer of such a fully populated structure. The authoritative ID of the signal. This ID may be carried forward from the acquisition sytem to other system element in the delivery platform. In addition to the attributes defined, a signaled point may include additional, custom attributes as needed by the application. Acquisiton Point Info Type - information about a specific acquisiton point Information for each acquisition point UTC Zulu combined date and time encoding of the wall clock for the signal point (e.g., the splice time as referenced by the SCTE 35 splice_time, i.e., cue time). This UTC time value typically should not match the acquisitionTime value. NPT point within the stream StreamTimes contains one or more time values that are generated and interpreted by the underlying subsystem. While implementation specific, this data is intended to be passed as is through intervening systems unaltered. A unique identity of the acquisition point. (ex. MUX5) A globally unique ID for the point referenced. UTC Zulu combined date and time encoding of the wall clock when the signal was captured (e.g., the SCTE 35 splice_info_section() acquisition time). For SCTE 35, this time value is not the splice time as referenced by a cue time or time_signal() but rather the date and time of when the signal was received/encountered by the acquisition point. Identifier for this entity. Use core:AssetRefType when referencing a signalPointID. NOTE: not to be confused with the acquisitionSignalID generated by an acquisiton device if this signal is instantiated based on receipt of some instream signaling. In addition to the attributes defined, acquisition point info may include additional, custom attributes as needed by the application. Specify a group of signal points and/or regions. One or more SignalPoint elements that exist in an asset. One or more SignalRegion elements that exist in an asset. A signal group may include additional, custom attributes as needed by the application. Type definition for a region of interest. The region can be defined by reference or by fully describing each point that bounds the region. The End Point is optional since not all End Points are signaled (ex. SCTE 35 out point signals only) Any number of alternate identifiers that may be used to identify this region. For example, may be referenced by a shared POGroup with PORegion A description for the Signal Region In line definition for a start point. In line definition for an end point. A pointer to the signal point identified by signalPointId. Optional pointer to the signal point identified by signalPointId. Identifier for this entity. Use core:AssetRefType when referencing a signalRegionID. Defines the effective duration of a signal region. Duration should only be used for regions that are signaled (ex. a SCTE 35 cue message for an out point that does not have a authoriative in point) that do not have a matching end signal. There is no known use case for using the duration attribute on an end point. The provider-supplied version number for the signal region. Should be incremented each time the signal region is changed by the provider. The internal version number for the signal region. This version number should be set to 0 by the provider whenever providerVersionNum is changed. Likewise, this version number should be increased when internal variants of the signal region are generated. A signal region may include additional, custom attributes as needed by the application. Based type for signals Any number of alternate identifiers that may be used to identify this region. For example, may be referenced by a shared POGroup with POPoint A description for the Signal Point Soruce of value may be: 1) Passed as part of a metadata package (ex. pitched VOD asset) 2) If signaled in the stream this is populated upon receipt of an authoritative signal 3) For an end point may be derived based on the start point plus a duration supplied from an external source. Acquisition point information. If present the SignalPoint is instantiated based on receipt of a signal in the stream (ex. SCTE 35) Identifier for this entity. Use core:AssetRefType when referencing a signalPointID. NOTE: not to be confused with the acquisitionSignalID generated by an acquisiton device if this signal is instantiated based on receipt of some instream signaling. The provider-supplied version number for the signal point. Should be incremented each time the signal point is changed by the provider. The internal version number for the signal point. This version number should be set to 0 by the provider whenever providerVersionNum is changed. Likewise, this version number should be increased when internal variants of the signal point are generated. In addition to the attributes defined, a signal may include additional, custom attributes as needed by the application. The identity of signal. Should be Universally Unique Identifier as defined by RFC 4122 The NPT for a point that specifies a point of interest or the start or end point of a region. NPT always has an nptPoint but may also include a date constraint on the NPT. The date is useful when defining NPT offsets into what was previously a live stream For live streams. NPT Date in xsd:date format. If nptDate is present, nptPoint is offset from start of day. nptPoint wraps to 0 at UTC mid-night. NPT point format:(ss.sss|EOS|BOS). If nptDate is present BOS is same as 00.000 and EOS is same as 86399.999 In addition to the attributes defined, NPT Point Descriptor may include additional, custom attributes as needed by the application. An NPT postition expressed as seconds with a fractional part for milliseconds The date portion of NPT postition expressed as a date Type to hold the UTC time of a point. UTC point. In addition to utcPoint, UTC Point Descriptor may include additional, custom attributes as needed by the application. UTC Point Type expressed as XSD:dateTime Specifies a bounded interval of time when a signal should be considered valid. If a signal arrives outside the valid time range it shall not be considered valid. Specifies the start of the valid time range. Specifies the end of the valid time range. If more than one signal shares the same expected arrive time range, order will contain an incrementing value, starting at 1, to drive the order of evaluation by a signal acquisition system. The valid time range may include additional, custom attributes as needed by the application. StreamTimes contains one or more time values that are generated and interpreted by an underlying subsystem. While implementation specific, this data is intended to be passed as is through intervening subsystems unaltered. Stream times may include additional, custom attributes as needed by the application. A single platform specific time comprised of a type and value pair. In addition to the attributes defined, a stream time may include additional, custom attributes as needed by the application.