Copyright (C) 2008-2010, Cable Television Laboratories, Inc. SaFI Interactive Application Messaging Interface XML Schema Version 1.1.-1 AppMsg is the wrapper element containing each message. It contains exactly one message header along with one or more Application Message Blocks. This is the payload of the AppMsg. Each message must contain 1 or more AppMsgBlocks. Each AppMsgBlock will have an inheirited PEID from the Applcation Message Header along with an EPSID for unique identification. The AppMsgBlock can contain multiple AppReportBlocks each with its own EventID for identification. AppReportBlocks are the finest level of reporting. They allow reporting at the EventID level. UnitID represents the device unique identifier. This could be the device MAC address. This group contains the data elements representing the Header of ab Application Message. The header info appears exactly once in each message. It is constructed from the following elements, each contracted to save space: MS - MinSchemaVersionType (Replaces ProtocolVersion as the common schema/protocol versioning element across all interfaces) UID - Unit ID PEID - Programming Event ID GID - Geographic ID/Code T - Timestamp (Timestamp is a reference time in UTC (YYYY-MM-DDThh:mm:ss.mm) that is sent with each message so that each Event carried in an Application Message can reference times in a more compact format specifically as an offset of the reference time. Note: The common TimestampType from CommonTypes.xsd is not used here as Applcaition messaging requires a more compact timing scheme. Context information related to the instance of the application Information about the encoder sending the message