THIS VERSION IS NOT THE LATEST RELEVANT DDEX STANDARD. DDEX RECOMMENDS TO USE THE LATEST VERSION.

Skip to end of metadata
Go to start of metadata

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

Release Profile
Name and description

Resources contained in Release

 

Primary Resources/Collections

Secondary Resources

 

1. Audio Single
A single SoundRecording plus supporting cover image.

  • 1-∞ SoundRecording of type MusicalWorkSoundRecording
  • 1 Image of type FrontCoverImage,
  • 0-∞ items of bonus material
  
 

2. Video Single

A single music video recording plus support screen capture image.

  • 1-∞ Video of type ShortFormMusicalWorkVideo
  • 1 Image of type VideoScreenCapture
  • 0-∞ items of bonus material
  
 

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.

  • 0-∞ SoundRecordings of type MusicalWorkSoundRecording
  • 0-∞ Videos of type ShortForm­MusicalWorkVideo
  • 0-∞ Images of type Photo­graph, FrontCover­Image, BackCoverImage, Booklet­FrontImage BookletBack­Image, Poster or Wallpaper
  • 0-∞ Texts
  • At least 2 Resources of different types
  • 1 Image of type FrontCoverImage
  • 0-∞ Images of type Video­ScreenCapture
  • 0-∞ items of bonus material (e.g. such as Images and Booklets)
  
 
 

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.

  • 1-∞ SoundRecordings of type MusicalWorkSoundRecording or NonMusicalWorkSound­Recording
  • 1 Image of type FrontCoverImage
  • 0-∞ items of bonus material
  
 

5. Video Album

A product with several video recordings, plus screen capture per track and supporting cover image.

  • 1-∞ Video of type ShortFormMusicalWorkVideo
  • 1 Image of type FrontCoverImage
  • 0-∞ Images of type VideoScreenCapture
  • 0-∞ items of bonus material
  
 

6. Ringtone

A single audio mobile ringtone clip.

  • 1 SoundRecording of type RingtoneClip
  • 0-1 Image of type FrontCoverImage
  
 

7. Long-form Music Video

A multi-chapter long form video recording, plus a supporting cover image and potentially a screen capture per chapter.

  • 1 Video with a type of either LongFormMusicalWorkVideo, ConcertVideo or Documentary
  • 1 Image of type FrontCoverImage
  • 0-∞ Images of type VideoScreenCapture
  • 0-∞ items of bonus material
  
 

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).

  • 0-∞ SoundRecordings of type MusicalWorkSoundRecording
  • 0-∞ Videos of type ShortFormMusicalWorkVideo

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.

  • 1-∞ SoundRecordings of type MusicalWorkSoundRecording, albeit with additional elements as defined below
  • 1 Image of type FrontCoverImage
  • 0-∞ items of bonus material
 

 

10. Single Resource Release

A single Resource not for distribution to consumers. Typically provided to a partner for finger printing /rights management type services.

  • 1 Resource of any type

None

 


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):

  1. All available Titles, DisplayArtistNames are mandatory to be provided for Releases and Resources;
  2. If the sender of the sales report has it’s own ProprietaryId for a Release, Resource or MusicalWork, such ProprietaryIds shall be provided;(*)
  3. If the sender of the sales report has any ProprietaryId, allocated by a third party for a MusicalWork, such ProprietaryIds shall be provided;
  4. Territorial variations of Releases and Resources should be avoided where possible and the only TerritoryCode should be WorldWide; the use of ExcludedTerritoryCode should be avoided; and
  5. Collections and CueSheets should 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.

 

  • No labels