6.2.1 Schema Validation
A message is conformant to this specification only when it validates against the set of XML Schema files provided.
6.2.2 Allowed Value Lists
The allowed values are listed, defined and provided through the DDEX Data Dictionary Standard in accordance with its latest version. Other values are not possible unless by using the mechanism described below:
This Standard does not explicitly list allowed values. The XML Schema files contain the allowed values at the time of writing of this Standard (see Annex A). Some of the allowed value sets contain a provision to either use a User Defined Value instead of a DDEX-defined value (in that case the
MessageSender has to select the value “
UserDefined” from the AVS and provide its own value in the XML attribute “
UserDefinedValue”) or to augment a DDEX-defined value (in that case the
MessageSender may not select the value “
UserDefined” from the AVS but shall provide its additional information in the XML attribute “
UserDefinedValue”). In either case the
Namespace attribute shall be used to indicate where the
UserDefinedValue is defined and maintained.
6.2.3 Allowed Values for
Namespace attributes can be used to allow message parties to use proprietary value lists.
The allowed value for the
Namespace attribute which is recommended to be used is the DDEX Party Identifier of the party controlling the proprietary allowed value, as defined in, and administered in accordance with the latest version of the DDEX Party ID Standard.
6.2.4 Indicating Unknown Values
When the sender of a message is required to provide a data element but cannot do so, the following values shall be entered:
- In fields of type xs:string: “
- In fields of type xd:date: “
- In fields of type xs:datetime: “
- In fields of typexs:duration: “
The circumstances under which such behaviour is permissible may be limited in the specific business relationship between message sender and message recipient.
6.2.5 Character Coding
All messages shall be sent in UTF-8.