Skip to end of metadata
Go to start of metadata

Declaration

The sample Declaration claims a few ficticious resources. The message is compliant with the XSD and has been successfully verified against RDx.

The message structure is quite simplistic but does include all the main claim elements: SoundRecording; SoundRecordingDetailsByTerritory; Artist; Contributor; Composer; RightsController and HostSoundCarrier.

Download sample

Requests

These are sample "Request" messages which validate against the XSD and are successfully tested against RDx.

The first example contains a request which specifies the ISRC of the requested Resource. Although only one Request node is included, multiple can be included as siblings beneath the header node.

The second example  contains a request which specifies the original source's ProprietaryId of the requested Resource, specified under namespace of the source of the ProprietaryId. Although only one Request node is included, multiple can be included as siblings beneath the header node.


Request messages can in generally make a request using the structures specified in the XSD, including by reference to the artist name or track title. The samples here do not illustrate these other approaches.

Download sample 1; download sample 2

Revoke

The sample Revoke message asks the message recipient to revoke a list of claims that have been made in error.  The message complies with the XSD and has been successfully tested against RDx. Each resource specified within the list for revocation is specified using both the ISRC of the Resource and the ProprietaryId of the claimant which is the party issuing the Revoke.  The ProprietaryId is specified in its namespace in the normal way.  Messages would be logically inconsistent unless the ISRC and the ProprietaryId both refer to the same claimed Resource.

Download sample

  • No labels