DDEX Standard

Skip to end of metadata
Go to start of metadata

This section of the DDEX Knowledge Base contains the Single Record Block Variants for the Parts 3-5 of the Digital Sales Reporting Message Suite Standard.

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 and/or Music Publishers) 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 reporting usages, revenues or sales in a simplified variant of the Flat File Sales Reporting format.

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
 

 

 

 

2 Scope

 2.1 Introduction
The messages defined in this Standard define Single Record Block Variants (the term Single Record Block Variants is defined in Part 1 (Architecture of the Flat File Variant) of the Digital Sales Reporting Message Suite Standard) for the Basic Audio Profile, the UGC Profile and the Audio-visual Profile.
 2.2 Organisation of the Standard
This standard comprises eight clauses. Clauses 1-4 provide the scope, abbreviations and core definitions used in this standard. Clauses 5-7 then define the Single Record Block Variants for the three profiles defined herein.

It is expected that the Single Record Block Variants defined herein will be added to the relevant Multi Record Block Variant Profile Standards (unchanged) when those are being updated. Once that is complete, the Single Record Block Variant standard in this form will be retired.

3 Normative References

 3 Normative References
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

 4 Terms and Abbreviations

5 SRBV for the Basic Audio Profile

 5.1 Introduction

Part 3 of the Digital Sales Report Message Suite Standard defines the default (Multi-Record Block) Variant of the Basic Audio Profile. In some instances it may be more efficient to communicate reporting audio-only Usage, Revenue or Sales in a Single-Record Block Variant. This Variant is defined herein. 

To indicate that a Sales/Usage Report is created in accordance with the Single-Record Block Variant of the Basic Audio Profile, the Profile Cell in the HEAD Record shall contain the value BasicAudioProfileSRB and the ProfileVersion Cell shall contain the value 1.2. 

When Usages, Revenues or Sales are to be reported for Resources using the Single-Record Block Variant of the Basic Audio Profile all usage, sale and/or revenue information shall be communicated, together with Release and Resource information, in a series of 0-n Single Block Records SR01 (for downloading models) or SR02 (for streaming models). It is not permitted to send SR01 and SR02 Records together in a single sales/usage report using this profile.

The SRxx Records shall be preceded exactly by one or more Summary Records of type SY01.01, SY02.02, SY04.01, SY05.02 or SY06.02 (depending on the commercial model) for commercial model and territory the Releases and/or Resource contained in the Sales Report Message using this profile has been traded under. 

The figures below show how to report Usages, Revenues or Sales for Audio Resources with the Single-Record Block Variant of the Basic Audio Profile.

 5.2 SRBV for Download Use Cases

Figure 1 –  Reporting Usages, Revenues or Sales for Audio Resources with the Single-Record Block Variant of the Basic Audio Profile for Download Use Cases


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

Record TypeCard.Comment
HEAD1 

SY01.01 or
SY02.02 or
SY04.01 or
SY05.02 or
SY06.02

1-n

A combination of the summary record types is allowed:

  • first, all SY01.01 Records (if there are any),
  • then, all SY02.02 Records (if there are any),
  • then, all SY04.01 Records (if there are any),
  • then, all SY05.02 Records (if there are any),
  • then, all SY06.02 Records (if there are any).
SR010-n

The SR01 Record Type has been derived from the Record Types used in the Multi-Record Block Variant of the Basic Audio Profile.

SRFO1This footer record differs from the one used in the other Variants.
 5.3 SRBV for Streaming Use Cases

Figure 2 –  Reporting Usages, Revenues or Sales for Audio Resources with the Single-Record Block Variant of the Basic Audio Profile for Streaming Use Cases

 

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

Record TypeCard.Comment
HEAD1 

SY01.01 or
SY02.02 or
SY04.01 or
SY05.02 or
SY06.02

1-n

A combination of the summary record types is allowed:

  • first, all SY01.01 Records (if there are any),
  • then, all SY02.02 Records (if there are any),
  • then, all SY04.01 Records (if there are any),
  • then, all SY05.02 Records (if there are any),
  • then, all SY06.02 Records (if there are any).
SR020-n

The SR02 Record Type has been derived from the Record Types used in the Multi-Record Block Variant of the Basic Audio Profile.

SRFO1This footer record differs from the one used in the other Variants.

6 SRBV for the for the UGC Profile

 6.1 Introduction
Part 4 of the Digital Sales Report Message Suite Standard defines the default (Multi-Record Block) Variant of the UGC Profile. In some instances it may be more efficient to communicate reporting UGC Usages, Revenues or Sales in a Single-Record Block Variant. This Variant is defined herein.

When Usages, Revenues or Sales are to be reported for Resources using the Single-Record Block Variant of the UGC all usage, sale and/or revenue information shall be communicated, together with Release and Resource information, in a series of 0-n Single Block Records comprising SR03 data records.

To indicate that a Sales/Usage Report is created in accordance with  the Single-Record Block Variant of the UGC Profile, the Profile Cell in the HEAD Record shall contain the value UGCProfileSRB and the ProfileVersion Cell shall contain the value 1.2.

The SRxx Records shall be preceded by one or more Summary Records SY02.02, SY04.01 or SY09 for each type of use, commercial model and territory any Release contained in the Sales Report Message using this profile has been traded under.

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

When using SY04.01, all SY04.01 Records for the same RightsType and sales context (as defined in Clause 6.5 of Part 1 of the Digital Sales Report Message Suite Standard) may carry the same SummaryRecordId if per-subscriber minima information needs communicating per context, but across different subscriber types. Each SY04.01 record shall be followed by 1-n SY05.02 Records:

  • 0-n SY04.01
    • 1-n SY05.02
 6.2 Default SRBV for UGC


Figure 3 –  Reporting Usages, Revenues or Sales with the Single-Record Block Variant of the UGC Profile (note: multiple summary records are permitted)

 

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

Record TypeCard.Comment
HEAD1 

SY02.02 or
SY04.01/SY05.02

1-n

Also a combination of the four Summary record types is allowed:

  • First, all SY02.02 Records (if there are any),
  • Then, all SY04.01/SY05.02 Records as follows: each SY04.01 shall be followed by 1-n SY05.02 Records.

SR03

0-n

The SR03 Record Type has been derived from the Record Types used in the Multi-Record Block Variant of the UGC Profile

SRFO1This footer record differs from the one used in the other Variants.
 6.3 SRBV for Ad-supported and Subscription Models

Figure 4 –  Reporting Usages, Revenues or Sales with the Single-Record Block Variant of the UGC Profile for Ad-supported or Subscription Models (note: multiple summary records are permitted) 

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

Record TypeCard.Comment
HEAD1 
SY01.01 or
SY02.02 or
SY04.01/SY05.02 
1-n

Also a combination of the three Summary record types is allowed:

  • first, all SY01.01 Records (if there are any),
  • then, all SY02.02 Records (if there are any),
  • then, all SY04.01/SY05.02 Records (if there are any)
SR060-n

The SR06 Record Type has been derived from the Record Types used in the Multi-Record Block Variant of the Basic Audio Profile.

SRFO1This footer record differs from the one used in the other Variants.

7 SRBV for the Audio-visual Profile

 7.1 Introduction
Part 5 of the Digital Sales Report Message Suite Standard defines the default (Multi-Record Block) Variant of the Audio-visual Profile. In some instances it may be more efficient to communicate reporting sales and usages of audio-visual Recordings in a Single-Record Block Variant. This Variant is defined herein.

To indicate that a Sales/Usage Report is created in accordance with the Single-Record Block Variant of the Audio-visual Profile, the Profile Cell in the HEAD Record shall contain the value AudioVisualProfileSRB and the ProfileVersion Cell shall contain the value 1.1.

When Usages, Revenues or Sales are to be reported for Resources using the Single-Record Block Variant of the Audio-visual Profile all usage, sale and/or revenue information shall be communicated, together with Release and Resource information, in a series of 0-n Single Block Records SR01  (for downloading models), SR02 (for streaming models) or SR03 for (models specific to audiovisual content) data records. It is not permitted to send two  different SRxx  Records in a single sales/usage report using this profile.

The SRxx Records shall be preceded exactly by one or more Summary Record of type  SY01.01 SY02.02SY04.01 SY05.02 or SY06.02 (depending on the commercial model) for the type of use, commercial model and territory the Releases and/or Resource contained in the Sales Report Message using this profile has been traded under. The figures below show how to report Usages, Revenues or Sales for Audio Resources with the Single-Record Block Variant of the Audio-visual Profile.

 7.2 SRBV for Downoad Use Cases

Figure 4 –  Reporting Usages, Revenues or Sales for Audiovisual Resources with the Multiple Record Block Variant of the Audiovisual Profile for Download Use Cases

 

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

Record TypeCard.Comment
HEAD1 
SY01.01 or 
SY02.02 or 
SY04.01 or 
SY05.02 or
SY06.02
1-n

A combination of the Summary record types is allowed:

  • first, all SY01.01 Records (if there are any),
  • then, all SY02.02 Records (if there are any),
  • then, all SY04.01 (if there are any),
  • then SY05.02 Records (if there are any).
  • then, all SY06.02 Records (if there are any).

SR04

0-n 
SRFO1This footer record differs from the one used in the other Variants.
 7.3 SRBV for Streaming Use Cases

Figure 5 –  Reporting Usages, Revenues or Sales for Audiovisual Resources with the Single-Record Block Variant of the Audiovisual Profile for Streaming Use Cases

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

Record TypeCard.Comment
HEAD1 
SY01.01 or 
SY02.02 or 
SY04.01 or 
SY05.02 or
SY06.02
1-n

