8.1 File name convention

All files that make up CDM messages shall be named in accordance with the following syntax:

MessageType_MessageRecipient_MessageSender_ServiceDescription_MessageNotificationPeriod_TerritoryOfUseOrSale_MessageCreatedDateTime.ext

The following defines what each element of the syntax means:

MessageType

The name of the profile as defined in the appropriate part of the CDM standard. For CDM Statements, for example, this might be Claims for a CDM Statement using the Claims profile or OverclaimDiscrepancy for a CDM Notification using the Notification of Overclaim Discrepancies profile. In case of retractions in accordance with Clause 6.2, the message type shall be set to CDMRetraction.

MessageRecipient

The party name or DDEX Party ID (DPID) of the CDM message recipient.

This data shall be the same as the data conveyed in the header Record in the RecipientPartyId or RecipientName Cell of the CDM message.

DDEX Party IDs do not contain special characters (including dashes).

MessageSender

The party name or DDEX Party ID (DPID) of the sender of the CDM message or, where appropriate, the entity on behalf of whom the CDM message is sent.

This data shall be the same as the data conveyed in the header Record in the RecipientPartyId or RecipientName Cell of the CDM message.

DDEX Party IDs do not contain special characters (including dashes).

ServiceDescription

A description of the service name (e.g. a service tier) to be reported on. Multiple tiers can be communicated by separating them with dashes (Unicode U+2010).

This data shall be the same as the data conveyed in the header Record.

Message-
Notification-
Period

The reporting period covered by the CDM message in accordance with ISO 8601. The only allowed syntaxes

are:

  • yyyy for a year;

  • yyyy-mm for a month;

  • yyyy-mm-dd for a day;

  • yyyy-qq for a quarter;

  • yyyy-ww for a week (starting on a Monday); and

  • yyyy-mm-dd--yyyy-mm-dd with the two dates being the start and end date of the period as signified by the two dashes between the two dates.

TerritoryOf-
UseOrSale

The territory in respect of which the sales and/or usage data originally provided in a DSR Message took place and for which the various messages created in accordance with the CDM standard are exchanged between the licensee and the licensor in order to establish the relevant musical work claims in respect of such sales and/or usage.

The TerritoryOfUseOrSale shall be provided as a single ISO Territory Code if one territory is to be communicated. Otherwise, the sender and the recipient shall agree a value acceptable to both.

MessageCreatedDateTime

The date and time on which the CDM message was created. The only allowed format is the full basic ISO 8601 format without a time zone designator: yyyyymmddthhmmss. The time zone is assumed to be the one of the CDM message sender's location. 20220304T123255020 would represent 12:32:55.020 on 4th March 2022.

ext

The file extension, to be .tsv

When the file is compressed, for example with gzip, the extension should indicate this and may be .tsv.gz.

 

The following further constraints apply in respect of the elements of the file naming syntax:

  1. None of the file name elements may contain an underscore character;

  1. None of the file name elements may contain a space character;

  1. No file name element may be omitted;

  1. Other file naming conventions may be agreed between the sender and the recipient (specifically for testing).

Search