5.3.2 Hub-based Choreography
The processes of communicating through a Hub comprises the following steps, it should be noted, that the approach to the communication between (prospective) Licensee and a Hub, and the communication between a (prospective) Licensor and the Hub are (virtually) identical:
The Hub replies to this call with an Atom feed providing URLs for all
MusicalWorkRightsClaimNotificationMessages that are ready to be collected;
The Hub will respond with the requested
The Hub replies to this call with an Atom feed providing a URL for all
MusicalWorkRightsClaimRequestMessages that are ready to be collected;
The Hub replies to this call with a
18.104.22.168 Identification of specific Claim Requests
One crucial aspect for companies making or releasing (or planning to make or release) a sound recording that makes use of a Musical Work is to establish the various applicable Right Shares for said Musical Work. For this, a (prospective) Licensee typically does some research in order to collate a list of companies it believes own or administer (part of) the Musical Work and from whom a licence can be sought. The company would typically then contact all (prospective) Licensors to establish their Shares before attempting to obtain licences.
When obtaining such Right Share information from a Hub, it is essential that the (prospective) Licensee can link right share notifications to its Right Share requests so that it can determine if all of its requests have been replied to (or not). To support this,
MusicalWorkRightsClaimNotificationMessage carry identifiers that a Hub will need to handle appropriately as follows:
Field in the MusicalWorkRightsClaimRequestMessage (as provided by the prospective Licensee to the Hub)
Field in the MusicalWorkRightsClaimNotificationMessage (as provided by the prospective Hub to the prospective Licensee)
The field shall be omitted in all other cases.