DDEX Knowledge Base

https://kb.ddex.net
Admin
DDEX Knowledge Base provides comprehensive documentation and implementation guidance for DDEX...
Tokens:149,168
Snippets:1,677
Trust Score:9.7
Update:3 months ago
Show doc for...
Tokens:
Raw
### Example of DisplayArtistName and DisplayArtist

Source: https://kb.ddex.net/implementing-each-standard/recording-data-and-rights-standards-%28rdr%29/recording-data-and-rights-notification-%28rdr-n%29/rdr-n-explained/rdr-n%3A-soundrecording-detailsbyterritory-%28version-1.4%29

Shows how to represent artist names, including full names, IDs, and roles, for a sound recording. This example includes a main artist and a featured artist.

```xml
<DisplayArtistName> The Weeknd ft. Daft Punk</DisplayArtistName> 
<DisplayArtist SequenceNumber="1"> 
 <PartyName LanguageAndScriptCode="en"> 
 <FullName>The Weeknd</FullName> 
 </PartyName> 
 <PartyId> 
 <ProprietaryId Namespace="PADPIDA2007061301U">1234567</ProprietaryId> 
 </PartyId> 
 <DisplayArtistRole>MainArtist</DisplayArtistRole> 
</DisplayArtist> 
<DisplayArtist SequenceNumber="2"> 
 <PartyName LanguageAndScriptCode="en"> 
 <FullName>Daft Punk</FullName> 
 </PartyName> 
 <PartyId> 
 <ProprietaryId Namespace="PADPIDA2007061301U">7654321</ProprietaryId> 
 </PartyId> 
 <DisplayArtistRole>FeaturedArtist</DisplayArtistRole> 
</DisplayArtist>
```

--------------------------------

### Example ReleaseVisibility with DoNotDisplayDates

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/deals-and-commercial-aspects/donotdisplaydates-in-ern-4.3-and-later

This example shows how to set the DoNotDisplayDates flag to 'true' within the ReleaseVisibility composite to prevent DSPs from displaying preview dates to consumers. The default behavior is to omit the flag.

```xml
<DealList>
    [...] 
    <ReleaseVisibility DoNotDisplayDates="true">
        <VisibilityReference>V1</VisibilityReference>
        <TerritoryCode>US</TerritoryCode>
        <FullTrackListingPreviewStartDateTime>
            2022-06-01
        </FullTrackListingPreviewStartDateTime>
    </ReleaseVisibility>
    [...]
</DealList>
```

--------------------------------

### Display Artist Details (ERN 3.7 - Jay-Z Example)

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-contributors%2C-artists-and-writers/communicating-displayartists-and-displayartistname

Example showing how to represent a primary artist and featured artists with their respective roles and IDs.

```xml
<SoundRecordingDetailsByTerritory> ... <DisplayArtist> <PartyName> <FullName>Jay-Z feat. Alicia Keys</FullName> </PartyName> <ArtistRole>Artist</ArtistRole> </DisplayArtist> <DisplayArtist SequenceNumber="1"> <PartyName> <FullName>Jay-Z</FullName> </PartyName> <PartyId Namespace="...">123</PartyId> <ArtistRole>MainArtist</ArtistRole> </DisplayArtist> <DisplayArtist SequenceNumber="2"> <PartyName> <FullName>Alicia Keys</FullName> </PartyName> <PartyId Namespace="...">456</PartyId> <ArtistRole>FeaturedArtist</ArtistRole> </DisplayArtist> ... </SoundRecordingDetailsByTerritory>
```

--------------------------------

### ℗ Notice Formatting Examples

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-releaseresourcework-metadata/pline-and-cline

Examples of correct and incorrect formatting for ℗ notices, emphasizing the inclusion of the rights owner and full corporate entity name.

```text
℗ 2007 XYZ Record Company Limited, under exclusive licence to Exclusive-Licensee Co Limited for the UK
```

```text
℗ 2007 Exclusive-Licensee Company Limited
```

```text
℗ 2007 XYZ Record Company Limited
```

--------------------------------

### PartyName XML Structure Examples

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-contributors%2C-artists-and-writers/splitting-names-and-the-importance-of-the-keyname

Examples of the PartyName composite structure for individual and collaborative artist names.