A combination of the Summary record types is allowed:

  • first, all SY01.01 Records (if there are any),
  • then, all SY02.02 Records (if there are any),
  • then, all SY04.01 (if there are any),
  • then SY05.02 Records (if there are any).
  • then, all SY06.02 Records (if there are any).

SR05

0-n

 

SRFO1This footer record differs from the one used in the other Variants.

8 Record Type Definitions for SRBVs

8.1 Header and Record Types

 8.1.1 HEAD — Header Record
This is the Header Record for all Single Record Block Sales Report Messages created in accordance with this standard. Each file of a Sales Report Message shall have exactly one such Header Record. It shall be the first Record in each file.
Cell Name Field DefinitionData TypeM/O/C?[1]Example
1

RecordType

The Type of the Record; always to contain “HEAD”.

Fixed string

M

HEAD

2

MessageVersion

The Version of the Message. This shall be in the form dsrf/xxx/yyy/zzz with

  • xxx being the version number of Part 1 (Architecture)
  • yyy being the version number of Part 2 (Allowed Value Sets) and
  • zzz being the version number of Part 8 (Record Type Definitions) that is needed to ingest the Message. This document represents version 1.1.
    (As indicated in Clause 2.2 of this standard, all Record Type definitions contained in Clause 8 of this standard will be moved into Part 8 (Record Type Definitions) of the Digital Sales Reporting Message Suite Standard in the foreseeable future. Therefore zzz represents the current and latest version of Part 8 of the Digital Sales Reporting Message Suite Standard.)

dsrf/1.1.2/1.6/1.0 would therefore signal that the Message was created in accordance with the Architecture in version 1.1.2, the allowed value set of version 1.6 and the Record Type Record Type Definitions of version 1.0.

If the MessageVersion is provided as dsrf/30, Parts 1 and 2 are deemed to be in the initial version as published in 2016. This capability has been retained for backwards compatibility.

Fixed string

M

dsrf/1.1.2/1.6/1.0

3Profile

The Identifier of the Profile used for the Message.

StringMBasicAudioProfileSRB
4

ProfileVersion

The Identifier of the Version of the Profile used for the Message. The value for this field is defined in the relevant Profile standard.

String

M

1.0

5

MessageId

A string used to uniquely identify the Message. The MessageId shall be, in combination with the MessageSenderId, globally unique. Thus, a MessageSender shall never re-use a MessageId.

String

M

1234567890

6

MessageCreatedDateTime

The DateTime on which the Message was created (the only allowed format is ISO 8601:2004: YYYY-MM-DDThh:mm:ssTZD).

ISO datetime

M

2014-12-14T10:05:00Z

7

FileNumber

Sequence number of the file within the Sales Report Message. This shall always be set to "1".

This Cell is included to make the HEAD record compatible between Single Record Block Variants (where it is permitted to split sales/usage reports into multiple files) and Multiple Record Block Variants (where it is not permitted to split sales/usage reports into multiple files).

Fixed string

M

1

8

NumberOfFiles

The number of files that the Sales Report Message is provided in. This shall always be set to "1".

This Cell is included to make the HEAD record compatible between Single Record Block Variants (where it is permitted to split sales/usage reports into multiple files) and Multiple Record Block Variants (where it is not permitted to split sales/usage reports into multiple files).

Fixed string

M

1

9

UsageStartDate

The StartDate of the reporting Period covered by the Message (in ISO 8601:2004 format). This is a string with the syntax YYYY[-MM[-DD]].

ISO date

M

2014-12-01

10

UsageEndDate

The EndDate of the reporting Period covered by the Message (in ISO 8601:2004 format). This is a string with the syntax YYYY[-MM[-DD]].

ISO date

M

2014-12-01

11

SenderPartyId

The DDEX PartyId (DPID) of the MessageSender

DDEX Party ID

M

PADPIDA2008120501W

12

SenderName

The Full Name of the MessageSender

String

M

Apple

13

ServiceDescription

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

The ServiceDescription shall only be used if it aids the MessageRecipient in determining the sales context(s) of the Message.

The ServiceDesctiption is intended to be a human-readable expression of the totality of the services reported in the Message. For sales/usage reports covering one sales context (see Clause 6.5 in Part 1 of the Digital Sales Report Message Suite Standard) this should be the same string that is used in the file name (see Clause 9.1 in Part 1) and the single Summary Record contained in the Message.

For sales reports covering multiple sale contexts, the ServiceDescription in the Header should be the same as in the file name and represent a human-readable summary of the sales contexts provided in the Summary Records.

String

C

PremiumService

14

RecipientPartyId

The DDEX PartyId (DPID) of the MessageRecipient. This element is mandatory when the Sales Report Message is sent to one MessageRecipient and must not be included when the Sales Report Message is sent to more than one MessageRecipient.

DDEX Party ID

O

PADPIDA2007081601G

15

RecipientName

The Full Name of the MessageRecipient. This element is mandatory when the Sales Report Message is sent to one MessageRecipient and must not be included when the Sales Report Message is sent to more than one MessageRecipient.

String

O

SACEM

16

RepresentedRepertoire

Content owners represented by the MessageRecipient. This only needs to be provided if there are more than one repertoires being administered by the MessageRecipient.

RepresentedRepertoire is of value only if the sales/usage report is sent to a collective rights management organisation.

Multiple strings

O

GEMA|PAECOL

 



[1] Mandatory – Optional – Conditional

 8.1.2 SRFO — Footer Record For Single-Record Block Variants
This is the Footer Record for all Single-Record Block Variant sales/usage reports created in accordance with this standard. Each Sales Report Message shall have exactly one such Footer Record. It shall be the last Record in the Sales Report Message.
Cell NameField DefinitionData TypeM/O/C?Example
1

RecordType

The Type of the Record; always to contain “SRFO”.

Fixed string

M

SRFO

2

NumberOfLinesInReport

Number of data lines communicated in the Sales Report Message, including Header and Footer Records as well as empty Records (in accordance with Clause 6.6.7 of Part 1 of the Digital Sales Report Message Suite Standard) and commented-out Records (in accordance with Clause 6.6.9 of Part 1 of the Digital Sales Report Message Suite Standard).

Integer

M

1234

3NumberOfSummaryRecordsNumber of Summary Records communicated in the Sales Report Message.IntegerM20

8.2 Summary Record Types

 8.2.1 SY01.01 – Basic Summary Record (with Exchange Rate)
This is the Record to communicate basic summary information about Usages, Sales and Revenues.

 

Cell NameField DefinitionData TypeM/O/C?Example
1RecordType

The Type of the Record; always to contain “SY01.01”.

Fixed stringMSY01.01
2SummaryRecordId
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
3DistributionChannel

The Party that generated the sales/usages reported in this Sales/Usage Report.

DistributionChannel needs to be provided if the Message Sender offers multiple distribution channels that need to be differentiated in the Sales/Usage Report.

StringCMyCo
4DistributionChannelDPID

The DDEX Party ID of the DistributionChannel.

DistributionChannelDPID shall be provided when essential to the commercial relationship being reported on.

DPIDCDPIDA12345SDF
5CommercialModel

The Type of CommercialModel of the SalesTransaction. The CommercialModel defines how a Consumer has paid for access to a Service or Release/Resource.

AVSMPayAsYouGoModel
6UseType

The nature of a Service as used by a Consumer. This also allows the communication of Device Usages (that is, which type of device a consumer was using to access the Release/Resource) by using the appropriate use type “UseAsDevice”.

AVSMPermanentDownload
7Territory

The Territory for which the Sale/Usage is reported.

AVSMDE
8ServiceDescription

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

ServiceDescription shall be provided if a Message Sender offers multiple services that need to be differentiated in theis sales/usage report.

StringCPremiumService
9Usages

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

The Releases or Resources to be reported here are those controlled by the MessageRecipient/RightsController, according to the knowledge of the MessageSender at the time of sending the message.

IntegerM123554
10Subscribers

The number of subscribers to a Service.

Subscribers shall only be provided when the service is based on subscriptions.

Decimal

C12345
11

CurrencyOfReporting

 

The Currency in which the DspNetRevenue and IndirectNetRevenue are provided (represented by an ISO 4217 CurrencyCode).

AVSMCAD
12NetRevenue

Net Revenue of the DSP generated from the distribution of Releases or Resources, as well as sales of products based on Releases or Resources.

Decimal

M223345.12
13IndirectNetRevenue

Net Revenue of the MessageSender that was generated and that cannot be allocated to individual Releases. This field is Contractually Mandatory.

IndirectNetRevenue shall only be provided when indirect revenues were generated.

Decimal

C13424.50
14

CurrencyOfTransaction

The currency in which the Licensee generated the revenue.

AVSOUSD
15ExchangeRate

The Exchange rate used to convert from the currency used for the transactions into the currency of reporting.

Decimal

O

1.205648

 8.2.2 SY02.02 – Summary Record for Ad-Supported and Interactive Streaming Services (with RightsType and ContentCategory)
This Record can be used to communicate summary information about Usages, Sales and Revenues for ad supported and interactive streaming services.
Cell NameField DefinitionData TypeM/O/C?Example
1

RecordType

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

Fixed String

M

SY02.02

2SummaryRecordIdThe 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
3DistributionChannel

The Party that generated the sales/usages reported in the Sales/Usage Report.

DistributionChannel needs to be provided if the Message Sender offers multiple distribution channels that need to be differentiated in the Sales/Usage Report.

StringCMyCo
4DistributionChannelDPID

The DDEX Party ID of the DistributionChannel.

DistributionChannelDPID shall be provided when essential to the commercial relationship being reported on.  

DPIDCDPIDA12345SDF
5

CommercialModel

