RDR-N: SoundRecording (version 1.5)

Each SoundRecording composite itself comprises two main sections of information, firstly details at the SoundRecording level, which are invariant across territory; then one or more SoundRecordingDetailsByTerritory composites containing territory-specific information for that SoundRecording. The same principle also applies to the Video composite.

The "Recommended Profile" is what DDEX recommends is sent, at a minimum, from record companies to music licensing companies as well as from music licensing companies to other music licensing companies in order to register a claim. The data set has been defined because it will enable most music licensing companies to accept the claim as stated and thus collect revenue for the rights holder. In some cases it may not be possible for the sender of the message to collate all the data elements listed in the "Recommended Profile". In that case the message sender should consider using the "Core Data Profile". This data set typically allows a claim to be registered, but the data provided may not be sufficient, on their own, to enable the music licensing company to accept the claim and thus undertake the correct collection of revenues. Amalgamated with data from other sources it may, however, be possible for music licensing companies to collect revenues and to pay out.

In the table below, tags are shown as "mandatory" or “include” as within the core or the recommended datasets for a recording, and thus core or recommended for inclusion in Declaration messages. The tags marked as "mandatory" are to ensure that implementers deliver messages that are technically valid agains the XSD. The tags shown as "include" have been added to provide practical guidance to record companies (and other senders of the claim message) on which data is generally needed by music licensing companies on operational grounds:

It is noted for good order that DDEX is not able to give definitive advice on the data policy of any specific music licensing company as there may be bilateral and contractual requirements for additional data sets – the table below is for general guidance.

In Version 1.5 the SoundRecording composite has been extended, which is partly due to simplifications made on the SoundRecordingDetailsByTerritory composite level. It now also includes the RightsController, PerformingContributor, OtherContributor and InitialProducer composites and new elements listed here: Upgrading from Version 1.4 to Version 1.5.

The LanguageAndScriptCode applied at this level applies to all child nodes, unless overridden in any of the child nodes.

<SoundRecording IsUpdated="true" LanguageAndScriptCode="fr">
 
    <SoundRecordingType Namespace="PADPIDA2007061301U">MusicalWorkSoundRecording</SoundRecordingType>
    <IsArtistRelated>true</IsArtistRelated>
    <SoundRecordingId IsReplaced="false">
        <ISRC>FRUM70701194</ISRC>
        <CatalogNumber Namespace="PADPIDA2007061301U">123456</CatalogNumber>
        <ProprietaryId Namespace="PADPIDA2007061301U">00010075760152</ProprietaryId>
    </SoundRecordingId>
 
    <ResourceReference>A00010075760152</ResourceReference>
 
    <ReferenceTitle>
        <TitleText>100 VIP</TitleText>
    </ReferenceTitle>
 
    <IsMedley>false</IsMedley>
    <IsPotpourri>false</IsPotpourri>
    <IsInstrumental>false</IsInstrumental>
    <IsBackground>false</IsBackground>
    <IsHiddenResource>false</IsHiddenResource>
    <IsBonusResource>false</IsBonusResource>
    <IsComputerGenerated>false</IsComputerGenerated>
    <NoSilenceBefore>true</NoSilenceBefore>
    <NoSilenceAfter>true</NoSilenceAfter>
 
    <Duration>PT0H2M54S</Duration>
 
    <CreationDate 
        IsApproximate="false" 
        IsBefore="false" 
        IsAfter="false" 
        ApplicableTerritoryCode="FR">2008-09-26</CreationDate>
    <MasteredDate 
        IsApproximate="false" 
        IsBefore="false" 
        IsAfter="false">2008-09-26</MasteredDate>
 
    <SoundRecordingDetailsByTerritory>
        <!-- described in a following section -->
    </SoundRecordingDetailsByTerritory>
 
</SoundRecording>

Mandatory Fields

[1] The date of birth is a key field for many music licensing companies to disambiguate contributors. It is therefore recommended that message senders provide this information at all times, assuming they have access to it.

Implementation Notes

The following notes are more detailed guidelines including sample data for some of the tags listed in the above table.

• SoundRecordingType – in most cases, parties will be communicating details of a MusicalWorkSoundRecording; a SoundRecording that is related to a musical work (as opposed to SoundRecordingType of an audio book or ambient recording, say).

• OriginalResourceReleaseDate can be to the nearest year and is used by music licensing companies in assessing whether the copyright term has expired or not.  The ApplicableTerritoryCode conveys the country(ies) of (simultaneous) first publication, which is a “point of attachment” determining eligibility under the treaties.

• The IsReplaced flag in the SoundRecordingId tag indicates whether this Identifier is old and has been replaced by a new one (=true) or not (=false). The Flag may only be set to True when the new Identifier is also provided.

• IsArtistRelated - is an optional Boolean that flags whether the resource is related to an artist. In most cases this will be set to “true”.

