DDEX Standard

Skip to end of metadata
Go to start of metadata

5.3.1.1 General

The following common rules shall apply to all Profiles defined in this standard:


(1) All identifiers shall be globally unique. For proprietary identifiers this uniqueness shall apply in conjunction with their namespace.  

Conformance Weighting: 1
(See the ERN Conformance Standard for details.)


(2) The message composite shall contain the Resources for the appropriate profile as indicated in Clause 5.1 (Definition of Release Profiles) 

Conformance Weighting: 1


(3) The MessageID element shall be, in combination of the DDEX Party ID of the Message Sender, globally unique. Thus, a Message Sender shall never re-use a MessageID.

Conformance Weighting: 1


(4) All identifiers with a published syntax shall conform to that syntax.

Conformance Weighting: 1


(5) It is only permissible to communicate a UserDefinedValue attribute if a Namespace attribute is provided alongsid e it, and when the containing element contains UserDefined. 

Conformance Weighting: 1


(6) Percentages shall be provided in the interval [0,100]. 

Conformance Weighting: 1


(7) Where it is mandatory to communicate one data element for each territory for which a Deal is provided, the Message Sender shall either:

  1. Communicate a single element with no TerritoryCode attribute;
  2. Communicate at least one element with the IsDefault attribute set to true (this is typically set to Worldwide). No other elements may have the IsDefault attribute set to true;
  3. Communicate exactly one element with the TerritoryCode attribute set to each of the territories covered by the Deal .

Conformance Weighting for items (7)1-3: 1


(8) Any available information on Contributors that have any of the following roles should be provided if available to the Message Sender : Adapter, Arranger , AssociatedPerformer, Author, Composer, ComposerLyricist, Librettist, Lyricist, NonLyricAuthor, SubArranger, Translator.

Conformance Weighting: 1


(9) Any data fields or composite not defined as being mandatory for a specific Release Profile may still be used by the Message Sender. The Message Recipient may, however, discard any such information at its own discretion. 

Conformance Weighting: 1


5.3.1.2 For Releases and/or Resources

The following common rules shall apply to all Releases and Resources in all Profiles defined in this standard:


(1) All DisplayArtists must be sequenced. 

Conformance Weighting: 1


(2) To communicate "compound main artists" (e.g. "Carlos Santana feat. Eric Clapton") the following information shall be provided:

  1. A DisplayArtistName showing the full name of the compound artist as it should be displayed.
  2. A DisplayArtist composite for each of the artists that make up the compound artist.

    1. The main artist (in the example above Carlos Santana) shall have a DisplayArtistRole of MainArtist.

    2. Additional artists (in the example above Eric Claption) may not have a DisplayArtistRole of MainArtist.

Conformance Weighting for items (2)1-2: 2


(3) It is also permissible to communicate a compound display artist name ("John & Paul") in the DisplayArtist or Contributor composite should the Message Sender be unable, despite best effort, to separate out the constituent artists' names. It should be noted that some companies have established rules for concatenating the constituent components of a compound artist (in the above example an ampersand has been used) and that DDEX, while acknowledging the existence of such rules, does not standardise them.

Conformance Weighting 1


(4) For each SoundRecording and Video, a DisplayTitle and a DisplayTitleText shall be provided as follows to communicate the title as the Release Creator suggests it should be shown to consumers: 

  1. A DisplayTitleText shall be communicated containing, in a single string, the title plus any available sub-title information;
  2. DisplayTitle shall be communicated with the main title in the TitleText sub-element and the sub-title or version title information in the SubTitle element. Sub-title or version title information shall be removed from the TitleText and SubTitle elements alongside any characters that separate the TitleText and SubTitle (such as parentheses);   
  3. Further titles may be provided in the AdditionalTitle composite where main title and sub/version title information shall be separated as in the DisplayTitle composite;
  4. If a title of a SoundRecording or Video contains sub-title or version title information, but the Release Creator wishes the sub/version title information not to be shown to consumers, the Release Creator shall provide:
    1. DisplayTitleText without the sub/version title information;
    2. DisplayTitle without the sub/version title information; and
    3. An AdditionalTitle composite of type ReferenceTitle that does contain the sub/version title information to aid the Message Recipient in managing its catalog of SoundRecordings and Videos.

Conformance Weighting for items (4)1-4: 1


