THIS VERSION IS NOT THE LATEST RELEVANT DDEX STANDARD. DDEX RECOMMENDS TO USE THE LATEST VERSION

Skip to end of metadata
Go to start of metadata
 

1 Introduction

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).

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 http://ddex.net/implementing-ddex-standards.


Essential Reading

Download/Print standard (PDF)

 

 

2 Scope

 2.1 Introduction
The message defined in this standard provides a mechanism for Licensees (typically Digital Service Providers, including Mobile Service Providers and Internet Service Providers, ISPs) to report to Rights Controllers (typically Music Rights Societies, Music Licensing Companies, Music Publishers and/or Record Companies) Usage, Revenue or Sales from the exploitation of Products based on electronic Releases containing Sound Recordings and/or Music Audio-Visual Recordings which embody Musical Works and/or other Resources.

The Flat File Variant is intended to provide a format for reporting information about the level of usage, revenue or sales generated from the exploitation of Releases and Resources for companies that do not wish to handle XML-formatted sales/usage reports.

Version 3.0 of the Flat File Variant if the Digital Sales Reporting Message Suite Standard is provided in several standards. One standards defines the underlying architecture which is then employed by a series of profile standards. This standard defines one of these profiles.

 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 UGC profile and the Record Types that are used by this profile.

Finally Annexes A provides some examples.

 2.3 Release Notes (Informative)
Version 3 of the Flat File Variant of the Digital Sales Reporting Message Suite Standard utilities a fundamentally different architecture than Version 2. This new architecture allows more Profiles to be supported than was possible in Version 2.

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.

 

4 Terms and Abbreviations

 Click here to expand...

5 UGC Profile

 5 UGC Profile
This Profile is for reporting all Usage, Revenue or Sales for user-generated content where the Message Sender has received a claim for a sound recording from the owner of that sound recording (the “master” Recording). The Message Sender may or may not include information specific to the Licensors or RightsControler  of the Musical Works. 

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 UGC Profile and the ProfileVersion Cell shall contain the value 1.0.

The following Records shall be communicated for each Block in this order:

  1. One Resource Record of type AS02 describing the Resource including basic information of the underlying Work.
    The Message Sender may wish to split the information into multiple Records.
    1. The first Record, of type AS01, contains information regarding the Sound Recordings, Videos and other “master” Resources that have been used in creating the user-generated content that has been accessed
    2. The following one or more Musical Work Record(s), of type MW01 contain information about the Musical Work(s) utilised.

  2. None, one or more UGC Release Usage Records of type RU01 describing the use of UGC Releases.
    Instead of the RU01 record, the Message Sender may use one RU02 Record for each UGC Release and its use. Up to one hundred (100) individual RU02 UGC Releases, and their usage can be reported in a single Record.
    For the avoidance of doubt, it is not permissible to communicate RU01 and RU02 Records in one Block.

  3. None, one or more Intra-Block Groupings of Records providing
    1. One UGC Sales/Usage Record of type SU03 Record followed by
    2. None, one or more Licensor-specific Usage Data Record of type LI01 providing Licensor-specific information for the usages reported in the preceding SU03.

The Blocks shall be preceded by one or more Summary Records SY02 or SY03 for each type of use, commercial model and territory any Release contained in the Sales Report Message has been traded under. In cases where a Message Sender provides information at RightsControler level, the fields at Rightscontroller level in SY02 or SY03 and LI01 records can be provided.

It is permissible to communicate different types of Summary Records in a single sales/usage report.

It is recommended to provide the Summary Records in a logical order to aid human readability. This would typically mean that Summary Records of different types are not mixed. For example a sequence of  SY03 SY03 SY02 SY02 SY02 meets this recommendation, whereas SY03 SY02 SY03 does not.

 

Figure 7 shows two ways in which this Profile can be implemented. The left-hand diagram shows the case where Musical Work information is provided as part of the Resource Record (AS02) and only a usage summary Record is RU01 is provided and the right-hand diagram shows the case where Musical Work information is provided on an extra MW01 Record and usage information is provided in multiple RU02 Records. For the avoidance of doubt, it is also possible to use AS02 Records together with RU02 Records as well as AS01/MW01 with RU01.

Figure 5 – One Block of Records when Reporting UGC-related Usages, Revenues or Sales 


 The table below provides an overview of the order and cardinality of the Records to be used in this Profile.

