This section of the DDEX Knowledge Base contains version 1.0 of the "Choreography for the Transfer of Catalogues between Rights Holders of Sound Recordings and other such Rights Holders "
Evaluation Licence for DDEX Standards
8 Message Definition
The hierarchical structure of the messages is provided through indentation in the tables below. In addition to the tabular description of the message, which should always be read in conjunction with Annex A, additional conformance rules, which go beyond XML Schema validation, are provided where necessary. The general conformance rules for all messages within this Standard are provided in Clause 8.2.
Specific business processes between sender and recipient may require even further conformance rules. These are, however, not part of the Standard and will need to be agreed by the business partners. Rules relating to the authority of business partners to unilaterally change the Message
8.2.1 Schema Validation
A message is conformant to this specification only when it validates against the set of XML Schema files provided in Annex B.
8.2.2 Allowed Value Lists
The allowed values are listed, defined and provided through the DDEX Data Dictionary Standard in accordance with the latest version of DDEX-DICT. Other values are not possible unless by using the mechanism described below:
This Standard does not explicitly list allowed values. The XML Schema files – as provided in Annex B – contain the allowed values at the time of writing of this Standard. 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.
8.2.3 Contractually Mandatory
The messages defined in this standard contain fields with cardinality “0-1” or “0-n”. Therefore these fields are from the standard’s point of view, optional. Such fields may, however, be mandatory when a DDEX message is sent in a specific commercial context.
In such circumstances, a message is deemed conformant only if and when it contains all the “contractually mandatory” fields as agreed by MessageSender and Message Recipient.
8.2.4 Schema Version Id
For messages defined directly herein the only valid value for this field is "2011/CCHO/10".
For messages defined in DDEX-AMEP, the relevant value of that standard shall be used.