(5) For linking Releases and Resources:  

  1. Each main Release shall have at least one ResourceGroup;
  2. If the Primary Resources of a Release are to be grouped in multiple sets, two (or more) second-level ResourceGroups shall be provided. Each of these shall have a ResourceGroupType of either Side, Component, ComponentRelease, ReleaseComponent or MultiPartWork. The last three values are only valid if used in a message conformant with relevant Variants defined in Clause 5.5 below. Each of these ResourceGroups may contain further ResourceGroups;
  3. R esourceGroups of type Component, ComponentRelease, Side or MultiWorkPart shall be sequenced in the context of their immediate parent ResourceGroup;

  4.  Primary Resources (even if there is only one) shall be sequenced in their ResourceGroupContentItem in the context of their parent ResourceGroup;

  5. Sequence numbers typically start with 1 (but do not have to) and shall increase monotonically, typically by 1 (other increments are also allowed). No duplicates are allowed;

  6. There is only one sequence within a ResourceGroup. ResourceGroups and ResourceGroupContentItems are both numbered within this sequence;

  7. Secondary Resources (e.g. cover images) content items shall not be sequenced;
  8. FrontCoverImages, if included, shall be linked from the top-level ResourceGroup's LinkedReleaseResourceReference  .

  9. Video screen captures, if included, shall be linked from the ResourceGroupContentItem of the Resource they represent by a LinkedReleaseResourceReference element with a LinkDescription of VideoScreenCapture.

Conformance Weighting for items (5)1-6: 1

Conformance Weighting for items (5)7-9: 2


(6) If a Cue is provided either a start time or a duration shall be provided.

Conformance Weighting 2


5.3.1.3 For Releases

The following common rules shall apply to all Releases in all Profiles defined in this standard:


(1) Any main Release intended for consumers shall be identified by either a GRid or by an ICPN  or by a ProprietaryID. Other identifiers may also be provided.

Conformance Weighting: 1


(2) TrackReleases consumption shall be identified by either a GRid, ICPN or by a ProprietaryID.

Conformance Weighting: 1


(3) If a Message Sender is considering the use of an ISRC as an identifier for a TrackRelease, it shall be communicated as a ProprietaryID.

Conformance Weighting: 1


(4) TrackReleases should be identified with an identifier unique to the content and the context (i.e. the main Release it has been taken from).

This can be achieved by, for instance, concatenating the ISRC identifying the TrackRelease's Sound Recording and the ICPN of the album Release.

No Conformance Weighting


(5) There needs to be a Label for each territory for which a deal is provided.

Conformance Weighting: 1


(6) A CLine may be communicated where applicable. If a CLine is provided, the recipient shall ingest it.

Conformance Weighting: 1


(7) At least one ReleaseDate or OriginalReleaseDate (the former is preferred) shall be provided for the Release if available to the Message Sender.

Conformance Weighting: 2


(8) A ResourceGroup of type Side shall only be provided for Releases that may (also) be available with a UseType of PurchaseAsPhysicalProduct. For all other Releases, the only allowed ResourceGroupTypes are Component and  MultiWorkPart .

Conformance Weighting: 2


5.3.1.4 For Resources 

The following common rules shall apply to all Resources in all Profiles defined in this standard:


(1) Primary Resources that are eligible for an ISRC shall be identified by an ISRC.

Conformance Weighting: 2


(2) Secondary Resources shall be identified by a ProprietaryId.  

Conformance Weighting: 1


(3) Within the ResourceList composite, at least one Resource has to be present. Resources need to be provided in the order they appear in the XML Schema. However, that order does not imply that the Resources are sequenced. To sequence resources, the ResourceGroup composite has to be used.

Conformance Weighting: 1


(4) For each Resource, the sender shall provide any identifier for any underlying Musical Work (preferably an ISWC), that it has reasonable access to. 

Conformance Weighting: 1


(5) Information about Composers, Lyricists, ComposerLyricists and Adapters should be provided in the Contributor composite for each Primary Resource, if available.

Conformance Weighting: 2


(6) If a Party is playing multiple roles in creating a SoundRecording or Video, only one Contributor composite shall be provided and all roles the party plays shall be included in that one Contributor field.   

Conformance Weighting: 1


(7) A FirstPublicationDate should be provided for each Primary Resource if available to the Message Sender.

Conformance Weighting: 2


(8) To indicate that a Resource is a pre-order incentive track on a Release, the respective attributes in the relevant ResourceGroupContentItem shall be used. The same applies to instant gratification tracks.

Conformance Weighting: 1


  • No labels