This schema file is part of the aseXML schema set, and is subject to the terms and conditions that are detailed in the aseXML_r*.xsd schema file with which this file is used Purpose - Define the common format to be used to report events. Detail - aseXML encourages the use of events in transactions to report status information. They are also used in message and transaction acknowledgements. Purpose - Identify a release of aseXML Details - Release identifiers are used extensively in aseXML to enable versioning of transactions. Purpose - Release r3 identifier Purpose - Release r4 identifier Purpose - Release r5 identifier Purpose - Release r6 identifier Purpose - Release r7 identifier Purpose - Release r8 identifier Schema - Common Schema - Common Schema - Common Schema - Common Purpose - Release r12 identifier Purpose - Release r13 identifier Purpose - Release r14 identifier Purpose - Release r15 identifier Purpose - Release r16 identifier Purpose - Release r17 identifier Purpose - Release r18 identifier Purpose - Release r19 identifier Purpose - Release r20 identifier Purpose - Release r21 identifier Purpose - Release r22 identifier Purpose - Release r23 identifier Purpose - Provide a high level categorisation of events Detail - Message events pertain to the structure and delivery of aseXML messages. Application events are generated by the applications communicating via aseXML. Processing events reflect environmental issues associated with running applications. Purpose - Provide an indication as to the action required as a result of receiving an event Detail - The severity dictates the further processing possible after receiving the event. Purpose - Helper type in defining EventCode Purpose - Provide a numeric indentification of the event that has occurred Detail - The aseXML guidelines define a set of common codes, as well as ranges for application specfiic errors. Where the receiving system does not know the textual definition of the code, the description attribute should be provided with the code, as per the aseXML guidelines. Purpose - Provide information to allow identification of the data that triggered the event Detail - Where the combination of class and code are insufficient to completely describe an event, KeyInfo may be used to provide further detail as to the information needed to locate the source of the event within the original transaction. Purpose - Identify the specific data/condition that caused the event Detail - The portion of the input to which the event applies should be provided. Purpose - Provide the set of versions supported for a particular transaction Detail - Where an unsupported version of a supported transaction is received, the receiver should indicate those versions that are supported, allowing the receiver to choose a compatible transaction version. Purpose - Common format used to report events Detail - aseXML encourages the use of events in transactions to report status information. They are also used in message and transaction acknowledgements. Where possible, an element name of "Event" should be used. Purpose - Top level element used when reporting transport level errors, e.g. decompression failures Detail - There may be a number of error conditions detected by a transport receiving an aseXML message, that prevent it detecting a valid message. In order that these can be reported as XML in a consistent fashion, this top level element may be used. It should be noted that this element is not to be used via the ref="Event" mechanism of XML Schema. Rather, this should always be achieved via a type="Event" attribute. For an example, refer to the acknowledgements schema.