Record TypeCardinality
Comment
HEAD1 
SY02 or SY031-nAlso a combination of the three Summary record types is allowed:
first all SY02 Records (if there are any), then all SY03 Records (if there are any)
Block0-n 
   AS01 or AS021-n 
        MW010-nMay only follow an AS01 record
   RU01 or RU020-n 
   Intra-Block Grouping0-n 
    SU03
1 
       LI01
0-n 
FOOT1 

 

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.


6 Record Types

 6.1 Introduction
This Clause defines all Record Types that can be communicated within a Sales Report Message formatted in accordance with this standard. Each Flat File Sales Report Message will contain a series of Records, depending on the Profile used.

 

Table 4 – Header and Footer Record Types

Record Type

Description

HEAD

Global Header Record for all Sales Report Message formatted in accordance with this standard. This Record Type is defined in the Digital Sales Reporting Message Suite Standard (Version 3.0) - Architecture of the Flat File Variant.

FOOT

Global Footer Record for all Sales Report Message formatted in accordance with this standard. This Record Type is defined in the Digital Sales Reporting Message Suite Standard (Version 3.0) - Architecture of the Flat File Variant.


Table 5 – Summary Record Types

Record Type

Description

SY02

Summary Record for Ad-Supported and Interactive Streaming Services

SY03

Summary for Subscription Services

 

Table 6 – Resource Record Types

Record Type

Description

AS01

Basic Sound Recording Record to describe sound recordings and music videos that have been used or sold individually or as part of a Release (without Musical Work Information)

AS02

Basic Sound Recording Record to describe sound recordings and music videos that have been used or sold individually or as part of a Release (with Musical Work Information)


Table 7 – Work and Cue Record Types

Record Type

Description

MW01

Basic Record to describe a Musical Work that has been utilised

 

Table 8 – Record Types to describe Usages, Revenues or Sales

Record Type

Description

SU03

Usage, Revenue or Sales Record for UGC

RU01

UGC Release Usage Summary Record to provide a summary of the uses of up to 100 uses UGC Releases.

RU02

UGC Release Usage Record to provide details of the Uses of a single UGC Release

LI01

Record to Communicate UGC-related Revenues and amounts to Works RightsControllers

 6.2 Summary Records
 6.2.1 SY02 – Summary Record for Ad-Supported and Interactive Streaming Services

6.2.1.1 Purpose of Record

This Record can be used to communicate summary information about Usages, Sales and Revenues with support for ad supported and interactive streaming services.

6.2.1.2 Definition of Cells

Cell NameField DefinitionData TypeM/O/C?Example

RecordType

The Type of the Record; always to contain “SY02”

Fixed String

M

SY02

SummaryRecordIdThe Identifier (specific to the Message) of the Summary Record. This Identifier shall be used by Usage/Revenue/Sales Records to indicate to which Summary Record they provide details.StringM34
DistributionChannelThe Licensee on whose behalf the Sales/Usage has been generated.StringCMyCo
DistributionChannelDPID

The DDEX Party ID of the DistributionChannel.

DPIDCDPIDA12345SDF

CommercialModel

The Type of CommercialModel of the SalesTransaction. The CommercialModel  indicates how a Consumer pays for a Service or Release.

AVS

M

AdvertisementSupportedMode

UseType

The nature of a Service, or a Release, as used by a Consumer.

AVS

M

Stream

Territory

The Territory for which the sale/transaction is reported.

AVS

M

FR

ServiceDescription

The service name (e.g. a service tier) under which the SalesTransaction took place.  The ServiceDescription may not contain space characters or underscores.

String

M

Premium Service

Usages

The number of Usages of the Release or Resource from the MessageSender to Consumers, including any sales adjustments. Sales adjustments include e.g. file failures.

For the avoidance of doubt: this Cell shall contain all relevant Usages of Releases plus all relevant Usages of Resources.

Integer

M

1234

Users

The number of Users with whom the Release or Resource were transacted.

IntegerO1234

Currency

