You are viewing an old version of this page. View the current version.
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).
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.
Finally Annexes A provides some examples.
3 Normative References
4 Terms and Abbreviations
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 Broadcast Reporting Profile
To indicate that a Sales/Usage Report is created in accordance with this Variant, the
Profile Cell in the
HEAD Record shall contain the value
BroadcastReportingProfile and the
ProfileVersion Cell shall contain the value
The following Records shall be communicated for each Block in this order:
- None or one Release Record
- One Sound Recording Record
AS01followed by one or more Musical Work Records
MW01.01or one Sound Recording Record
AS02.01. The Sound Recording Record is the Record against which any sales/usage figure is provided.
- For each
AS02.01Record: One or more Sales/Usage Records
The Blocks shall be preceded by one or more Summary Record
SY08 for each Broadcast Channel and 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.
Figure 1 – Two Blocks of Records when Reporting Broadcasts
The table below provides an overview of the order and cardinality of the Records to be used in this Profile.
|Record Type||Cardinality ||Comment|
|1|| If no (or partial) musical work information is available, an |
May only follow an
|1-n||There shall be one |
Annex A (informative) Examples
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.