```xml
<PartyName>    <FullName>Bob Geldof, KBE</FullName>    <FullNameIndexed>Geldof, Bob</FullNameIndexed>    <NamesBeforeKeyName>Bob</NamesBeforeKeyName>    <KeyName>Geldorf</KeyName>    <NamesAfterKeyName>KBE</NamesAfterKeyName></PartyName>
```

```xml
<PartyName>    <FullName>Quincy Jones &amp; Friends</FullName>    <FullNameIndexed>Jones, Quincy &amp; Friends</FullNameIndexed>    <NamesBeforeKeyName>Quincy</NamesBeforeKeyName>    <KeyName>Jones</KeyName>    <NamesAfterKeyName>&amp; Friends</NamesAfterKeyName></PartyName>
```

--------------------------------

### ERN 4.1 Release Visibility and Deal Terms

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/deals-and-commercial-aspects/availability-and-visibility

This example shows how to define release visibility and deal terms in ERN 4.1. It includes the start date for the release display, track listing preview, and cover art preview within the DealTerms.

```xml
<DealList>  <ReleaseDeal>    <DealReleaseReference>R1</DealReleaseReference>    <Deal>      <DealTerms>        <ValidityPeriod>          <StartDateTime>2020-05-01T00:00:00Z</StartDateTime>        </ValidityPeriod>        <UseType>NonInteractiveStream</UseType>        <ReleaseDisplayStartDateTime>2020-02-01T00:00:00Z</ReleaseDisplayStartDateTime>        <TrackListingPreviewStartDateTime>2020-03-01T00:00:00Z</TrackListingPreviewStartDateTime>        <CoverArtPreviewStartDateTime>2020-02-01T00:00:00Z</CoverArtPreviewStartDateTime>              </DealTerms>    </Deal>  </ReleaseDeal>        </DealList>
```

--------------------------------

### Additional Performer Data Example

Source: https://kb.ddex.net/implementing-each-standard/recording-data-and-rights-standards-%28rdr%29/recording-data-and-rights-notification-%28rdr-n%29/rdr-n-explained/rdr-n%3A-soundrecording-detailsbyterritory-%28version-1.4%29

Includes examples for the number of featured and non-featured performing contributors, and a flag indicating if the lineup is complete. This data aids in accurately representing artist contributions.

```xml
<NumberOfFeaturedPerformingContributors>4</NumberOfFeaturedPerformingContributors><NumberOfNonFeaturedPerformingContributors>2</NumberOfNonFeaturedPerformingContributors><LineupComplete>false</LineupComplete>
```

--------------------------------

### DDEX Release Metadata Example

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-releaseresourcework-metadata/communicating-previews-and-clips-used-for-shorts-in-ern-4.3-and-later

This snippet shows the structure for a full album release, including its tracks and associated metadata.