• While the  ResourceReference  field is superfluous for the communication of claims, it is technically mandatory in the current RDR-N standard.  Each SoundRecording is identified locally within the scope of a single message by an anchor reference formed of the letter ‘A’ concatenated with an integer that increments for each SoundRecording composite. 
  The example shows is for the first SoundRecording. The second would contain a value ‘A2’ and so on. These references need only be unique within in a given message.

<ResourceReference>A1</ResourceReference>

• ReferenceTitle - This is part of the 'reference descriptive metadata' for the recording.  It is structured as the TitleTextand SubTitle. In the DDEX standards, the TitleText is for the normal title of a recording and the SubTitle is a catch-all for version and/or subtitle information.  
  SubTitle is used to differentiate different recorded versions such as ‘live’, ‘radio edit’, ‘extended mix’ etc.  The language of the title is carried within the tag (represented by an ISO 639 LanguageCode).

<ReferenceTitle LanguageAndScriptCode="en">
 <TitleText>My Song</TitleText>
 <SubTitle>Album Version</SubTitle>
</ReferenceTitle>

• CreationDate - The date of First Fixation / Date of Recording, to the year.  (Ref. Rome Convention.)
  The flag IsApproximate can be included in the tag when specifying the date to the year (which is all that is required by most music licensing companies).  The ApplicableTerritoryCode is the country of First Fixation.  (Note: nationality of producer is separately within the InitialProducer composite.)
  The ApplicableTerritoryCode here at the SoundRecording level is the territory where the majority of the recording took place.

<CreationDate IsApproximate="true" ApplicableTerritoryCode="GB">2011-01-01</CreationDate>

• PerformingContributor
  Some music licensing companies need data about the contributors to a recording and the nature of their contributions, so that contributors that are eligible and qualifying for equitable remuneration can be paid.  The “contribution category” of a contributor can be “featured” or “non-featured”, and “contracted” or “non-contracted”. This information is communicated using the flags HasMadeFeaturedContribution and HasMadeContractedContribution in PerformingContributor\Contribution. Music licensing companies use the contribution category along with the role and/or roles in determining remuneration.

A PerformingContributor is either an individual person or a collective (such as an orchestra), referred to by their name and/or the identifier used to designate them within systems such as SCAPR’s IPD.

A “featured” contribution is one made by a performer who is prominently featured in relation to the release (as opposed to a session musician, who would typically make a “non-featured” contribution).

There will often be multiple PerformingContributors, enumerated using the SequenceNumber attribute.  For each PerformingContributor, the following are necessary:

• PartyName\FullName

  • PartyId\IPN (if available)

  • PartyId\ProprietaryId with the sender’s proprietary ID

  • DateAndPlaceOfBirth (place is optional) [1]

  • Contribution\Role

  • Contribution\InstrumentType

  • Contribution\HasMadeFeaturedContribution

  • Contribution\HasMadeContractedContribution

  • Contribution\Event

Roles – Within the PerformingContributor composite each Contribution node composite expresses one Role in which the performer has contributed to the recording. 

Roles such as soloist, musician, conductor, and so on can be expressed using DDEX role values or if appropriate using SCAPR SDEG role codes. InstrumentType details can also be provided, and the Event element can convey the date and location of the performance.

<PerformingContributor>
    <PartyName>
        <FullName>Joe Cocker</FullName>
    </PartyName>
    <PartyId>
        <ISNI>0000000109078187</ISNI>
        <ProprietaryId Namespace="PADPIDA123456789">123
            </ProprietaryId>
    </PartyId>
    <Contribution>
        <Role>Vocalist</Role>
        <HasMadeFeaturedContribution>true
            </HasMadeFeaturedContribution>
    </Contribution>
</PerformingContributor>

• RightsController - This is mandatory along with the following fields

  • PartyName\FullName

  • PartyId\ProprietaryId with the sender’s proprietary ID.  Local producer ID is always used by music licensing companies.

  • PartyId\ProprietaryId with the recipient’s proprietary ID

  • RightsControlType – This is necessary for several music licensing companies. Type of rights holder can be ExclusiveLicensee, LocalPayee, OriginalOwner, RightsAdministrator, or SuccessorInTitle as defined by the DDEX AVS.

  • RightsStatement\UseType. The type of use for which the recording may be licensed.  This takes a value from the DDEX AVS.

  • RightsStatement\ExcludedUseType. This provides details of the use for which Rights are not delegated. 

  • RightsStatement\Period. This provides details about a Period of Time for which the delegation of usage Rights applies. 

  • RightsStatement\Territory. This is to provide information on territories for which the delegation of usage rights applies expressed as ISO 3166-1 alpha-2 codes or Worldwide. 

  • RightsStatement\ExcludedTerritory. This is to provide information on territories for which the delegation of usage rights does not apply.