Skip to end of metadata
Go to start of metadata

This section of the Knowledge Base, aimed at explaining how to implement and use the DDEX standards for Release Deliveries – typically sent from record companies to online retailers/digital service providers – to technical implementers as well as operational personnel.

Before starting an implementation, DDEX recommends to read Starting an Implementation and Licensing DDEX Standards. And consider joining the DDEX Implementers' Forum.

Implementing Release Deliveries requires familiarity with three core concepts:

  • The Baseline XML standard

     Click here to expand...

    The Electronic Release Notification Message Suite Standard (informally called the "Release Notification Message Standard", see URL) is one of several XML message formats published by DDEX. Release notifications are messages that record labels or aggregators send to distributors to inform them of new releases that are available for distribution, and the terms and conditions under which such releases can be made available.

    The Release Notification Message Standard addresses the problem of a record company or aggregator having to send its products to distribution partners in multiple formats. It can be used for everything from a single release with a single deal, to the communication of a sales campaign that includes price changes over the course of time. Its three main elements are Resources, Releases, and Deals. Resources are the primary assets such as audio or video tracks, and also secondary assets such as cover images and PDF booklets. Releases are the principal products that encompass the resources, and Deals are the descriptions that define how a Release may be used.

  • Profiles that narrow down the baseline standard for use in specific use cases

     Click here to expand...

    The Release Notification Standard is quite large to accommodate the numerous business models in use today within the digital music supply chain. In order to reduce the complexity for implementing organisations, DDEX has developed two complementary standards to assist with this process.

    The profile standards define subsets of the full standard for the most common types of Releases and Deals — thus making an implementation straightforward and comparatively simple — by differentiating different kinds of business models (e.g. Download Services, Subscription Streaming Services, Web Radio, etc.) and different kinds of Re-leases (e.g. albums, singles, classical albums, ringtones, etc.).

  • A choreography allowing sender and recipient to automate the exchange of information

     Click here to expand...

    The Release Delivery Choreography Standard (see URL) provides a rich set of capabilities developed by DDEX that allows small niche firms to large multinational companies to utilise the Release Notification Standard.

    The most basic specification — using FTP — is designed to be simple to implement, but has no additional functionality allowing customisation or visibility into the supply chain. At the other end of the scale, the more granular specification — using web services — allows considerable additional flexibility, much greater visibility and a more efficient supply chain.

    DDEX recommends using acknowledgements when using the FTP choreographies to support non-repudiation. Read more here.

The formal documents addressing these three aspects can be downloaded from the box on the right.

This section of the DDEX Knowledge Base covers the following areas:


Download Standard

Electronic Release Notification (Version 3.8.2)

Versions 3.7.1 and 3.4.1 (incl. Profiles and samples) can be accessed here.

Choreography Standards

ERN Conformance

To access older versions, please contact the DDEX Secretariat.

Before starting an implementation, DDEX recommends to read Starting an Implementation and Licensing DDEX Standards.

Essential Reading

MusicBiz and DDEX have created a "Starter Guide" for Release Notifications. You can download the guide here.

Terms used in the above standards

Contact DDEX

If you have a question or suggestion or if you are experiencing problems with your implementation, please have a look at the DDEX Implementers' Forum. You may find an answer to your question there Or contact the DDEX Secretariat; we may be able to help.


  • No labels
Write a comment…