The Currency in which the NetRevenue, AmountPayable and AllocatedNetRevenue are provided (represented by an ISO 4217 CurrencyCode.

AVS

M

CAD

NetRevenue

Net Revenue of the MessageSender for the Territory, CommercialModel  and UseType. This element is, in most cases, the basis for royalty calculations.

Float

M

10545.12

RightsController 

Name of the RightsController that is believed by the MessageSender to control a RightShare of the Work

String

O

SACEM

RightsControllerPartyId

PartyId of the RightsController that is believed by the MessageSender to control a RightShare of the Work

PartyIdOISNI::0000000081266409

Allocated Usages

The number of Usages allocated to the RightsController.

Multiple float

O

411.29

AmountPayable

The amount due to the RightsController for the Uses reported

Multiple float

O

20.45

AllocatedNetRevenue

Net Revenue of the generated that are to be ascribed to the RightsController

Float

O

781.73

 6.2.2 SY03 – Summary Record for Subscription Services

6.2.2.1 Purpose of Record

This Record can be used to communicate summary information about Usages, Sales and Revenues with support for subscription services.

6.2.2.2 Definition of Cells

Cell NameField DefinitionData TypeM/O/C?Example

RecordType

The Type of the Record; always to contain “SY03”

Fixed string

M

SY03

SummaryRecordId The Identifier (specific to the Message) of the Summary Record. This Identifier shall be used by Usage/Revenue/Sales Records to indicate to which Summary Record they provide details. StringM34
DistributionChannelThe Licensee on whose behalf the Sales/Usage has been generated.StringCMyCo
DistributionChannelDPIDThe DDEX Party ID of the DistributionChannelDPIDCDPIDA12345SDF

CommercialModel

The Type of CommercialModel of the SalesTransaction. The CommercialModel indicates how a Consumer pays for a Service or Release.

AVS

M

SubscriptionModel

UseType

The nature of a Service, or a Release, as used by a Consumer.

AVS

M

Stream

Territory

The Territory for which the sale/transaction is reported.

AVS

M

FR

ServiceDescription

The service name (e.g. a service tier) under which the SalesTransaction took place. The ServiceDescription may not contain space characters or underscores.

String

M

Premium Service

Usages

The number of Usages of the Release or Resource from the MessageSender to Consumers, including any sales adjustments. Sales adjustments include e.g. file failures.

For the avoidance of doubt: this Cell shall contain all relevant Usages of Releases plus all relevant Usages of Resources.

Integer

M

1234

Subscribers

The number of paying Subscribers

Float

M

1239867

Currency

The Currency in which the NetRevenue, ConsumerPaidUnitPrice, AmountPayable and AllocatedNetRevenue are provided (represented by an ISO 4217 CurrencyCode.

AVS

M

CAD

NetRevenue

Net Revenue of the MessageSender for the Territory, CommercialModel   and UseType. This element is, in most cases, the basis for royalty calculations.

Float

M

10545.12

RightsController

Name of the RightsController that is believed by the MessageSender to control a RightShare of the Work

String

O

SACEM

RightsControllerPartyId

PartyId of the RightsController that is believed by the MessageSender to control a RightShare of the Work

PartyIdOISNI::0000000081266409

AllocatedUsages

The number of Usages allocated to the RightsController.

Multiple float

O

411.29

AmountPayable

The amount due to the RightsController for the Usages, Revenues or Sales reported

Multiple floats

O

20.45

AllocatedNetRevenue

Net Revenue of that which is generated that is to be ascribed to the RightsController

Float

O

781.73

RightsController MarketShare

The ratio in percent between NumberOfUser s and AllocatedUsages.

Float

O

18.25

ConsumerPaidUnitPrice

The average price paid by the Subscribers

Float

M

6.62

FreeOrTrialSubscribersThe number of non-paying Subscribers (including Subscribers in a non-paying trial period).

Float

M

1239867

ExchangeRateBaseCurrencyThe currency in which the revenue has to be reported.AVSOUSD

ExchangeRate

The Exchange rate used to calculate the AmountPayable in the specified Currency

Float

O

1.205648

 6.3 Release Records
There are no Release Records in this Profile.

 6.4 Resource Records
 6.4.1 AS01 – Basic Sound Recording Record

6.4.1.1 Purpose of Record

This is the Record to describe sound recordings and music videos that have been used or sold individually or as part of a Release (without Musical Work Information). This specifically also includes music videos.

6.4.1.2 Definition of Cells

Cell NameField DefinitionData TypeM/O/C?Example

RecordType

The Type of the Record; always to contain “AS01”

Fixed string

M

AS01

BlockId

The Identifier (specific to the Message) of the Block that this Record belongs to. All Records in a single Block shall have the same BlockId

String

M

7

ResourceReference

The Identifier (specific to the Block) of the Record, that allows other Records to reference this Record

String

M

15

DspResourceId

The ProprietaryIdentifier of the Resource assigned by the MessageSender

String

M

12345678

ISRC

The ISRC (International Standard Recording Code as defined in ISO 3901) for the SoundRecording. An ISRC comprises four parts: two characters, followed by three alphanumeric characters, then two digits and five digits.

String

C

USS1Z1412345

Title

The ReferenceTitle of the SoundRecording.

String

M

Bohemian Rhapsody

SubTitleA Descriptor which is supplementary to, but not contained within, a Title.StringOLive Version
DisplayArtistName

The Name to be used by a DSP when presenting Artist details of the Resource to a Consumer.

StringMQueen
DisplayArtistPartyIdThe PartyId of the DisplayArtistPartyIDOISNI::0000000081266409
DurationThe Duration of the SoundRecording (using the ISO 8601:2004 PT[[hhH]mmM]ssS format, where lower case characters indicate variables, upper case characters are part of the string, e.g. one hour, two minutes and three seconds would be PT1H2M3S). The seconds section ss may include fractions (e.g. one minute and 30.5 seconds would be PT1M30.5S).ISO durationMPT1H2M3S
ResourceType

The Type of the Resource

AVSMSoundRecording

6.4.1.3 Conditions

The ISRC must be provided if they are available to the Message Sender.

 6.4.2 AS02 – Basic Sound Recording Record with Musical Work Details

6.4.2.1 Purpose of Record

This is the Record to describe sound recordings and music videos that have been used or sold individually or as part of a Release (with Musical Work Information). This specifically also includes music videos.

6.4.2.2 Definition of Cells

The AS02 Record has the same structure as defined above, with two differences. Firstly, the RecordType shall contain the string AS02, instead of AS01, and, secondly, the following Cells will appear in addition, and to the right of, the Cells defined above.

Cell NameField DefinitionData TypeM/O/C?Example

ISWC

The ISWC (International Standard Musical Work Code defined in ISO 15707) identifying the MusicalWork. An ISWC comprises three parts: the letter 'T', followed by nine digits and then one check digit.

String

C

T0030749586

ComposerAuthor

The Name of a Writer of the Musical Work used in creating the Resource

Multiple String

C

Johann Sebastian Bach

ComposerAuthorPartyIdThe PartyId(s) of the ComposerAuthor(s)Multiple PartyIDOISNI::0000000081266409

Arranger

The Name of an Arranger of the Musical Work used in creating the Resource

Multiple String

C

August Wilhelmj

ArrangerPartyIdThe PartyId(s) of the Arranger(s)Multiple PartyIDOISNI::0000000081266409
MusicPublisher

The Name of the MusicPublisher(s) of the Musical Work for the relevant Territory.

Multiple StringCUMP
MusicPublisherPatryIdThe PartyID(s) of the MusicPublisher(s).Multiple PartyIDOISNI::00000000111111111

WorkContributor

The Name of a contributor of the Work. This Cell shall only be used if the Message Sender does not know whether the contributor is a ComposerAuthor or an Arranger, or if the contributor played a role other than a  ComposerAuthor or Arranger.

Multiple String

C

UMP

WorkContributorPartyIdThe PartyId(s) of the WorkControibutor(s)Multiple PartyIDOISNI::0000000081266409

6.4.2.3 Definition of Conditions

The following Cells must be provided if they are available to the Message Sender: ISWC, ComposerAuthor, Arranger, MusicPublisher and WorkContributor.

 

 6.5 Work and Cue Records
 6.5.1 MW01 – Basic Musical Work Record

6.5.1.1 Purpose of Record

This is the basic Record to describe a Musical Work that has been utilised.

6.5.1.2 Definition of Cells

Cell NameField DefinitionData TypeM/O/C?Example

RecordType

The Type of the Record; always to contain “MW01”

Fixed string

M

MW01

BlockId

The Identifier (specific to the Message) of the Block that this Record belongs to. All Records in a single Block shall have the same BlockId

String

M

7

DspWorkId

The ProprietaryIdentifier of the Musical Work assigned by the MessageSender

String

M

12345678

ISWC

The ISWC (International Standard Musical Work Code defined in ISO 15707) identifying the MusicalWork. An ISWC comprises three parts: the letter 'T', followed by nine digits and then one check digit.

String

C

T0030749586

Title

The ReferenceTitle of the Musical Work

String

M

Bohemian Rhapsody

SubTitle

A Descriptor which is supplementary to, but not contained within, a Title.

String

O

Live version

ComposerAuthor

The Name of a Writer of the Musical Work used in creating the Resource

Multiple String

C

Johann Sebastian Bach

ComposerAuthorPartyIdThe PartyId(s) of the ComposerAuthor(s)Multiple PartyID(s)OISNI::0000000081266409

Arranger

The Name of an Arranger of the Musical Work used in creating the Resource

Multiple String

C

August Wilhelmj

ArrangerPartyIdThe PartyId(s) of the Arranger(s)Multiple PartyID(s)OISNI::0000000081266409
MusicPublisher

The Name of the MusicPublisher(s) of the Musical Work for the relevant Territory.

Multiple StringCUMP
MusicPublisherPatryIdThe PartyID(s) of the MusicPublisher(s).Multiple PartyIDOISNI::00000000111111111

WorkContributor

The Name of a  contributor of the Work. This Cell shall only be used if the Message Sender does not know whether the contributor is a ComposerAuthor or an Arranger, or if the contributor played a role other than a  ComposerAuthor or Arranger.

Multiple String

C

UMP

WorkContributorPartyIdThe PartyId(s) of the WorkContributor(s)Multiple PartyID(s)OISNI::0000000081266409

DataProvider

The Name of the company that provided the MusicalWork information to the MessageSender

String

O

UMG

6.5.1.3 Definition of Conditions

The following Cells must be provided if they are available to the MessageSender: ISWC, ComposerAuthor, Arranger, MusicPublisher and WorkContributor.

 6.6 Records to describe Usages, Sales or Revenues
 6.6.1 RU01 - UGC Release Usage Summary Record

6.6.1.1 Purpose of Record

The UGC Release Usage Summary Record can be used to provide a summary of the Uses of up to 100 uses of UGC Releases.

Records that describe Usages, Revenues or Sales do so with respect to a sales context (see Clause 6.5 in Part 1). The context is, however, not directly provided in the Record. Instead, the context is available in the Summary Record SYxx that the Sales/Usage Record points to through its SummaryRecordId Cell.

6.6.1.2 Definition of Cells

Cell NameField DefinitionData TypeM/O/C?Example

RecordType

The Type of the Record; always to contain “RU01”

Fixed string

M

RU01

BlockId

The Identifier (specific to the Message) of the Block that this Record belongs to. All Records in a single Block shall have the same BlockId

String

M

7

SummaryRecordIdThe Identifier (specific to the Message) of the Summary Record that this Usage, Revenue or Sales Record provides details for.
StringM34

DspReleaseId

The ProprietaryIdentifier of the UGC Release assigned by the MessageSender

Multiple Strings

M

12345|12346

 Usages

The number of times the UGC Release has been used in the sales period covered by the Sales Report Message.

Multiple Integer

M

400|655

 6.6.2 RU02 – UGC Release Usage Record

6.6.2.1 Purpose of Records

The UGC Release Usage Record can be used to provide details of the Uses of a single UGC Release with title and URL of the Resource.

Records that describe Usages, Revenues or Sales do so with respect to a sales context (see Clause 6.5 in Part 1). The context is, however, not directly provided in the Record. Instead, the context is available in the Summary Record SYxx that the Sales/Usage Record points to through its SummaryRecordId Cell.

6.6.2.2 Definition of Cells

Cell NameField DefinitionData TypeM/O/C?Example

RecordType

The Type of the Record; always to contain “RU02”

Fixed string

M

RU02

BlockId

The Identifier (specific to the Message) of the Block that this Record belongs to. All Records in a single Block shall have the same BlockId

String

M

7

SummaryRecordIdThe Identifier (specific to the Message) of the Summary Record that this Usage, Revenue or Sales Record provides details for.
StringM34

DspReleaseId

The ProprietaryIdentifier of the UGC Release assigned by the MessageSender

String

M

12345

ReleaseTitle

The Title of the UGC Release, as given by the user who uploaded the UGC Release

String

M

I am singing in the shower

ReleaseURL

The URL from which the MessageSender made the UGC Release available to Consumers

String

M

http://test.te/view/1234

 Usages

The number of times the “Head” Resource or Work has been used in the sales period covered by the Sales Report Message

Integer

M

400

 6.6.3 SU03 – UGC Sales and Usage Record

6.6.3.1 Purpose of Records

This is the Record to communicate Usages, Revenues or Sales of UGC Resources.

Records that describe Usages, Revenues or Sales do so with respect to a sales context (see Clause 6.5 in Part 1). The context is, however, not directly provided in the Record. Instead, the context is available in the Summary Record SYxx that the Sales/Usage Record points to through its SummaryRecordId Cell.

6.6.3.2 Definition of Cells

Cell NameField DefinitionData TypeM/O/C?Example

RecordType

The Type of the Record; always to contain “SU03”

Fixed string

M

SU03

BlockId

The Identifier (specific to the Message) of the Block that this Record belongs to. All Records in a single Block shall have the same BlockId

String

M

7

SalesTransactionId

ProprietaryIdentifier of the Sales Transaction, allocated by the MessageSender, which allows an invoice to be tied back to an individual SalesTransaction composite/record. Globally and perpetually unique together with the Message ID. The SalesTransactionId may change when the report is re-generated.

String

M

34456

SummaryRecordIdThe Identifier (specific to the Message) of the Summary Record that this Usage, Revenue or Sales Record provides details for.
StringM34

DspReleaseId

The ProprietaryIdentifier of the UGC Release assigned by the MessageSender

String

M

12345

Usages

The number of times the “Head” Resource or Work has been used in the sales period covered by the Sales Report Message

Integer

C

400

NetRevenue

Net Revenue of the MessageSender for the Territory, CommerciualModelType and UseType. This element is, in most cases, the basis for royalty calculations.

Float

M

10545.12

ValidityPeriodStart

The first date at which, to the knowledge of the MessageSender, the information provided in the RighsController and RightShare% Cells is accurate.

Note: the ValidityPeriodStart may be earlier (or later) than the first day covered by the sales/usage report.

ISO date

O

2015-06-01

ValidityPeriodEnd

The last date at which, to the knowledge of the MessageSender, the information provided in the RighsController and RightShare% Cells is accurate.

Note: the ValidityPeriodEnd may be later (or earlier) than the latest day covered by the sales/usage report.

ISO date

O

2015-06-15

 6.6.4 LI01 – Licensor-specific Usage Data Record

 6.6.4.1 Purpose of Record

This Record can be used to communicate UGC Sales/Usage Record to a RightsController to allow provision of revenue and amounts due to individual RightsControllers.

Records that describe Usages, Revenues or Sales do so with respect to a sales context (see Clause 6.5 in Part 1). The context is, however, not directly provided in the Record. Instead, the context is available in the Summary Record SYxx that the Sales/Usage Record points to through its SummaryRecordId Cell.

6.6.4.2 Definition of Cells

Cell NameField DefinitionData TypeM/O/C?Example

RecordType

The Type of the Record; always to contain “LI01”

Fixed string

M

LI01

BlockId

The Identifier (specific to the Message) of the Block that this Record belongs to. All Records in a single Block shall have the same BlockId

String

M

7

SummaryRecordIdThe Identifier (specific to the Message) of the Summary Record that this Usage, Revenue or Sales Record provides details for.
StringM34

RighsController

Name of the RightsController that is believed by the MessageSender to control a RightShare of the Work

String

M

SACEM

RighsControllerPartyIdThe PartyId of the RightsControllerPartyIDOISNI::0000000081266409

RightsControllerWorkId

The ProprietaryId given to the MusicalWork used by the RightsContoller

String

O

12gc

RightShare%

Percentage of the Musical Works used in the Head Resource (or the Head Work itself) that is believed by the MessageSender to be controlled by the RightsController. A quarter share is represented by “25” (and not 0.25).

Float

M

25

RightsTypeThe right for which the RightShare% is providedAVSOMechanicalRight

AllocatedNetRevenue

Net Revenue of generated by the DSP that is to be ascribed to the Head Resource of Work allocated to the RightShare% to the RightsController

Float

M

34567

AllocatedAmount

The amount due to the RighsController for the Uses, Revenue or Sales as reported in this Block

Float

M

2560.77

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.