DDEX Standard

Skip to end of metadata
Go to start of metadata
 

1 Introduction

The Digital Sales Reporting Message Suite Standard was developed by the member organisations of the Digital Data Exchange, LLC (DDEX) and the various profiles within the Standard provide a uniform mechanism to enable Licensees (typically Digital Service Providers) to report to Rights Controllers (typically Music Rights Societies, Music Publishers, Music Licensing Companies and/or Record Companies) information regarding the level of sales, usage and/or revenue generated from the distribution of such products to the relevant Rights Controllers and to enable the exchange of information between such parties in relation to various business processes that support those activities.

This Profile of the Digital Sales Reporting Message Suite Standard enables a Licensee to communicate to a Licensor a list of Resources (such as sound recordings or videos) that are used in their service before sending any sales or usage  figures. This allows Licensors to carry out the matching of Musical Works to those Resources before any sales or usage figures are received, and thus report back to the Licensee its claims in respect of the Musical Works they represent . 

Any organisation wishing to implement this (or any other DDEX standard) is required to apply for an Implementation Licence. The terms of the licence and an application form can be found on https://ddex.net/implementation/implementation-licence-and-ddex-party-identifiers.

Essential Reading

Download/Print standard (PDF)

This standard is Part 10 of a multi-part standard. The other parts (incl. samples) are available here.

 

 

2 Scope

 2.1 Introduction
The message defined in this Part provides a mechanism for Licensees (typically Digital Service Providers) to communicate to Rights Controllers (typically Music Rights Societies and/or Music Publishers) a list of Resources, potentially with information about the underlying Musical Work(s) without any sales or usage figures. Licensors are thereby able to make claims in respect of the Musical Works contained on those Resources – for example using the DDEX Claim Detail Message Suite Standard – before the Licensor is in receipt of any sales or usage information from the Licensor – for example using one of the Profiles for such reporting set out in other parts of the Digital Sales Reporting Message Suite Standard.
 2.2 Organisation of the Standard
This standard comprises five clauses and one annex. Clauses 1-4 provide the scope, abbreviations and core definitions used in this standard. Clause 5 then defines the Masterlist profile. 

Finally, Annex A provides some examples.

3 Normative References

 Click here to expand...

The following normative documents contain provisions, which through reference in this text constitute provisions of this standard. For dated references, subsequent amendments to, or revisions of, any of these publications do not apply. For undated references, the latest version applies.

  • DDEX. Digital Sales Reporting Message Suite Standard - Part 1: Architecture of the Flat File Variant.
  • DDEX. Digital Sales Reporting Message Suite Standard - Part 2: Allowed Value Sets.
  • DDEX. Digital Sales Reporting Message Suite Standard - Part 8: Record Type Definitions.

4 Terms and Abbreviations

 Click here to expand...

5 Masterlist profile

 5.1 Introduction
This Profile sets out a standard message format that enables a Licensee to communicate information about Resources it has received from the owner of those Resources (the “master” Recording), or as part of a claims process by the owner of the Resources, to the Licensors or RightsController of the Musical Works contained in those Resources. The message may or may not include information specific to the Licensors or RightsControllers, to enable each Licensor or RightsController to make claims in all or part of any Musical Work embodied in the Resources before any sales or usage information is exchanged. 

To indicate that a message is created in accordance with the Multi-Record Block Variant of this Profile, the Profile Cell in the HEAD Record shall contain the value MasterListProfile and the ProfileVersion Cell shall contain the value 1.0.

To indicate that a message is created in accordance with the Single-Record Block Variant of this Profile, the Profile Cell in the HEAD Record shall contain the value MasterListProfileSRB and the ProfileVersion Cell shall contain the value 1.0.

If a Licensee and Licensor use the DSR standard for both pre-usage and post-usage reporting, the Licensee shall make reasonable endeavours that the data provided for describing Releases, Resources and Works remain stable. 

 5.2 Multi Record Block Variant of this Profile where Release Information is available
When masterlist information is to be communicated where information about the Releases containing the Resources is available to the Message Sender, the following Records shall be communicated for each Block in this order
  1. One Record describing a Release of type RE01.01

  2. Exactly one or more Resource Records describing a Resource of type AS02.03 providing information regarding the Sound Recording, Videos and other Resources that are to be reported. Musical Work information, if provided, should be the metadata as sent to the Licensee by the company that provided the metadata about the Resource containing that Musical Work.

  3. Exactly one Master List Data Record ML01.
  4. For each of the AS02.03 Records: None, one or more Musical Work Records of type MW02 providing any information previously provided by the Licensor to the Licensee about the Musical Works that are embodied in the Resources reported in the AS02.03 Records.

