You are viewing an old version of this page. View the current version.
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 "
DDEX has standardised a series of Message Suite Standards that define the syntax and semantics of business metadata exchanged by members of the digital media delivery chain. Amongst these are notifications of new products, including updates, to Digital Service Providers. That standard, the Electronic Release Notification Standard (ERN), can also be used when a catalogue of Releases is transferred from one record company to another record company.This standard defines the process and Choreography for the notification of the intent of a catalogue transfer (typically from the “selling” record company to its distribution partners, or DSPs), the notification of a completed catalogue transfer (typically from the “selling” record company to its DSPs) and the provision of label copy information to the “buying” record company by the “selling” record company.The process defined herein may also be used to inform third parties such as Music Licensing Companies or chart companies about a catalogue transfer.
Any organisation wishing to implement this (or any other DDEX Standard) is required to apply for an Implementation Licence. The terms of the licence and an application form can be found at https://ddex.net/implementation/implementation-licence-and-ddex-party-identifiers.
Downloads & Older Versions
XML Schema Definition Files (ZIP)
Older versions of this standard can be accessed here.
Finally, the standard defines a uniform method for the transferring catalogue owner or licensee to provide the receiving company with detailed information about the Releases and Resources that make up the catalogue. The term “exclusive” here refers to those sound recording/Resource rights for a specific territory or set of territories.
This specification allows the transmission of information to be secured and caters for non-repudiation requirements to be met. While the location and owner of the FTP/SFTP server used for such transmission is not defined herein (this is left to be agreed by Release Creator and Release Distributor), the structure of the FTP/SFTP severs and names for files are defined by this standard. At this stage, this standard does not address issues arising from data mismatches detected during the information exchange.
This DDEX Standard has seven clauses and two annexes. Clauses 1 and 2 provide a general introduction and the scope of this Standard. Clauses 3 to 5 give a set of normative references as well as terms, definitions and abbreviations that are used in this Standard. Clause 6 then explains the general approach taken by DDEX to message standardisation.
Annex A provides a list of all allowed value sets, including their allowed values and respective definitions as used in this Standard. Finally, Annex B provides the relevant XML Schema files
- DDEX: DDEX Data Dictionary Standard. Latest Version
- DDEX: DDEX Party Identifier (DPID) Standard. Latest Version
- DDEX: DDEX Digital Signature Standard. Latest Version
- DDEX: DDEX Automated Message Exchange Protocol
- DDEX: DDEX Electronic Release Notification Message Suite Standard. Latest Version
- W3C: XML Schema Part 1: Structures. Second Edition. 2004
- W3C: XML Schema Part 2: Data types. Second Edition. 2004
4 Terms and Definitions
A grouping of one or more DDEX Messages to be processed by the recipient together.
A well-defined collection of items such as rights in Musical Works, Right Shares and/or Releases.
Note that the XML tags use the spelling “catalog” instead of catalogue.
An entity in a DDEX Message that has the technical cardinality of 0-1 or 0-n but that is mandatory when a DDEX message is sent in a specific commercial context.
Contractually Mandatory 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 Message Sender and Message Recipient.
Exclusive Rights Owner or Licensee
A company that is either the exclusive owner of all rights for a specific territory of all Resources within a Release or the sole licensee from an exclusive Rights Owner for sound recording/Resource rights for a The term “exclusive” here refers to those sound recording/Resource rights for a specific territory or set of territories.
A company that plays both roles of Release Creator (e.g. in communications to downstream Release Distributors) and Release Distributor (e.g. in communications upstream Release Creators).
A series of message calls and their responses which together communicate a more comprehensive level of meaning between the two business partners.
The concept of ensuring that a party cannot repudiate, or refute, the sending or receiving of a message.
A Release is an abstract entity representing a bundle of one or more Resources compiled by an Issuer. The Resources in Releases are normally primarily sound recordings or music audio-visual recordings, but this is not invariably the case. The Release is not itself the item of trade (or “Product”). Products have more extensive attributes than Releases; one Release may be disseminated in many different Products.
Release Creator is an organisation which is the owner of copyrights in sound and/or music audiovisual recordings and/or exclusive licensees of copyrights in sound and/or music audiovisual recordings.
Release Distributor is an organisation, which is duly authorised by a Release Creator to offer Releases manifested in the form of Products to consumers. Release Distributors include Digital Service Providers (DSPs) and Mobile Service Providers (MSPs) as well as other organisations.
A set of Releases that are closely related. A typical example of a Release Family is an album communicated as a Main Release plus all the Track Releases whose Resources together form the Album.
A digital fixation of an expression of an abstract Work (such as a sound recording, a video, an image, software or a passage of text). Resources are individual assets that make up a Release. Typical Resources are sound recordings, video clips and cover art images.
A unique identifier that links several Web Service Calls/Responses together.
Web Service Call
The sending of an XML document to a port/address on a web server, using HTTP or HTTPS.
|AMEP||Automated Message Exchange Protocol|
|ACA||Appointed Certification Agency|
|AVS||Allowed Value Set|
Confédération internationale des sociétés d'auteurs et compositeurs, the International Confederation of Societies of Authors and Composers (see cisac.org)
|DAW||Digital Audio Workstation|
Digital Data Exchange
|DSP||Digital Service Provider (incudes Mobile Service Providers)|
|DSR||Digital Sales Reporting|
|ERN||Electronic Release Notification|
|FTP||File Transfer Protocol (FTP specifically includes SFTP)|
|GRid||Global Release Identifier|
|HTTP||Hypertext Transport Protocol (HTTP specifically includes HTTPS)|
|HTTPS||Secure Hypertext Transport Protocol|
|IEC||International Electrotechnical Commission (see iec.ch)|
|ISO||International Organisation for Standardisation (see iso.org)|
|MIME||Multipurpose Internet Mail Extensions|
|MLC||Music Licensing Company|
|MWL||Musical Works Licensing|
|MWN||Musical Works Notification|
|PCA||Private Certification Agency|
|Portable Document Format|
|RIN||Recording Information Notification|
|TIS||Territory Information System (a CISAC Standard)|
|TLS||Transport Layer Security|
|URL||Uniform Resource Locator|
|XML||eXtensible Markup Language|
|XSD||XML Schema Definition|
|W3C||World Wide Web Consortium (see w3c.org)|
6 Message Design Approach (informative)
The data elements that are common across multiple message suites will be defined within a Baseline Schema. Individual message suites (such as the one defined by this Standard) are constructed using a combination of “local” elements (which are specific only to the message set) and common elements taken from the Baseline Schema.
Elements taken from the “Baseline Schema” have either a ddex or ddexC namespace prefix (for elements defined by DDEX) or a namespace starting with iso (for elements defined by the International Organisation for Standardisation ISO), whereas elements defined for a particular Standard have namespace prefixes specific to the particular Standard. The elements necessary for the purpose of the Catalogue Transfer Choreography Standard (as defined in this document) have the ccho namespace prefix.
The full namespace for the XML Schema document for this Standard is
The full namespaces for the relevant baseline schema files are constructed to the following schema: http://ddex.net/xml/<date>/<schema>. The applicable baseline schema files for this Standard are indicated in Annex B.
In addition to including the baseline schemas, the schema file defined by this standard includes the schema files of other DDEX standards: DDEX-AMEP and DDEX-ERNM.
W3C’s XML Schema Standard has been used to define the structure of the messages and some of the business rules. However, XML Schema alone cannot easily provide a means for complex and conditional validation but XML tools such as eXtensible Stylesheet Language Transformation (XSLT) and XPath could provide a means of developing standard validation modules for each message set.
7 Catalogue Transfer Choreography
The three mandatory steps of this choreography are:
- An Exclusive Rights Owner Or Licensee who wishes to transfer a catalogue to a new rights owner or licensee, informs its Release Distributor partners. This communication is understood by the Release Distributors as a takedown notice;
- The Exclusive Rights Owner Or Licensee wishing to transfer the catalogue provides the catalogue in the form of an electronic feed to the new exclusive rights owner or licensee; and
- The new Exclusive Rights Owner Or Licensee informs its Release Distributor partners about the transfer. This feed shall include all new identifiers allocated by the new exclusive rights owner or licensee and may, where appropriate, contain new deals that will allow a Distribution Partner to keep the content “live” within its distribution system.
A further step is optional:
- The new Exclusive Rights Owner Or Licensee informs any third parties such as Music Licensing Companies or chart companies about the transfer. This feed shall include all new identifiers allocated by the new rights owner or licensee.
This process, which is ideally completed well in advance of the actual transfer date to give all involved parties sufficient time to act upon the received information, is depicted in Figure 1 below.
Figure 1: Overall Choreography of the Catalogue Transfer Choreography Standard
Security and non-repudiation issues are addressed as specified by DDEX-AMEP.
Step 2 of the process defined in the preceding Subclause shall be executed in accordance with the process described in this Subclause as depicted in Figure 2.
Step 4 of the process defined in the preceding Subclause shall be executed in accordance with the ECHO standard as implemented between the relevant parties. In case where the volume of a catalogue transfer would endanger normal operations or where message exchanges have not yet been established, the process described in this Subclause as depicted in Figure 2 shall be used.
Figure 2: Using FTP to exchange Messages
The trigger to indicate that a Batch is complete is a ManifestMessage as defined in Clause 8.3 of this standard. In exceptional circumstances, such as the support of human intervention, it is permissible to use a zero-byte semaphore file to indicate the upload is complete. This semaphore has to be used instead of an XML manifest formatted in accordance with Clause 8.3. The use of such a semaphore file may trigger a flag on the recipient’s side, indicating the manual nature of the override.
The FtpAcknowledgementMessage is defined in the latest version of DDEX-AMEP.
The structure and file naming conventions are defined in the remainder of this Clause.
In line with the ECHO standard, a Batch is identified by the date and time of its creation in the form YYYYMMDDhhmmssnnn with
- YYYY being the year of Batch creation;
- MM being the month of Batch creation;
- DD being the day of Batch creation;
- hh being the hour of Batch creation;
- mm being the minute of Batch creation;
- ss being the second of Batch creation; and
- nnn being the millisecond of Batch creation.
The message sender shall make sure that the BatchId is unique.
The ManifestMessage, and FtpAcknowledgementMessage (if used), shall be placed into the root folder of the Batch.
Note, if possible, the ReleaseId used should be a GRid as defined in the GRid standard. However, if that is not possible, the Release Creator and Release Distributor shall mutually agree a different unique identifier.
For the avoidance of doubt, this standard supports exchanging information via FTP and/or SFTP. It is for the message sender and message recipient to agree the specific protocol to be used
The file name of the AcknowledgementMessage for each Batch shall be the string “ACK_” followed by the BatchId and the .xml file extension.
The NewReleaseMessages shall be named using the same ReleaseId as used for the enclosing folder with an .xml file extension.
7.5.1 Example of FTP Server Organisation and File Naming Convention (Informative)
The example below shows one Batch with two Releases being delivered. The Batch is not yet acknowledged.
Table 1: Example of FTP Server Organisation and File Naming Convention (Informative)
7.5.2 Order of Processing
The Release Distributor is expected to process Batches in sequence as indicated by the date of the batch name.
In all communications, the NewReleaseMessage, as defined in DDEX-ERNM, shall be used in accordance with the appropriate Business and Release Profiles.
In steps 1, 2 and 4 defined in Clause 7.1, the NewReleaseMessage, as defined in DDEX-ERNM, shall not contain any Deal information.
Figure 3: CatalogTransfer composite within the NewReleasMessage
Note: The CatalogTransfer composite was specifically developed for use within this choreography. It is not part of any other DDEX message suite standard.
Evaluation Licence for DDEX Standards
Subject to your compliance with the terms and conditions of this Agreement, DDEX™ grants you a limited, nonexclusive, non-transferable, non-sublicenseable, royalty-free licence solely to reproduce, distribute within your organisation, and use the DDEX standard specifications (“DDEX Standards”) solely for the purpose of your internal evaluation. You may not make any commercial use of the DDEX Standards under this agreement. No other licences are granted under this agreement.
No representations or warranties (either express or implied) are made or offered by DDEX with regard to the DDEX Standards. In particular, but without limitation, no representations or warranties are made in relation to:
- The suitability or fitness of the standards for any particular purpose;
- The merchantability of the standards;
- The accuracy, completeness, relevance or validity of the standards; or
- The non-infringement of any third party intellectual property rights related to the DDEX Standards.
Accordingly, DDEX and/or its members shall not be liable for any direct, indirect, special, consequential or punitive loss or damages howsoever arising out of or in connection with the use of the standards. IN THE EVENT THAT ANY COURT OF COMPETENT JURISDICTION RENDERS JUDGEMENT AGAINST DDEX AND/OR ITS MEMBERS NOTWITHSTANDING THE ABOVE LIMITATION, THE AGGREGATE LIABILITY TO YOU IN CONNECTION WITH THIS AGREEMENT SHALL IN NO EVENT EXCEED THE AMOUNT OF ONE HUNDRED U.S. DOLLARS (US$ 100.00).
Users of the DDEX Standards are cautioned that it is subject to revision. Users are recommended to use the latest versions, which are available at http://www.ddex.net. The use of outdated versions of the standards is not recommended but may be required by agreement between implementers in particular cases.