Search

5.1 Data exchange between rights holders and CMOs or DSPs

The figure below depicts the choreography of message exchange between rights holders and collective management organisations (CMOs), digital service providers (DSPs) or other business partners using the messages defined in this standard.

Figure 1 – Direct communication between a rights holder (or other licensor) and a CMO or DSP (or other business partner)

The table below summarises the points at which the messages defined in this standard are sent.

Message Name		Initiating Event	Sender	Recipient
1	`MusicalWork` `ClaimRequest` `Message`	If a CMO or DSP (or other business partner) wishes to receive information about a musical work and/or right share data (e.g. for registering a musical work).	CMO or DSP (or other business partner)	Rights holder (or other licensor)
2	`MusicalWork` `ClaimNotification` `Message`	If a rights holder or other licensor wishes to inform a CMO or DSP (or other business partner) about its musical work and/or right share data because: It has received a `MusicalWorkClaimRequestMessage`; or because Another trigger has occurred. Such triggers may include circumstances where the rights holder has acquired the rights in a musical work and wishes to register it. This also applies when a rights holder or other licensor wishes to update a previously sent `MusicalWorkClaimNotificationMessage` because some data has changed. In such a case the second `MusicalWorkClaimNotificationMessage` shall update all the data in respect of the same musical work and/or right share data sent in the first `MusicalWorkClaimNotificationMessage`. This also applies when a rights holder or other licensor has noticed that a CMO or DSP (or other business partner) has stored right share data for a musical work that the rights holder has no interest in and so wishes to revoke such claim. In such a case a `MusicalWorkClaimNotificationMessage` can be sent to communicate a revocation.	Rights holder (or other licensor)	CMO or DSP (or other business partner)
3	`MusicalWork` `ClaimRequest` `Message`	If a rights holder or other licensor wishes to receive information about a musical work and/or right share data stored by a CMO or DSP (or other business partner), e.g. for verifying the registration of a musical work.	Rights holder (or other licensor)	CMO or DSP (or other business partner)
4	`MusicalWork` `ClaimNotification` `Message`	If a CMO or DSP (or other business partner) wishes to inform a rights holder or other licensor about the musical work and/or right share data stored in its systems because: It has received a `MusicalWorkClaimRequestMessage`; or because Another trigger has occurred. Such triggers may include circumstances where the CMO or DSP (or other business partner) has detected a conflict relating to the musical work and/or right share data registered by the rights holder or other licensor. In the case of a conflict the `MusicalWorkClaimNotificationMessage` contains musical work and/or right share data received by the CMO or DSP (or other business partner) from other rights holders or other licensors.	CMO or DSP (or other business partner)	Rights holder (or other licensor)
5	`MusicalWork` `ClaimRequest` `RecallMessage`	If a sender of a MusicalWorkClaimRequestMessage notices that it no longer requires musical work and/or right share data and wishes to recall its MusicalWork ClaimRequestMessage.	CMO or DSP (or other business partner)	Rights holder (or other licensor)
6	`MusicalWork` `ClaimNotification` `RecallMessage`	If a sender of a `MusicalWorkClaimNotificationMessage` notices that it has sent the message in error and wishes to recall it.	Rights holder (or other licensor)	CMO or DSP (or other business partner)

While this choreography primarily describes the exchange of messages between different types of companies, e.g. between rights holders and CMOs, it is also applicable to the exchange between companies of the same type, e.g. between rights holders wishing to send information about a musical work and/or right share data to another rights holder.