```xml
<ReleaseList>
        <Release>
            <ReleaseReference>R0</ReleaseReference>
            <ReleaseType>Album</ReleaseType>
            <ReleaseId>
                <ICPN>91809101019025</ICPN>
            </ReleaseId>
            <DisplayTitleText IsDefault="true">Release with Preview and Standalone Clip</DisplayTitleText>
            <DisplayTitle IsDefault="true">
                <TitleText>Release with Preview and Standalone Clip</TitleText>
            </DisplayTitle>
            <AdditionalTitle IsDefault="true" TitleType="FormalTitle">
                <TitleText>Release with Preview and Standalone Clip</TitleText>
            </AdditionalTitle>
            <DisplayArtistName IsDefault="true">Tom McThompson</DisplayArtistName>
            <DisplayArtist SequenceNumber="1">
                <ArtistPartyReference>P1</ArtistPartyReference>
                <DisplayArtistRole>MainArtist</DisplayArtistRole>
            </DisplayArtist>
            <ReleaseLabelReference IsDefault="true">P2</ReleaseLabelReference>
            <PLine IsDefault="true">
                <PLineText>(P) Tom McThompson Records</PLineText>
            </PLine>
            <CLine IsDefault="true">
                <CLineText>(C) Tom McThompson Records</CLineText>
            </CLine>
            <Duration>PT3M1S</Duration>
            <Genre IsDefault="true">
                <GenreText>Alternative</GenreText>
            </Genre>
            <ReleaseDate IsDefault="true">2018-09-10</ReleaseDate>
            <ReleaseVisibilityReference>V1</ReleaseVisibilityReference>
            <ParentalWarningType IsDefault="true">ExplicitContentEdited</ParentalWarningType>
            <ResourceGroup>
                <ResourceGroup ResourceGroupType="Component">
                    <SequenceNumber>1</SequenceNumber>
                    <ResourceGroupContentItem>
                        <SequenceNumber>1</SequenceNumber>
                        <ReleaseResourceReference>A2</ReleaseResourceReference>
                    </ResourceGroupContentItem>
                    <ResourceGroupContentItem>
                        <SequenceNumber>2</SequenceNumber>
                        <ReleaseResourceReference>A3</ReleaseResourceReference>
                    </ResourceGroupContentItem>
                </ResourceGroup>
                <LinkedReleaseResourceReference>A1</LinkedReleaseResourceReference>
            </ResourceGroup>
        </Release>
        <TrackRelease>
            <ReleaseReference>R1</ReleaseReference>
            <ReleaseId>
                <ProprietaryId Namespace="ISRC">ZZZZ80000001</ProprietaryId>
                <ProprietaryId Namespace="PADPIDA1111111111U">91809101019025_ZZZZ80000001</ProprietaryId>
            </ReleaseId>
            <DisplayTitleText IsDefault="true">First Song</DisplayTitleText>
            <DisplayTitle IsDefault="true">
                <TitleText>First Song</TitleText>
            </DisplayTitle>
            <AdditionalTitle IsDefault="true" TitleType="FormalTitle">
                <TitleText>First Song</TitleText>
            </AdditionalTitle>
            <ReleaseResourceReference>A2</ReleaseResourceReference>
            <ReleaseLabelReference IsDefault="true">P2</ReleaseLabelReference>
            <Genre IsDefault="true">
                <GenreText>Alternative</GenreText>
            </Genre>
            <ReleaseVisibilityReference>V2</ReleaseVisibilityReference>
        </TrackRelease>
        <TrackRelease>
            <ReleaseReference>R2</ReleaseReference>
            <ReleaseId>
                <ProprietaryId Namespace="ISRC">ZZZZ80000002</ProprietaryId>
                <ProprietaryId Namespace="PADPIDA1111111111U">91809101019025_ZZZZ80000002</ProprietaryId>
            </ReleaseId>
            <DisplayTitleText IsDefault="true">Second Song</DisplayTitleText>
            <DisplayTitle IsDefault="true">
                <TitleText>Second Song</TitleText>
            </DisplayTitle>
```

--------------------------------

### Example Track Release Identifier (ERN-4 Syntax)

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-identifiers%2C-iso-codes-lists-and-dates/can-a-release-be-identified-by-an-isrc

This example demonstrates how a Track Release can be identified using a proprietary identifier in ERN-4 syntax. It concatenates the main release identifier with the ISRC of the contained sound recording.

```xml
<TrackRelease>        <ReleaseReference>R1</ReleaseReference>        <ReleaseId>                  <ProprietaryId Namespace="PADPIDA2013042401U">00094631432057_JPTO09404900</ProprietaryId>        </ReleaseId>        <!-- ... --> <TrackRelease>
```

--------------------------------

### Original Deal Terms

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/deals-and-commercial-aspects/cancelling-a-deal-before-street-date

Example of DealTerms sent to DSPs before the street date.

```xml
<Deal>  <DealTerms>     <TerritoryCode>US</TerritoryCode>     <ValidityPeriod>       <StartDate>2015-12-01</StartDate>     </ValidityPeriod>     <CommercialModelType>PayAsYouGoModel</CommercialModelType>     <UseType>PermanentDownload</UseType>   </DealTerms></Deal>
```

--------------------------------

### Example of Title in SoundRecordingDetailsByTerritory

Source: https://kb.ddex.net/implementing-each-standard/recording-data-and-rights-standards-%28rdr%29/recording-data-and-rights-notification-%28rdr-n%29/rdr-n-explained/rdr-n%3A-soundrecording-detailsbyterritory-%28version-1.4%29

Illustrates how to specify a title, including its language, type, text, and subtitle, within the SoundRecordingDetailsByTerritory structure.

```xml
<Title LanguageAndScriptCode="en" TitleType="DisplayTitle"> 
 <TitleText>My Song</TitleText> 
 <SubTitle>Album Version</SubTitle> 
</Title>
```

--------------------------------

