This section of the DDEX Knowledge Base contains Version 1.0.1 of the Standard for the Bulk Communication of Work and Recording Metadata.

1 Introduction

This standard was developed by the member organisations of the Digital Data Exchange, LLC (DDEX) and provides a lightweight mechanism for communicating, in bulk, Musical Work and Recording information. This standard has been developed to support the activities of the Mechanical Licensing Collective established under the Music Modernization Act (MMA) that was signed into US law in 2018 but may also be used for other purposes.

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 at https://ddex.net/implementation/implementation-licence-and-ddex-party-identifiers.

Essential Reading

Download/Print standard (PDF)

Download Samples (ZIP) covering work and party information. The samples will be extended to cover recordings data at a later stage.

BWARM is a "Candidate Standard", which is a formal standard approved by DDEX for which DDEX has not had any information about live implementations. Once DDEX has received such input, it is expected that BWARM will be promoted to "DDEX Standard".

2 Scope

2.1 Introduction

Version 1.0.1 of this standard provides a mechanism to communicate information about Musical Works, Recordings that make use of such Works as well as Musical Work Right Shares. In that, this standard serves a similar purpose to the Musical Work Right Share Notification Choreography Standard (MWN). MWN is, however, best-suited to communicate detailed information on a comparatively small number of Musical Works in the context of Musical Work Licensing. This standard is targeted at communicating, in a bulk feed, information on large sets of Musical Works.

DDEX expects to extend the bulk feed format with an interactive feed.

2.2 Organisation of the Standard

This Standard has seven clauses. Clauses 1 and 2 provide a general introduction and the scope of this Standard. Clauses 3 and 4 give a set of normative references as well as terms, definitions and abbreviations that are used in this Standard.

Clause 5 provides the overall choreography supported by this Standard. Clause 6 then specifies the bulk data feed. Finally, Clause 7 provides the Allowed Value Sets used in this Standard.

3 Normative References

Click here to expand...

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

DDEX Data Dictionary Standard. Latest Version
DDEX Party Identifier (DPID) Standard. Latest Version
ISO 3166-1. Codes for the representation of names of countries and their sub-divisions – Part 1: Country codes. Latest Version
ISO 3901. Information and documentation – International Standard Recording Code (ISRC). Latest Version
ISO 8601. Data elements and interchange formats – Information interchange – Representation of dates and times^[1]. Latest Version

