This standard was developed by the member organisations of the Digital Data Exchange, LLC (DDEX) and provides a message that gives 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 usage and/or revenue generated from the distribution of such products, as well as sales of products based on Releases, to the relevant Rights Controllers.
This Profile of version 3.0 of the Flat File Variant has been developed in response to concerns regarding the file size and computational complexity of the XML Variant, and will lead to reduced implementation and running cost for Licensees and Licensors for user-generated content where the Message Sender either has, or has not, received a claim for a sound recording from the owner of that sound recording (the “master” Recording).
This standard is Part 6 of a multi-part standard. The other parts (incl. samples) are available here.
Samples for the current version of the DSR Standard can be found here.
The message defined in this standard provides a mechanism for Licensees (typically Digital Service Providers) to report to Rights Controllers (typically Music Rights Societies, Music Licensing Companies, Music Publishers and/or Record Companies) Royalties based on usages of musical Releases that took place in counties where there is a contractual link between Message Sender and Message Recipient (e.g. the US and Canada) to report royalties in addition to usage/sales figures.
This Profile is not intended to be used for “notices of intent” or “statutory rate” type of usages which (specifically in the case of streaming royalties) require a different data set to work out the royalty.
2.2 Organisation of the Standard
This standard comprises six clauses and one annex. Clauses 1-4 provide the scope, abbreviations and core definitions used in this standard. Clauses 5 and 6 then defines the profile.
Finally Annexes A provides some examples.
2.3 Release Notes (Informative)
Version 1.0.1 corrects an error in the structure of the profile and the LI01 record.
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...
The terms and abbreviations used in Digital Sales Reporting Message Suite Standard – Part 1: Architecture of the Flat File Variant. also apply to this Standard.
5 Royalty Reporting Profile
5 Royalty Reporting Profile
This Profile is for reporting Royalties based on Usages, Revenues and/or Sales of Releases.
To indicate that a Sales/Usage Report is created in accordance with this Profile standard, the Profile Cell in the HEAD Record shall contain the value RoyaltyReportingProfile and the ProfileVersion Cell shall contain the value 1.0.1.
The following Records shall be communicated for each Block in this order:
None or one Release Record of type RE01 describing a Head Release. If the Message Sender has received a NewReleaseMessage defined in DDEX’s Release Notification Message Suite Standard, the “Head Release” is the AlbumRelease as defined in the NewReleaseMessage;
One or more Intra-Block Groupings of Records providing:
One Resource Records describing Resources of type AS01 or AS02.01. These Records provide information regarding all the Sound Recordings, Videos and other Resources that are contained in the Head Release. While the AS02.01 Record allows the communication of the basic details of a Musical Work that underpins the Resource, the AS01 Record does not allow this. Only Resources that have been used or sold shall be included in this section of the Block. For the avoidance of doubt, if a Head Release has been used or sold, all Resources of that Head Release need to be included in the Sales Report Message;
None, one or more Musical Work Records of type MW01.01 describing Musical Works. These Records provide information regarding all the Musical Works that are utilised in the Head Release and/or one of its Resources. As shown in Figure 5, the Musical Work Records are interspersed with the Resource Records. The Musical Work records immediately following a Resource record describe Works used in that Resource. MW01.01 Records may not be used in combination with AS02.01 Records;
For each Work (in AS02.01 or MW01.01)
None, one or many Records providing Resource Usage, Revenue or Sales figures of type RU01 or RU02.
At least one sub-grouping shall be provided, which relates to the Work and consists of
One Sales/Usage Record of type SU03.01; and
One or more Licensor-specific Sales/Usage Record of type LI01.01.
The Blocks shall be preceded by one or more Summary Record SY07 for each Rights Controller to whom the Sales Report Message is addressed, to provide information on Usage, Revenue or Sales allocated to that Rights Controller according to the calculations made by the Message Sender. Each LI01.01 Record shall point to one of the SY07 Records.
The layout of a Block is depicted below (note that the RE01 can be omitted if no Release information is available ad the AS02.01 can be replaced by a AS01 followed by a MW01.01):
Figure 1 – One Block of Records when Reporting Royalties
The table below provides an overview of the order and cardinality of the Records to be used in this Profile.
AS01 or AS02.01
May only follow AS01
RU01 or R02
For cases where the Message Sender has not received a claim for a sound recording from its owner, the AS01/AS02 record shall be virtually empty, only containing a RecordType and a BlockId.
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:
The suitability or fitness of the standards for any particular purpose;
The merchantability of the standards;
The accuracy, completeness, relevance or validity of the standards; or
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.