This section of the Knowledge Base intended to aid developers in properly implementing the DDEX RDR DeclarationOfSoundRecordingRightsClaim message. This sheet is written according to DDEX MLC 1.3.1. The example XML (provided by SCPP) is also based on DDEX MLC 1.3.1.
It addresses these issues:
- Choreography to automate RDR information exchange
- Definition of Terms and Allowed Values
- Upgrading from Version 1.2 to Version 1.3
- Upgrading from Version 1.3 to Version 1.4
- Anatomy of DDEX RDR Messages
- Implementation: XML Declaration
- Implementation: Message Header
- Implementation: Message Notification Period
- Implementation: ResourceList
- Implementation: SoundRecording
- Implementation: SoundRecordingDetailsByTerritory (v 1.3)
- Implementation: SoundRecordingDetailsByTerritory (v 1.4)
- Message Exchange (FTP)
- Display Titles in RDR
- Semantics of LineupComplete
General Advice on Implementation
- Map the local database terminology to the DDEX terms and Allowed Value Sets (AVS). The AVS provides for ‘User Defined’ values, but the use of this in practice compromises interoperability and is not a substitute for careful mapping of local variable into the DDEX system;
- Be able to process the XML language so as to generate messages and/or receive them and extract the data;
- Implement at least one of the DDEX RDR messages;
- Make tests of generation of DDEX messages from your IT system;
- Exchange test files with other DDEX RDR Message Suite users; and then:
- Go live!
Download Standard
Music Licensing Company Message Suite and Choreography Standard (Version 1.4)
Before starting an implementation, DDEX recommends to read Starting an Implementation and Licensing DDEX Standards.
Essential Reading
Contact DDEX
If you have a question or suggestion or if you are experiencing problems with your implementation, please feel free to contact the DDEX Secretariat; we may be able to help.