[1] Information on ISO 8601 can be found in Annex D of Part 2 (Datatypes Second Edition) of the XML Schema standard (http://www.w3.org/TR/xmlschema-2/#isoformats).

4 Terms and Abbreviations

4.1 Terms and Definitions

Cell

An individual data element in a Record. Cells are separated by Delimiters.

Delimiter

A character that delineates, in a flat file, either one Record from another Record or one Cell from another Cell.

Manifest

An XML message signifying the delivery of a Batch.

Musical Work

A Work intended to be perceivable as a combination of sounds, with or without accompanying text.

Any words that are intended to be expressed with a MusicalWork (often termed Lyrics) form part of that MusicalWork; not all MusicalWorks have Lyrics.
A MusicalWork may be expressed and fixed to become part of a SoundRecording or a Video Recording, or may be used to create notated music (sheet music, scores, instrumental parts) or sound generation codes (such as MIDI files).
In some cases, the MusicalWork comes into existence simultaneously with its expression. This is common in extemporised forms such as jazz music.

Record

A line in a flat file containing data about a specific data entity. The Record type is indicated in the first Cell. Data elements are contained in Cells which are separated by a specifically defined Delimiter.

Secondary Delimiter

Delimiter used to separate data elements within a single Cell.

Right Share

A percentage or fraction of a right for a Musical Work for a particular time and place in which a party claims a controlling interest. Note: controlling interest includes ownership and/or administration.

4.2 Abbreviations

AMEP	Automated Message Exchange Protocol
ACA	Appointed Certification Agency
AVS	Allowed Value Set
BP	Business Profile
BWARM	Bulk Communication of Work and Recording Metadata
CISAC	Confédération internationale des sociétés d'auteurs et compositeurs, the International Confederation of Societies of Authors and Composers (see cisac.org)
CA	Certification Agency
CT	Conformance Tester
DAW	Digital Audio Workstation
DDEX	Digital Data Exchange
DSIG	Digital Signature
DSP	Digital Service Provider (incudes Mobile Service Providers)
DSR	Digital Sales Reporting
ERN	Electronic Release Notification
FTP	File Transfer Protocol (FTP specifically includes SFTP)
GRid	Global Release Identifier
HTTP	Hypertext Transport Protocol (HTTP specifically includes HTTPS)
HTTPS	Secure Hypertext Transport Protocol
IEC	International Electrotechnical Commission (see iec.ch)
ISO	International Organisation for Standardisation (see iso.org)
MEAD	Media Enrichment And Description
MIME	Multipurpose Internet Mail Extensions
MWL	Musical Works Licensing
MWN	Musical Works Notification
MRBV	Multi-Record-Block Variant
PCA	Private Certification Agency
PDF	Portable Document Format
PIE	Party Identification and Enrichment
REST	REpresentational State Transfer
RIN	Recording Information Notification
SFTP	Secure FTP
SRBV	Single-Record-Block Variant
TIS	Territory Information System (a CISAC Standard)
TLS	Transport Layer Security
UGC	User-generated content
URL	Uniform Resource Locator
XML	eXtensible Markup Language
XSD	XML Schema Definition
W3C	World Wide Web Consortium (see w3c.org)
WS	Web Service

5 Choreographies

5.1 Introduction

This standard defines two mechanisms, each with their own choreography, for exchanging Musical Work and Recording information .

The choreography for the Bulk Feed is depicted below. The exchange of files defined in the Bulk Feed shall use SFTP using the naming convention defined in subsequent Clauses of this standard.

Figure 1 – Choreography of the Bulk Communication of Work and Recording Metadata Standard

In this version of the standard no acknowledgement message is included in the choreography, as there is no need for the Feed Provider to receive a feed back. If the users of the standard need to express that the files have been downloaded, to communicate a summary of what data has been extracted from the files or to report errors, such a message may be added in later versions.

5.2 Bulk Feed Content

Each Bulk Feed comprises:

Exactly one file describing Musical Works, created in accordance with Clause 6.4;
Exactly one file providing alternative titles for such Musical Works, created in accordance with Clause 6.5;
Exactly one file providing proprietary identifiers for Musical Works, created in accordance with Clause 6.6;
Exactly one file describing Parties who have an interest in such Musical Work Shares (such as Publishers and Writers), created in accordance with Clause 6.7;
Exactly one file describing Right Shares for such Musical Works, created in accordance with Clause 6.8;
Exactly one file describing Sound Recordings for such Musical Works (or for unclaimed Right Shares for which no Musical Works have been identified), created in accordance with Clause 6.9;
Exactly one file providing alternative titles for such Recordings, created in accordance with Clause 6.10;
Exactly one file providing proprietary identifiers for such Recordings, created in accordance with Clause 6.11;
Exactly one file describing Releases for such Recordings, created in accordance with Clause 6.12;
Exactly one file providing proprietary identifiers for such Releases, created in accordance with Clause 6.13;
Exactly one file providing links between such Recordings and underlying Musical Works, created in accordance with Clause 6.14; and
Exactly one file providing information about usages for which (some) Right Shares have not yet been claimed, created in accordance with Clause 6.15.

Some files in a Feed may be empty (e.g. when no Recordings are to be communicated).

The diagram below shows an entity relationship diagram for the above files .

Figure 2 – Entity relationship diagram for the Bulk Communication of Work and Recording Metadata Standard

5.3 Folder and File Naming Convention for Bulk Data Feed

The arrival of the files of a Feed on the SFTP server shall be signified by placing a Manifest file at the appropriate location. The Manifest shall refer to all files that are part of the Feed. The Manifest may only be placed on the SFTP server, once all other files have been completely uploaded.

A Feed is identified by the date and time of its creation in the form BWARM_DataFeedProvider_[DataFeedRecipient]_YYYYMMDDhhmmssnnn[.ext] with

DataFeedProvider being the DDEX Party ID of the organisation providing the Feed;
DataFeedRecipient being the optional DDEX Party ID of the organisation for whom the Feed folder is created. For “broadcast feeds”, this element shall be left empty;
YYYY being the year of Feed creation;
MM being the month of Feed creation;
DD being the day of Feed creation;
hh being the hour of Feed creation;
mm being the minute of Feed creation;
ss being the second of Feed creation;
nnn being the millisecond of Feed creation; and
.ext being a file extension if the Feed is provided in an archived and/or compressed format (such as .zip for a zip archive or .gtar for a GNU tar ball). If the Feed is provided as an uncompressed set of files in a folder, no extension shall be used.

The files inside a Feed folder shall be named in accordance with Clause 6.

The Manifest shall be placed in the same folder as the Feed itself and have the following filename: BWARM_Manifest_DataFeedProvider_[DataFeedRecipient]_YYYYMMDDhhmmssnnn.tsv.

6 Bulk Data Feed

6.1 Introduction

This Clause 6 defines the syntax for all files listed in Clause 5.2.

6.2 Technical Details

6.2.1 Character Coding

Each file shall be encoded using UTF-8 with a big-endian byte ordering.

6.2.2 Delimiters

6.2.2.1 Record Delimiter

Each file shall be separated into individual Records with each Record being placed into one line terminated by a line feed (Unicode U+000A) or a carriage return and line feed pair (Unicode U+000D 000A).

6.2.2.2 Primary (Cell) Delimiter

Cells within a Record are separated by tab characters (Unicode U+0009).

6.2.2.3 Secondary Delimiter

Should a Cell contain two or more data elements, these data elements shall be separated by a pipe character (Unicode U+007C). This is referred to as a Secondary Delimiter.

All data elements in a multi-value Cell shall be of the same primitive data type.

6.2.2.4 Namespace Delimiter

Should a Cell contain a data element whose provenance needs to be provided, the data element shall be preceded by a string that provides a "namespace" and two colon characters (Unicode U+003A). The double colon is referred to as a Namespace Delimiter. Examples include specifically identifiers where, e.g., a party ID can be communicated as "ISNI::0000000081266409", indicating that the identifier (0000000081266409) is an International Standard Name Identifier (ISNI).

6.2.2.5 Spaces and Delimiters

Delimiters shall not be surrounded by extra space characters. The same principle applies to the Secondary Delimiter.

Example: The writer pair Lennon/McCartney should be communicated as "Lennon|McCartney" and not as "Lennon | McCartney".

6.2.2.6 Communicating Delimiters

To communicate a primary Delimiter in a Cell, such a Cell shall not be enclosed in double quote characters. Instead the Delimiter shall be immediately preceded by an escaping code.

To escape a tab character contained in a text string, the escaping code is the backslash character (Unicode U+005C). Therefore the string A[TAB]B would have to be communicated as A\[TAB]B (with [TAB] representing the tabulator).

To escape a pipe character contained in a text string, the escaping code is a double backslash character (Unicode U+005C). Therefore the string A|B would have to be communicated as A\\|B.

To communicate a backslash character, three backslash characters need to be communicated. Therefore the string A\B would have to be communicated as A\\\B.

This “escaping mechanism” must be used for all special characters in all Cells, whether those Cells allow multiple values or not. A non-escaped pipe character in a single-value cell is, consequently, an error.

For the avoidance of doubt, escaping a character that should not be escaped, or not escaping a character that should have been escaped, will lead to an invalid Feed file.

6.2.3 Primitive Data Types

Within this standard the following primitive data types are used.

Data Type	Definition	Example
String	A sequence of characters with a length of at least one character. This standard does not define a maximum length. Strings may not contain non-printable characters (Unicode U+0000 to U+001F).	Johannes Brahms
Boolean	A string containing either “true” or “false”.	true
Integer	A sequence of digits to represent positive or negative integer numbers, or zero.	142356
Decimal	A sequence of digits to represent positive or negative integer numbers, positive or negative decimal fractions or zero. The character used to separate the integers from fractions is the dot (“.”, Unicode U+002E). Thousands separators or any other digit grouping shall not be used.	123 123.567 -5.25 0
ISO Date	A date in the ISO 8601 format to indicate a single year (YYYY), month (YYYY-MM) or day (YYYY-MM-DD).	2015-01-09
Duration	A duration in the ISO 8601 format (P[nY][nM][nD][T[nH][nM]nS]). Elements including their designator may be omitted if their value is zero. Note that the expressions “PT3M2S” (three minutes and two seconds) and “PT182S” (182 seconds) are both permitted and are equivalent.	PT3M2S
DPID	A string of 18 characters in accordance with the DDEX Party ID standard. Note that the DDEX Party ID standard defines that DDEX Party IDs do not contain dashes in computer-to-computer communications. Therefore, DDEX Party IDs, when included in a Feed, shall not contain dashes.	PADPIDA2014122301Q
AVS	A string from a set of allowed values as defined in Clause 7.	Work
Multiple String	A sequence of 0-n strings in accordance with a defined data type separated by Secondary Delimiters. If the Feed provider has only one data item to provide, the value shall be included without any Secondary Delimiters. The same applies to cases where the Feed provider has multiple data elements but only wishes to communicate one in accordance with the bilateral agreement between Feed provider and Feed recipient. If the cardinality of such an element is "M", at least one such data item must be provided. The same concept can also be used for all other primitive data types listed above.	"12" or "12\|54\|123" or "12\|\|123" (without the quotes)

6.2.4 Maximum Cell Size

While some Cells have an inherent length limitation, other Cells have no length limitation.

Note: this has an implication for developers using databases with field length limitations. Such developers will be forced to shorten fields if the data received exceeds their databases’ capabilities.

6.2.5 Communicating Decimals and Integers

This standard does not prescribe a specific precision in which decimal numbers are to be given. Feed provider and Feed recipient must agree a mutually agreeable precision for the type of transactions at hand. The same applies to Integers.

Implementers are reminded that some accounting applications may only be able to handle six, or even four, decimal places.

When a field of type “decimal” is used to communicate an integer, the number may be represented with a trailing decimal point, a trailing “.0” or with no trailing characters. For example, the number five can be represented as “5”, “5.” for “5.0”.

When the number 0 (zero) is to be communicated in a Cell for decimal values, this shall be represented as 0 (and not 0.0 or 0.000000).

6.3 Manifest File

6.3.1 Introduction

Once the Feed provider has uploaded all files of the Feed the Feed provider shall upload a Manifest file. Its filename and location are defined in Clause 5.3.

The Manifest file shall comprise (in this order)

Exactly one Manifest Header Record;
Exactly one Manifest Data Record for each of the files that make up the Feed; and
Exactly one Manifest Footer Record.

6.3.2 Manifest Header Record

Cell Name		Field Definition	Data Type	M/O/C[1]	Example
1	Version	The Version of the Standard as defined in Clause 2.1.	String	M	1.0
2	FeedProvider	The name of the organisation providing the data Feed.	String	O	The MLC
3	FeedProviderDPID	The DDEX Party ID of the FeedProvider.	DPID	M	PADPIDA2008120501W
4	FeedRecipient	The name of the organisation receiving the data Feed.	String	O	Sony/ATV
5	FeedRecipientDPID	The DDEX Party ID of the FeedRecipient.	DPID	O	PADPIDA2008120501W
6	FeedCreatedDateTime	The DateTime on which the Message or Feed was created (the only allowed format is ISO 8601: YYYY-MM-DDThh:mm:ssTZD). This shall be the same datetime as indicated in the Feed file name.	ISO Datetime	M	2014-12-14T10:05:00Z

[1] Mandatory – Optional – Conditional

6.3.3 Manifest Data Record

Cell Name		Field Definition	Data Type	M/O/C	Example
1	TableType	The type of file described by the summary record. Allowed values are defined in Clauses 6.4-6.15.	String	M	Works
2	FileName	The name of the file in the Feed.	String	M	works.tsv
3	NumberOfLinesInFile	The number of lines in the file.	Integer	M	432
4	MD5HashSum	The hex-encoded MD5 hash sum of the file.	String	O

6.3.4 Manifest Footer Record

Cell Name		Field Definition	Data Type	M/O/C	Example
1	EndOfFileMarker	A fixed string to indicate the end of the file. Always to be “EOF”.	String	M	EOF
2	NumberOfLinesInManifest	The number of lines in the Manifest file, including Header and Footer Records.	Integer	M	9

6.4 Works File

The works file shall be called works.tsv and be referenced in the Manifest's TableType as “Works”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersWorkId	The Feed provider's proprietary identifier of the Musical Work. This is the primary key of the database table for Works (see Figure 2).	String	M	165DE541A
2	ISWC	The ISWC (International Standard Musical Work Code defined in ISO 15707) identifying the Musical Work. An ISWC comprises three parts: the letter "T", followed by nine digits and then one check digit.	String	O	T9000109397
3	WorkTitle	The title of the Musical Work.	String	M	I've Got a Feeling
4	OpusNumber	The MusicalWorkId identifying the Musical Work within the catalog of its Composer (typically of classical music) as an opus number.	String	O	Op. 27 No. 2
5	ComposerCatalogNumber	A MusicalWorkId identifying a Musical Work within the catalog of its Composer (typically of classical music) according to a standardized numbering (e.g. "K" numbers for Koechel's catalog of Mozart).	Multiple String	O	K. 621
6	NominalDuration	The nominal duration of the Musical Work.	ISO Duration	O	PT3M20S
7	HasRightsInDispute	A Flag indicating whether a Musical Work has rights that are in dispute (=true) or not (=false).	Boolean	M	false
8	TerritoryOfPublicDomain	A Territory in which the Musical Work is in the public domain using the TerritoryCode allowed value set defined in Clause 7.5.	Multiple AVS	O	US
9	IsArrangementOfTraditionalWork	A Flag indicating whether the Musical Work is an arrangement of a traditional Work (=true) or not (=false).	Boolean	M	false
10	AlternativeWorkFor UsStatutoryReversion	If the rights in a Work have reverted to the writer in accordance with sections 203 and 304 of the US Copyright Act, implementers may choose to output two versions of the Work, one pre-termination (“Reverted Work”) and one post-termination (“New Work”). This is a foreign key to the database table for Works (see Figure 2) that allows feed creators to point from the “Reverted Work” to the `FeedProvidersWorkId` of the “New Work”.	String	O	76AC54D3ED
11	UsStatutoryReversionDate	The date on which a US statutory reversion has happened (or will happen). This cell is mandatory if an AlternativeWorkForUsStatutoryReversion is provided.	ISO Date	C	2020-01-01

US statutory reversions can be dealt with in two ways: (i) by creating two Works, one pertaining to pre-termination and the other to post-termination usage, or (ii) by having different Right Shares with different validity periods for the same Work. Given the data structure limitations of most copyright systems, the common approach is the former (i). The determination of which Work to pay is based on whether the date of the applicable rights grant (typically a license date) falls before or after the effective date of the termination (UsStatutoryReversionDate).

6.5 Alternative Work Titles File

The alternative work titles file shall be called workalternativetitles.tsv and be referenced in the Manifest's TableType as “WorkAlternativeTitles”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersWorkAlternativeTitleId	The Feed provider's proprietary identifier of the Musical Work's alternative title. This is the primary key of the database table for alternative Work titles (see Figure 2).	String	M	AB77PL6
2	FeedProvidersWorkId	The Feed provider's proprietary identifier of the Musical Work. This is a foreign key to the database table for Works (see Figure 2).	String	M	165DE541A
3	AlternativeTitle	The alternative title of the Musical Work.	String	M	Everybody Had a Hard Year
4	LanguageAndScriptCode	The Language and script for of the Title as defined in IETF RfC 5646. Language and script are provided as lang[-script][-region][-variant].	String	O	en
5	TitleType	A Type of the Title which defines its origin or the function it fulfils in relation to the Musical Work.	AVS	O	IncorrectTitle

6.6 Proprietary Work Identifiers File

The proprietary work identifier file shall be called workidentifiers.tsv and be referenced in the Manifest's TableType as “WorkIdentifiers”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersWorkProprietaryIdentifierId	The Feed provider's proprietary identifier of the Musical Work's proprietary identifier. This is the primary key of the database table for proprietary Work identifiers (see Figure 2).	String	M	TY985246
2	FeedProvidersWorkId	The Feed provider's proprietary identifier of the Musical Work. This is a foreign key to the database table for Works (see Figure 2).	String	M	165DE541A
3	Identifier	The proprietary identifier of the Musical Work.	String	M	AC20018
4	FeedProvidersAllocatingPartyId	The Feed provider's proprietary identifier of the party allocating the proprietary identifier, as used in the Parties file. This is a foreign key to the database table for Parties (see Figure 2).	String	M	132P9863

6.7 Parties File

The writers and publishers file shall be called parties.tsv and be referenced in the Manifest's TableType as “Parties”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersPartyId	The Feed provider's proprietary identifier of the Party. This is the primary key of the database table for Parties (see Figure 2).	String	M	132P9863
2	ISNI	An International Standard Name Identifier, the ISO 27729 Standard Identifier for names, of the Party.	String	O	000000012146438X
3	IpiNameNumber	An Interested Party Identifier, a CISAC standard Identifier, of the Party. An IpiNameNumber comprises 11 digits.	String	O	00045620792
4	CisacSocietyId	A CISAC Society Identifier, a CISAC standard Identifier for music rights societies, of the Party.	String	O
5	DPID	An Identifier of the Party according to the DDEX PartyId standard DDEX-DPID.	DPID	O	PADPIDA2007081601G
6	FullName	The complete Name of the Party, in its normal form of presentation.	String	M	The Beatles
7	NamesBeforeKeyName	The Name(s) preceding the KeyName in the FullName (and that is placed after it in an indexed form). Not all PartyNames have a NamesBeforeKeyName.	String	O	The
8	KeyName	The Part of a Name of the Party normally used to index an entry in an alphabetical list. For persons, this normally corresponds to the "family name" or names, which in Western name forms usually comes as a surname at the end of a FullName, and in Asian name forms often at the beginning of a FullName.	String	O	Beatles
9	NamesAfterKeyName	The Name(s) following the KeyName. This is common, e.g., in many Asian personal name forms where a FullName begins with the KeyName, which is followed by other names.	String	O	Inc.
10	ContactName	The name of a person that can be contacted for specific purposes (usually for companies such as publishers, not so much for writers).	String	O	John Doe
11	ContactEmail	An email address that can be used to contact the Party.	String	O	contact@example.com
12	ContactPhone	A phone number that can be used to contact the Party.	String	O	(212) 121 2222
13	ContactAddress	An address that can be used to contact the Party.	String	O	20 Madison Avenue, New York, NY 10010
14	NoValidContactInformationAvailable	A Flag indicating whether the Feed provider has information that the Party may not be reachable (=true) via the provided contact information (`ContactEmail`, `ContactPhone`, `ContactAddress`) or whether they are believed to be contactable (=false). This Flag may only be provided if contact information is provided. If this Flag is omitted, the Feed provider has no reason to believe that the Party is not reachable via the contact information provided.	Boolean	C	true

6.8 Work Right Shares File

The right share file shall be called workrightshares.tsv and be referenced in the Manifest's TableType as “WorkRightShares”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersWorkRightShareId	The Feed provider's proprietary identifier of the Right Share. This is the primary key of the database table for Right Shares (see Figure 2).	String	M	4545L0012
2	FeedProvidersWorkId	The Feed provider's proprietary identifier of the Musical Work relating to the Right Share. This is a foreign key to the database table for Works (see Figure 2).	String	M	165DE541A
3	FeedProvidersPartyId	The Feed provider's proprietary identifier of the Party controlling and/or collecting the Right Share. This is a foreign key to the database table for Parties (see Figure 2).	String	M	132P9863
4	PartyRole	The role played by the Party in relation to the Musical Work. This is mandatory information if the `RightShareType` is `MusicalWorkManuscriptShare`.	AVS	C	Composer
5	RightSharePercentage	The percentage of the Musical Work that is controlled by the Party. A quarter share is represented by '25' (and not 0.25).	Decimal	O	50
6	RightShareType	A type of the Right Share. The value of this cell can be used to derive the type of the Party as follows: if it is `MusicalWorkManuscriptShare`, it is a writer; if it is `OriginalPublisherShare`, it is an original publisher; if it is `MusicalWorkCollectionShare` or `LicensingShare`, it is a publisher.	Multiple AVS	O	LicensingShare
7	RightsType	A type of right that is covered by the Right Share.	Multiple AVS	O	PrintRight
8	ValidityStartDate	The Date that marks the beginning of the validity period (in ISO 8601 format: YYYY-MM-DD). At least one of the two Dates for the validity period needs to be provided. The `ValidityStartDate` must be no later than the `ValidityEndDate` if both are provided.	ISO Date	C	2002-11-22
9	ValidityEndDate	The Date that marks the end of the validity period (in ISO 8601 format: YYYY-MM-DD). At least one of the two Dates for the validity period needs to be provided. The `ValidityEndDate` must be no earlier than the `ValidityStartDate` if both are provided.	ISO Date	C	2012-04-30
10	FeedProvidersParentWorkRightShareId	The Feed provider's proprietary identifier of a previous Right Share, which allows a collection share to point to a previous collection share or the original publisher share or to a manuscript share; and for an original publisher share to point to a manuscript share. This is a foreign key to the database table for Right Shares (see Figure 2).	Multiple String	O	4545L0013
11	TerritoryCode	A Territory to which the RightShare applies using the TerritoryCode allowed value set defined in Clause 7.5.	Multiple AVS	O	US
12	UseType	A nature of a Service, or a Release, as used by a Consumer. If no value is given, it means that there is no restriction to a specific use type.	Multiple AVS	O	Download

6.9 Recordings File

The recordings file shall be called recordings.tsv and be referenced in the Manifest's TableType as “Recordings”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersRecordingId	The Feed provider's proprietary identifier of the Recording. This is the primary key of the database table for Recordings (see Figure 2).	String	M	U124X987
2	ISRC	The ISRC (International Standard Recording Code as defined in ISO 3901) for the Recording. An ISRC comprises four parts: two characters, followed by three alphanumeric characters, then two digits and five digits.	String	O	USS1Z1412345
3	RecordingTitle	The title of the Recording.	String	M	I've Got a Feeling
4	RecordingSubTitle	A subtitle of the title, including titles of versions used to differentiate different versions of the same title, as required by the GRid and ISRC ReferenceDescriptiveMetadataSets.	String	O	Naked Version / Remastered 2013
5	DisplayArtistName	The name to be used by a DSP when presenting Artist details of the Recording to a Consumer.	String	M	The Beatles
6	DisplayArtistISNI	The ISNI of the display artist whose name is given in `DisplayArtistName.`	String	O	000000012146438X
7	PLine	A PLine for the Recording.	Multiple String	O
8	Duration	The duration of the Recording.	ISO Duration	O	PT3M20S
9	FeedProvidersReleaseId	The Feed provider's proprietary identifier of the Release that is linked to the Recording. This is a foreign key to the database table for Releases (see Figure 2).	String	O	165DE541A
10	StudioProducerName	The name of a StudioProducer, i.e. a Party responsible for an artistic input to the production of the Recording.	Multiple String	O	Phil Spector
11	StudioProducerId	The identifier of a StudioProducer, i.e. a Party responsible for an artistic input to the production of the Recording. The identifier shall be preceded by a namespace identifier in the syntax ns::id. Only one identifier shall be provided per StudioProducer and the number and order of the individual data elements in `StudioProducerName` and `StudioProducerId` shall be the same so that the recipient is able to relate them correctly.	Multiple String::String	O	ns::12345
12	OriginalDataProviderName	The name of the Party that provided the original data for the Recording.	String	O	John Doe
13	OriginalDataProviderDPID	The DPID of the Party that provided the original data for the Recording.	DPID	O	PADPIDA2008120501W
14	IsDataProvidedAsReceived	A Flag indicating whether the data for the Recording is provided as received from the original provider (=true) or not (=false). This Flag has to be provided if a Party is specified in `OriginalDataProviderName` or `OriginalDataProviderDPID`.	Boolean	C	true

6.10 Alternative Recordings Titles File

The alternative recording titles file shall be called recordingalternativetitles.tsv and be referenced in the Manifest's TableType as “RecordingAlternativeTitles”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersRecordingAlternativeTitleId	The Feed provider's proprietary identifier of the Recording's alternative title. This is the primary key of the database table for alternative Recording titles (see Figure 2).	String	M	GH77PO6
2	FeedProvidersRecordingId	The Feed provider's proprietary identifier of the Recording. This is a foreign key to the database table for Recordings (see Figure 2).	String	M	U124X987
3	AlternativeTitle	The alternative title of the Recording.	String	M	I Have Got a Feeling
4	LanguageAndScriptCode	The Language and script for of the Title as defined in IETF RfC 5646. Language and script are provided as lang[-script][-region][-variant].	String	O	en
5	TitleType	A Type of the Title which defines its origin or the function it fulfils in relation to the Release.	AVS	O	IncorrectTitle

6.11 Proprietary Recording Identifiers File

The proprietary recording identifier file shall be called recordingidentifiers.tsv and be referenced in the Manifest's TableType as “RecordingIdentifiers”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersRecordingProprietaryIdentifierId	The Feed provider's proprietary identifier of the Recording's proprietary identifier. This is the primary key of the database table for proprietary Recording identifiers (see Figure 2).	String	M	RX12389
2	FeedProvidersRecordingId	The Feed provider's proprietary identifier of the Recording. This is a foreign key to the database table for Recordings (see Figure 2).	String	M	U124X987
3	Identifier	The proprietary identifier of the Recording.	String	M	C240018
4	FeedProvidersAllocatingPartyId	The Feed provider's proprietary identifier of the party allocating the proprietary identifier, as used in the Parties file. This is a foreign key to the database table for Parties (see Figure 2).	String	M	132P9863

6.12 Release File

The releases file shall be called releases.tsv and be referenced in the Manifest's TableType as “Releases”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersReleaseId	The Feed provider's proprietary identifier of the Release. This is the primary key of the database table for Releases (see Figure 2).	String	M	165DE541A
2	ICPN	An ICPN used as proxy for identification of the Release. Only applicable when the Release is an abstraction of a complete PhysicalProduct. An ICPN comprises 12 or 13 digits, depending whether it is an EAN (13) or a UPC (12).	Multiple String	O	T9000109397
3	ReleaseTitle	The title of the Release.	String	O
4	ReleaseSubTitle	A subtitle of the title, including titles of versions used to differentiate different versions of the same title, as required by the GRid and ISRC ReferenceDescriptiveMetadataSets.	String	O
5	DisplayArtistName	The name to be used by a DSP when presenting Artist details of the Release to a Consumer.	String	O	The Beatles
6	DisplayArtistISNI	The ISNI of the display artist whose name is given in `DisplayArtistName`.	String	O	000000012146438X
7	LabelName	The Name of the Label for the Release.	Multiple String	O
8	ReleaseDate	The date when the Release was first made available, whether for physical or electronic/online distribution.	Multiple ISO Date	O	2020-05-29
9	OriginalDataProviderName	The name of the Party that provided the original data for the Release.	String	O	John Doe
10	OriginalDataProviderDPID	The DPID of the Party that provided the original data for the Release.	DPID	O	PADPIDA2008120501W
11	IsDataProvidedAsReceived	A Flag indicating whether the data for the Release is provided as received from the original provider (=true) or not (=false). This Flag has to be provided if a Party is specified in `OriginalDataProviderName` or `OriginalDataProviderDPID`.	Boolean	C	true

6.13 Proprietary Release Identifiers File

The proprietary release identifiers file shall be called releaseidentifiers.tsv and be referenced in the Manifest's TableType as “ReleaseIdentifiers”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersReleaseProprietaryIdentifierId	The Feed provider's proprietary identifier of the Release's proprietary identifier. This is the primary key of the database table for proprietary Release identifiers (see Figure 2).	String	M	ABC10034
2	FeedProvidersReleaseId	The Feed provider's proprietary identifier of the Release. This is a foreign key to the database table for Releases (see Figure 2).	String	M	165DE823
3	Identifier	The proprietary identifier of the Release.	String	M	XS41218
4	FeedProvidersAllocatingPartyId	The Feed provider's proprietary identifier of the party allocating the proprietary identifier, as used in the Parties file. This is a foreign key to the database table for Parties (see Figure 2).	String	M	132P9863

6.14 Linking Works to Recordings File

The file for linking Works to Recordings shall be called worksrecordings.tsv and be referenced in the Manifest's TableType as “Works-to-Recordings”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersLinkId	The Feed provider's proprietary identifier of the link between a Musical Work and a Recording. This is the primary key of the database table for Work-Recording links (see Figure 2).	String	M	90ERF11
2	FeedProvidersWorkId	The Feed provider's proprietary identifier of the Musical Work that is linked to the Recording. This is a foreign key to the database table for Recordings (see Figure 2).	String	M	165DE541A
3	FeedProvidersRecordingId	The Feed provider's proprietary identifier of the Recording that is linked to the Musical Work. This is a foreign key to the database table for Works (see Figure 2).	String	M	U124X987

6.15 Unclaimed Work Right Share File

The unclaimed right shares file shall be called unclaimedworkrightshares.tsv and be referenced in the Manifest's TableType as “UnclaimedWorkRightShares”. It shall contain none, one or more data Records as follows:

Cell Name		Field Definition	Data Type	M/O/C	Example
1	FeedProvidersRightShareId	The Feed provider's proprietary identifier of the unclaimed Right Share. This is the primary key of the database table for unclaimed Right Shares (see Figure 2).	String	M	K201K66
2	FeedProvidersRecordingId	The Feed provider's proprietary identifier of the Recording relating to the unclaimed Right Share. This is a foreign key to the database table for Recordings (see Figure 2). This cell should be omitted if a `RecordingTitle` and a `DisplayArtistName` are specified, but it should be given if they are not specified.	String	C	U124X987
3	FeedProvidersWorkId	The Feed provider's proprietary identifier of the Musical Work relating to the unclaimed Right Share. This is a foreign key to the database table for Works (see Figure 2).	String	O	165DE541A
4	ISRC	The ISRC of the Recording relating to the unclaimed Right Share.	String	O	USS1Z1412345
5	DspRecordingId	A DSP's proprietary identifier of the Recording relating to the unclaimed Right Share.	String::String	M
6	RecordingTitle	The title of the Recording. This cell is mandatory if no `FeedProvidersRecordingId` is specified, but it should be omitted if a `FeedProvidersRecordingId` is specified.	String	C	I've Got a Feeling
7	RecordingSubTitle	A subtitle of the title, including titles of versions used to differentiate different versions of the same title, as required by the GRid and ISRC ReferenceDescriptiveMetadataSets.	String	O	Naked Version / Remastered 2013
8	AlternativeRecordingTitle	An alternative or parenthetical title of the Recording.	Multiple String	O	I've Got a Feeling (Remastered)
9	DisplayArtistName	The name to be used by a DSP when presenting Artist details of the Recording to a Consumer. This cell is mandatory if no `FeedProvidersRecordingId` is specified, but it should be omitted if a `FeedProvidersRecordingId` is specified.	String	C	The Beatles
10	DisplayArtistISNI	The ISNI of the display artist whose name is given in `DisplayArtistName.`	String	O	000000012146438X
11	Duration	The duration of the Recording.	ISO Duration	O	PT3M20S
12	UnclaimedPercentage	The percentage of the Musical Work that is not claimed to the Feed provider at the time listed in the `FeedCreatedDateTime` specified in the Manifest file. This can be 100, but it cannot be 0. This Cell is mandatory if a `FeedProvidersWorkId` is specified. It shall be omitted otherwise.	Decimal	C	60
13	PercentileForPrioritisation	The percentile that indicates how important the Feed provider considers the provision of a Claim for the Musical Work at hand to be compared to other unclaimed Work Right Shares. It is an integer value that ranges from 0 to 100.	Integer	O	50

Note that while the Unclaimed Work Right Share File can carry a FeedProvidersRecordingId, this data element is optional. This is because the Feed provider may not have allocated such an identifier for a Recording for which they do not have a claim (or claims amounting to less than 100%). This is also the reason why the Unclaimed Work Right Share File contains fields for the metadata about the Recording.

7 Allowed Value Sets

7.1 Introduction

This Clause lists all allowed value sets with their allowed values and definitions that are valid within this standard.

Allowed values are listed, defined and provided in accordance with the DDEX Data Dictionary and the latest version of the DDEX Data Dictionary Standard. To override a DDEX-defined value, some allowed value sets provide the DDEX-defined value “UserDefined”, followed by a single space character and a string representing the term to be communicated. This string shall only comprise lower case letters, upper case letters or digits, e.g. "UserDefined StreamInOnlineGame". Such user-defined values will need to be agreed between Message Sender and Message Recipient and users are encouraged to raise these issues with DDEX with a view to having these values added to the list of DDEX-defined allowed values.

7.2 PartyRole

PartyRole		A creative Role played by a Contributor in relation to a MusicalWork
Allowed Value Set & Allowed Value		Definition
	Adapter	An Author of adapted Lyrics of a MusicalWork. Note: The adapted Lyrics may or may not result in a new copyright Creation.
	Arranger	A modifier of musical components of a Work. Note: The arranged MusicalWork may or may not result in a new copyright Creation.
	Composer	A Creator of the musical elements of a MusicalWork.
	ComposerLyricist	A Creator that plays the roles of Composer and Lyricist of a MusicalWork.
	Creator	A Maker of a Creation.
	Lyricist	A Creator of the Lyrics of a MusicalWork.
	MusicPublisher	A Party that enters into contracts and/or assignments with composer(s) in respect of their copyright MusicalWorks and in return for a proportion of the royalties generated from their use, undertakes work on behalf of the composer(s) including but not limited to promoting the usage of the Works, licensing their use, collecting and distributing royalties and developing writing partnerships with other composer(s). This term includes OriginalPublisher and SubPublisher.
	OriginalPublisher	A RightsController who is assigned rights directly by the writer (as opposed to by another publisher). Note that a writer may have zero, one or many OriginalPublishers.
	RightsAdministrator	A Party that administers Rights on behalf of one or more RightsControllers.
	SubArranger	A Creator of arrangements made on behalf of a SubPublisher.
	SubLyricist	A Creator who substitutes or modifies the existing Lyrics of a MusicalWork.
	SubPublisher	A Party which has acquired, by Agreement with a MusicPublisher, Rights in one or more MusicalWorks for a specified Territory and Period. Note: This includes Rights which are passed to subsidiaries or affiliates of a larger Organization.
	SubstitutedPublisher	A Party acting on behalf of a MusicPublisher or other controller of Rights in a MusicalWork.
	Translator	A Party that translates Lyrics and/or Text from one Language into another. This is also known as sub-Lyricist.

7.3 RightsType

RightsType		A Type of Right
Allowed Value Set & Allowed Value		Definition
	MechanicalRight	The Right to record and distribute a Work on a Carrier.
	PerformingRight	The Right to perform a Work. This is, to present a Work by action such as playing, reciting, singing, or projecting to the public in their presence.
	PrintRight	The Right to make a visual copy of a Work (and distribute it).
	SynchronizationRight	The Right to include and combine a Work either completely or in parts in timed relation with Works of other types for the making of an audio-visual or multimedia Creation or a database.

7.4 RightShareType

RightsShareType		A Type of RightShare
Allowed Value Set & Allowed Value		Definition
	LicensingShare	A RightShare which entitles a Party to issue Licenses for a Work.
	MusicalWorkManuscriptShare	A RightShare of a MusicalWork as agreed between the writers. The sum of all MusicalWorkManuscriptShares on a MusicalWork equals 100%. It is possible (though unusual) for MusicalWorkManuscriptShares to vary by Territory or Rights Type. Manuscript Shares are often referred to as Writer Shares.
	MusicalWorkCollectionShare	A RightShare as calculated for the collection of money for RightShares.

7.5 TerritoryCode

For a list of ISO Territory Codes please visit https://www.iso.org/obp/ui/#search (DDEX uses the two-letter alphabetic codes for current territories and four-letter codes for former territories). DDEX adds one code “Worldwide” defined as “An Identifier which identifies all Territories in the world”.

TerritoryCode		A code representing a Territory. This includes ISO 3166-1 two-letter codes, plus a code for Worldwide.
Allowed Value Set & Allowed Value		Definition
	AD	Andorra (Source:ISO 3166-1).
	AE	The United Arab Emirates (Source:ISO 3166-1).
	AF	Afghanistan (Source:ISO 3166-1).
	AG	Antigua and Barbuda (Source:ISO 3166-1).
	AI	Anguilla (Source:ISO 3166-1).
	AL	Albania (Source:ISO 3166-1).
	AM	Armenia (Source:ISO 3166-1).
	AN	Netherlands Antilles (Source:ISO 3166-1). This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	AO	Angola (Source:ISO 3166-1).
	AQ	Antarctica (Source:ISO 3166-1).
	AR	Argentina (Source:ISO 3166-1).
	AS	American Samoa (Source:ISO 3166-1).
	AT	Austria (Source:ISO 3166-1).
	AU	Australia (Source:ISO 3166-1).
	AW	Aruba (Source:ISO 3166-1).
	AX	Åland Islands (Source:ISO 3166-1).
	AZ	Azerbaijan (Source:ISO 3166-1).
	BA	Bosnia and Herzegovina (Source:ISO 3166-1).
	BB	Barbados (Source:ISO 3166-1).
	BD	Bangladesh (Source:ISO 3166-1).
	BE	Belgium (Source:ISO 3166-1).
	BF	Burkina Faso (Source:ISO 3166-1).
	BG	Bulgaria (Source:ISO 3166-1).
	BH	Bahrain (Source:ISO 3166-1).
	BI	Burundi (Source:ISO 3166-1).
	BJ	Benin (Source:ISO 3166-1).
	BL	Saint Barthélemy (Source:ISO 3166-1).
	BM	Bermuda (Source:ISO 3166-1).
	BN	Brunei (Source:ISO 3166-1).
	BO	Bolivia (Source:ISO 3166-1).
	BQ	Bonaire, Sint Eustatius and Saba (Source:ISO 3166-1).
	BR	Brazil (Source:ISO 3166-1).
	BS	The Bahamas (Source:ISO 3166-1).
	BT	Bhutan (Source:ISO 3166-1).
	BV	Bouvet Island (Source:ISO 3166-1).
	BW	Botswana (Source:ISO 3166-1).
	BY	Belarus (Source:ISO 3166-1).
	BZ	Belize (Source:ISO 3166-1).
	CA	Canada (Source:ISO 3166-1).
	CC	Cocos Islands (Source:ISO 3166-1).
	CD	The Democratic Republic of the Congo (Source:ISO 3166-1).
	CF	The Central African Republic (Source:ISO 3166-1).
	CG	The Congo (Source:ISO 3166-1).
	CH	Switzerland (Source:ISO 3166-1).
	CI	Côte d'Ivoire (Source:ISO 3166-1).
	CK	Cook Islands (Source:ISO 3166-1).
	CL	Chile (Source:ISO 3166-1).
	CM	Cameroon (Source:ISO 3166-1).
	CN	China (Source:ISO 3166-1).
	CO	Colombia (Source:ISO 3166-1).
	CR	Costa Rica (Source:ISO 3166-1).
	CS	Czechslovakia (until 1993) or Serbia and Montenegro (2003-2006) (Source:ISO 3166-1). This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	CU	Cuba (Source:ISO 3166-1).
	CV	Cape Verde (Source:ISO 3166-1).
	CW	Curaçao (Source:ISO 3166-1).
	CX	Christmas Island (Source:ISO 3166-1).
	CY	Cyprus (Source:ISO 3166-1).
	CZ	Czechia (Source:ISO 3166-1).
	DE	Germany (Source:ISO 3166-1).
	DJ	Djibouti (Source:ISO 3166-1).
	DK	Denmark (Source:ISO 3166-1).
	DM	Dominica (Source:ISO 3166-1).
	DO	The Dominican Republic (Source:ISO 3166-1).
	DZ	Algeria (Source:ISO 3166-1).
	EC	Ecuador (Source:ISO 3166-1).
	EE	Estonia (Source:ISO 3166-1).
	EG	Egypt (Source:ISO 3166-1).
	EH	Western Sahara (Source:ISO 3166-1).
	ER	Eritrea (Source:ISO 3166-1).
	ES	Spain (Source:ISO 3166-1).
	ES-CE	Ceuta, Spain (Source:ISO 3166-2).
	ES-CN	Canary Islands, Spain (Source:ISO 3166-2).
	ES-ML	ES-ML Melilla, Spain (Source:ISO 3166-2).
	ET	Ethiopia (Source:ISO 3166-1).
	FI	Finland (Source:ISO 3166-1).
	FJ	Fiji (Source:ISO 3166-1).
	FK	Falkland Islands (Source:ISO 3166-1).
	FM	Micronesia (Source:ISO 3166-1).
	FO	Faroe Islands (Source:ISO 3166-1).
	FR	France (Source:ISO 3166-1).
	GA	Gabon (Source:ISO 3166-1).
	GB	The United Kingdom (Source:ISO 3166-1).
	GD	Grenada (Source:ISO 3166-1).
	GE	Georgia (Source:ISO 3166-1).
	GF	French Guiana (Source:ISO 3166-1).
	GG	Guernsey (Source:ISO 3166-1).
	GH	Ghana (Source:ISO 3166-1).
	GI	Gibraltar (Source:ISO 3166-1).
	GL	Greenland (Source:ISO 3166-1).
	GM	The Gambia (Source:ISO 3166-1).
	GN	Guinea (Source:ISO 3166-1).
	GP	Guadeloupe (Source:ISO 3166-1).
	GQ	Equatorial Guinea (Source:ISO 3166-1).
	GR	Greece (Source:ISO 3166-1).
	GS	South Georgia and The South Sandwich Islands (Source:ISO 3166-1).
	GT	Guatemala (Source:ISO 3166-1).
	GU	Guam (Source:ISO 3166-1).
	GW	Guinea-Bissau (Source:ISO 3166-1).
	GY	Guyana (Source:ISO 3166-1).
	HK	Hong Kong (Source:ISO 3166-1).
	HM	Heard Island and McDonald Islands (Source:ISO 3166-1).
	HN	Honduras (Source:ISO 3166-1).
	HR	Croatia (Source:ISO 3166-1).
	HT	Haiti (Source:ISO 3166-1).
	HU	Hungary (Source:ISO 3166-1).
	ID	Indonesia (Source:ISO 3166-1).
	IE	Ireland (Source:ISO 3166-1).
	IL	Israel (Source:ISO 3166-1).
	IM	Isle of Man (Source:ISO 3166-1).
	IN	India (Source:ISO 3166-1).
	IO	The British Indian Ocean Territory (Source:ISO 3166-1).
	IQ	Iraq (Source:ISO 3166-1).
	IR	Iran (Source:ISO 3166-1).
	IS	Iceland (Source:ISO 3166-1).
	IT	Italy (Source:ISO 3166-1).
	JE	Jersey (Source:ISO 3166-1).
	JM	Jamaica (Source:ISO 3166-1).
	JO	Jordan (Source:ISO 3166-1).
	JP	Japan (Source:ISO 3166-1).
	KE	Kenya (Source:ISO 3166-1).
	KG	Kyrgyzstan (Source:ISO 3166-1).
	KH	Cambodia (Source:ISO 3166-1).
	KI	Kiribati (Source:ISO 3166-1).
	KM	The Comoros (Source:ISO 3166-1).
	KN	Saint Kitts and Nevis (Source:ISO 3166-1).
	KP	The Democratic People's Republic of Korea (Source:ISO 3166-1).
	KR	The Republic of Korea (Source:ISO 3166-1).
	KW	Kuwait (Source:ISO 3166-1).
	KY	Cayman Islands (Source:ISO 3166-1).
	KZ	Kazakhstan (Source:ISO 3166-1).
	LA	Laos (Source:ISO 3166-1).
	LB	Lebanon (Source:ISO 3166-1).
	LC	Saint Lucia (Source:ISO 3166-1).
	LI	Liechtenstein (Source:ISO 3166-1).
	LK	Sri Lanka (Source:ISO 3166-1).
	LR	Liberia (Source:ISO 3166-1).
	LS	Lesotho (Source:ISO 3166-1).
	LT	Lithuania (Source:ISO 3166-1).
	LU	Luxembourg (Source:ISO 3166-1).
	LV	Latvia (Source:ISO 3166-1).
	LY	Libya (Source:ISO 3166-1).
	MA	Morocco (Source:ISO 3166-1).
	MC	Monaco (Source:ISO 3166-1).
	MD	Moldova (Source:ISO 3166-1).
	ME	Montenegro (Source:ISO 3166-1).
	MF	Saint Martin (Source:ISO 3166-1).
	MG	Madagascar (Source:ISO 3166-1).
	MH	The Marshall Islands (Source:ISO 3166-1).
	MK	Macedonia (Source:ISO 3166-1).
	ML	Mali (Source:ISO 3166-1).
	MM	Myanmar (Source:ISO 3166-1).
	MN	Mongolia (Source:ISO 3166-1).
	MO	Macao (Source:ISO 3166-1).
	MP	Northern Mariana Islands (Source:ISO 3166-1).
	MQ	Martinique (Source:ISO 3166-1).
	MR	Mauritania (Source:ISO 3166-1).
	MS	Montserrat (Source:ISO 3166-1).
	MT	Malta (Source:ISO 3166-1).
	MU	Mauritius (Source:ISO 3166-1).
	MV	Maldives (Source:ISO 3166-1).
	MW	Malawi (Source:ISO 3166-1).
	MX	Mexico (Source:ISO 3166-1).
	MY	Malaysia (Source:ISO 3166-1).
	MZ	Mozambique (Source:ISO 3166-1).
	NA	Namibia (Source:ISO 3166-1).
	NC	New Caledonia (Source:ISO 3166-1).
	NE	The Niger (Source:ISO 3166-1).
	NF	Norfolk Island (Source:ISO 3166-1).
	NG	Nigeria (Source:ISO 3166-1).
	NI	Nicaragua (Source:ISO 3166-1).
	NL	The Netherlands (Source:ISO 3166-1).
	NO	Norway (Source:ISO 3166-1).
	NP	Nepal (Source:ISO 3166-1).
	NR	Nauru (Source:ISO 3166-1).
	NU	Niue (Source:ISO 3166-1).
	NZ	New Zealand (Source:ISO 3166-1).
	OM	Oman (Source:ISO 3166-1).
	PA	Panama (Source:ISO 3166-1).
	PE	Peru (Source:ISO 3166-1).
	PF	French Polynesia (Source:ISO 3166-1).
	PG	Papua New Guinea (Source:ISO 3166-1).
	PH	The Philippines (Source:ISO 3166-1).
	PK	Pakistan (Source:ISO 3166-1).
	PL	Poland (Source:ISO 3166-1).
	PM	Saint Pierre and Miquelon (Source:ISO 3166-1).
	PN	Pitcairn (Source:ISO 3166-1).
	PR	Puerto Rico (Source:ISO 3166-1).
	PS	The Occupied Palestinian Territory (Source:ISO 3166-1).
	PT	Portugal (Source:ISO 3166-1).
	PW	Palau (Source:ISO 3166-1).
	PY	Paraguay (Source:ISO 3166-1).
	QA	Qatar (Source:ISO 3166-1).
	RE	Réunion (Source:ISO 3166-1).
	RO	Romania (Source:ISO 3166-1).
	RS	Serbia (Source:ISO 3166-1).
	RU	Russia (Source:ISO 3166-1).
	RW	Rwanda (Source:ISO 3166-1).
	SA	Saudi Arabia (Source:ISO 3166-1).
	SB	Solomon Islands (Source:ISO 3166-1).
	SC	Seychelles (Source:ISO 3166-1).
	SD	The Sudan (Source:ISO 3166-1).
	SE	Sweden (Source:ISO 3166-1).
	SG	Singapore (Source:ISO 3166-1).
	SH	Saint Helena (Source:ISO 3166-1).
	SI	Slovenia (Source:ISO 3166-1).
	SJ	Svalbard and Jan Mayen (Source:ISO 3166-1).
	SK	Slovakia (Source:ISO 3166-1).
	SL	Sierra Leone (Source:ISO 3166-1).
	SM	San Marino (Source:ISO 3166-1).
	SN	Senegal (Source:ISO 3166-1).
	SO	Somalia (Source:ISO 3166-1).
	SR	Suriname (Source:ISO 3166-1).
	SS	South Soudan (Source:ISO 3166-1).
	ST	Sao Tome and Principe (Source:ISO 3166-1).
	SV	El Salvador (Source:ISO 3166-1).
	SX	Sint Maarten (Source:ISO 3166-1).
	SY	Syria (Source:ISO 3166-1).
	SZ	Eswatini (Source:ISO 3166-1).
	TC	Turks and Caicos Islands (Source:ISO 3166-1).
	TD	Chad (Source:ISO 3166-1).
	TF	The French Southern Territories (Source:ISO 3166-1).
	TG	Togo (Source:ISO 3166-1).
	TH	Thailand (Source:ISO 3166-1).
	TJ	Tajikistan (Source:ISO 3166-1).
	TK	Tokelau (Source:ISO 3166-1).
	TL	Timor-Leste (Source:ISO 3166-1).
	TM	Turkmenistan (Source:ISO 3166-1).
	TN	Tunisia (Source:ISO 3166-1).
	TO	Tonga (Source:ISO 3166-1).
	TR	Turkey (Source:ISO 3166-1).
	TT	Trinidad and Tobago (Source:ISO 3166-1).
	TV	Tuvalu (Source:ISO 3166-1).
	TW	Taiwan (Source:ISO 3166-1).
	TZ	Tanzania (Source:ISO 3166-1).
	UA	Ukraine (Source:ISO 3166-1).
	UG	Uganda (Source:ISO 3166-1).
	UM	United States Minor Outlying Islands (Source:ISO 3166-1).
	US	The United States (Source:ISO 3166-1).
	UY	Uruguay (Source:ISO 3166-1).
	UZ	Uzbekistan (Source:ISO 3166-1).
	VA	The Holy See (Source:ISO 3166-1).
	VC	Saint Vincent and The Grenadines (Source:ISO 3166-1).
	VE	Venezuela (Source:ISO 3166-1).
	VG	British Virgin Islands (Source:ISO 3166-1).
	VI	US Virgin Islands (Source:ISO 3166-1).
	VN	Viet Nam (Source:ISO 3166-1).
	VU	Vanuatu (Source:ISO 3166-1).
	WF	Wallis and Futuna (Source:ISO 3166-1).
	WS	Samoa (Source:ISO 3166-1).
	YE	Yemen (Source:ISO 3166-1).
	YT	Mayotte (Source:ISO 3166-1).
	ZA	South Africa (Source:ISO 3166-1).
	ZM	Zambia (Source:ISO 3166-1).
	ZW	Zimbabwe (Source:ISO 3166-1).
	Worldwide	An Identifier which identifies all Territories in the world.

7.6 TitleType

TitleType		A Type of Title
Allowed Value Set & Allowed Value		Definition
	AbbreviatedDisplayTitle	A shortened version of the DisplayTitle which may be used for devices that have limited display capability.
	AlternativeTitle	An alternative to a primary Title, e.g. a ReferenceTitle or a DisplayTitle. Example: a song may become well known or 'also known as (a.k.a.)' by its first line or a line from its chorus: 'Don't Stop Me Now' performed by Queen may have an AlternativeTitle 'Having A Good Time' or, 'I will always love you' performed by Whitney Houston may have an AlternativeTitle of 'Theme from Bodyguard'.
	DisplayTitle	A Title expressed by the RightsController as to how a Title should be displayed for presentation to the Consumer.
	FirstLineOfText	A Title which consists of the first line of the text of which it is a Title.
	FormalTitle	A Title structured according to a naming convention. In many cases, a FormalTitle will be communicated together with a GroupingTitle. Example: This is often used for classical works. The 1st movement of Vivaldi's Spring concerto may have a FormalTitle of 'Concerto No. 1 in E major, Op. 8, RV 269, 'Spring' (La primavera), 1. Allegro (in E major)'.
	GroupingTitle	A Title given to a grouping of Creations. This is often used for classical works to indicate the parent work to the one being described. In many cases, a GroupingTitle will be communicated together with a FormalTitle. Example: When describing the 1st movement of Vivaldi's Spring concerto, a suitable GroupingTitle would be its FormalTitle without the last part. 'Concerto No. 1 in E major, Op. 8, RV 269, 'Spring' (La primavera)'.
	IncorrectTitle	A Title by which a Creation is often incorrectly known.
	MisspelledTitle	A Title that contains common typographic errors.
	OriginalTitle	A Title given to a Creation by its Creator(s), in its original Language. Note: A Creation may be given more than one OriginalTitle. Note: The OriginalTitle of a Creation X may be the DisplayTitle of a Creation that X is based on. Example: the OriginalTitle of the MusicalWork 'My Way' (whose lyrics were written by Paul Anka) is 'Comme d'habitude' (written and composed by Claude François).
	SearchTitle	A Title created to aid database searching (for example, where special characters, puns, or slang have been replaced by standardized elements).
	SortingTitle	A Title which has been arranged such that it can be used for alphabetic sorting.
	TitleAsPart	A Title of a Creation as Part of another Creation.
	TitleWithoutPunctuation	A Title from which all initial articles and punctuation have been removed.
	TranslatedTitle	A translation into a different Language of the value contained in an OriginalTitle Element. Note: this is not the same as the OriginalTitle of a translation of a Creation, though the two will often be represented by the same text string. Example: the TranslatedTitle of 'Le Nozze di Figaro' is 'The Marriage Of Figaro'.
	Unknown	A Type of an Entity used when a sender of a DdexMessage wishes to indicate that the value within the allowed value set is unknown.
	UserDefined	A Type of an Entity which is defined by a sender of a DdexMessage in a manner acceptable to its recipient.

7.7 UseType

UseType		A Type of a nature of a Service, or a Release, as used by a Consumer.
Allowed Value Set & Allowed Value		Definition
	AsPerContract	A Type of an Entity used when a MessageSender wishes to indicate that the value within the allowed value set is defined by the contractual relationship between MessageSender and MessageRecipient.
	Broadcast	To Deliver a Resource using radio waves on the radio frequency portion of the electromagnetic spectrum. This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	ConditionalDownload	To Download under a condition (e.g. tethered to a service or device).
	ContentInfluencedStream	To Stream where the only interactivity provided allows the Consumer to start, stop, pause, fast forward and rewind the Stream, and where there is limited flexibility to influence the content of the Stream.
	Display	To display a Resource on a device where it will disappear when the device is switched off. This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	Download	To transfer a Release from a Service's Computer to a Consumer's Computer for later consumption. This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	DubForAdvertisement	To reproduce an audio Resource in the creation of the soundtrack of an audio or audiovisual Advertisement. Note: this use does not include the public performance of the included Resource.
	DubForLivePerformance	To reproduce a Resource to enable a live Performance event. Note: this includes dramatic performances, dance shows and fashion exhibitions.
	DubForMovies	To reproduce an audio Resource in the creation of a soundtrack of an audiovisual Work. Note: this use does not include the public performance of the included Resource.
	DubForMusicOnHold	To reproduce an audio Resource in the creation of a music on hold system. Note: this use does not include the public performance of the included Resource.
	DubForPublicPerformance	To reproduce an audio Resource to enable a public Performance. Note: this use does not include the public performance of the included Resource.
	DubForRadio	To reproduce an audio Resource to enable any form of radio transmission. Note: this use does not include the public performance of the included Resource.
	DubForTV	To reproduce an audio Resource to enable any form of television transmission. Note: this use does not include the public performance of the included Resource.
	ExtractForInternet	To reproduce and perform an excerpt from a Resource in an on demand internet service.
	KioskDownload	To Download directly from a Kiosk to a consumer device. This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	Narrowcast	To Deliver a Resource to a specific list of recipients, by terrestrial or satellite transmission. This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	NonInteractiveStream	To Stream a Release as part of a scheduled program that has been a-priori arranged. Consumers cannot directly influence the content or order of a NonInteractiveStream. NonInteractiveStreams are often referred to as web casts or pre-programmed Streams.
	OnDemandStream	To Stream a Release with full interactivity.
	PerformAsMusicOnHold	To Perform a Resource in a music on hold service.
	PerformInLivePerformance	To Perform a Resource as part of a live Performance event. Note: this includes dramatic performances, dance shows and fashion exhibitions.
	PerformInPublic	To Perform publicly. This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	PermanentDownload	To Download for permanent storage and subsequent consumption by the Consumer.
	Playback	To play a Resource in a Release as an analogue signal for listening and/or viewing by an individual or small group.
	PlayInPublic	To play a Resource in a Release publicly. This UseType is typically used when reporting such usages to rights holders.
	Podcast	To Deliver a series of Resources as a download via web syndication.
	Print	To Copy a Resource on paper or an another permanent Medium where it can be seen. This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	PrivateCopy	To Copy a Resource for private use. This UseType is typically used when reporting revenues related to private copying levies.
	ProgrammedContentStream	To Stream a Resource whose content has been pre-programmed, usually by the DSP.
	PurchaseAsPhysicalProduct	To purchase a PhysicalProduct.
	Rent	To allow access to a Release for a limited Period of Time.
	Simulcast	To Stream simultaneously over two or more different media systems or channels. This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	Stream	To stream a Resource.
	TetheredDownload	To Download to a tethered download host (a device which must be connected to a DSP's service through a broadband connection whenever a downloaded Resource is played).
	TimeInfluencedStream	To Stream where the only interactivity provided allows the Consumer to start, stop, pause, fast forward and rewind the Stream.
	Unknown	A Type of an Entity used when a sender of a DdexMessage wishes to indicate that the value within the allowed value set is unknown.
	UseAsAlertTone	To use a Resource in a Release as an alert primarily on a MobileTelephone for an event other than an incoming phone call. Examples: an incoming text message or a new voice mail.
	UseAsDevice	To Use a Resource in a Release that has been provided to a Consumer as part of a hardware purchase.
	UseAsKaraoke	The use of a Release for a form of entertainment in which an amateur singer or singers sing along with recorded music on microphone.
	UseAsRingbackTone	To Use a Resource in a Release as the audible ringing that is heard primarily on a MobileTelephone by the calling party after dialing and prior to the call being answered at the receiving end.
	UseAsRingbackTune	To Use a Resource in a Release as ringbacktune.
	UseAsRingtone	To Use a Resource in a Release as an alert for an incoming phone call primarily on a MobileTelephone.
	UseAsRingtune	To Use a Resource in a Release as ringtune. This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.
	UseAsScreensaver	To use a Resource in a Release as a screen saver for an idling device.
	UseAsVoiceMail	To Use a Resource as a voice greeting that contains an audio master clip in the background. Such a greeting can be used for outgoing and/or incoming voicemails.
	UseAsWallpaper	[missing definition]
	UseForIdentification	To use a Resource in a Release to aid identification processes (e.g. to support rights management operations). For the avoidance of doubt: this UseType does not include making the Release available to Consumers.
	UseInMobilePhoneMessaging	To reproduce and perform a Resource in a phone messaging system.
	UseInPhoneListening	To reproduce and perform a Resource in a service for phone based listening.
	UserDefined	A Type of an Entity which is defined by a sender of a DdexMessage in a manner acceptable to its recipient.
	UserMakeAvailableLabelProvided	A UseType in which Consumers use a Release as part of their own Creation (e.g. a web site) only when the Release is provided by the ReleaseCreator to the service provider (e.g. the web site hosting company) and where the ReleaseCreator has stipulated to the service provider the ways in which the Release may be used by Consumers and these stipulations are conveyed to Consumers.
	UserMakeAvailableUserProvided	A UseType in which Consumers use a Release as part of their own Creation (e.g. a web site) when the Release is not provided by the ReleaseCreator to the service provider (e.g. the web site hosting company) but by the Consumer or by other Consumers making the Release available through the service provider.
	Webcast	To Deliver a Resource over the Internet using streaming technology. This allowed value is deprecated. DDEX advises that this value will be removed at a future date and therefore recommends against using it.

Annex A (informative) Release Notes

Click here to expand...

Version 1.0.1 corrects a bug in the Unclaimed Work Right Share File where the cardinality of Cell 12 has been changed from mandatory to conditional to cater for cases where no FeedProvidersWorkId has been provided.

Evaluation Licence for DDEX Standards

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

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

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

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

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

Bulk Communication of Work and Recording Metadata

This section of the DDEX Knowledge Base contains Version 1.0.1 of the Standard for the Bulk Communication of Work and Recording Metadata.

2 Scope

3 Normative References

4 Terms and Abbreviations

Cell

Delimiter

Manifest

Musical Work

Record

Secondary Delimiter

Right Share

5 Choreographies

6.2.2.1 Record Delimiter

6.2.2.2 Primary (Cell) Delimiter

6.2.2.3 Secondary Delimiter

6.2.2.4 Namespace Delimiter

6.2.2.5 Spaces and Delimiters

6.2.2.6 Communicating Delimiters

7 Allowed Value Sets

Evaluation Licence for DDEX Standards

8 Child Pages