5 Choreography
Figure 1 shows the choreography of processes that this standard enables. Table 1 summarises the point in the relevant business processes when the message is sent. The table also indicates who sends the message to whom.
The use of an Acknowledgement Message, shown as ACK, is optional and not defined in this standard.
Figure 1 - Simple scenario of the choreography of the Recording Data and Rights Revenue Reporting Standard
Figure 2 – Two-step scenario of the choreography for the Recording Data and Rights Revenue Reporting Standard
| Message Name | Initiating Event | Message Sender | Message Recipient |
|---|---|---|---|
| A Music Licensing Company has generated revenue for a Sound Recording or Music Video for which it has received a claim and wishes to report these revenues to a Recording Rights Controller | Music Licensing Company (Collecting Music Licensing Company and Paying Music Licensing Company) | Recording Rights Controller that made a claim for the Sound Recording or Music Video to the Collecting Music Licensing Company |
| A Music Licensing Company has generated revenue for a Sound Recording or Music Video for which it has received a claim and wishes to report these revenues to the Claiming Music Licensing Company | Music Licensing Company (Collecting Music Licensing Company and Paying Music Licensing Company) | Music Licensing Company (Claiming Music Licensing Company) that made a claim for the Sound Recording or Music Video to the Collecting Music Licensing Company |
RevenueDeclarationMessage | A Music Licensing Company has received a revenue report from a Collecting Music Licensing Company and wishes to report these revenues to a Recording Rights Controller | Music Licensing Company (Paying Music Licensing Company) | Recording Rights Controller that made a claim for the Sound Recording or Music Video to the Paying Music Licensing Company (Claiming Music Licensing Company) |
Table 1 – Messages in the Recording Data and Rights Revenue Reporting Standard