### Define ClipDetails in ERN 4.3 XML

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-releaseresourcework-metadata/communicating-previews-and-clips-used-for-shorts-in-ern-4.3-and-later

Example showing the structure of a SoundRecording with a preview clip defined in the ClipDetails composite.

```xml
<?xml version="1.0" encoding="UTF-8"?><ernm:NewReleaseMessage xmlns:ernm="http://ddex.net/xml/ern/43Draft" LanguageAndScriptCode="en" AvsVersionId="1" ReleaseProfileVersionId="Audio" xmlns:avs="http://ddex.net/xml/avs/avs" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://ddex.net/xml/ern/43Draft release-notification.xsd">    <MessageHeader>        <MessageThreadId>997cde6a-a2bf-4ade-84a3-57a2e0d1beba</MessageThreadId>        <MessageId>UG36799159</MessageId>        <MessageSender>            <PartyId>PADPIDA1111111111U</PartyId>            <PartyName>                <FullName>Galactic Music Group</FullName>            </PartyName>        </MessageSender>        <MessageRecipient>            <PartyId>PADPIDA123456789</PartyId>            <PartyName>                <FullName>Full Partner Name</FullName>            </PartyName>        </MessageRecipient>        <MessageCreatedDateTime>2022-03-21T11:03:30.634Z</MessageCreatedDateTime>        <MessageControlType>LiveMessage</MessageControlType>    </MessageHeader>    <PartyList>        <Party>            <PartyReference>P1</PartyReference>            <PartyName>                <FullName>Tom McThompson</FullName>            </PartyName>        </Party>        <Party>            <PartyReference>P2</PartyReference>            <PartyName>                <FullName>TOM INC</FullName>            </PartyName>        </Party>    </PartyList>    <ResourceList>        <SoundRecording>            <ResourceReference>A2</ResourceReference>            <Type>MusicalWorkSoundRecording</Type>            <SoundRecordingEdition>                <ResourceId>                    <ISRC>ZZZZ80000001</ISRC>                </ResourceId>                <PLine IsDefault="true">                    <PLineText>Tom McThompson Records</PLineText>                </PLine>                <RecordingMode>Stereo</RecordingMode>                <TechnicalDetails>                    <!-- full length audio -->                    <TechnicalResourceDetailsReference>T2</TechnicalResourceDetailsReference>                    <DeliveryFile>                        <Type>AudioFile</Type>                        <AudioCodecType>MP3</AudioCodecType>                        <BitRate UnitOfMeasure="kbps">128</BitRate>                        <NumberOfChannels>2</NumberOfChannels>                        <SamplingRate UnitOfMeasure="kHz">44.1</SamplingRate>                        <BitsPerSample>16</BitsPerSample>                        <Duration>PT0H0M30.000S</Duration>                        <File>                            <URI>resources/91809101019025_T2_audtrk.mp3</URI>                            <HashSum>                                <Algorithm>MD5</Algorithm>                                <HashSumValue>full_length</HashSumValue>                            </HashSum>                        </File>                    </DeliveryFile>                    <IsClip>false</IsClip>                    <!-- 90 second preview provided as file -->                    <ClipDetails>                        <TechnicalResourceDetailsReference>T2P</TechnicalResourceDetailsReference>                        <ClipType>Preview</ClipType>                        <Timing>                            <StartPoint>48</StartPoint>                            <DurationUsed>PT0H1M30.000S</DurationUsed>                        </Timing>                    </ClipDetails>
```

--------------------------------

### Sample 1: Preview Clip Communication (XML)

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-releaseresourcework-metadata/clip-samples

