5.3 Definition of the Sales/Usage Report structure where release data is available

When sales and/or usage data is to be reported using the MRBV of the Basic Audio Profile of the DSR standard, where release data is available to the licensee, the following Records shall be communicated in this order:

1. One HEAD Record.

2. One or more summary Records of type SY01.03, SY02.04, SY03.02, SY04.03, SY05.04 or SY12.01.

Which of these summary Records is used is determined by the commercial model the licensee uses, which type of use and the territory any release contained in the Sales/Usage Report has been traded in. The summary Records are described in detail in Part 8 of the DSR standard. It is permissible to communicate different types of summary Records in a single Sales/Usage Report.

It is recommended that the summary Records are provided in a logical order to aid human readability. This would typically mean that summary Records with the same Record identifier are not mixed up even if the Record identifiers may not appear in their numerical order. For example a sequence of SY01.03, SY01.03, SY04.03, SY02.04 and SY02.04 meets this recommendation, whereas SY04.04, SY01.03 and SY04.04 does not.

3. One or more Blocks that contain the following Records:

(a) One Record of type RE01.03.

This Record provides data describing a Head Release. If the licensee has received a NewReleaseMessage defined in DDEX’s Electronic Release Notification Message Suite, the Head Release for the purposes of a Sales/Usage Report created in accordance with this profile is the Album Release as defined in the NewReleaseMessage.

(b) One or more Records of type AS02.04.

Each of these Records provide data describing each sound recording, music video or other resource that is contained in the Head Release and basic details about the musical work(s) that are embodied in each such sound recording, music video or other resource.

Only a resource (that is a sound recording, music video or other resource) that has been sold or used shall be included in the AS02.04 Record in this section of the Block. For the avoidance of doubt, if the Block is describing a Head Release that has been sold or used, which contains multiple resources, all the resources that embody musical work(s) that are contained in that Head Release need to be included in multiple AS02.04 Records in the Block.

(c) Instead of using an AS02.04 Record the licensee may wish to present the data in two Records. This is achieved as follows:

(i) One or more of Record of type AS01.03.

Each of these Records provide data describing each sound recording, music video or other resource that is contained in the Head Release but without any details about the musical work(s) embodied in that sound recording, music video or other resource.

Only a resource (that is a sound recording, music video or other resource) that has been sold or used shall be included in the AS01.03 Record in this section of the Block.

(ii) None, one or more Records, of type MW01.03.

Each of these Records provides data describing the musical work(s) embodied in the sound recording, music video or other resource (as described in the AS01.03 Record).

If the Block containing an AS01.03 Record followed by MW01.02 Record(s) is describing a Head Release that has been sold or used, which contains multiple resources, all the resources that embody musical work(s) that are contained in that Head Release need to be included in the Block. This is achieved by stringing together multiple AS01.03+MW01.03 pairs of Records.

This is shown in Figure 1, where the musical work Records (MW01.03) are interspersed with the resource Records (AS01.03). The MW01.03 Record immediately following an AS01.03 Record describes the musical work(s) embodied in that resource.

MW01.02 Records may not be used in combination with AS02.04 Records.

AS01.03 + MW01.03 and AS02.04 Records may be used together within a single Block. One example would be where the licensee communicates the writers of ten tracks to the licensor but where the eleventh track is a medley created by the licensee comprising multiple musical works.

(d) None, one or more Records of type RE02:

Each of these Records provide data describing Sub-Releases. These Sub-Releases are either single resource Track Releases (as communicated in a NewReleaseMessage) and/or releases that the licensee 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 sold or used shall be included in this section of the Block.

(e) One or more Records of type SU01.04 or SU02.03:

These Records provide data describing sales and/or usage of the Head Release or Sub-Release described in the Block. Which sales and/or usage Record is to be used for a particular Sales/Usage Report is determined by the commercial model and use type the licensee is using (see Clause 5.4). Each SU Record shall point to the Head Release or Sub-Release Record to which the sales and/or usage data relates.

4. One FOOT Record.

Figure 2 depicts the layout of the MRBV of this profile where release data is available. In the diagram on the left, the illustrative Block contains a Head Release (the RE01.03 Record) with three resources, all of which (the AS02.04 Records) include musical work data in the resource Record. Sales and/or usage data is then reported for that release.

Figure 2 – Layout of a Block (as described in Point 3 above) in the MRBV of the Basic Audio Profile where release data is available

Figure 3 below depicts more complex use cases where the first SU Record provides sales and/or usage data for a Sub Release comprising two or the three resources that make up the Head Release, whereas the remaining two SU Records provide sales and/or usage data for the Head Release. Thus the first SU Record points to the RE02 Record which, in turn points to multiple AS Records.

Figure 3 – Layout of the MRBV of the Basic Audio Profile where release data is available

The table below provides an overview of the order and cardinality of the Records to be used in this profile where release data is available.