The Type of CommercialModel of the SalesTransaction. The CommercialModel defines how a Consumer has paid for access to a Service or Release/Resource.

AVS

M

AdvertisementSupportedMode

6

UseType

The nature of a Service as used by a Consumer. This also allows the communication of Device Usages (that is, which type of device a consumer was using to access the Release/Resource) by using the appropriate use type “UseAsDevice”.

AVS

M

Stream

7

Territory

The Territory for which the Sale/Usage is reported.

AVS

M

FR

8

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

PremiumService

9

Usages

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

Integer

M

1234

10Users

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

IntegerO1234
11

CurrencyOfReporting

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

AVS

M

CAD

12

NetRevenue

Net Revenue of the DSP generated from the distribution of Releases or Resources, as well as sales of products based on Releases or Resources.

Decimal

M

10545.12

13

RightsController 

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

String

O

SACEM

14RightsControllerPartyId

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

PartyIdOISNI::0000000081266409
15

AllocatedUsages

The number of Usages allocated to the RightsController.

Multiple Decimals

O

411.29

16

AllocatedRevenue

The amount allocated to the MessageRecipient/RightsController for the usages reported.

This is sometimes known as Amount Payable.

Multiple Decimals

O

20.45

17

AllocatedNetRevenue

Net Revenue generated that is to be allocated to the MessageRecipient/RightsController.

Decimal

O

781.73

18

RightsType

A Type of Right which is covered.

AVS

O

MechanicalRight
19

ContentCategory

A string categorising the content that has been used or distributed as agreed between sender and recipient.

StringMMusic
20

CurrencyOfTransaction

The currency in which the Licensee generated the revenue.

AVSOUSD
21ExchangeRate

The Exchange rate used to convert from the currency used for the transactions into the currency of reporting.

Decimal

O

1.205648

22RightsTypePercentage

The percentage of how much of the revenue or royalties should be allocated to the RightsType communicated in Cell 18.

The RightsTypePercentage may only be provided if a RightsType is provided. For the avoidance of doubt, it is permissable to communicate a RightsType without a RightsTypePercentage.

Cells 9 (Usages), 10 (Users) and 12 (NetRevenue) shall be provided not pro-rated by the RightsTypePercentage, i.e. if a RightsType only attracts 25% of the royalties, 100% of these values shall be reported in the respective Cells.

DecimalC10.00
 8.2.3 SY04.01 — Per-subscriber Minima Summary Record for Subscription Services with Ratio
This is the Record to summarise usage-independent per subscriber minima that apply to a series of sales/usages, typically in the context of subscription services.

It is permissible that multiple SY04.01 records carry the same SummaryRecordId value as long as they carry the same sales/usage context information (as defined in Clause 6.5 of Part 1 of this Digital Sales Report Message Suite Standard), i.e. the same DistributionChannel, DistributionChannelDPID, CommercialModel, UseType, Territory. This allows multiple sales/usage Records to refer to this group of the SY04.01 Records and their context.

Cell Name

Field Definition

Data Type

M/O/C

Example

1

RecordType

The Type of the Record; always to contain “SY04.01”

Fixed string

M

SY04.01

2

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.

String

M

34

3

DistributionChannel

The Party that generated the sales/usages reported in the Sales/Usage Report.

DistributionChannel needs to be provided if the Message Sender offers multiple distribution channels that need to be differentiated in this Sales/Usage Report.

String

C

MyCo

4

DistributionChannelDPID

The DDEX Party ID of the DistributionChannel.

DistributionChannelDPID shall be provided when essential to the commercial relationship being reported on.

DPID

C

DPIDA12345SDF

5

CommercialModel

The Type of CommercialModel of the SalesTransaction. The CommercialModel defines how a Consumer has paid for access to a Service or Release/Resource.

AVS

M

SubscriptionModel

6

UseType

The nature of a Service as used by a Consumer. This also allows the communication of Device Usages (that is, which type of device a consumer was using to access the Release/Resource) by using the appropriate use type “UseAsDevice”.

AVS

M

Stream

7

Territory

The Territory for which the Sale/Usage is reported.

AVS

M

FR

8

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

PremiumService

9

SubscriberType

The type of Subscriber.

String

M

Student

10

Subscribers

The number of subscribers to a Service for each SubscriberType.

Decimal

M

1239867

11

SubPeriodStartDate

The StartDate of the reporting Period covered by the Summary Record (in ISO 8601:2004 format) to allow reporting per-subscriber minima in a more granular form than for the overall reporting period. This is a string with the syntax YYYY[-MM[-DD]].

SubperiodStartDate shall only be provided when it differs from the UsageStartDate and UsageEndDate in the message header Record. SubperiodStartDate and SubPeriodEndDate shall always be provided together.

The SubperiodStartDate must not be earlier than than the UsageEndDate provided in the relevant header record.

Date

C

2014-12-01

12

SubPeriodEndDate

The EndDate of the reporting Period covered by the Summary Record (in ISO 8601:2004 format) to allow reporting per-subscriber minima in a more granular form than for the overall reporting period. This is a string with the syntax YYYY[-MM[-DD]].

SubperiodEndDate shall only be provided when it differs from the UsageStartDate and UsageEndDate in the message header Record. SubperiodStartDate and SubperiodEndDate shall always be provided together.

The SubPeriodEndDate must not be later than than the UsageEndDate provided in the relevant header record and must not be earlier than the SubPeriodStartDate.

Date

C

2014-12-01

13

UsagesInSubPeriod

The number of Usages of the Release or Resource provided to Consumers, including any sales adjustments in the sub period. Sales adjustments include e.g. file failures.

UsagesInSubPeriod and UsagesInReportingPeriod are conditional depending on the commercial relationship between Message Sender and Message Recipient.

Integer

C

1234

14

UsagesInReportingPeriod

The number of Usages of the Release or Resource provided to Consumers, including any sales adjustments in the overall reporting period. Sales adjustments include e.g. file failures.

UsagesInSubPeriod and UsagesInReportingPeriod are conditional depending on the commercial relationship between Message Sender and Message Recipient.

Integer

C

1234

15

CurrencyOfReporting

Currency used to report NetRevenue, AllocatedNetRevenue and AllocatedRevenue (represented by an ISO 4217 CurrencyCode).

AVS

M

CAD

16

CurrencyOfTransaction

The currency in which the Licensee generated the revenue.

AVS

O

USD

17

ExchangeRate

The Exchange rate used to convert from the currency used for the transactions into the currency of reporting.

Decimal

O

1.205648

18

ConsumerPaidUnitPrice

The average price paid by the Subscribers

Decimal

M

6.62

19

NetRevenue

Net Revenue of the DSP generated from the distribution of Releases or Resources, as well as sales of products based on Releases or Resources.

Decimal

M

10545.12

20

MusicUsagePercentage

The percentage of musical content in the subscription service.

Decimal between 0 and 100

M

14.54

 8.2.4 SY05.02 – Licensor Usage and Revenue Summary Record for Subscription Services (with Currency, SubPeriods and ContentCategory)
This is the Record to summarise subscription service-based sales/usages for individual Licensors.

DistributionChannel, DistributionChannelId, TotalUsages and MusicUsageRatio shall be provided when essential to the commercial relationship being reported on.  ServiceDescription shall be provided if a Message Sender offers multiple services that need to be differentiated in this sales/usage report. 


Cell Name

Field Definition

Data Type

M/O/C

Example

1

RecordType

The Type of the Record; always to contain “SY05.02”

Fixed string

M

SY05.02

2

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.

String

M

34

3

DistributionChannel

The Licensee on whose behalf the Sales/Usage has been generated.

String

C

MyCo

4

DistributionChannelDPID

The DDEX Party ID of the DistributionChannel

DPID

C

DPIDA12345SDF

5

CommercialModel

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

AVS

M

SubscriptionModel

6

UseType

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

AVS

M

Stream

7

Territory

The Territory for which the sale/transaction is reported.

AVS

M

FR

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

RightsController

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

String

O

SACEM

10

RightsControllerPartyId

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

PartyId

O

ISNI::0000000081266409

11

RightsType

Type of Right for which the Revenue and Usages applies

AVS

M

PerformingRight

12TotalUsagesThe number of Usages generated by the Service.IntegerC2324
13

AllocatedUsages

The number of Usages allocated to the RightsController.

Multiple Decimal

O

411.29

14MusicUsageRatioThe ratio for the usages of Resources with musical content in relation to the usages of all Resources.DecimalC34.7687
15

AllocatedNetRevenue

The amount due to the RighsController for the Uses, Revenue or Sales.

Multiple Decimals

O

20.45

16

AllocatedRevenue

The amount allocated to the MessageRecipient/RightsController for the usages reported.

This is sometimes known as Amount Payable.

Decimal

O

781.73

17

RightsControllerMarketShare

The ratio in percent between TotalUsages and AllocatedUsages

Decimal

O

18.25

18

CurrencyOfReporting

Currency used to report AllocatedNetRevenue and AllocatedRevenue (represented by an ISO 4217 CurrencyCode).

AVS

O

EUR

19

CurrencyOfTransaction

The currency in which the Licensee generated the revenue.

AVSOCHF
20ExchangeRate

The Exchange rate used to convert from the currency used for the transactions into the currency of reporting.

Decimal

O1.23
21

SubscriberType

The type of Subscriber.

String

O

Student

22SubPeriodStartDate

Start of the SubPeriod, the meaning of which is agreed between Sender and Recipient.

DateO2015-01-01
23SubPeriodEndDate

End of the SubPeriod, the meaning of which is agreed between Sender and Recipient.

DateO2015-10-01
24

ContentCategory

A string categorising the content that has been used or distributed as agreed between sender and recipient.StringMMusic
25RightsTypePercentage