This sample demonstrates communicating a sound recording with a short preview clip. The clip is provided as an instruction to the DSP for generation, without a specific deal associated with it.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<ern:NewReleaseMessage xmlns:ern="http://ddex.net/xml/ern/43"     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"     xsi:schemaLocation="http://ddex.net/xml/ern/43 http://service.ddex.net/xml/ern/43/release-notification.xsd"     AvsVersionId="3" LanguageAndScriptCode="en">
    
    
    <!-- This sample is solely for the porpose of showcasing clips and previews in ERN 4.3 -->
    <!-- This sample, while validating against the ERN 4.3 XSD does NOT follow all relevant profile rules -->
    
    <!-- Sample 1: Preview delivered by the record company -->
    
    <MessageHeader>
        <MessageId/>
        <MessageSender>
            <PartyId>PADPIDASENDER</PartyId>
        </MessageSender>
        <MessageRecipient>
            <PartyId>PADPIDARECIPIENT</PartyId>
        </MessageRecipient>
        <MessageCreatedDateTime>2022-11-07T10:50:00Z</MessageCreatedDateTime>
    </MessageHeader>
    <PartyList>
        <Party>
            <PartyReference>P1</PartyReference>
            <PartyName>
                <FullName>Marillion</FullName>
            </PartyName>
            <PartyId>
                <ISNI>0000000114819103</ISNI>
            </PartyId>
        </Party>
        <Party>
            <PartyReference>P2</PartyReference>
            <PartyName>
                <FullName>Parlophone UK</FullName>
            </PartyName>
        </Party>
    </PartyList>
    <ResourceList>
        <SoundRecording>
            <ResourceReference>A1</ResourceReference>
            <Type>MusicalWorkSoundRecording</Type>
            <SoundRecordingEdition>
                <ResourceId>
                    <ISRC>GBAYE8300142</ISRC>
                </ResourceId>
                <TechnicalDetails>
                    <TechnicalResourceDetailsReference>T1</TechnicalResourceDetailsReference>
                    <DeliveryFile>
                        <Type>AudioFile</Type>
                        <File>
                            <URI>file://0000000114819103-128.mp3</URI>
                        </File>
                    </DeliveryFile>
                    <IsClip>false</IsClip>
                    <ClipDetails>
                        <TechnicalResourceDetailsReference>T1P</TechnicalResourceDetailsReference>
                        <ClipType>Preview</ClipType>
                        <Timing>
                            <StartPoint>93</StartPoint>
                            <EndPoint>103</EndPoint>
                        </Timing>
                        <ExpressionType>Instructive</ExpressionType>
                    </ClipDetails>
                </TechnicalDetails>
            </SoundRecordingEdition>
