DDEX Standard

Skip to end of metadata
Go to start of metadata

The syntax and semantics of the messages defined in this standard are provided in an XML Schema Definition file and in tabular form provided in a separate document. Both, the XSD and the tabular form are an integral part of this standard. They are available from the blue box here. These include the allowed value sets as specified in Clause 6.2.

The hierarchical structure of the messages is provided through indentation. On the MessageHeader for example, the PartyName is a child of Sender. Thus, a Sender contains a PartyName (plus a PartyId). A second example from the MessageHeader is the MessageAuditTrail that contains MessageAuditTrailEvents which, in turn, contains a MessagingPartyDescriptor and a DateTime element. All elements that have sub-elements are printed in bold. The MessageAuditTrailEvents element also shows a second structural feature of the tabular message summary: the cardinality. In the case of MessageAuditTrailEvents the entry "1-n" means that each MessageAuditTrail contains one or more MessageAuditTrailEvents.

Other possible cardinality entries are: "1" (for: exactly one), "0-1" (for none or one) or "0-n" (for none to multiple). Elements shown in italics are represented in the XML Schema as XML Attributes. In several places within the messages, the message sender may need to make a choice between using two or more XML elements. These instances are marked in the tabular representation of the messages below with the keyword XmlChoice. This keyword is not part of the messages. Instead exactly one of the “branches” below the XmlChoice keyword has to be used.


  • No labels