Candidate Standard

Skip to end of metadata
Go to start of metadata

The figures below depict the choreography defined by this standard. 

This standard supports two approaches to exchanging Right Share information: Either a (prospective) Licensee and a (prospective) Licensor can exchange information directly with one another, or the communication can be communicated via a central Hub which may act as a information routing service and/or as a Right Share information cache.

Figure 1: Direct communication between a (prospective) Licensee and a (prospective) Licensor


Figure 2: Communication between a (prospective) Licensee and a central Hub


Figure 3: Communication between a central Hub and a (prospective) Licensor

 

The table below summarises the points in the Musical Work Right Share Notification Choreography that a message is sent.

Message Name

Initiating Event

SenderRecipient

1a

MusicalWorkClaimRequestMessage

If a record company, DSP, Hub or other company wishes to receive information about a Musical Work and/or its ownership (e.g. for the purposes of obtaining a licence or to make available or monetise a Release containing a Musical Work) but has no, or insufficient, claims or Right Share information.

This also applies when a record company, DSP, Hub or other company wishes to update its request (e.g. because of changes to the writer or publisher information). This is only illustrated in Fig. 1, but also applies to the choreographies involving a Hub (Figs. 2 and 3).

(prospective) Licensee(prospective) Licensor
1b(prospective) LicenseeCentral Hub
1cCentral Hub(prospective) Licensor

2a

MusicalWorkClaimNotificationMessage

If a Works Licensor or Hub wishes to inform a DSP or Hub about its own or other companies' claims or Right Share information with respect to Works embodied in a Release [1]

  • In response to a MusicalWorkClaimRequestMessage or
  • Based on a trigger other than the receipt of a MusicalWorkClaimRequestMessage. Such triggers may include the case where the Licensor has previously provided a Right Claim for a Musical Work and subsequently loses the rights to that Right Share or Musical Work, or the resolution of a Right Share ownership conflict.

This also applies when a Works Licensor or Hub wishes to update a previously sent MusicalWorkClaimNotificationMessage. This is only illustrated in Fig. 1, but also applies to the choreographies involving a Hub (Figs. 2 and 3).

 
(prospective) Licensor(prospective) Licensee
2b(prospective) LicensorCentral Hub
2cCentral Hub(prospective) Licensee
3MusicalWorkClaimRequestRecallMessage

If a record company, DSP, Hub or other company notices that it no longer requires claim information and wishes to recall its MusicalWorkClaimRequestMessage.

This is only illustrated in Fig. 1, but also applies to the choreographies involving a Hub (Figs. 2 and 3).

(prospective) Licensee(prospective) Licensor
(prospective) LicenseeCentral Hub
Central Hub(prospective) Licensor

 

The exchange of the information in these messages can be effected by two different message exchange protocols: SFTP and Web Services. Details on these are defined in Clauses 5.2 ad 5.3 respectively.

 


[1] As indicated, the message can be used by a Licensor to communicate ownership information regarding a Musical Work not owned or controlled by the sender of the message. In that case, the recipient may use the information not as authoritative but solely as “helpful information”.

  • No labels