```

--------------------------------

### Define ResourceReference for SoundRecording

Source: https://kb.ddex.net/implementing-each-standard/recording-data-and-rights-standards-%28rdr%29/recording-data-and-rights-notification-%28rdr-n%29/rdr-n-explained/rdr-n%3A-soundrecording-%28version-1.5%29

Example of the mandatory ResourceReference tag, where the value is an anchor reference starting with 'A' followed by an incrementing integer.

```xml
<ResourceReference>A1</ResourceReference>
```

--------------------------------

### XML Message Notification Period Example

Source: https://kb.ddex.net/implementing-each-standard/recording-data-and-rights-standards-%28rdr%29/recording-data-and-rights-notification-%28rdr-n%29/rdr-n-explained/rdr-n%3A-message-notification-period

This XML snippet shows the structure for defining a message notification period with start and end dates. Ensure the namespace is correctly handled.

```xml
<MessageNotificationPeriod xmlns=""><StartDate>1985-01-01</StartDate><EndDate>2017-05-03</EndDate></MessageNotificationPeriod>
```

--------------------------------

### Basic Contributor Role and DisplayCredits Example

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-contributors%2C-artists-and-writers/artist-roles-and-displaycredits

Demonstrates the use of Role, InstrumentType, and DisplayCredits within a SoundRecording contributor composite.

```xml
<SoundRecording>    ...    <Contributor SequenceNumber="1">        <ContributorPartyReference>P12345</ContributorPartyReference>        <Role>ComposerLyricist</Role>        <Role>Musician</Role>        <InstrumentType>Guitar</InstrumentType>        <InstrumentType>Voice</InstrumentType>    <DisplayCredits>John: Music (melody and words), Vocals and Guitar</DisplayCredits>    </Contributor>     <Contributor SequenceNumber="2">        <ContributorPartyReference>P54321</ContributorPartyReference>        <Role>ComposerLyricist</Role>        <Role>Musician</Role>        <Role>BackgroundVocalist</Role>        <InstrumentType>Drums</InstrumentType>        <DisplayCredits>Paul: Music and Drums</DisplayCredits>    </Contributor>    <Contributor SequenceNumber="3">        <ContributorPartyReference>P15243</ContributorPartyReference>        <Role>BackgroundVocalist</Role>        <DisplayCredits>Additional vocals provided by Yoko</DisplayCredits>    </Contributor>    ...</SoundRecording>
```

--------------------------------

### OriginalResourceReleaseDate Example

Source: https://kb.ddex.net/implementing-each-standard/recording-data-and-rights-standards-%28rdr%29/recording-data-and-rights-notification-%28rdr-n%29/rdr-n-explained/rdr-n%3A-soundrecording-detailsbyterritory-%28version-1.4%29

Provides examples of OriginalResourceReleaseDate with TerritoryCode for different countries. This field is used to assess copyright term expiration.

```xml
<OriginalResourceReleaseDate TerritoryCode="US">2011-01-02</OriginalResourceReleaseDate><OriginalResourceReleaseDate TerritoryCode="GB">2012-01-02</OriginalResourceReleaseDate>
```

--------------------------------

### Resource-Specific Previews (ERN-3)

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-previews/resource-specific-previews

This XML snippet demonstrates how to set up deals for resource-specific previews using the ERN-3 format. It includes separate ReleaseDeal entries for normal exploitation (download) and previews (stream), referencing specific resources.

```xml
<DealList>    <ReleaseDeal>      <!-- This is the deal for the 'normal' exploitation (here: download) -->      <DealReleaseReference>R1</DealReleaseReference>      <Deal>         <DealTerms>             <Usage>                 <UseType>Download</UseType>             </Usage>             <TerritoryCode>FO</TerritoryCode>             <ValidityPeriod>                 <StartDate>2016-01-01</StartDate>             </ValidityPeriod>         </DealTerms>         <DealTechnicalResourceDetailsReferenceList>             <DealTechnicalResourceDetailsReference>T1</DealTechnicalResourceDetailsReference>             <DealTechnicalResourceDetailsReference>T2</DealTechnicalResourceDetailsReference>         </DealTechnicalResourceDetailsReferenceList>      </Deal>   </ReleaseDeal>     <ReleaseDeal>       <!-- This is the deal for the preview (here: stream) -->       <DealReleaseReference>R1</DealReleaseReference>       <Deal>          <DealTerms>              <Usage>                 <UseType>Stream</UseType>              </Usage>              <TerritoryCode>FO</TerritoryCode>              <ValidityPeriod>                 <EndDate>2016-01-01</EndDate>              </ValidityPeriod>          </DealTerms>          <DealTechnicalResourceDetailsReferenceList>             <DealTechnicalResourceDetailsReference>T1P</DealTechnicalResourceDetailsReference>             <DealTechnicalResourceDetailsReference>T2P</DealTechnicalResourceDetailsReference>          </DealTechnicalResourceDetailsReferenceList>       </Deal>    </ReleaseDeal> </DealList>
```

--------------------------------

### A la carte Download DealTerms Example

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/deals-and-commercial-aspects/recommended-use-of-commercialmodeltype-and-usetype-in-ern-4

Represents a consumer purchasing a specific release for a one-time fee, allowing indefinite download and storage on personal devices for private use. Use 'PayAsYouGoModel' for the commercial model and 'PermanentDownload' for the use type.

```xml
<DealTerms>
    <ValidityPeriod>
        <StartDateTime>2018-12-25T17:00:00</StartDateTime>
    </ValidityPeriod>
    <CommercialModelType>PayAsYouGoModel</CommercialModelType>
    <UseType>PermanentDownload</UseType>
</DealTerms>
```

--------------------------------

### Correctly Referencing SoundRecordings using Sequential IDs

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-xml-issues/referencing-composites-using-id-and-idref

This example illustrates the recommended practice for assigning ResourceReference values, using simple sequential numbers (e.g., A1) to ensure uniqueness and adherence to DDEX standards.

```xml
<SoundRecording>
  <SoundRecordingId>
    <ISRC>USRC17607839</ISRC>
  <SoundRecordingId>
  <Title>
    <TitleText>Crazy Eyes</TitleText>
  </Title>
  <ResourceReference>A1</ResourceReference>
