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:
One Release Record of type
RE01describing a Head Release.
If the Message Sender has received a
NewReleaseMessagedefined in DDEX’s Release Notification Message Suite Standard, the “Head Release” is the “
AlbumRelease” as defined in the
One or more Resource Records describing Resources of type
These Records provide information regarding all the Sound Recordings, Videos and other Resources that are contained in the Head Release.
AS02.0Record allows the communication of the basic details of a Musical Work that underpins the Resource, the
AS01.01Record does not allow this. Only Resources that have been used or sold shall be included in this section of the Block. For the avoidance of doubt, if a Head Release has been used or sold, all Resources of that Head Release need to be included in the Sales Report Message.
- None, one or more Musical Work Records of type
MW01.01describing Musical Works.
These Records provide information regarding all the Musical Works that are utilised in the Head Release and/or one of its Resources. As shown in Figure 5, the Musical Work Records are interspersed with the Resource Records. The Musical Work records immediately following a Resource record describe Works used in that Resource.
MW01.01Records may not be used in combination with
For the avoidance of doubt:
AS02.02records may be used within a single Block. One example would be where a DSP communicates, the writers of ten tracks as communicated by the licensee to a works licensor or Rights Conroller but where the eleventh track is a medley created by the DSP comprising multiple Musical Works.
None, one or more Records describing “Sub-Releases” of type
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 and/or Musical Works 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.
One or more Records providing Usage, Revenue or Sales figures of type
SU01/02Records 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 Records
SY05.02 (depending on the commercial model) for each type of use, commercial model and territory any Release contained in the Sales Report Message has been traded under. It is permissible to communicate different types of Summary Records in a single sales/usage report.
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
SY01.01 SY01.01 SY04.01 SY02.02 SY02.02 meets this recommendation, whereas
SY04.01 SY01.01 SY04.01 does not.
Figure 1 shows a Block providing a Head Release with four Resources, three of which include Musical Work information in the Resource Record, whereas one Resource is augmented by Musical Work information in an
MW01.01 Record. Usage, Revenue or Sales are reported for two Sub-Releases as well as for the Head Release.
Note that in the diagram the first
SUxx Record provides Usages, Revenues or Sales for a Sub Release, the second Record provides Usages, Revenues or Sales for a Resource and the last 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.
Also a combination of the three Summary record types is allowed:
If no (or partial) musical work information is available, an
May only follow an