The percentage of how much of the revenue or royalties should be allocated to the RightsType communicated in Cell 11.

The RightsTypePercentage may only be provided if a RightsType is provided. For the avoidance of doubt, it is permissable to communicate a RightsType without a RightsTypePercentage.

Cell 12 (TotalUsages) shall be provided not pro-rated by the RightsTypePercentage, i.e. if a RightsType only attracts 25% of the royalties, 100% of this value shall be reported in Cell 12.

DecimalC10.00
 8.2.5 SY06.02 – Summary Record for AV Content (with Exchange Rate Information and Listener Hours)
Summary Record to summarise audio-visual Sales/Usages. 

This Record Type is an update to the SY06.01 Record Type defined in Part 8 of the DSR Standard and has the same structure as SY06.01, albeit with two differences:

  • The RecordType shall contain the string SY06.02, instead of SY06.02; and
  • The following Cell will appear in addition, and to the right of, the Cells defined in SY06.01:
    • ViewingHours.

 

Cell Name

Field Definition

Data Type

M/O/C

Example

1

RecordType

The Type of the Record; always to contain “SY06.02

Fixed string

M

SY06.02

2

SummaryRecordId

The Identifier (specific to the Message) of the Summary Record.

This Identifier shall be used by Usage/Revenu e/Sales Records to indicate to which Summary Record they provide details.

String

M

7

3

DistributionChannel

The Party that generated the sales/usages reported in this Sales/Usage Report.

DistributionChannel needs to be provided if the Message Sender offers multiple distribution channels that need to be differentiated in this Sales/Usage Report.

String

C

MyCo

4

DistributionChannelDPID

The DDEX Party ID of the DistributionChannel

DistributionChannelDPID is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

DPID

C

DPIDA12345SDF

5

CommercialModel

The Type of CommercialModel of the SalesTransaction. The CommercialModel defines how a Consumer has paid for access to a Service or Release/Resource.

AVS

M

PayAsYouGoModel

6

UseType

The nature of a Service as used by a Consumer. This also allows the communication of Device Usages (that is, which type of device a consumer was using to access the Release/Resource) by using the appropriate use type “UseAsDevice”.

AVS

M

PermanentDownload

7

Territory

The Territory for which the Sale/Usage is reported.

AVS

M

DE

8

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

Purchase

 

9

Usages

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

Integer

M

123554

10

Subscribers

The number of subscribers to a Service.

Subscribers shall only be provided when the service is based on subscriptions.

Decimal

C

123445

11

CurrencyOfReporting