</SoundRecording>
```

--------------------------------

### Multiple UseTypes and CommercialModelTypes in a Deal

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/deals-and-commercial-aspects/multiple-commercialmodeltypes-or-usetypes-in-one-deal

Communicate that a Release is available for non-interactive streams, ad-supported on-demand streams, and as a subscription download. This example shows separate DealTerms for each combination.

```xml
<DealList>        <ReleaseDeal>                <DealReleaseReference>R1</DealReleaseReference>                <Deal>                        <DealTerms>                                <TerritoryCode>Worldwide</TerritoryCode>                                <ValidityPeriod>                                        <StartDate>2016-04-25</StartDate>                                </ValidityPeriod>                                <CommercialModelType>AdvertisementSupportedModel</CommercialModelType>                                <UseType>NonInteractiveStream</UseType>                                <UseType>OnDemandStream</UseType>                        </DealTerms>                </Deal>                <Deal>                        <DealTerms>                                <TerritoryCode>Worldwide</TerritoryCode>                                <ValidityPeriod>                                        <StartDate>2016-04-25</StartDate>                                </ValidityPeriod>                                <CommercialModelType>SubscriptionModel</CommercialModelType>                                <UseType>Download</UseType>                        </DealTerms>                </Deal>        </ReleaseDeal>       </DealList>
```

--------------------------------

### Referencing SoundRecordings from a Release

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-xml-issues/referencing-composites-using-id-and-idref

This example demonstrates how a Release composite can reference multiple SoundRecording composites using ReleaseResourceReference elements, linking to the respective ResourceReference IDs.

```xml
<ResourceList>
  <SoundRecording>
    <!-- ... -->
    <ResourceReference>A1</ResourceReference>
    <!-- ... -->
  </SoundRecording>
  <SoundRecording>
    <!-- ... -->
    <ResourceReference>A2</ResourceReference>
    <!-- ... -->
  </SoundRecording>
</ResourceList>
<ReleaseList>
  <Release>
    <!-- ... -->
    <ReleaseResourceReference>A2</ReleaseResourceReference>
    <ReleaseResourceReference>A1</ReleaseResourceReference>
    <!-- ... -->
  </Release>
</ReleaseList>
```

--------------------------------

### XML Sample: Main Release with Party and Resource Lists

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-contributors%2C-artists-and-writers/why-artist-information-is-in-multiple-places

This XML snippet demonstrates a DDEX NewReleaseMessage, including the MessageHeader, a PartyList with various parties involved, and a ResourceList containing a SoundRecording. It illustrates how different parties are defined and referenced within the message.

```xml
<ern:NewReleaseMessage xmlns:ern="http://ddex.net/xml/ern/41"     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"     xsi:schemaLocation="http://ddex.net/xml/ern/41 http://ddex.net/xml/ern/41/release-notification.xsd"     LanguageAndScriptCode="en">
    <MessageHeader>
        <MessageId/>
        <MessageSender>
            <PartyId>PADPIDA11111111111</PartyId>
        </MessageSender>
        <MessageRecipient>
            <PartyId>PADPIDA22222222222</PartyId>
        </MessageRecipient>
        <MessageCreatedDateTime>2015-09-15T10:00:00Z</MessageCreatedDateTime>
    </MessageHeader>
    <PartyList>
        <Party>
            <PartyReference>P0</PartyReference>
            <PartyName>
                <FullName>Jools Holland</FullName>
            </PartyName>
        </Party>
        <Party>
            <PartyReference>P1</PartyReference>
            <PartyName>
                <FullName>Jools Holland's Rhythm and Blues Orchestra</FullName>
            </PartyName>
        </Party>
        <Party>
            <PartyReference>P2</PartyReference>
            <PartyName>
                <FullName>Sting</FullName>
            </PartyName>
        </Party>
        <Party>
            <PartyReference>P3</PartyReference>
            <PartyName>
                <FullName>Willie Dixon</FullName>
            </PartyName>
        </Party>
        <Party>
            <PartyReference>P4</PartyReference>
            <PartyName>
                <FullName>George Harrison</FullName>
            </PartyName>
        </Party>
        <Party>
            <PartyReference>P5</PartyReference>
            <PartyName>
                <FullName>Dhani Harrison</FullName>
            </PartyName>
        </Party>
        <Party>
            <PartyReference>P6</PartyReference>
            <PartyName>
                <FullName>Paul Weller</FullName>
            </PartyName>
        </Party>
        <Party>
            <PartyReference>P7</PartyReference>
            <PartyName>
                <FullName>Billy Preston</FullName>
            </PartyName>
        </Party>
        <Party>
            <PartyReference>P8</PartyReference>
            <PartyName>
                <FullName>Bruce Fisher</FullName>
            </PartyName>
        </Party>
        <Party>
            <PartyReference>P10</PartyReference>
            <PartyName>
                <FullName>The Best Record Companuy, LLC</FullName>
            </PartyName>
        </Party>
    </PartyList>
    <ResourceList>
        <SoundRecording>
            <ResourceReference>A1</ResourceReference>
            <Type>MusicalWorkSoundRecording</Type>
            <ResourceId/>
            <DisplayTitleText>Seventh Son</DisplayTitleText>
            <DisplayTitle>
                <TitleText>Seventh Son</TitleText>
            </DisplayTitle>
            <DisplayArtistName>Jools Holland And
