8.4 DJ mix profile

A release for a DJ mix profile release shall meet the following rules in addition to the rules stipulated in Clause 7:

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

2. The NewReleaseMessage shall contain at least two SoundRecordings classified as Secondary Resources that are not directly referenced from the Release via the ResourceGroup element (the mix components).

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

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

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

6. Notwithstanding the rules on the identification of Secondary Resources elsewhere in this part of the ERN standard, mix component SoundRecordings shall be identified with an ISRC. There is no requirement to identify them with a ProprietaryId.

7. If a record company or distributor wishes to send DJ mixes but does not have access to the data required above, that record company or distributor cannot use the DJ mix profile. Instead, such releases can be communicated using the audio profile (as set out in Clause 6.2).