1

RecordType

The type of the Record which shall always contain the value HEAD.

Fixed string

M

HEAD

2

MessageVersion

The version of the DSR message.

This shall be in the form dsrf/xxx/yyy/zzz with 

• xxx being the version number of Part 1: Architecture

• yyy being the identifier of the version of the allowed-value sets used for the DSR message.

• zzz being the version number of Part 8: Record type definitions (this document) that is needed to ingest the DSR messages. This document is version 1.5 of the Record type definitions part of the DSR standard. 

The specific values for the architecture is provided in each of the parts defining a profile for this standard.

The value dsrf/1.1.2/1.6/1.0 would therefore signal that the DSR message was created in accordance with the architecture in version 1.1.2, the allowed-value set of version 1.6 and the Record type definitions of version 1.0.

If the MessageVersion is provided as dsrf/30, Parts 1 and 2 are deemed to be in the initial version as published in 2016.

This capability has been retained for backwards compatibility.

Fixed string

M

dsrf/1.1.2/6/1.0

3

Profile

The identifier of the profile used for the DSR message.

String

M

BasicAudioProfile

4

ProfileVersion

The identifier of the version of the profile used for the DSR message. The value for this Cell is defined in the relevant profile of the DSR standard.

String

M

1.0

5

MessageId

A string used to uniquely identify the DSR message. The MessageId shall be, in combination with the MessageSenderId, globally unique. Thus, a MessageSender shall never re-use a MessageId.

String

M

1234567890

6

MessageCreated Date Time

The date and time on which the DSR message was created. The only allowed format is RFC 3339: YYYY-MM-DDThh:mm:ssTZD, where TZD stands for time zone designator, which can be the letter Z or an offset from UTC in the format +hh:mm or -hh:mm.

Datetime

M

2014-12-14T10:05:00Z

7

FileNumber

Sequence number of the file within the DSR message. The first file shall be numbered “1”. The FileNumber must not be larger than NumberOfFiles.

Integer

M

2

8

NumberOfFiles

The number of files that the DSR message is provided in.

Integer

M

3

9

UsageStartDate

The start date of the reporting period covered by the DSR message in ISO 8601:2004 format. This is a string with the syntax YYYY[-MM[-DD]].

Date

M

2014-12-01

10

UsageEndDate

The end date of the reporting period covered by the DSR message in ISO 8601:2004 format. This is a string with the syntax YYYY[-MM[-DD]].

Date

2014-12-01

11

SenderPartyId

The DDEX Party Identifier (DPID) of the DSR message sender.

DDEX Party Identifier

M

PADPIDA2008120501W

12

SenderName

The full name of the sender of the DSR message.

String

M

Apple

13

Service Description

The service name to which all the sales and/or usage data being reported in the DSR message relates. The ServiceDescription is intended to be a human-readable expression of the totality of the service(s) for which sales and/or usage is being reported in the DSR message. 

The sales and/or usage data being reported in the DSR message may be only in respect of one service offering/tier under the ServiceDescription name in accordance with the bilateral agreement between the licensee and the licensor.

The value in the ServiceDescription Cell may not contain space characters or underscores.

String

M

PremiumService

14

Recipient PartyId

The DDEX Party Identifier (DPID) of the licensor.

A value in the RecipientPartyId Cell is mandatory if the DSR message is sent to one licensor and must not be included when the DSR message is sent to more than one licensor.

DDEX Party Identifier

C

PADPIDA2007081601G

15

RecipientName

The full name of the licensor. 

A value in the RecipientName Cell is mandatory if the DSR message is sent to one licensor and must not be included when the DSR message is sent to more than one licensor.

String

C

SACEM

16

Represented Repertoire

The rights controller(s) of the repertoire represented by the licensor.

Multiple Strings

O

GEMA|PAECOL