```

--------------------------------

### Define a MainArtist in XML

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-contributors%2C-artists-and-writers/displayartistroles

Example of a single main artist for a recording.

```xml
<!-- Cruel Summer --><Party>  <PartyReference>P1</PartyReference>  <PartyName>    <FullName>Taylor Swift</FullName>  </PartyName></Party>…<DisplayArtist>  <ArtistPartyReference>P1</ArtistPartyReference>  <DisplayArtistRole>MainArtist</DisplayArtistRole></DisplayArtist>
```

--------------------------------

### ERN 4.2 Release Visibility and Deal Terms

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/deals-and-commercial-aspects/availability-and-visibility

This example demonstrates release visibility and deal terms in ERN 4.2. It separates ReleaseVisibility from DealTerms, referencing it via ReleaseVisibilityReference. This allows for more granular control over when release information, cover art, and track listings can be displayed.

```xml
<DealList>  <ReleaseDeal>    <DealReleaseReference>R1</DealReleaseReference>    <Deal>      <DealTerms>        <ValidityPeriod>          <StartDateTime>2020-05-01T00:00:00Z</StartDateTime>        </ValidityPeriod>        <UseType>NonInteractiveStream</UseType>      </DealTerms>    </Deal>  </ReleaseDeal>    <ReleaseVisibility>    <VisibilityReference>V1</VisibilityReference>    <ReleaseDisplayStartDateTime>2020-02-01T00:00:00Z</ReleaseDisplayStartDateTime>    <CoverArtPreviewStartDateTime>2020-02-01T00:00:00Z</CoverArtPreviewStartDateTime>    <FullTrackListingPreviewStartDateTime>2020-03-01T00:00:00Z</FullTrackListingPreviewStartDateTime>          </ReleaseVisibility></DealList>
```

--------------------------------

### Define a Brand in XML

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-contributors%2C-artists-and-writers/displayartistroles

Example of a recording associated with a brand, using ERN 4.3.0 syntax.

```xml
<!-- Act a Fool --><Party>  <PartyReference>P1</PartyReference>  <PartyName>    <FullName>Ludacris</FullName>  </PartyName></Party><Party>  <PartyReference>P2</PartyReference>  <PartyName>    <FullName>Fast &amp; Furious</FullName>  </PartyName></Party>…<DisplayArtist>  <ArtistPartyReference>P1</ArtistPartyReference>  <DisplayArtistRole>MainArtist</DisplayArtistRole></DisplayArtist><DisplayArtist>  <ArtistPartyReference>P2</ArtistPartyReference>  <DisplayArtistRole>Brand</DisplayArtistRole></DisplayArtist>
```

--------------------------------

### Define a standard UseType value

Source: https://kb.ddex.net/implementing-each-standard/best-practices-for-all-ddex-standards/guidance-on-allowed-value-sets-%28avs%2C-aka-code-lists%29/user-defined-values

Example of using a standard DDEX-defined value for the UseType tag.

```xml
<UseType>Download</UseType>
```

--------------------------------

### DDEX RightShare Example

Source: https://kb.ddex.net/implementing-each-standard/musical-work-data-and-rights-communication-%28mwdr%29/musical-work-right-share-notification-standard-%28mwn%29/mwn-samples/mwn-response-providing-a-claim-with-co-ownership

This snippet shows a RightShare element for a MechanicalRight, including its controller, territory, and percentage.

```xml
<RightShare>
							<RightShareReference>S7185122</RightShareReference>
							<RightShareType>MechanicalRight</RightShareType>
							<RightsController>
								<RightsControllerPartyReference>P7185122</RightsControllerPartyReference>
							</RightsController>
							<RightSharePercentage>25</RightSharePercentage>
						</RightShare>
```
Tokens:
Raw