This standard defines ten Release Profiles. They are categorised by the structure of elements and sub-elements as defined in the table below.
Table 1 — Release Profiles defined in this Standard
Resources contained in Release
1. Audio Single
2. Video Single
A single music video recording plus support screen capture image.
3. Mixed Media Bundle
A product with a mixture of several audio and video recordings and potentially images and text, plus supporting screen capture per video track and a single cover image.
4. Audio Album
A product with several audio recordings, some of which are not songs, plus supporting cover image, including singles containing more than one Resource. Examples include comedy shows.
5. Video Album
A product with several video recordings, plus screen capture per track and supporting cover image.
A single audio mobile ringtone clip.
7. Long-form Music Video
A multi-chapter long form video recording, plus a supporting cover image and potentially a screen capture per chapter.
8. Digital Boxed Set
A multi-volume/component digital product made up of a number of other existing digital products, plus supporting cover image(s).
1-∞ Images of type FrontCoverImage
0-∞ Images of type VideoScreenCapture
0-∞ items of bonus material
9. Classical Audio Album
A product with several audio recordings, grouped into classical works, plus supporting cover image.
10. Single Resource Release
A single Resource not for distribution to consumers. Typically provided to a partner for finger printing /rights management type services.
Details or communicating such Releases are defined in the DDEX Standard Release Profile for Common Release Types, Version 1.1 with the addition of following constraints (note, the above table has been taken from that standard):
- All available Titles,
DisplayArtistNamesare mandatory to be provided for
- If the sender of the sales report has it’s own
Release, Resource or
ProprietaryIdsshall be provided;(*)
- If the sender of the sales report has any
ProprietaryId, allocated by a third party for a
ProprietaryIdsshall be provided;
- Territorial variations of Releases and Resources should be avoided where possible and the only
WorldWide; the use of
ExcludedTerritoryCodeshould be avoided; and
- Collections and
CueSheetsshould not be provided and may be ignored by the message recipient.
(*) In most circumstances it is recommended to not send any proprietary IDs but to focus on identifiers such as GRid, ISRC and ISWC. However, for sales reports, where recipients often do not have any information about sold Releases before ingesting such reports, any identifiers can help matching the received data to data available in the recipients’ system(s). For example a music publisher might receive, from a record company catalogue information which contains the labels’ internal work identifier (typically called “song ID” or “song code”). If a label would forward this information to all it’s distribution partners and if these then forward this work identifier to the music publisher when sales are reported, the amount of work the publisher needs to do to identify the composer is greatly reduced.