The Blocks shall be preceded by one or more Summary Records SY11.


Figure 1 – Block of the Masterlist Profile where Release Information is available (MRBV)

 

The table below provides an overview of the order and cardinality of the Records to be used in this Variant. It is also depicted in Figure 1 above.

RecordTypeCardinality
Comment

HEAD

1 

SY11

1-n

 

Block0-n 
| RE01.01 0-1  1 

| | AS02.03

1-n

This AS02.03 record is to contain any Musical Work information that has been previously sent from the company that provided the Resource metadata to the Licensee.

| | | ML011 
| | | MW020-n

These MW02 Records shall contain any Musical Work information previously provided to the Licensee by a Licensor.

FOOT 1 
 5.3 Multi Record Block Variant of this Profile where Release Information is not available
When masterlist information is to be communicated where no information about the Releases containing the Resources is available to the Message Sender, the following Records shall be communicated for each Block in this order:
  1. Exactly one Resource Record describing a Resource of type AS02.03  providing information regarding the Sound Recording, Videos and other Resources that are to be reported. Musical Work information, if provided, should be the metadata as sent to the Licensee by the company that provided that metadata about the Resource containing the Musical Work.

  2. Exactly one  Master List Data Record ML01.
  3. For each of the AS02.03 Records: None, one or more Musical Work Records of type MW02 providing any information previously provided by the Licensor to the Licensee about the Musical Works that are embodied in the Resources reported in the AS02.03 Record.

The Blocks shall be preceded by one or more Summary Records  SY11.


Figure 2 – Block of the Masterlist Profile where Release Information is not available (MRBV)

 

The table below provides an overview of the order and cardinality of the Records to be used in this Variant. It is also depicted in Figure 2 above.

RecordTypeCardinality
Comment

HEAD

1 

SY11

1-n

 

Block0-n 

| AS02.03

1-n

This  AS02.03 record is to contain any Musical Work information that has previously been sent from the company that provided the Resource metadata to the Licensee.

| | ML011 
| | MW020-n

These MW02 Records shall contain any Musical Work information previously provided to the Licensee by a Licensor.

FOOT 1 
 5.4 Single Record Block Variant of this Profile
The Single Record Block Variant differs from the Multiple Record Block Variant in that the Block of the Multiple Record Block Variant is replaced by an SR07 Record and that the generic Footer record FOOT is replaced by a Footer Record specifically designed for Single Record Block Variants: SRFO.

 

Figure 3 – Format of the Masterlist Profile (SRBV) 

 

The table below provides an overview of the order and cardinality of the Records to be used in this Variant. It is also depicted in Figure 3 above.

 

 

RecordTypeCardinality
Comment

HEAD

1 

SY11

1-n

 

SR07

0-n 
SRFO 1 

Annex A (informative) Examples

 Click here to expand...

Published alongside this standard are a series of Examples in the form of an Excel workbook. To transform them into Sales Report messages in accordance with this standard, the individual tabs of the spreadsheet can be saved as a tab-delimited file

Evaluation Licence for DDEX Standards

 

 

Subject to your compliance with the terms and conditions of this Agreement, DDEX™ grants you a limited, nonexclusive, non-transferable, non-sublicenseable, royalty-free licence solely to reproduce, distribute within your organisation, and use the DDEX standard specifications (“DDEX Standards”) solely for the purpose of your internal evaluation. You may not make any commercial use of the DDEX Standards under this agreement. No other licences are granted under this agreement.

No representations or warranties (either express or implied) are made or offered by DDEX with regard to the DDEX Standards. In particular, but without limitation, no representations or warranties are made in relation to:

  1. The suitability or fitness of the standards for any particular purpose;
  2. The merchantability of the standards;
  3. The accuracy, completeness, relevance or validity of the standards; or
  4. The non-infringement of any third party intellectual property rights related to the DDEX Standards.

Accordingly, DDEX and/or its members shall not be liable for any direct, indirect, special, consequential or punitive loss or damages howsoever arising out of or in connection with the use of the standards. IN THE EVENT THAT ANY COURT OF COMPETENT JURISDICTION RENDERS JUDGEMENT AGAINST DDEX AND/OR ITS MEMBERS NOTWITHSTANDING THE ABOVE LIMITATION, THE AGGREGATE LIABILITY TO YOU IN CONNECTION WITH THIS AGREEMENT SHALL IN NO EVENT EXCEED THE AMOUNT OF ONE HUNDRED U.S. DOLLARS (US$ 100.00).

Users of the DDEX Standards are cautioned that it is subject to revision. Users are recommended to use the latest versions, which are available at http://www.ddex.net. The use of outdated versions of the standards is not recommended but may be required by agreement between implementers in particular cases.