- Created by DDEX Secretariat, last modified on 2020-05-19
This section of the DDEX Knowledge Base contains Version 2.2 of the Release Profiles for Common Release Types for ERN 4.2.
Download Standard (PDF)
General Index
The general index contains all terms used in the latest AVS (Version 4) as well as all terms from RIN 2.0, MEAD 1.1, PIE 1.0 and RDR-N 1.5. Other standards will be added over time. Clicking on an entry in the general index will take you to the relevant edition of the DDEX Data Dictionary.
Message Editions
... for the Electronic Release Notification (ERN 4.3)
... for Recording Information Notification (RIN 2.0)
... for Media Enrichment and Description (MEAD 1.1)
... for Party Identification and Enrichment (PIE 1.0)
... for the Recording Data and Rights Notification Standard (RDR-N, Version 1.5).
Allowed Value Set Editions
... for the Allowed Value Sets (Version 4)
... for the Allowed Value Sets (Version 3)
... for the Allowed Value Sets (Version 2)
... for the Allowed Value Sets (Version 1)
Data Dictionary editions published before 2022
... for the Recording Data and Rights Choreography Standard (RDR-C, Version 1.0): Message Structure and AVSs
... for the US Letters of Direction Choreography Standard (LoD, Version 1.0): Message Structure and AVSs
... for the Electronic Release Notification Message Suite Standard (ERN, Version 4.2): Message Structure and AVSs
... for the US Musical Work Licensing Choreography Standard (MWL, Version 1.0): Message Structure and AVSs
... for the Standard for the Communication of Media Enrichment and Description Information (MEAD): Message Structure and AVSs
... for the Musical Work Right Share Notification Choreography Standard (MWN, Version 1.1)
... for the Standard for communicating links between Resources and Musical Works (Version 1.1)
... for the Recording Data and Rights Standard (Version 1.4)
... for Release Deliveries using SFTP or Web Service (Version 1.7)
... for the Recording Information Notification (Version 1.1)
Older versions of this standard can be accessed here.
1 Introduction
Such descriptions can, however, vary between different uses. For instance, the description of a Release that contains a single video ringtone track would differ greatly from the description of a Release representing a digital equivalent of a 10-track pop album with previews.
In order to aid companies that only wish to communicate a small subset of the types of products that the “full” DDEX standards allow, DDEX has developed a series of “profiles”. This standard defines a set of profiles that define how to use Version 4 of the Electronic Release Notification Message Suite Standard to express the most common types of Releases.
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.
2 Scope
This document also contains information on how to determine to what extent software is conformant to this standard in the form of conformance weightings. This information is provided as shown below and needs to be read in conjunction with the relevant DDEX Conformance Standard (see Section 3).
Conformance Weighting: ...
Complete and valid sample XML files supporting these Release Profiles are available for download from http://kb.ddex.net.
The fifth clause defines a number of Release Profiles, including their variants and how they are to be communicated in a NewReleaseMessage
.
Annex A provides a link to a set of sample messages.
Version 2.1 updated the requirements for the identification of TrackReleases. Version 2.1 has been designed to work with ERN Version 4.1.
Version 2.2 adds support for Audio Books and Audio Dramas and updates the DjMix Profiles by adding the ability to send TrackReleases. Version 2.1 has been designed to work with ERN Version 4.2.
3 Normative References
- Digital Data Exchange (DDEX): Electronic Release Notification Message Suite Standard, Version 4 (or later)
- Digital Data Exchange (DDEX): ERN Conformance Standard. Version 1.0
Note: the provisions within this standard are specific to the above-mentioned standard. However, users of older versions of the baseline standards are encouraged to still follow the rules defined herein wherever technically and practically possible as the provisions within this profile standard are accepted best practice for the communication of Release information.
Users should take special notice of the definitions, abbreviations and conformance rules used/defined in these standards, which also apply to this standard.
4 Nomenclature
Primary Resource
A Resource that is a main Resource of a Release. A change in a Primary Resource typically requires a new Release Identifier, whereas change in a Secondary Resource does not.
All Resources that are referenced in aReleaseResourceReference
composite in a NewReleaseMessage
are Primary Resources for that Release.
Release
A Release is an abstract entity representing a bundle of one or more Resources compiled by an Issuer. The Resources in Releases are normally primarily sound recordings or music audio-visual recordings, but this is not invariably the case. The Release is not itself the item of trade (or “Product”). Products have more extensive attributes than Releases; one Release may be disseminated in many different Products.
Release Creator
Release Creator is an organisation which is the owner of copyrights in sound and/or music audiovisual recordings and/or exclusive licensees of copyrights in sound and/or music audiovisual recordings.
Main Release
A Release, communicated in a Release notification that represents the main purpose for sending the NewReleaseMessage
. When communicating an album, the Main Release would be said Album Release. A typical NewReleaseMessage
contains, besides the Main Release, one or more Track Releases.
Track Release
A Release, communicated in a Release notification that does not represent the main purpose for sending the NewReleaseMessage
. When communicating a 10-track album, a typical NewReleaseMessage
would contain, besides the Main Release, ten Track Releases (i.e. one for each sound recording that together make up the album).
Secondary Resource
A Resource that is not a main Resource of a Release. It supports the Primary Resources (examples are lyrics, cover art etc). A change in a Primary Resource typically requires a new Release Identifier, whereas change in a Secondary Resource does not.
All Resources that are referenced in aLinkedReleaseResourceReference
composite in a NewReleaseMessage
are Secondary Resources for that Release.
- “0-1” means that at most one (i.e. either none or one) element has to be included in the relevant Profile;
- “0-n” means that any number (i.e. either none, one or more) of elements may be included in the relevant Profile; and
- “1-n” means that at least one element has to be included in the relevant Profile.
The term “mandatory” encompasses the two cardinality expressions “1” and “1-n”. The term “optional” encompasses the two cardinality expressions “0-1” and “0-n”.
5 Release Profiles
The Release Profiles defined in this Standard is a subset of the descriptions for Releases, including their components and the order/grouping of such resources that can be expressed with the NewReleaseMessage
defined in the Electronic Release Notification Message Suite Standard. A Release Profile comprises of exactly one Basic Release Profile combined with none, one or more Profile Variants.
Regardless of the Profile, a NewReleaseMessage
needs to contain exactly one Main Release.
Conformance Weighting: 1
(See the ERN Conformance Standard for details.)
A NewReleaseMessage
needs to contain none, one, or many Track Releases as defined in Clause 5.1.2 (Basic Release Profiles and Profile Variants) below.
Conformance Weighting: 1
Where Clause 5.1.2 (Basic Release Profiles and Profile Variants) indicates that Track Releases(s) need to be provided, the NewReleaseMessage
must contain exactly one TrackRelease
composite in accordance with Clause 5.6 (Track Release) for each Primary Resource referenced in the Main Release, regardless of whether there are any deals available for the TrackRelease
.
Conformance Weighting: 1
the Profile-specific rules set out or referenced in Clause 5.1.2 (Basic Release Profiles and Profile Variants) below, the NewReleaseMessage
shall conform to the common rules defined in Clause 5.3 (Rules for all Profiles) and rules on signalling the profile as defined in Clause 5.2 (Signalling a Specific Release Profile).
Conformance Weighting: 1
Basic Release Profiles | Profile ID1 | Releases to be included in a NewReleaseMessage 1 | Possible Variants (see Clause 5.5) | |||||
---|---|---|---|---|---|---|---|---|
Name & Description | Main Release | Track Release | ||||||
1. Audio A Release containing one or more sound recordings, accompanied by a representational image. This profile can be used to communicate audio singles, albums and EPs which differ only in the total length of the Release. |
| 1
| Yes |
| ||||
2. Video A Release containing one or more video resources, accompanied by a representational image. This profile can be used to communicate video singles as well as video albums which differ only in the total length of the Release. | Video
| 1
| Yes |
| ||||
3. Mixed Media A Release with a mixture of sound recording and video resource and, potentially, images and text, plus supporting screen captures for each video resource and a single cover image. This profile can be used to communicate multimedia singles as well as multimedia albums which differ only in the total length of the Release. | MixedMedia
| 1
| Yes |
| ||||
4. Simple Audio Single A Release with one Primary Resource of type This profile is usually used for streaming services and may be accompanied with a cover art image. | Simple AudioSingle | 1
| No | |||||
5. Simple Video Single A Release with one Primary Resource of type This profile is usually used for streaming services and may be accompanied by a cover art image. | Simple VideoSingle | 1
| No | |||||
6. Ringtone A Release made up of a single audio mobile ringtone clip using a | Ringtone | 1
| No | |||||
7. Long-form Musical Work Video, TV or Film Release A Release containing either a multi-chapter long form video recording or, individual films and film bundles (including TV episodes, series and seasons), plus a supporting cover image and potentially a screen capture per chapter. Long-form Musical Work Video Releases typically contain cue sheets. | LongForm Musical WorkVideo | 1 Release composite in accordance with Clauses 5.2 (Signalling a Specific Release Profile) and 5.3 (Rules for all Profiles) and 5.4.3 (Longform Videos) containing
| No | |||||
8. DjMix A music Release comprising at least one sound recording as the Primary Resource (the mix) plus a cover image. The mix is made up from a series of Secondary sound recording Resources that are not directly referenced from the Release. | DjMix | 1
| Yes | |||||
9. Audio Drama or Book A Release comprising at least one SoundRecording containing one or more Recordings of a book being read or, alternatively, a documentary, comedy, panel show, dramatised performance of a story, etc. | AudioDramaOrBook | 1
| Yes | none |
1) Please note that Profile IDs do not contain any white-space characters. Spaces/new-line characters in the Profile ID column are solely to keep the table as narrow as possible. The same applies to ResourceType names used in the table.
- The table below shows which
ReleaseTypes
may be used in which profile. Other combinations are not encouraged. <No Conformance Weighting> - Notwithstanding the above, the value
UserDefined
may always be communicated. <No Conformance Weighting> - It is permitted to communicate more than one
ReleaseType
for a Release as long as allReleaseType
s are marked as valid in the table below. <No Conformance Weighting>
Profile ReleaseType | Audio | Video | Mixed Media | Simple Audio | Simple Video | Ringtone | Long-form Musical Work Video, TV or Film Release | DjMix | |
---|---|---|---|---|---|---|---|---|---|
1 | Album | X | X | X | |||||
2 | AlertToneRelease | X | |||||||
3 | Bundle | X | X | X | |||||
4 | ClassicalAlbum | X | X | X | |||||
5 | ClassicalDigitalBoxedSet | X | X | X | |||||
6 | ClassicalMultimediaAlbum | X | |||||||
7 | ConcertVideo | X | X | ||||||
8 | DigitalBoxSetRelease | X | X | X | X | ||||
9 | DjMix | X | |||||||
10 | Documentary | X | X | X | X | ||||
11 | EBookRelease | X | X | ||||||
12 | EP | X | X | X | |||||
13 | Episode | X | X | X | X | ||||
14 | FeatureFilm | X | |||||||
15 | KaraokeRelease | X | X | ||||||
16 | LiveEventVideo | X | |||||||
17 | LongFormMusicalWorkVideoRelease | X | |||||||
18 | LongFormNonMusicalWorkVideoRelease | X | |||||||
19 | MaxiSingle | X | X | X | |||||
20 | MiniAlbum | X | X | X | |||||
21 | MultimediaAlbum | X | |||||||
22 | MultimediaDigitalBoxedSet | X | |||||||
23 | MultimediaSingle | X | |||||||
24 | Playlist | X | X | X | X | X | X | X | X |
25 | RingbackToneRelease | X | |||||||
26 | RingtoneRelease | X | |||||||
27 | Season | X | X | X | X | ||||
28 | Series | X | X | X | X | ||||
29 | Single | X | X | X | X | ||||
30 | SingleResourceRelease | X | X | ||||||
31 | StemBundle | X | |||||||
32 | VideoAlbum | X | |||||||
33 | VideoMastertoneRelease | X | |||||||
34 | VideoSingle | X |
5.2.1 ReleaseProfileVersionId
attribute
To indicate in the NewReleaseMessage
the use of a specific Profile, the ReleaseProfileVersionId
attribute on the root tag of the message shall be set as defined in column 2 of the table in Clause 5.1 (Definition of Release Profiles).
For the avoidance of doubt, the above is only valid for a NewReleaseMessage
in accordance with Version 4 or above of the Electronic Release Notification Message Suite Standard.
Note: ReleaseProfileVersionId
may not include any white-space characters.
5.2.2 ReleaseProfileVersionVariantId
attribute
If the NewReleaseMessage
uses of a specific Profile Variant, the ReleaseProfileVariantVersionId
attribute on the root tag of the message shall be set as follows:
yyy[ yyy]*
With “yyy” being the name of the profile variant as defined in Clause 5.5 (Rules for Release Profile Variants). Multiple variants shall be separated by a space character.
A profile may only be combined with those variants listed in the last column in the table in Clause 5.1 (Definition of Release Profiles). Multiple variants can be communicated as shown below. They must be communicated in the order defined in Clause 5.5 (Rules for Release Profile Variants).
For the avoidance of doubt, the above is only valid for a NewReleaseMessage
in accordance with Version 4 or above of the Electronic Release Notification Message Suite Standard.
Note: ReleaseProfileVersionVariantId
may not include any white-space characters other than to separate multiple variants.
5.3.1.1 General
The following common rules shall apply to all Profiles defined in this standard:
(1) All identifiers shall be globally unique. For proprietary identifiers this uniqueness shall apply in conjunction with their namespace.
Conformance Weighting: 1
(See the ERN Conformance Standard for details.)
(2) The message composite shall contain the Resources for the appropriate profile as indicated in Clause 5.1 (Definition of Release Profiles).
Conformance Weighting: 1
(3) The MessageID
element shall be, in combination of the DDEX Party ID of the Message Sender, globally unique. Thus, a Message Sender shall never re-use a MessageID
.
Conformance Weighting: 1
(4) All identifiers with a published syntax shall conform to that syntax.
Conformance Weighting: 1
(5) It is only permissible to communicate a UserDefinedValue
attribute if a Namespace
attribute is provided alongsid e it, and when the containing element contains UserDefined
.
Conformance Weighting: 1
(6) Percentages shall be provided in the interval [0,100].
Conformance Weighting: 1
(7) Where it is mandatory to communicate one data element for each territory for which a Deal is provided, the Message Sender shall either:
- Communicate a single element with no
TerritoryCode
attribute; - Communicate at least one element with the
IsDefault
attribute set totrue
(this is typically set toWorldwide
). No other elements may have theIsDefault
attribute set totrue
; - Communicate exactly one element with the
TerritoryCode
attribute set to each of the territories covered by theDeal
.
Conformance Weighting for items (7)1-3: 1
(8) Any available information on Contributors that have any of the following roles should be provided if available to the Message Sender : Adapter,
Arranger
, AssociatedPerformer
, Author
, Composer
, ComposerLyricist
, Librettist
, Lyricist
, NonLyricAuthor
, SubArranger
, Translator
.
Conformance Weighting: 1
(9) Any data fields or composite not defined as being mandatory for a specific Release Profile may still be used by the Message Sender. The Message Recipient may, however, discard any such information at its own discretion.
Conformance Weighting: 1
5.3.1.2 For Releases and/or Resources
The following common rules shall apply to all Releases and Resources in all Profiles defined in this standard:
(1) All DisplayArtists
must be sequenced.
Conformance Weighting: 1
(2) To communicate "compound main artists" (e.g. "Carlos Santana
feat. Eric Clapton") the following information shall be provided:
- A
DisplayArtistName
showing the full name of the compound artist as it should be displayed.
A
DisplayArtist
composite for each of the artists that make up the compound artist.
The main artist (in the example above Carlos Santana) shall have a
DisplayArtistRole
ofMainArtist
.
Additional artists (in the example above Eric Claption) may not have a
DisplayArtistRole
ofMainArtist
.
Conformance Weighting for items (2)1-2: 2
(3) It is also permissible to communicate a compound display artist name ("John & Paul") in the DisplayArtist
or Contributor
composite should the Message Sender be unable, despite best effort, to separate out the constituent artists' names. It should be noted that some companies have established rules for concatenating the constituent components of a compound artist (in the above example an ampersand has been used) and that DDEX, while acknowledging the existence of such rules, does not standardise them.
Conformance Weighting 1
(4) For each SoundRecording
and Video
, a DisplayTitle
and a DisplayTitleText
shall be provided as follows to communicate the title as the Release Creator suggests it should be shown to consumers:
- A
DisplayTitleText
shall be communicated containing, in a single string, the title plus any available sub-title information;
- A
DisplayTitle
shall be communicated with the main title in theTitleText
sub-element and the sub-title or version title information in theSubTitle
element. Sub-title or version title information shall be removed from theTitleText
andSubTitle
elements alongside any characters that separate theTitleText
andSubTitle
(such as parentheses);
- Further titles may be provided in the
AdditionalTitle
composite where main title and sub/version title information shall be separated as in theDisplayTitle
composite;
- If a title of a
SoundRecording
orVideo
contains sub-title or version title information, but the Release Creator wishes the sub/version title information not to be shown to consumers, the Release Creator shall provide:
- A
DisplayTitleText
without the sub/version title information;
- A
DisplayTitle
without the sub/version title information; and
- An
AdditionalTitle
composite of typeReferenceTitle
that does contain the sub/version title information to aid the Message Recipient in managing its catalog ofSoundRecording
s andVideos
.
- A
Conformance Weighting for items (4)1-4: 1
(5) For linking Releases and Resources:
- Each main Release shall have at least one
ResourceGroup
;
- If the Primary Resources of a Release are to be grouped in multiple sets, two (or more) second-level
ResourceGroup
s shall be provided. Each of these shall have aResourceGroupType
of eitherSide
,Component
,ComponentRelease
,ReleaseComponent
orMultiPartWork
. The last three values are only valid if used in a message conformant with relevant Variants defined in Clause 5.5 below. Each of theseResourceGroup
s may contain furtherResourceGroup
s;
R
esourceGroups
of typeComponent
,ComponentRelease
,Side
orMultiWorkPart
shall be sequenced in the context of their immediate parentResourceGroup
;
Primary Resources (even if there is only one) shall be sequenced in their
ResourceGroupContentItem
in the context of their parentResourceGroup
;
Sequence numbers typically start with 1 (but do not have to) and shall increase monotonically, typically by 1 (other increments are also allowed). No duplicates are allowed;
There is only one sequence within a
ResourceGroup
.ResourceGroups
andResourceGroupContentItems
are both numbered within this sequence;- Secondary Resources (e.g. cover images) content items shall not be sequenced;
FrontCoverImage
s, if included, shall be linked from the top-levelResourceGroup
'sLinkedReleaseResourceReference
.
- Video screen captures, if included, shall be linked from the
ResourceGroupContentItem
of the Resource they represent by aLinkedReleaseResourceReference
element with aLinkDescription
ofVideoScreenCapture
.
Conformance Weighting for items (5)1-6: 1
Conformance Weighting for items (5)7-9: 2
(6) If a Cue
is provided either a start time or a duration shall be provided.
Conformance Weighting 2
5.3.1.3 For Releases
The following common rules shall apply to all Releases in all Profiles defined in this standard:
(1) Any main Release intended for consumers shall be identified by either a GRid
or by an ICPN
or by a
. Other identifiers may also be provided.ProprietaryID
Conformance Weighting: 1
(2) TrackRelease
s consumption shall be identified by either a GRid
, ICPN
or by a ProprietaryID
.
Conformance Weighting: 1
(3) If a Message Sender is considering the use of an ISRC as an identifier for a TrackRelease
, it shall be communicated as a ProprietaryID
.
Conformance Weighting: 1
(4) TrackRelease
s should be identified with an identifier unique to the content and the context (i.e. the main Release it has been taken from).
This can be achieved by, for instance, concatenating the ISRC
identifying the TrackRelease
's Sound Recording and the ICPN
of the album Release.
No Conformance Weighting
(5) There needs to be a Label
for each territory for which a deal is provided.
Conformance Weighting: 1
(6) A CLine
may be communicated where applicable. If a CLine
is provided, the recipient shall ingest it.
Conformance Weighting: 1
(7) At least one ReleaseDate
or OriginalReleaseDate
(the former is preferred) shall be provided for the Release if available to the Message Sender.
Conformance Weighting: 2
(8) A ResourceGroup
of type Side
shall only be provided for Releases that may (also) be available with a UseType
of PurchaseAsPhysicalProduct
. For all other Releases, the only allowed ResourceGroupType
s are Component
and MultiWorkPart
.
Conformance Weighting: 2
5.3.1.4 For Resources
The following common rules shall apply to all Resources in all Profiles defined in this standard:
(1) Primary Resources that are eligible for an ISRC
shall be identified by an ISRC
.
Conformance Weighting: 2
(2) Secondary Resources shall be identified by a ProprietaryId
.
Conformance Weighting: 1
(3) Within the ResourceList
composite, at least one Resource has to be present. Resources need to be provided in the order they appear in the XML Schema. However, that order does not imply that the Resources are sequenced. To sequence resources, the ResourceGroup
composite has to be used.
Conformance Weighting: 1
(4) For each Resource, the sender shall provide any identifier for any underlying Musical Work (preferably an ISWC), that it has reasonable access to.
Conformance Weighting: 1
(5) Information about Composers
, Lyricists
, ComposerLyricists
and Adapters
should be provided in the Contributor
composite for each Primary Resource, if available.
Conformance Weighting: 2
(6) If a Party is playing multiple roles in creating a SoundRecording
or Video
, only one Contributor
composite shall be provided and all roles the party plays shall be included in that one Contributor
field.
Conformance Weighting: 1
(7) A FirstPublicationDate
should be provided for each Primary Resource if available to the Message Sender.
Conformance Weighting: 2
(8) To indicate that a Resource is a pre-order incentive track on a Release, the respective attributes in the relevant ResourceGroupContentItem
shall be used. The same applies to instant gratification tracks.
Conformance Weighting: 1
- The element shall contain the value “
UserDefined
”; - The
UserDefinedValue
attribute shall be set to the value from the later standard; and - The
Namespace
attribute shall be set to the same value as defined as normative content for theMessageVersionId
attribute for that standard.
For example, to communicate a UseType
of DownBeaming
, a term defined for Version 6.9 of the Electronic Release Notification Message Suite Standard (which does not exist at the time of writing) in a Version 4 message the following XML code shall be used:
<UseType UserDefinedValue="DownBeaming" Namespace="ern/69"> UserDefined </UseType>
The following rules shall apply to the Communication of Resource Files:
(1) Resource Availability
When communicating a Release for which no pre-order Deal is available, the Message Sender shall ensure that for all Resources a Resource File is communicated to the Message Recipient before the Release is to be made available to consumers.
For the avoidance of doubt, it is sufficient, that the Resource is communicated via a NewReleaseMessage
, sufficiently well before the Release is to "go live" to allow the Message Recipient to meet the "go live" date.
It is, however, preferred, that all Resources are communicated together (if possible).
(2) Resource Availability (Pre-order Releases)
When communicating a Release for which a pre-order Deal is available, the Message Sender shall ensure that for all Resources a Resource File is communicated to the Message Recipient before it is to be made available to consumers as part of the Release.
For the avoidance of doubt, it is sufficient, that the Resource is communicated via a NewReleaseMessage
, sufficiently well before it is to "go live" to allow the Message Recipient to meet the "go live" date.
It is, however, preferred, that all Resources of the Release are communicated together (if possible).
Conformance Weighting: 1
(3) Signalling Resource Availability
- When communicating a Resource File, the Message Sender shall include a
TechnicalResourceDetails
composite in the relevant Resource composite in theNewReleaseMessage
. Where a Resource File is not present, noTechnicalResourceDetails
composite may be present either.
When updating Resource information, the Message Sender is not obliged to re-send Resource Files (unlessTechnicalResourceDetails
are updated). - When the Message Sender wishes to update a Resource File for a specific Resource, the Message Sender shall include a
TechnicalResourceDetails
composite in the relevant Resource composite in theNewReleaseMessage
.
Conformance Weighting for items (3)1 and (3)2
(4) Primary and Secondary Resources
- If the Message Sender needs to update one (or more) primary Resource File(s), all primary Resource Files must be updated in accordance with Clause 5.3.3.2. This does not mean that any secondary Resource File needs to be updated.
- If the Message Sender needs to update one (or more) secondary Resource File(s), all secondary Resource Files must be updated in accordance with this Clause 5.3.3.2. This does not mean that any primary Resource File needs to be updated.
- In the context of a pre-order Release, the term "all" in the above sentences is to be understood as all Resources that are (or are to be made) available. This may well be a subset of the complete set.
Conformance Weighting for items (4)1-3
(5) Optimising Resource Delivery (Informative)
The provisions of Clause 5.3.3.4 prioritise simplicity of implementation over reducing data traffic. There are, however, means to reduce the data traffic.
When a Message Recipient receives a NewReleaseMessage
containing a number of TechnicalResourceDetails
composite, it knows that for each TechnicalResourceDetails
one resource file will be available. Assuming the Message Sender included a hash sum for the Resource File (in the TechnicalResourceDetails/File/HashSum
composite), the Message Recipient can decide whether to ingest the new Resource file or whether to use the Resource file it already has received in the past. This is especially powerful when the Release delivery process is based on web services (rather than SFTP).
A Release for the Simple Audio Single or Simple Video Single Profiles shall meet the following rules in addition to the rules stipulated in Clauses 5.2 and 5.3 :
(1) There shall only be one ResourceGroup
in the main Release.
Conformance Weighting: 1
(See the ERN Conformance Standard for details.)
(2) The ResourceGroup
shall only contain one ResourceGroupContentItem
composite.
Conformance Weighting: 1
(3) The ResourceGroupContentItem
shall only contain:
One
ReleaseResourceReference
pointing to the Primary Resource; and
One
LinkedReleaseResourceReference
pointing to an Image of typeFrontCoverImage
orVideoScreenCapture
.
Conformance Weighting for items (3)1-2: 1
(4) A ResourceRightsController
providing information on the company administering the rights of a SoundRecording
, Video
or other Resource may be provided with:
A
RightsControllerPartyReference
to theParty
composite that describes the rights controller;The list of
Territory
s that identify the territorial reach of the ownership (or claim thereof);
The
RightsControllerRole
;
A
StartDate
and/orEndDate
if known; and
A
RightSharePercentage
if known.
Conformance Weighting for items (4)1-3, 5: 1
Conformance Weighting for items (4)4: 2
A Release for a Ringtone
shall meet the following rules in addition to the rules stipulated in Clauses 5.2 and 5.3 :
(1) Primary Resources shall be identified with a ProprietaryId
or an ISRC
.
Conformance Weighting: 1
(See the ERN Conformance Standard for details.)
(2) There shall only be one ResourceGroup
in the main Release.
Conformance Weighting: 1
(3) The ResourceGroupContentItem
shall only contain:
One
ReleaseResourceReference
pointing to the Primary Resource; andOne
LinkedReleaseResourceReference
pointing to anImage
of typeFrontCoverImage
(if a Secondary Resource is provided).
Conformance Weighting for items (3)1-2: 1
(4) A RelatedRelease
of type IsReleaseFromRe lease
shall be provided if such a Release exists and the Message Sender has reasonable access to it.
Conformance Weighting: 2
A Long-form Musical Work Video, Film or TV Release shall meet the following rules in addition to the rules stipulated in Clauses 5.2 and 5.3 :
(1) Primary Resources shall be identified with an ISRC
(if eligible) or by a ProprietaryId
.>
Conformance Weighting: 1
(See the ERN Conformance Standard for details.)
(2) Each Primary Resources may be chaptered by including a VideoChapterReference
:
Each
Chapter
item shall have aChapterId
Each
Chapter
shall have aStartTime
indicating theChapter
start time on the Video; and
Each
Chapter
item may have aRepresentativeImageReference
which references theScreenCaptureImage
resource representing thatChapter
;
Conformance Weighting for items (2)1-2: 1
No Conformance Weighting for item (2)3
(3) Each primary Resource of type LongFormMusicalWorkVideo
or ConcertVideo
shall contain a VideoCueSheetReference
or a ReasonForCueSheetAbsence
.
Conformance Weighting: 2
(4) Cue
s, when provided, shall meet these requirements:
Each
Cue
shall have aStartTime
orDuration
;
Each
Cue
shall contain an identifier of typeISRC
orISWC
;
Each
Cue
shall contain at least oneContributor
; and
Each
Cue
that is identified by anISRC
shall contain aPLine
.
Conformance Weighting for items (4)2: 1
Conformance Weighting for items (4)1, 3, 4 : 2
(5) All other primary Resources may have a Cue
.
No Conformance Weighting
(6) If the ReleaseType
is FeatureFilm
the Release shall contain an Image of type Poster
.
Conformance Weighting: 2
A Release for a DjMix shall meet the following rules in addition to the rules stipulated in Clauses 5.2 and 5.3 :
(1) The NewReleaseMessage
shall contain exactly one SoundRecording
, classified in accordance with Clause 4.1 as a Primary Resource that is directly referenced from the Release
via the ResourceGroup
element (the "mix").
Conformance Weighting: 1
(See the ERN Conformance Standard for details.)
(2) The NewReleaseMessage
shall contain at least two SoundRecordings
"classified in accordance with Clause 4.1" as a Secondary Resource that are not directly referenced from the Release via the ResourceGroup
element (the "mix components").
Conformance Weighting: 1
(3) These Secondary Resources shall have the IsSupplemental
flag set to "true".
Conformance Weighting: 1
(4) The mix component shall be referenced, together with a StartPoint
and DurationUsed
, from the mix by a RelatedResource
of type HasContentFrom
.
Conformance Weighting: 1
(5) Each mix component shall be pointed to from the mix.
Conformance Weighting: 1
(6) Notwithstanding the rules on the identification of secondary Resources elsewhere, mix component Sound Recordings shall be identified with an ISRC
. There is no requirement to identify them with a ProprietaryId
.
Conformance Weighting: 1
(7) If a message sender wishes to send DJ mixes but does not have access to the data required above, that message sender cannot use the DjMix Release Profile. Instead, such Releases can be communicated using the Audio profile.
A Release for an Audio Drama or Audio Book shall meet the following rules in addition to the rules stipulated in Clauses 5.2 and 5.3 :
(1) At least one Contributor with one of the following role codes shall be provided: NonLyricAuthor, Actor, VoiceActor or Narrator. If no Contributor with the aforementioned roles can be provided, a suitable alternative role (e.g. Artist) shall be used.
Conformance Weighting: 1
(See the ERN Conformance Standard for details.)
Notwithstanding rules expressed elsewhere in this standard a Release of any type marked as being of a BoxedSet Variant shall meet the following rules:
(1) The Main Release
composite of a Boxed Set Release shall contain at least two ResourceGroup
s of type ReleaseComponent
that do not represent the full Boxed Set.
Conformance Weighting: 1
(See the ERN Conformance Standard for details.)
(2) Each of these ResourceGroup
s shall meet the requirements laid out in Clauses 5.1.2 and 5.3 for their relevant profile and may contain further ResourceGroup
s as needed.
Conformance Weighting: 1
(3) The identifier of the "component" Release
s that make up the Boxed Set Release shall be placed into the ReleaseId
composite of the relevant ResourceGroup
.
Conformance Weighting: 1
Notwithstanding rules expressed elsewhere in this standard a Release of any type marked as being of a Classical Variant shall contain at least one Primary Resource that meets the following rules:
(1) This profile variant may only be used for Releases containing at least one Musical Work that comprises more than one "segment".
Conformance Weighting: 1
(See the ERN Conformance Standard for details.)
(2) Each of these multi-segmented Works shall be grouped using a ResourceGroup
that follows the following rules:
- A logical grouping of a multi-segmented Work shall be represented by a
ResourceGroup
of typeMultiWorkPart
;
-
ResourceGroups
of typeMultiWorkPart
shall contain at least twoResourceGroupContentItems
;
- The only exception to the above rule is a
ResourceGroup
of typeMultiWorkPart
that is split over the boundary of a parentResourceGroup
. In this case it is allowed to have aResourceGroup
of typeMultiWorkPart
containing just oneResourceGroupContentItem
if, and only if, there is aResourceGroup
of typeMultiWorkPart
at the same nesting level immediately preceding or following it, that describes the same Work; - It is permitted to combine
ResourceGroup
s of typeMultiWorkPart
withResourceGroup
s of other types within the same Release; and - If combining
ResourceGroups
of typeMultiWorkPart
withResourceGroups
of other types within the same Release, theResourceGroups
of typeMultiWorkPart
should be nested inside theResourceGroups
of other types.
Conformance Weighting for items (2)1-3,5: 1
No Conformance Weighting for item (2)4
(3) Each of these multi-segmented Works shall carry title elements a follows:
- Each
SoundRecording
orVideo
that is part of a multi-segmented Work shall carry, in addition to theDisplayTitle
andDisplayTitleText
(see Clause 5.3.1.2 Item 4 ) anAdditionalTitle
of typeFormalTitle
;
- An
AdditionalTitle
of typeGroupingTitle
denoting the parent of eachSoundRecording
orVideo
may be communicated if theSoundRecording
is a part of a multi-segmented Work;
- Each
ResourceGroup
that contains more than oneSoundRecording
orVideo
of the same multi-segmented Work shall carry aDisplayTitle
and/orDisplayTitleText
of the segment in accordance with Clause 5.3.1.2 Item 4 ;
- Each
ResourceGroup
that contains more than oneSoundRecording
orVideo
of the same multi-segmented Work shall also carry an anAdditionalTitle
of typeFormalTitle
if the Message Sender considers theDisplayTitle
orDisplayTitleText
to not be the full formal title of the segment; - Such
AdditionalTitle
s of typeFormalTitle
should include as much Information as possible. The precise syntax of theFormalTitle
s is left to the Message Sender;
- Message Recipients should ingest
AdditionalTitle
s of typeFormalTitle
and use it for catalogue management and search, but to use theDisplayTitle
and/orDisplayTitleText
for display purposes; and
- The above rules on titles may and shall also be applied to other
ResourceTypes
where necessary.
Conformance Weighting for item (3)3: 1
No Conformance Weighting for items (3)1-2,4-6
Same conformance Weighting as noted above for item (3)7
The SoundRecording
containing the first movement of the first concerto of Vivaldi's Four Seasons may have a FormalTitle
of “Concerto for Violin and Strings in E-Major, Op. 8, No. 1, RV 296 ‘La Primavera: 1. allegro’” (while the DisplayTitle
might be "Vivaldi's First Spring Movement"). The ResourceGroup
that contains this SoundRecording
would have a FormalTitle
of “Concerto for Violin and Strings in E-Major, Op. 8, No. 1, RV 296 ‘La Primavera’” (note the absence of the "allegro" in the ResourceGroup
's FormalTitle
).
Table 3: Samples of structured Classical Albums (Informative)
Type of Release | Release Group structure for this Type of Release |
Single Work with multiple segments | |
Collection of two multi-segment Works | ResourceGroup representing the Release containing |
Works and “tracks” mixed (disc | |
Works and “tracks” mixed (disc Note: the only differences are | |
Same Work repeated in product | ResourceGroup of type |
Work spanning multiple discs | |
While technically also possible to | |
Collection of two multi-segment Works. | ResourceGroup representing the Release containing ResourceGroup of type Component (SequenceNumber=1) containing the 1st disc of the 1st Work ResourceGroup of type MultiWorkPart (SequenceNumber=1) representing the 1st Work containing ResourceGroupContentItem representing the 1st segment of the 1st Work (SequenceNumber=1) ResourceGroupContentItem representing the 2nd segment of the 1st Work (SequenceNumber=2) ResourceGroupContentItem representing the 3rd segment of the 1st Work (SequenceNumber=3) ResourceGroup of type Component (SequenceNumber=2) containing the 2nd disc of the 1st Work ResourceGroup of type MultiWorkPart (SequenceNumber=1) representing the 1st Work containing ResourceGroupContentItem representing the 4th segment of the 1st Work (SequenceNumber=1) ResourceGroupContentItem representing the 5th segment of the 1st Work (SequenceNumber=2) ResourceGroupContentItem representing the 6th segment of the 1st Work (SequenceNumber=3) ResourceGroup of type Volume (SequenceNumber=1) containing the complete Work ResourceGroup of type MultiWorkPart (SequenceNumber=1) representing the 2nd Work containing ResourceGroupContentItem representing the 1st segment of the 2nd Work (SequenceNumber=1) ResourceGroupContentItem representing the 2nd segment of the 2nd Work (SequenceNumber=2) ResourceGroupContentItem representing the 3rd segment of the 2nd Work (SequenceNumber=3) |
Collection of one multi-segment Work The multi-segment Work comprises | ResourceGroup representing the Release containing ResourceGroup of type Component (SequenceNumber=1) containing the 1st disc of the 1st Work ResourceGroup of type MultiWorkPart (SequenceNumber=1) representing the 1st Work containing ResourceGroupContentItem representing the 1st segment of the 1st Work (SequenceNumber=1) ResourceGroupContentItem representing the 2nd segment of the 1st Work (SequenceNumber=2) ResourceGroupContentItem representing the 3rd segment of the 1st Work (SequenceNumber=3) ResourceGroup of type Component (SequenceNumber=2) containing the 2nd disc of the 1st Work ResourceGroup of type MultiWorkPart (SequenceNumber=1) representing the 1st Work containing ResourceGroupContentItem representing the 4th segment of the 1st Work (SequenceNumber=1) ResourceGroupContentItem representing the 5th segment of the 1st Work (SequenceNumber=2) ResourceGroupContentItem representing the 6th segment of the 1st Work (SequenceNumber=3) ResourceGroup of type Volume (SequenceNumber=1) containing the extra tracks ResourceGroupContentItem representing the 1st extra track (SequenceNumber=1) ResourceGroupContentItem representing the 2nd extra track (SequenceNumber=2) |
TrackRelease
shall meet the following rules:-
For additional information on Release IDs for TrackReleases see Track Releases.
The
ReleaseId
for theTrackRelease
should be unique for each combination of (i) content of the TrackRelease and (ii) the main Release that the TrackRelease is communicated with. <No Conformance Weighting> The Track Release composite shall contain (with a Conformance Weighting of 1)
- 1 Primary Resource of the type prevalent in the Main Release that the Track Release is communicated with; and
- No secondary resources.
- The Track Release shall meet all rules defined in Clause 5.3 with their relevant conformance weightings to the extent that this is possible with the XML Schema Definition of the Track Release composite.
- Notwithstanding the above, title information shall only be provided if it differs from the title information provided on the Resource referenced from the
ReleaseResourceReference
.
Annex
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.