5.2 Definition of Blocks where Release Information is Available

When Usages, Revenues or Sales are to be reported where Release information is available to the Message Sender, the following Records shall be communicated for each Block in this order:

1. One Release Record of type RE03.02 describing an audio-visual Head Release.
   If the Message Sender has received a NewReleaseMessage defined in DDEX’s Release Notification Message Suite Standard, the “Head Release” is the AlbumRelease as defined in the NewReleaseMessage.

2. One or more Resource Records describing Resources of type AS03.02.
   These Records provide information regarding all the Videos that are contained in the Head Release.

3. None, one or many Cue Records of type CU01.01.
   Cue Records allow the identification and description of cues, i.e. information about Musical Works or Resources that have been used in a specific Resource and how they have been used. As shown below, the Cue Records are interspersed with the Resource Records. The Cue record immediately following a Resource records are Cues for that Resource

4. None, one or many Cue Records of type CU02.
   Cue Records allow the identification and description of cues, i.e. information about Musical Works or Resources that have been used in a specific Resource and how they have been used. As shown below, the Cue Records are interspersed with the Resource Records. The Cue record immediately following a Resource records are Cues for that Resource

5. None, one or more Records describing “Sub-Releases” of type RE02.
   These Sub-Releases are either single-Resource Track Releases (as communicated in a NewReleaseMessage) and/or Releases that the Message Sender has generated exclusively from the Resources that are used in the Head Release. The Sub-Release Records shall point to the Resources they make use of. Only Sub-Releases that have been used or sold shall be included in this section of the Block.

6. One or more Records providing Usage, Revenue or Sales figures of type SU01.02 SU02.02, SU03.03, SU04.02 or SU06.
   The SUxx Records shall point to the Release Record to which the Usage, Revenue or Sale transaction relates.

The Blocks shall be preceded by one or more Summary Record SY02.03, SY04.02, SY05.03 or SY06.02 for each Rights Controller to whom the Sales Report Message is addressed, to provide information on Usage, Revenue or Sales allocated to that Rights Controller according to the calculations made by the Message Sender.

It is permissible to communicate different types of Summary Records in a single sales/usage report.

When using SY04.01, all SY04.01 records for the same RightsType and sales context (as defined in Clause 6.5 Part 1 of this standard) may carry the same SummaryRecordId if subscriber minima information needs communicating per context, but across different subscriber types.

It is recommended to provide the Summary Records in a logical order to aid human readability. This would typically mean that Summary Records of different types are not mixed. For example a sequence of SY02.03 SY02.03 SY06.02 SY06.02 SY06.02 meets this recommendation, whereas SY06.02 SY02.03 SY06.02 does not.

Note that in the diagram the first SUxx Record provides Usages, Revenues or Sales for a Sub Release, the second SUxx Record provides Usages, Revenues or Sales for the Head Release.

The table below provides an overview of the order and cardinality of the Records to be used in this Profile.