Territorial Variations in the SoundRecordingDetailsByTerritory Composite in RDR-N
DeclarationOfSoundRecordingRightsClaimMessage of the RDR-N Standard, the
SRDBT) composite within
ResourceList/SoundRecording composite can be repeated to indicate territorial differences. The type of information contained within this composite and the flexible nature of a repeating element creates some challenges. Guidance for message senders is needed so that users adopt a standardised approach and message recipients can reliably process such declarations.
While this document focuses on the best-practice for the message sender for RDR-N version 1.5, guidance for MLC version 1.4 elements that have been removed from the SRDBT composite in RDR-N 1.5 will be given in section 3 of this document. The structure of the SRDBT composite varies with respect to the
For detailed guidance on how to implement the SRDBT composite in MLC 1.4 please see the following article on the Knowledge Base.
This guidance is equally applicable to
Guidance for version 1.5
One (and only one)
There should be one occurrence of the
Please see 9 as an exception to this principle.
No use of
The XSD provides a choice when listing territories within
TerritoryCode not repeated across SRDBT elements
A territory should only be referenced once across all
SRDBT should use a list of
Territory types to use in
The territories declared in
HostSoundCarrierelement(s) only declared in default/worldwide SRDBT tag
Host Sound Carrier
For simplicity, all the Releases (host sound carriers) that the Resource is released on should be declared in the
Guidance for version 1.4
In RDR-N 1.5 the SRDBT has been simplified by moving the
OtherContributor composites up one level. Due to the structural differences between the two versions of the standard the below two principles need to be also taken into consideration in addition to principles 1 to 9 listed above.
RightsController sits within the
SRDBT composite, principle A below is the exemption to principle 2 above.
The XSD makes the
As the contributions to a Resource do not vary by territory, the performing contributor(s) and other contributor(s) should only be listed once in the