DDEX Standard

Skip to end of metadata
Go to start of metadata

A Release for a DjMix shall meet the following rules in addition to the rules stipulated in Clauses 5.2 and 5.3 :


(1) The NewReleaseMessage shall contain exactly one SoundRecording, classified in accordance with Clause 4.1 as a Primary Resource that is directly referenced from the Release via the ResourceGroup element (the "mix").

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


(2) The NewReleaseMessage shall contain at least two SoundRecordings "classified in accordance with Clause 4.1" as a Secondary Resource that are not directly referenced from the Release via the ResourceGroup element (the "mix components").

Conformance Weighting: 1


(3) These Secondary Resources shall have the IsSupplemental flag set to "true".

Conformance Weighting: 1


(4) The mix component shall be referenced, together with a StartPoint and DurationUsed, from the mix by a RelatedResource of type HasContentFrom.

Conformance Weighting: 1


(5) Each mix component shall be pointed to from the mix.

Conformance Weighting: 1


(6) Notwithstanding the rules on the identification of secondary Resources elsewhere, mix component Sound Recordings shall be identified with an ISRC. There is no requirement to identify them with a ProprietaryId.

Conformance Weighting: 1


(7) If a message sender wishes to send DJ mixes but does not have access to the data required above, that message sender cannot use the DjMix Release Profile. Instead, such Releases can be communicated using the Audio profile.


  • No labels