5.2 Multi Record Block Variant of this Profile

The following Records shall be communicated for each Block in this order:

1. One Resource Record of type AS02.03 describing the Resource including basic information of the underlying Work (the Work part of this data shall be included as provided by the record company to the Licensee). 
   The Message Sender may wish to split the information into multiple Records instead of using one AS02.03 Record:

   1. The first Record, of type AS01.02, contains information regarding the Sound Recordings, Videos and other “master” Resources that have been used in creating the user-generated content that has been accessed;

   2. The following none, one or more Musical Work Record(s), of type MW01.02 contain information about the Musical Work(s) utilised as provided by the record company to the Licensee. If the Resource contains more than one Work, the Work shall be communicated in multiple Blocks so that only one Work is reported in a Block). 

2. None, one or more Records providing data about the same Resource/Work described in the above AS/MW Records. However, these LC01 Records provide the information a received, by the Licensee, from the Record Company or Aggregator listed in the DataProvider Cell. The LC01 Records are optional as bi-laterally agreed between Licensee and Licensor.

3. None, one or more UGC Release Usage Records of type RU01.02 describing the use of UGC Releases. 
   Instead of a RU01.02 record, the Message Sender may use one RU02.02 Record for each UGC Release and its use. 
   It is not permissible to communicate RU01.02 and RU02.02 Records in one Block. 
   The Block shall contain multiple RUxx Records for each ASxx Record in that one RU01.02 Record shall be provided for each ContentCategory; one RU02.02 Record shall be provided for each UGC Release.

4. One or more UGC Sales/Usage Record of type SU03.02 Record followed by

   1. None, one or more Licensor-specific Usage Data Record of type LI01.03 providing Licensor-specific information for the usages reported in the preceding SU03.02.

   2. Each of the LI01.03 records followed by none or one MW01.02 Record to indicate Licensor-specific Work information. These Records shall contain the Work information provided to the DSP by the RightsContoller referenced in the preceding LI01.03 Record.

All records, unless specifically indicated, shall represent the data as used by the Licensee for its own processes.

The Blocks shall be preceded by one or more Summary Records SY02.03, SY04.02, SY05.03 or SY09.01 for each type of use, commercial model and territory any Release contained in the Sales Report Message has been traded under. In cases where a Message Sender provides information at RightsController level, the fields at RightsController level in SY02.03 or SY04.02/SY05.03 and LI01.03 records can be provided.

When using SY04.02, all SY04.02 Records for the same RightsType and sales context (as defined in Clause 6.5 of Part 1 of this standard) may carry the same SummaryRecordId if per-subscriber minima information needs communicating per context, but across different subscriber types. Each SY05.03 records shall be followed by 1-n groupings of 1 SY09.01 Record, followed by 1-n SY05.03 Records:

• 0-n SY04.02 

  • 1-n SY09.01

    • 1-n SY05.03

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  SY04.02 SY04.02 meets this recommendation, whereas SY02.04 SY02.03 SY04.02 

The figure shows two ways in which this Profile can be implemented. The left-hand diagram shows the case where Musical Work information is provided as part of the Resource Record (AS02.03) and only a usage summary Record is RU01.02 is provided and the right-hand diagram shows the case where Musical Work information is provided on an extra MW01.02Record and usage information is provided in multiple RU02.02 Records. For the avoidance of doubt, it is also possible to use AS02.03 Records together with RU02.02 Records as well as AS01.02/MW01.02 with RU01.02.

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

For cases where the Message Sender has not received a claim for a sound recording from its owner, the AS01.02/AS02.03  record shall be virtually empty, only containing a RecordType and a BlockId.