The Currency in which the DspNetRevenue and IndirectNetRevenue are provided (represented by an ISO 4217 CurrencyCode

AVS

M

CAD

12

NumberOfReleases

Total number of Releases reported in the Message

Integer

O

64

13

NetRevenue

Net Revenue of the DSP generated from the distribution of Releases or Resources, as well as sales of products based on Releases or Resources.

Decimal

O

223345.12

14

IndirectNetRevenue

Net Revenue of the MessageSender that was generated and that cannot be allocated to individual Releases. This field is Contractually Mandatory.

IndirectNetRevenue shall only be provided when indirect revenues were generated.

Decimal

C

13424.50

15

PreviewAvailable

Flag of whether the service offers previews.

Note, this is independent from whether any previews were accessed by Consumers.

Boolean

O

true

16

CurrencyOfTransaction

The currency in which the Licensee generated the revenue.

AVS

O

EUR

17ExchangeRateThe Exchange rate used to convert from the currency used for the transactions into the currency of reporting.DecimalO1234
18ViewingHours

The number of hours consumers listed to the content.

 

DecimalO10.2
 8.2.6 SY09 – Summary Record to communicate Rights Controller Market Shares
This is the Record to communicate market-shares per right type for individual rights controllers.

Cell Name

Field Definition

Data Type

M/O/C

Example

1

RecordType

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

Fixed String

M

SY09

2

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 Rights Controller they provide details.

String

M

123

3

CommercialModel

The Type of CommercialModel of the SalesTransaction. The CommercialModel defines how a Consumer has paid for access to a Service or Release/Resource.

AVS

M

AdvertisementSupportedModel

4UseType

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

AVSMStream
5

Territory

The Territory for which the Sale/Usage is reported.

AVS

M

DE

6

ServiceDescription

The service name (e.g. a service tier) under which the SalesTransaction took place. The ServiceDescription may not contain space characters or underscores.
ServiceDescription shall be provided when essential to the commercial relationship being reported on.

StringCPremiumService
7SubscriberType

The type of Subscriber.

SubscriberType needs to be provided if the sales report covers subscriptions.

StringCStudent
8

RightsController

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

String

O

SACEM

9

RightsControllerPartyID

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

PartyID

O

ISNI::0000000081266409

10

RightsType

The right utilised as a result of the way in which the Consumer accessed the Resource.

A RightsType shall be provided when it applies to the accessed Resource.

AVS

C

MechanicalRight

11

TotalUsages

The number of Usages of the Release or Resource provided to Consumers, including any sales adjustments. Sales adjustments include e.g. file failures. Releases or Resources to be reported here include all Releases or Resources provided across the service, not just the ones that are are controlled by the MessageRecipient/RightsController, according to the knowledge of the MessageSender at the time of sending the message. This allows the MessageRecipient/RightsController to calculate its market share of uses.
TotalUsages shall be provided when essential to the commercial relationship being reported on.

TotalUsages shall be provided not pro-rated by the RightsTypePercentage, i.e. if a RightsType only attracts 25% of the royalties, 100% of this value shall be reported in that Cell.

DecimalC1066.45
12AllocatedUsages

The number of Usages allocated to the RightsController.

DecimalO135.23
13NetRevenue

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

NetRevenue shall be provided not pro-rated by the RightsTypePercentage, i.e. if a RightsType only attracts 25% of the royalties, 100% of this value shall be reported in that Cell.

DecimalM1220.06
14IndirectNetRevenue

Net Revenue of the DSP not directly attributable to the transacted Release or Resource.

DecimalO120.81
15

RightsControllerMarketShare

The ratio in percent between TotalUsages and AllocatedUsages

Decimal

O10.54
16

CurrencyOfReporting

The Currency in which the NetRevenue and IndirectNetRevenue are provided (represented by an ISO 4217 CurrencyCode

AVSMCZK
17

CurrencyOfTransaction

The currency in which the Licensee generated the revenue.

AVS

O

EUR

18ExchangeRateThe Exchange rate used to convert from the currency used for the transactions into the currency of reporting.DecimalO1234
19RightsTypePercentage

The percentage of how much of the revenue or royalties should be allocated to the RightsType communicated in Cell 18.

The RightsTypePercentage may only be provided if a RightsType is provided. For the avoidance of doubt, it is permissable to communicate a RightsType without a RightsTypePercentage.

DecimalC10.00

 


8.3 Detailed Record Types

 8.3.1 SR01 — SRB Record Type for the Basic Audio Profile for Download Models
This is the Record to contain all information necessary to convey Release, resource, work and sales/usage information in a single-record block profile variants for download models. This Record supports the reporting of sales and/or usages of music and music videos based on Musical Works.

 

Cell Name

Field Definition

Data Type

M/O/C

Example

1

RecordType

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

Fixed String

M

SR01

2SummaryRecordId

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

StringM22

3

DspResourceId

The ProprietaryIdentifier of the Resource assigned by the MessageSender

String

M

12345678

4

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.

ISRC is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

USS1Z1412345

5

ResourceTitle

The ReferenceTitle of the Resource

String

M

Eight Days a Week

6

ResourceSubTitle

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

String

O

Live Version

7

ResourceDisplayArtistName

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

String

M

The Beatles

8

ResourceDisplayArtistPartyId

The PartyId of the DisplayArtist

PartyId

O

ISNI::0000000081266409

9

Duration

 

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

The Duration shall be provided if available to the Message Sender.

ISO duration

C

PT1H2M3S

10

ResourceType

The Type of the Resource

AVS

M

SoundRecording

11

ProprietaryWorkId

The ProprietaryIdentifier of the Musical Work, preceded by a namespace identifier in the syntax ns::id

String::String

O

myns::4534

12

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.

ISWC is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

T0030749586

13

ComposerAuthor

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

ComposerAuthor is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in ComposerAuthor and ComposerAuthorPartyId shall be the same so that the recipient is able to relate names and IDs correctly

Multiple Strings

C

Johann Sebastian Bach

14

ComposerAuthorPartyId

The PartyId(s) of the ComposerAuthor(s)

The order of the individual strings in ComposerAuthor and ComposerAuthorPartyId shall be the same so that the recipient is able to relate names and IDs correctly

Multiple PartyIds

O

ISNI::0000000081266409

15

Arranger

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

Arranger is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in Arranger and ArrangerPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple Strings

C

August Wilhelmj

16

ArrangerPartyId

The PartyId(s) of the Arranger(s)

The order of the individual strings in Arranger and ArrangerId shall be the same so that the recipient is able to relate names and IDs correctly

Multiple PartyIds

O

ISNI::0000000081266409

17

MusicPublisher

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

MusicPublisher is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in MusicPublisher and MusicPublisherPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple Strings

C

UMP

18

MusicPublisherPartyId

The PartyID(s) of the MusicPublisher(s).

The order of the individual strings in MusicPublisher and MusicPublisherPartyId shall be the same so that the recipient is able to relate names and IDs correctly

Multiple PartyIds

O

ISNI::00000000111111111

19

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. 

WorkContributor is mandatory when available to the MessageSender unless the contributor has already been included as a ComposerAuthor, Arranger or MusicPublisher. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in WorkContributor and WorkContributorPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple Strings

C

George Martin

20

WorkContributorPartyId

The PartyId(s) of the WorkContributor(s)

The order of the individual strings in WorkContributor and WorkContributorPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple PartyIds

O

ISNI::00000000111111111

21

DspReleaseId

The ProprietaryIdentifier of the Release assigned by the MessageSender

A DspReleaseId shall be provided if the sales transaction was in respect of a Release for which the message sender has information.

String

C

1234567

22

ProprietaryReleaseId

The ProprietaryIdentifier of the Release preceded by a namespace identifier in the syntax ns::id

Multiple String::String

O

myns::4534|ns2::4345

23

ReleaseCatalogNumber

The catalogue number of the Release assigned by the issuing record company

String

O

123456

24

ICPN

The ICPN used as proxy for identification of the Release. An ICPN comprises 12 or 13 digits, depending on whether it is an EAN (13) or a UPC (12). 14 character ICPNs are also permitted.

String

O

12345678904321

25

ReleaseDisplayArtistName

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

String

M

The Beatles

26

ReleaseDisplayArtistPartyId

The PartyId of the DisplayArtist

PartyId

O

ISNI::0000000081266409

27

ReleaseTitle

The ReferenceTitle of the Release

String

M

Beatles for Sale

28

ReleaseSubTitle

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

String

O

Live Version

29

ReleaseType

The form in which a ReleaseCreator anticipates offering the Release to Consumers.

AVS

O

Album

30

ReleaseLabel

The Name of the Label for the Release.

String

O

Apple Records

31

PLine

The PLine for the Release

String

O

℗1970 Apple Records

32

ReleaseDataProvider

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

String

O

UMG

33NumberOfTransactedResources

The number of the Resources that were transacted.

Note: this Cell is not part of the current version of the relevant Multi-Record Block Variant. DDEX expects the relevant Multi-Record Block Variant to be extended by this Cell at some stage.

IntegerM12
34

SalesTransactionId

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

If a Release containing, for example, 10 sound recordings is transacted, a sales/usage report in accordance with a Single-Record Block Variant is likely to contain up to 10 SR01 Records with the same SalesTransactionId.

String

M

34456

35

IsRoyaltyBearing

 

The Boolean flag indicating whether the MessageSender is contractually obliged to pay royalties to the RightsController for the SalesTransaction reported in the Record.

Boolean

M

true

36

SalesUpgrade

A Flag indicating whether the SalesTransaction applies to an upgraded Release (=true) or not (=false).

Boolean

M

false

37

Downloads

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

In the MRBV, downloads are reported in the Cell called Usages.

Integer

M

100

38

Returns

The number of Usages of a Release or Resource returned (with refund) by Consumers as a result of a reversal of a SalesTransaction or because of an earlier error in sales reporting.

Integer

M

20

39

PriceConsumerPaidExcSalesTax

A Price paid by Consumers, excluding SalesTax for each SalesTransaction. This may be a nominal price.

PriceConsumerPaidExcSalesTax is mandatory when the CommercialModel is PayAsYouGoModel.

Decimal

C

0.34

40CalculatedPriceConsumer PaidForResourceExcSalesTax

The calculated price the Consumer paid for the Resource being reported in this Record. If the transacted entity was a Release, the sum of all contained Resources' would equal the PriceConsumerPaidExcSalesTax.

Whether CalculatedPriceConsumer PaidForResourceExcSalesTax is required depends on bilateral agreements between Licensor and Licensee.

 Note: this Cell is not part of the current version of the relevant Multi-Record Block Variant. DDEX expects the relevant Multi-Record Block Variant to be extended by this Cell at some stage.

Decimal

C

0.64

41

PromotionalActivity

Free-text Description of a promotional activity that led to the Release being distributed.

String

O

 

 8.3.2 SR02 — SRB Record Type for the Basic Audio Profile for Streaming Models
This is the Record to contain all information necessary to convey Release, resource, work and sales/usage information in a single-record block profile variant for streaming models. This Record supports the reporting of sales and/or usages of Sound Recordings and music videos based on Musical Works.

 

Cell Name

Field Definition

Data Type

M/O/C

Example

1

RecordType

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

Fixed String

M

SR02

2SummaryRecordId

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

StringM22

3

DspResourceId

The ProprietaryIdentifier of the Resource assigned by the MessageSender

String

M

12345678

4

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.

ISRC is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

USS1Z1412345

5

ResourceTitle

The ReferenceTitle of the Resource

String

M

Eight Days a Week

6

ResourceSubTitle

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

String

O

Live Version

7

ResourceDisplayArtistName

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

String

M

The Beatles

8

ResourceDisplayArtistPartyId

The PartyId of the DisplayArtist

PartyId

O

ISNI::0000000081266409

9

Duration

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

The Duration shall be provided if available to the Message Sender.

ISO duration

C

PT1H2M3S

10

ResourceType

The Type of the Resource

AVS

M

SoundRecording

11

ProprietaryWorkId

The ProprietaryIdentifier of the Musical Work, preceded by a namespace identifier in the syntax ns::id

String::String

O

myns::4534

12

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.

ISWC is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

T0030749586

13

ComposerAuthor

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

ComposerAuthor is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in ComposerAuthor and ComposerAuthorPartyId shall be the same order so that the recipient is able to relate names to IDs correctly.

Multiple Strings

C

Johann Sebastian Bach

14

ComposerAuthorPartyId

The PartyId(s) of the ComposerAuthor(s)

The order of the individual strings in ComposerAuthor and ComposerAuthorPartyId shall be the same order so that the recipient is able to relate names to IDs correctly.

Multiple PartyIds

O

ISNI::0000000081266409

15

Arranger

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

Arranger is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in Arranger and ArrangerPartyId shall be the same order so that the recipient is able to relate names to IDs correctly.

Multiple Strings

C

August Wilhelmj

16

ArrangerPartyId

The PartyId(s) of the Arranger(s)

The order of the individual strings in Arranger and ArrangerPartyId shall be the same order so that the recipient is able to relate names to IDs correctly.

Multiple PartyIds

O

ISNI::0000000081266409

17

MusicPublisher

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

MusicPublisher is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in MusicPublisher and MusicPublisherPartyId shall be the same order so that the recipient is able to relate names to IDs correctly.

Multiple Strings

C

UMP

18

MusicPublisherPartyId

The PartyID(s) of the MusicPublisher(s).

The order of the individual strings in MusicPublisher and MusicPublisherPartyId shall be the same order so that the recipient is able to relate names to IDs correctly.

Multiple PartyIds

O

ISNI::00000000111111111

19

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.

WorkContributor is mandatory when available to the MessageSender unless the contributor has already been included as a ComposerAuthor, Arranger or MusicPublisher. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in WorkContributor and WorkContributorPartyId shall be the same order so that the recipient is able to relate names to IDs correctly.

Multiple Strings

C

George Martin

20

WorkContributorPartyId

The PartyId(s) of the WorkContributor(s)

The order of the individual strings in WorkContributor and WorkContributorPartyId shall be the same order so that the recipient is able to relate names to IDs correctly.

Multiple PartyIds

O

ISNI::00000000111111111

21

DspReleaseId

The ProprietaryIdentifier of the Release assigned by the MessageSender.

A DspReleaseId shall be provided if the sales transaction was in respect of a Release for which the message sender has information.

String

C

1234567

22

ProprietaryReleaseId

The ProprietaryIdentifier of the Release preceded by a namespace identifier in the syntax ns::id

Multiple String::String

O

myns::4534|ns2::4345

23

ReleaseCatalogNumber

The catalogue number of the Release assigned by the issuing record company

String

O

123456

24

ICPN

The ICPN used as proxy for identification of the Release. An ICPN comprises 12 or 13 digits, depending on whether it is an EAN (13) or a UPC (12). 14 character ICPNs are also permitted.

String

O

12345678904321

25

ReleaseDisplayArtistName

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

String

M

The Beatles

26

ReleaseDisplayArtistPartyId

The PartyId of the DisplayArtist

PartyId

O

ISNI::0000000081266409

27

ReleaseTitle

The ReferenceTitle of the Release

String

M

Beatles for Sale

28

ReleaseSubTitle

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

String

O

Live Version

29

ReleaseType

The form in which a ReleaseCreator anticipates offering the Release to Consumers.

AVS

O

Album

30

ReleaseLabel

The Name of the Label for the Release.

String

O

Apple Records

31

PLine

The PLine for the Release

String

O

℗1970 Apple Records

32

ReleaseDataProvider

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

String

O

UMG

33

SalesTransactionId

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

String

M

34456

34

IsRoyaltyBearing

 

The Boolean flag indicating whether the MessageSender is contractually obliged to pay royalties to the RightsController for the SalesTransaction reported in the Record.

Boolean

M

true

35

NumberOfStreams

The number of Streams of the Release from the MessageSender to Consumers.

Decimal

M

765.65

36

PromotionalActivity

Free-text Description of a promotional activity that led to the Release being distributed.

String

O

Valentines Day Special

 8.3.3 SR03 — Basic SRB Record Type for the UGC Profile
This is the basic Record to contain all information necessary to convey Release, resource, work and sales/usage information in a single-record block profile variant for UGC.

Cell Name

Field Definition

Data Type

M/O/C

Example

1

RecordType

The Type of the Record; always to contain “SR03

Fixed String

M

SR03

2SummaryRecordId

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

StringM22

3

DspResourceId

The ProprietaryIdentifier of the Resource assigned by the MessageSender

String

M

12345678

4

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.

ISRC is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

USS1Z1412345

5

ResourceTitle

The ReferenceTitle of the Resource

 

String

M

Yellow Submarine 

6 ResourceSubTitle A Descriptor which is supplementary to, but not contained within, a Title.  StringOLive Version

7

ResourceDisplayArtistName

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

ResourceDisplayArtistName must be provided if available.

String

C

The Beatles

8

ResourceDisplayArtistPartyId

The PartyId of the DisplayArtist

PartyId

O

ISNI::0000000081266409

9Duration

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

The Duration shall be provided if available to the Message Sender.

ISO DurationCPT1H2M3S
10ResourceType

The Type of the Resource

AVSMSoundRecording
11WorkTitle

The ReferenceTitle of the MusicalWork

String

M

Yellow Submarine

12DspWorkId

The ProprietaryIdentifier of the Musical Work assigned by the MessageSender

String

M

12345678

13ISWC

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.

ISWC is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

T0030749586

14

ComposerAuthor

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

ComposerAuthor is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in ComposerAuthor and ComposerAuthorPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple Strings

C

Johann Sebastian Bach

15

ComposerAuthorPartyId

The PartyId(s) of the ComposerAuthor(s)

The order of the individual strings in ComposerAuthor and ComposerAuthorPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple PartyIds

O

ISNI::0000000081266409

16

Arranger

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

Arranger is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in Arranger and ArrangerPartyID shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple String

C

August Wilhelmj

17ArrangerPartyId

The PartyId(s) of the Arranger(s)

The order of the individual strings in Arranger and ArrangerPartyID shall be the same so that the recipient is able to relate names and IDs correctly; a maximum of one ArrangerPartyId can be provided for each Arranger.

Multiple PartyID(s)OISNI::0000000081266409
18MusicPublisher

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

MusicPublisher is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in MusicPublisher and MusicPublisherPartyID shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple StringCUMP
19MusicPublisherPartyId

The PartyID(s) of the MusicPublisher(s).

The order of the individual strings in MusicPublisher and MusicPublisherPartyID shall be the same so that the recipient is able to relate names and IDs correctly; a maximum of one MusicPublisherPartyId can be provided for each MusicPublisher.

Multiple PartyIDOISNI::00000000111111111
20

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. 

WorkContributor is mandatory when available to the MessageSender unless the contributor has already been included as a ComposerAuthor, Arranger or MusicPublisher. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in WorkContributor and WorkContributorPartyID shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple String

C

UMP

21WorkContributorPartyId

The PartyId(s) of the WorkContributor(s)

The order of the individual strings in WorkContributor and WorkContributorPartyID shall be the same so that the recipient is able to relate names and IDs correctly; a maximum of one WorkContributorPartyId can be provided for each WorkContributor.

Multiple PartyID(s)OISNI::000000008126640

22

DspReleaseId

The ProprietaryIdentifier of the Release assigned by the MessageSender

A DspReleaseId shall be provided is the sales transaction was in respect of a Release for which the message sender has information.

String

C

1234567

23

ProprietaryReleaseId

The ProprietaryIdentifier of the Release preceded by a namespace identifier in the syntax ns::id

Multiple String::String

O

myns::4534|ns2::4345

24

CatalogNumber

The catalogue number of the Release assigned by the issuing record company

String

O

123456

25

ICPN

The ICPN used as proxy for identification of the Release. An ICPN comprises 12 or 13 digits, depending on whether it is an EAN (13) or a UPC (12). 14 character ICPNs are also permitted.

ICPN is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

12345678904321

26ReleaseDisplayArtistName

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

ReleaseDisplayArtistName shall be provided if available to the Message Sender.

StringCThe Beatles
27ReleaseDisplayArtistPartyIdThe PartyId of the DisplayArtistPartyIdOISNI::0000000081266409
28

ReleaseTitle

The ReferenceTitle of the Release

String

M

Beatles for Sale

29

ReleaseSubTitle

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

String

O

Live Version

30

ReleaseLabel

The Name of the Label for the Release.

String

O

Apple Records

31

PLine

The Pline for the Release

String

O

℗1970 Apple Records

32SalesTransactionId

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

String

M

34456

33

Usages

The number of Usages of the Release by Consumers using the MessageSender service, including any sales adjustments. Sales adjustments include e.g. file failures.

This includes all usages of the embedded Resources and is reported before taking any RightShare% or RightsType into account.

Decimal

M

100.1

34

NetRevenue

Net Revenue of the DSP generated from the distribution of Releases or Resources, as well as sales of products based on Releases or Resources. NetRevenue is reported before taking any RightShare% or RightsType into account.

Must be provided in accordance with bilateral agreement.

Decimal

C

10545.12

35ValidityPeriodStart

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 DateM2017-06-01
36ValidityPeriodEnd

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 DateM2017-06-01
37ContentCategory

A string categorising the content that has been used or distributed as agreed between sender and recipient.

StringMMusic
38

RightsController

Name of the RightsController that is believed by the MessageSender to control a RightShare of the Work. If a LI record applies to more than one RightsController, Message Sender and Message Recipient shall agree a mutually acceptable keywords (e.g. "all" or "conflict"). Clearly, Message Sender and Message Recipient, must take care to use keywords that do not conflict with real RightsControllers.

RightsController shall be provided if available and required based on the bilateral agreement between sender and recipient.

String

C

SACEM

39RightsControllerPartyId

The PartyId of the RightsController.

RightsControllerPartyId shall be provided if available and required based on the bilateral agreement between sender and recipient.

PartyID

C

ISNI::0000000081266409
40RightsControllerWorkIdThe ProprietaryId given to the MusicalWork used by the RightsContoller

String

O

12gc

41RightShare%

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 “0.25” (and not 25).

Must be provided in accordance with bilateral agreement.

Decimal

C

.25

42RightsType

The right for which the RightShare% is provided. If information for multiple RightsType needs to be communicated, multiple SR03 Records, one for each RightsType, need to be used.

AVSOMechanicalRight
43AllocatedNetRevenue

Net Revenue generated that is to be allocated to the MessageRecipient/RightsController.

Must be provided in accordance with bilateral agreement.

Decimal

C

34567

44

AllocatedAmount

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

 Must be provided in accordance with bilateral agreement.

Decimal

C

2560.77

45AllocatedUsages

The number of Usages allocated to the RightsController.

Decimal

C

10.5

46AllocatedNetUsage

The number of net Usages allocated to the RightsController.

Note: this Cell is not part of the current version of the relevant Multi-Record Block Variant. DDEX expects the relevant Multi-Record Block Variant to be extended by this Cell at some stage.

Decimal

C

 

8.4

 

 8.3.4 SR04 — SRB Record Type for the Audio-visual Profile for Download Models
This is the Record to contain all information necessary to convey Release, resource, work and sales/usage information in a single-record block profile variants for audio-visual download models.

Cell Name

Field Definition

Data Type

M/O/C

Example

1

RecordType

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

Fixed String

M

SR04

2SummaryRecordId

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

Note: this Cell appears out of order but Summary RecordId are always the second Cell in a Record.

StringM22

3

DspResourceId

The ProprietaryIdentifier of the Resource assigned by the MessageSender

String

M

12345678

4ISAN

The ISAN (International Standard Audiovisual Number as defined in ISO 15706) for the Video. An ISAN comprises four blocks of four hexadecimal characters followed by a check character followed, optionally by two further blocks of four hexadecimal characters, followed by a further check character.

ISAN is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

StringC0000-0001-8947-0000-8-0000-0000-D
5

EIDR

An Identifier of the Video assigned by the Entertainment Identifier Registry Association (EIDR).

EIDR is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

StringC10.5240/F85A-E100-B068-5B8F-B1C8-T
6PoprietaryResourceId

The ProprietaryIdentifier of the Resource preceded by a namespace identifier in the syntax ns::id

Multiple String::String

O

Myns::4534|ns2::4896

7VideoType

The primary Type of the Video. As only one value can be selected, the primary VideoType needs to be provided.

Note: this Cell is defined as a multiple AVS in the current version of the relevant Multi-Record Block Variant. DDEX expects the relevant Multi-Record Block Variant to be updated at some stage.

Multiple AVSMVideoReport

8

ResourceTitle

The Title of the Resource

String

M

Winter is Coming

9

ResourceSubTitle

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

String

O

Live Version

10ResourceOriginalTitle

A Title given to a Creation by its Creator(s), in its original Language.

ResourceOriginalTitle is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

O

The Hamburger Postulate

11EpisodeNumber

The number indicating the order of the Episodes within a Season (if available) or Series. This is the number allocated to the Season by the production house.

EpisodeNumber has to be provided for TV series episodes.

String

C

S1E5
12SeasonNumber

The number indicating the order of the Seasons within a Series. This is the number allocated to the Episode by the production house.

SeasonNumber has to be provided for seasons of TV series or parts thereof.

Stribng

C

S4
13Genre

The genre or style (such as Musical, literary or audio-visual) with which the Resource is associated.

String

O

Horror Comedy

14Duration

The Duration of the audio-visual Resource (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 duration

M

PT1H2M3S

15ResourceDisplayArtistNameThe Name to be used by a DSP when presenting Artist details of the Resource to a Consumer. To be provided for concert films or when the information is available.StringCThe Beatles
16ResourceDisplayArtistPartyIdThe PartyId of the DisplayArtist. To be provided for concert films or when the information is available.PartyIdC

ISNI::0000000081266409

17ProducerName

The Name(s) of the producer(s) of the audio-visual Resource

The order of the individual strings in ProducerName and ProducerPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple Strings

O

Scott Kraft

18ProducerPartyId

The PartyId(s) of the Producer(s)

The order of the individual strings in ProducerName and ProducerPartyId shall be the same so that the recipient is able to relate names and IDs correctly; a maximum of one ProducerPartyId can be provided for each ProducerName.

Multiple PartyID

O

ISNI::0000000081266409

19DirectorName

The Name(s) of the director(s) of the audio-visual Resource

DirectorName is mandatory for films and documentaries when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in DirectorName and DirectorPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple Strings

C

Mark Cendrowski

20DirectorPartyId

The PartyId(s) of the Director(s)

The order of the individual strings in DirectorName and DirectorPartyId shall be the same so that the recipient is able to relate names and IDs correctly; a maximum of one DirectorPartyId can be provided for each DirectorName.

Multiple PartyID

O

ISNI::0000000081266409

21ActorName

The Name(s) of the actor(s) of the audio-visual Resource

The order of the individual strings in ActorName and ActorPartyId shall be the same so that the recipient is able to relate names and IDs correctly

Multiple Strings

O

Jim Parsons

22ActorPartyId

The PartyId(s) of the Actor(s)

The order of the individual strings in ActorName and ActorPartyId shall be the same so that the recipient is able to relate names and IDs correctly

Multiple PartyID

O

ISNI::0000000081266409

23ProductionCompanyName

Name of the company that produced the Resource.

Note: this Cell is not part of the current version of the relevant Multi-Record Block Variant. DDEX expects the relevant Multi-Record Block Variant to be extended by this Cell at some stage.

StringOProduction123
24ProductionCompanyPartyId

The PartyId of the ProductionCompany.

Note: this Cell is not part of the current version of the relevant Multi-Record Block Variant. DDEX expects the relevant Multi-Record Block Variant to be extended by this Cell at some stage.

Multiple PartyID

O

ISNI::0000000081266409

25LanguageLocalizationType

Type of adaptation of an Audio-visual Resource for a specific audience and/or language.

LanguageLocalizationType needs to be provided if available to the message sender.

 

AVS

C

Dubbed

26HasCaptioning

Flag indicating whether the audio-visual Resource has captioning to the hard of hearing and/or deaf.

HasCaptioning is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

Boolean

C

false

27HasAudioDescription

A Flag indicating whether the audio-visual Resource has audio descriptions for the visually impaired and blind.

HasAudioDescription is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

Boolean

C

false

28OriginalLanguageOfPerformance

The main original Language of the Performance recorded in the audio-visual Resource. The first language code must be main language.

 

Multiple ISO Language Code

O

en

29LanguageOfDubbing

The Language of dubbing used in the audio-visual Resource The first language code must be main language.

LanguageOfDubbing is mandatory when LanguageLocalizationType is Dubbed, SubTitled or Multilingual.

Multiple ISO Language Code

O

de

30DateOfProductionOrRelease

The date when the audio-visual resource was produced, or when it was first released, in the ISO 8601 format: YYYY[-MM[-DD]].

DateOfProductionOrRelease is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

ISO date

C

2015

31CountryOfProduction

The country or countries in which the audio-visual resource was produced.

CountryOfProduction is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

Multiple ISO Country Codes

C

GB|IE

32OriginalBroadcastChannel

The broadcast channel on which the Release was originally broadcast in the territory that is being reported on.

OriginalBroadcastChannel is mandatory for services deemed to be “catch-up” television.

String

C

BBC One

33OriginalBroadcastDateTime

The date and, if available, time, of the original broadcast of the Resource in ISO 8601 format in the territory that is being reported on.

OrigialBroadcastDateTime is mandatory for services deemed to be “catch-up” television.

ISO 8601

C

1999-10-27T20:00:00Z

34DspReleaseId

The ProprietaryIdentifier of the Release assigned by the MessageSender. To be provided when the sales/usage information is provided for a resource that has been distributed in the context of a Release.

String

C

12345678

35PoprietaryReleaseId

The ProprietaryIdentifier of the Release preceded by a namespace identifier in the syntax ns::id

Multiple String::String

O

Myns::4534|ns2::4896

36ICPN

The ICPN used as proxy for identification of the Release. An ICPN comprises 12 or 13 digits, depending on whether it is an EAN (13) or a UPC (12). 14 character ICPNs are also permitted.

ICPN is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

1234567654321

37ReleaseTitle

The ReferenceTitle of the Release. To be provided when the sales/usage information is provided for a resource that has been distributed in the context of a Release.

String

C

The Hamburger Postulate

38ReleaseSubTile

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

String

O

 
39SeriesTitle

The title of the Series that the Release is part of.

SeriesTitle must be provided if the Release is part of a Series.

String

C

The Office

40ReleaseType

The form in which a ReleaseCreator anticipates offering the Release to Consumers.

AVS

O

LongFormNonMusical-WorkVideoRelease

41DataProvider

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

String

O

UMG

42VideoCategory

A description of the content of the video as agreed between sender and recipient to classify the used Release.

String

O

Sport

43

SalesTransactionId

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

Taken together the SalesTransactionId and the MessageId are globally and perpetually unique.

String

M

34456

44

DrmEnforcement

Flag indicating if the Release was technically protected.

DrmEnforcement is mandatory when available to the MessageSender and has an impact on licensing terms. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

Note: this Cell is defined as an AVS in the current version of the relevant Multi-Record Block Variant. DDEX expects the relevant Multi-Record Block Variant to be updated at some stage.

Boolean

C

false

45VideoDefinitionType

The type of resolution (or definition) in which a Video is provided.

VideoDefintionType is mandatory when available to the MessageSender and has an impact on licensing terms. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

AVS

C

HighDefinition

46CodingType

The type of coding in which a Video is provided.

CodingType is mandatory when available to the MessageSender and has an impact on licensing terms. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

AVS

C

Lossless

47BitRate

BitRate for the audiovisual data in Mbps.

BitRate is mandatory when available to the MessageSender and has an impact on licensing terms. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

Decimal

C

1.25

48IsRoyaltyBearing

The Boolean flag indicating whether the MessageSender is contractually obliged to pay royalties to the RightsController for the SalesTransaction reported in the Record.

Boolean

M

true

49

Downloads

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

Decimal

M

1000

50Returns

The number of Usages of a Release or Resource returned (with refund) by Consumers as a result of a reversal of a SalesTransaction or because of an earlier error in sales reporting.

Integer

M

2

51PriceConsumerPaidExcSalesTax

A Price paid by Consumers, excluding SalesTax for each SalesTransaction. This may be a nominal price.

PriceConsumerPaidExcSalesTax is mandatory when the CommercialModelType is PayAsYouGoModel.

Decimal

O

100.34

52PromotionalActivity

Free-text Description of a promotional activity that led to the Release being distributed.

String

O

Valentines Day Special

 


 8.3.5 SR05 — SRB Record Type for the Audio-visual Profile for Streaming Models
This is the Record to contain all information necessary to convey Release, resource, work and sales/usage information in a single-record block profile variants for audio-visual streaming models.

Cell Name

Field Definition

Data Type

M/O/C

Example

1

RecordType

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

Fixed String

M

SR05

2SummaryRecordId

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

Note: this Cell appears out of order but SummaryRecordId are always the second Cell in a Record.

StringM22

3

DspResourceId

The ProprietaryIdentifier of the Resource assigned by the MessageSender

String

M

12345678

4ISAN

The ISAN (International Standard Audiovisual Number as defined in ISO 15706) for the Video. An ISAN comprises four blocks of four hexadecimal characters followed by a check character followed, optionally by two further blocks of four hexadecimal characters, followed by a further check character.

ISAN is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

StringC0000-0001-8947-0000-8-0000-0000-D
5

EIDR

An Identifier of the Video assigned by the Entertainment Identifier Registry Association (EIDR).

EIDR is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

StringC10.5240/F85A-E100-B068-5B8F-B1C8-T
6ProprietaryResourceId

The ProprietaryIdentifier of the Resource preceded by a namespace identifier in the syntax ns::id

Multiple String::String

O

Myns::4534|ns2::4896

7VideoType

The primary Type of the Video. As only one value can be selected, the primary VideoType needs to be provided.

Note: this Cell is defined as a multiple AVS in the current version of the relevant Multi-Record Block Variant. DDEX expects the relevant Multi-Record Block Variant to be updated at some stage.

AVSMVideoReport

8

ResourceTitle

The Title of the Resource

String

M

Beatles for Sale

Winter is Coming

9

ResourceSubTitle

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

String

O

Live Version

10ResourceOriginalTitle

A Title given to a Creation by its Creator(s), in its original Language.

The ResourceOriginalTitle is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

O

The Hamburger Postulate

11EpisodeNumber

The number indicating the order of the Episodes within a Season (if available) or Series. This is the number allocated to the Season by the production house.

EpisodeNumber has to be provided for TV series episodes.

String

C

S1E5
12SeasonNumber

The number indicating the order of the Episodes within a Season (if available) or Series. This is the number allocated to the Season by the production house.

EpisodeNumber has to be provided for TV series episodes.

Stribng

C

S4
13Genre

The genre or style (such as Musical, literary or audio-visual) with which the Resource is associated.

String

O

Horror Comedy

14Duration

The Duration of he audio-visual Resource (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 duration

M

PT1H2M3S

 ResourceDisplayArtistNameThe Name to be used by a DSP when presenting Artist details of the Resource to a Consumer. To be provided for concert films or when the information is available.StringCThe Beatles
 ResourceDisplayArtistPartyId

The PartyId of the DisplayArtist. To be provided for concert films or when the information is available.

PartyIdO

ISNI::0000000081266409

15ProducerName

The Name(s) of the producer(s) of the audio-visual Resource

The order of the individual strings in ProducerName and ProducerPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple Strings

O

Scott Kraft

16ProducerPartyId

The PartyId(s) of the Producer(s)

The order of the individual strings in ProducerName and ProducerPartyId shall be the same so that the recipient is able to relate names and IDs correctly; a maximum of one ProducerPartyId can be provided for each ProducerName.

Multiple PartyID

O

ISNI::0000000081266409

17DirectorName

The Name(s) of the director(s) of the audio-visual Resource

DirectorName is mandatory for films and documentaries when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in DirectorName and DirectorPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple Strings

C

Mark Cendrowski

18DirectorPartyId

The PartyId(s) of the Director(s)

The order of the individual strings in DirectorName and DirectorPartyId shall be the same so that the recipient is able to relate names and IDs correctly; a maximum of one DirectorPartyId can be provided for each DirectorName.

Multiple PartyID

O

ISNI::0000000081266409

19ActorName

The Name(s) of the actor(s) of the audio-visual Resource

The order of the individual strings in ActorName and ActorPartyId shall be the same so that the recipient is able to relate names and IDs correctly

Multiple Strings

O

Jim Parsons

20ActorPartyId

The PartyId(s) of the Actor(s)

The order of the individual strings in ActorName and ActorPartyId shall be the same so that the recipient is able to relate names and IDs correctly

Multiple PartyID

O

ISNI::0000000081266409

21ProductionCompanyName

Name of the company that produced the Resource.

Note: this Cell is not part of the current version of the relevant Multi-Record Block Variant. DDEX expects the relevant Multi-Record Block Variant to be extended by this Cell at some stage. 

StringOProduction123
22ProductionCompanyPartyId

The PartyId of the ProductionCompany.

Note: this Cell is not part of the current version of the relevant Multi-Record Block Variant. DDEX expects the relevant Multi-Record Block Variant to be extended by this Cell at some stage.

Multiple PartyID

O

ISNI::0000000081266409

23LanguageLocalizationType

Type of adaptation of an Audio-visual Resource for a specific audience and/or language.

LanguageLocalizationType shall be provide when available to the Message Sender.

AVS

C

Dubbed

24HasCaptioning

Flag indicating whether the audio-visual Resource has captioning to the hard of hearing and/or deaf.

HasCaptioning is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

Boolean

C

false

25HasAudioDescription

A Flag indicating whether the audio-visual Resource has audio descriptions for the visually impaired and blind.

HasAudioDescription is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

Boolean

C

false

26OriginalLanguageOfPerformance

The main original Language of the Performance recorded in the audio-visual Resource. The first language code must be main language.

Multiple ISO Language Code

O

en

27LanguageOfDubbing

The Language of dubbing used in the audio-visual Resource. The first language code must be main language.

LanguageOfDubbing is mandatory when LanguageLocalizationType is Dubbed, SubTitled or Multilingual.

Multiple ISO Language Code

O

de

28DateOfProductionOrRelease

The date when the audio-visual resource was produced, or when it was first released, in the ISO 8601 format: YYYY[-MM[-DD]].

DateOfProductionOrRelease is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

ISO date

C

2015

29CountryOfProduction

The country or countries in which the audio-visual resource was produced.

CountryOfProduction is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

Multiple ISO Country Codes

C

GB|IE

30OriginalBroadcastChannel

The broadcast channel on which the Release was originally broadcast in the territory that is being reported on.

OriginalBroadcastChannel is mandatory for services deemed to be “catch-up” television or streaming.

String

C

BBC One

31OriginalBroadcastDateTime

The date and, if available, time, of the original broadcast of the Resource in ISO 8601 format in the territory that is being reported on.

OrigialBroadcastDateTime is mandatory for services deemed to be “catch-up” television or streaming.

ISO 8601

C

1999-10-27T20:00:00Z

32DspReleaseId

The ProprietaryIdentifier of the Release assigned by the MessageSender. To be provided when the sales/usage information is provided for a resource that has been distributed in the context of a Release 

String

C

12345678

33PoprietaryReleaseId

The ProprietaryIdentifier of the Release preceded by a namespace identifier in the syntax ns::id

Multiple String::String

O

Myns::4534|ns2::4896

34ICPN

The ICPN used as proxy for identification of the Release. An ICPN comprises 12 or 13 digits, depending on whether it is an EAN (13) or a UPC (12). 14 character ICPNs are also permitted.

ICPN is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

1234567654321

35ReleaseTitle

The ReferenceTitle of the Release. To be provided when the sales/usage information is provided for a resource that has been distributed in the context of a Release.

String

M

The Hamburger Postulate

36ReleaseSubTile

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

String

O

 
37SeriesTitle

The title of the Series that the Release is part of.

SeriesTitle must be provided if the Release is part of a Series.

String

C

The Office

38ReleaseType

The form in which a ReleaseCreator anticipates offering the Release to Consumers.

AVS

O

LongFormNonMusical-WorkVideoRelease

39

DataProvider

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

String

O

UMG

40VideoCategory

A description of the content of the video as agreed between sender and recipient to classify the used Release.

String

O

Sport

41SalesTransactionId

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

Taken together the SalesTransactionId and the MessageId are globally and perpetually unique.

String

M

34456

42VideoDefinitionType

The type of resolution (or definition) in which a Video is provided.

VideoDefintionType is mandatory when available to the MessageSender and has an impact on licensing terms. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

AVS

C

HighDefinition

43CodingType

The type of coding in which a Video is provided.

CodingType is mandatory when available to the MessageSender and has an impact on licensing terms. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

AVS

C

Lossless

44BitRate

BitRate for the audiovisual data in Mbps.

BitRate is mandatory when available to the MessageSender and has an impact on licensing terms. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

Decimal

C

1.25

45IsRoyaltyBearing

The Boolean flag indicating whether the MessageSender is contractually obliged to pay royalties to the RightsController for the SalesTransaction reported in the Record.

Boolean

M

true

46NumberOfStreams

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

Decimal

M

1000

47PromotionalActivity

Free-text Description of a promotional activity that led to the Release being distributed.

String

O

Valentines Day Special

 8.3.6 SR06 — SRB Record Type for the UGC Profile for Ad-supported and Streaming Models
This is the Record to contain all information necessary to convey Release, resource, work and sales/usage information in a single-record block profile variant for UGC when reporting sales/usages for ad-supported business models.

Cell Name

Field DefinitionData TypeM/O/C

Example

1

RecordType

The Type of the Record; always to contain “SR06

Fixed String

M

SR06

2SummaryRecordId

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

StringM22

3

DspResourceId

The ProprietaryIdentifier of the Resource assigned by the MessageSender

String

M

12345678

4

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.

ISRC is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

USS1Z1412345

5

ResourceTitle

The ReferenceTitle of the Resource

 

String

M

Yellow Submarine 

6 ResourceSubTitle A Descriptor which is supplementary to, but not contained within, a Title.  StringOLive Version

7

ResourceDisplayArtistName

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

ResourceDisplayArtistName should be provided if available to the Message Sender.

String

C

The Beatles

8

ResourceDisplayArtistPartyId

The PartyId of the DisplayArtist

PartyId

O

ISNI::0000000081266409

9WorkTitle

The ReferenceTitle of the MusicalWork

String

M

Yellow Submarine

10DspWorkId

The ProprietaryIdentifier of the Musical Work assigned by the MessageSender

String

M

12345678

11ISWC

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.

ISWC is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

String

C

T0030749586

12

ComposerAuthor

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

ComposerAuthor is mandatory when available to the MessageSender. This field is important for MessageRecipients for their processing and would ideally be mandatory in this Standard. However, as there are rare cases where licensees genuinely do not have this information, DDEX has decided to mark these Cells as “Conditional”.

The order of the individual strings in ComposerAuthor and ComposerAuthorPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple Strings

C

Johann Sebastian Bach

13

ComposerAuthorPartyId

The PartyId(s) of the ComposerAuthor(s)

The order of the individual strings in ComposerAuthor and ComposerAuthorPartyId shall be the same so that the recipient is able to relate names and IDs correctly.

Multiple PartyIds

O

ISNI::0000000081266409

14

Usages

The number of Usages of the Release by Consumers using the MessageSender service, including any sales adjustments. Sales adjustments include e.g. file failures.

This includes all usages of the embedded Resources and is reported before taking any RightShare% or RightsType into account.

Decimal

M

100.1

15ValidityPeriodStart

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 DateM2017-06-01
16ValidityPeriodEnd

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 DateM2017-06-01
17ContentCategory

A string categorising the content that has been used or distributed as agreed between sender and recipient.

StringMMusic
18

RightsController

Name of the RightsController that is believed by the MessageSender to control a RightShare of the Work. If a LI record applies to more than one RightsController, Message Sender and Message Recipient shall agree a mutually acceptable keywords (e.g. "all" or "conflict"). Clearly, Message Sender and Message Recipient, must take care to use keywords that do not conflict with real RightsControllers.

RightsController shall be provided if available and required based on the bilateral agreement between sender and recipient.

String

C

SACEM

19RightsControllerPartyId

The PartyId of the RightsController.

RightsControllerPartyId shall be provided if available and required based on the bilateral agreement between sender and recipient.

PartyID

C

ISNI::0000000081266409
20RightsControllerWorkIdThe ProprietaryId given to the MusicalWork used by the RightsContoller

String

O

12gc

21RightShare%

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 “0.25” (and not 25).

RightShare% shall be provided if available and required based on the bilateral agreement between sender and recipient.

Decimal

C

.25

22RightsType

The right for which the RightShare% is provided.

RightsType shall be provided if available and required based on the bilateral agreement between sender and recipient.

AVSCMechanicalRight
23

AllocatedAmount

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

 Must be provided in accordance with bilateral agreement.

Decimal

C

2560.77 

24AllocatedNetUsage

The number of net Usages allocated to the RightsController.

Decimal

C

8.4

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.