5.9.4 Choreography via a Hub

The process of communication between an Acquiring Music Publisher, a Licensee and a Relinquishing Music Publisher via a Hub contains these steps:

  1. The Acquiring Music Publisher informs a Hub of a Catalogue transfer:

    1. The Acquiring Music Publisher calls the Web Service endpoint published by the Hub using the POST LoD call with an LoDMessage;

    2. The Hub replies with an Acknowledgement;

  2. The Relinquishing Music Publisher can confirm to the Hub that a Catalogue transfer has taken place, directly (in line with steps 1a and 1b above) or as a result of the Hub requesting the information:

    1. The Relinquishing Music Publisher regularly calls the Web Service endpoint published by the Hub using the GET LoDList call;

    2. The Hub replies with an LoDMessage;

    3. The Relinquishing Music Publisher regularly calls the Web Service endpoint published by the Hub using the PUT LoDConfirmation call;

    4. The Hub replies with an Acknowledgement;

  3. The Hub informs a Licensee about a Catalogue transfer:

    1. The Licensee regularly calls the Web Service endpoint published by the Hub using the GET LoDList call;

    2. The Hub replies to this with an Atom feed providing a URL for all LoDMessages that are ready to be collected;

    3. The Licensee can then call the Hub's GET LoD Web Service endpoint for each URL provided in step 3b to which the Hub will respond with the requested LoDMessage.

A Hub may wish to use one Web Service endpoint for the GET LoDList calls defined above and the GET ClaimRequestList and GET ClaimNotificationList calls defined in the Musical Work Right Share Notification Choreography.

These steps are depicted below.

Search