Generating a MusicalWorkClaimNotificationMessage in response to a MusicalWorkClaimRequestMessage

This guideline document describes how a music publisher that has received a MusicalWorkClaimRequestMessage via a hub or directly from a record company should proceed when generating a MusicalWorkClaimNotificationMessage as a response.

General Rules

The overall structure of the MessageHeader element will be retained and elements from the MessageHeader of the request message will be re-used in the claim notification. For further details on the message header see below.

The PartyList element from the request message will be re-used. The sender of the claim notification may make amendments to the party information, so that the Party data may differ between request and notification.

The WorkList, ReleaseList and ResourceList elements from the request message will be retained in the claim notification. Formatting and values will be the same as received.

Message Header

The MessageId element from the claim request cannot be reused, as this identifier is unique per sender and two senders using the same identifier would cause the two claim notifications to have the same identifier. Also, multiple claim notifications in response to the same message need to have different identifiers. Therefore, an algorithm that creates a unique identifier for each claim notification has to be established.

The MessageSender element of the claim notification message can be hardcoded for all messages.

A recipient of a MusicalWorkClaimRequestMessage shall always reply to the sender of that message, whether it comes directly from a record company or whether it has been forwarded by a hub. Therefore, the data of the MessageSender element is copied to the MessageRecipient element.

If the request message has been forwarded by a hub, the SentOnBehalfOf element in the request message contains the details of the record company which the request had been issued on behalf of. The party specified in this SentOnBehalfOf element is not included in the response message.

The PartyId (a DPID) and PartyName elements can be taken from the claim request.

The MessageCreatedDateTime element captures the time at which the message is created. This has to be in the ISO 8601:2004 format with a time zone designator.

Party List

If available, parties need to have an IPI name number included in PartyId (in the IpiNameNumberelement). The IPI name number should be provided for all controlled writers, original publishers, sub-publishers and administrators. Uncontrolled writers do not have this populated.

Any proprietary identifiers which are included on the claim request should be included for further associated parties in their response.

The PartyName elements should not be taken from the claim request, but should be populated with the correct information from the internal systems of the message creator.

The NamesBeforeKeyName and KeyName elements should be added in the claim notification and populated with first and last name respectively.

Any additional writers not included in the original claim request need to be added to the PartyList. They need to have a new PartyReference identifier, the format for which is "P" followed by any number of characters (letters or numbers), which needs to be unique within the message. This PartyReference is solely to allow the referencing of a party from the different parts of the claim notification; the PartyReference has no applicability outside of the message.

The writers should then have their IpiNameNumber, FullName, NamesBeforeKeyName and KeyName elements populated from the internal systems of the message creator.

The IsOrganization flag needs to be set, if the party is a writer, to false and, if the party is a publisher, administrator or sub-publisher, to true.

Work List

In the MusicalWorkId element, the following data from the internal systems of the message creator is needed:

• The ISWC of the work if available (for the ISWC element); and

• Any proprietary identifier (for the ProprietaryId element, where the Namespace attribute is set to the DPID of the message creator).

In addition, each Work element needs to have a MusicalWorkReference element, the format for which is "W" followed by any number of characters. This reference identifier needs to be unique within the MWN message. This MusicalWorkReference is solely to allow the referencing of a work from the different parts of the claim notification; the MusicalWorkReference has no applicability outside of the message.

The controlled parties with a MusicalWorkManuscriptShare for the work need to be listed in the Writer element. The writer reference identifiers and roles which are controlled are listed in WriterPartyReference and Role elements respectively. Multiple references can exist depending on the controlled writers with a MusicalWorkManuscriptShare. The Writer ties back to an entry in the PartyList via the PartyReference attribute.

The Role element is populated for each party based on the CreativeMusicalWorkContributorRole allowed value set and may use a proprietary value from the internal systems of the message creator (in which case the Namespace attribute is set to the DPID of the message creator).

Titles in the claim request need to be matched against what is stored in the internal systems of the message creator. The data from the internal systems should be used to populate the TitleText element.

Right Share List

The RightShareList element with the claim information relevant to the response has to be created. Each right share in the list needs a RightShareReference element, the format for which is "S" followed by any number of characters. The reference identifier only needs to be unique within the MWN message. This RightShareReference is solely to allow the referencing of a right share from the different parts of the claim notification; the RightShareReference has no applicability outside of the message.

The RightShareWorkReference element includes the reference assigned to the work in the WorkList (in the MusicalWorkReference element).

Right Share Notification List

For each request that is responded to in the response message, a right share notification has to be added in the RightShareNotificationList element.

The NotificationId element is the identifier of the claim notification (not the identifier of the claim notification message). If an update to such a claim notification is issued, this identifier is put into the PreviousNotificationId element of the update message.

The RequestId element is the identifier of the request that the notification is responding to. This is a proprietary identifier specified by the sender of the request in the RequestId element in the RequestList and must be copied from there (including the Namespace attribute).

The RightShare element is the right share which is responded with in the claim notification and which is linked to the RightShareList using the RequestRightShareReference element. The value for this element is the RightShareReference element of the entry in the RightShareList.

The RightShareNotificationList element may also include right shares marked as uncontrolled.

The RightsControllerRequestId element shall be included against each entry in the RightShareNotificationList if it is given in the request message (in the RightsControllerRequestId element of the MusicalWorkShareRequest). This proprietary identifier specified by the sender of the request helps to associate the response with a specific request.