Main types
Event (complex)
Purpose: Common format used to report events.
Detail: aseXML A standard for energy transactions in XML. A set of schemas and usage guidelines that define how data should be exchanged under FRC in the gas and electricity industries in Australia. encourages the use of events in transactions to report status information. They are also used in message and transaction acknowledgements. Where possible use an element name of “Event”.
|
Field |
Restrictions |
aseXML |
Schema |
|---|---|---|---|
|
Event |
sequence |
complex |
Events_r41 |
|
Code |
Mandatory, sequence |
Events_r41 |
|
|
KeyInfo |
Optional, minOccurs=”0” |
Events_r41 |
|
|
Context |
Optional, minOccurs=”0” |
Events_r41 |
|
|
Explanation |
Optional, xsd:string, minOccurs=”0” |
element |
Events_r41 |
|
SupportedVersions |
minOccurs=”0” |
Events_r41 |
|
|
Class |
Optional, default=”Application” |
Events_r41 |
|
|
Severity |
Optional, default=”Fatal” |
Events_r41 |
Event (element)
Purpose: Top-level element used when reporting transport level errors, for example: decompression failures. Use this element to report aseXML in a consistent fashion.
Use this element via a Type=”Event” attribute. Do not use it via the ref=”Event”.
Detail: There may be a number of error conditions detected by a transport receiving an aseXML message, preventing it detecting a valid message. This Type of acknowledgement is useful for a single event only.
|
Field |
Restrictions |
aseXML |
Schema |
|---|---|---|---|
|
Event |
element |
Events_r41 |