ClusterId, ClusterCreatorClusterId, RequestClusterId
In ECM exchanges, the MessageId sits at the message level and uniquely identifies an entire message instance. Within that message, the ClusterId identifies each individual cluster to be communicated. Each cluster contained in a message must be uniquely identified by the MessageSender; this identifier serves as the anchor for subsequent references to that cluster in both the MusicalWorkClusterNotification and the DuplicateIsrcClusterNotification.
Global uniqueness of cluster identifiers
Parties that create a cluster shall ensure that any ClusterIds, when taken together with the relevant Namespace, are globally unique.
Relationship between request and notification messages
A notification message may be sent in response to none, one, or more request or notification messages.
ClusterId
The ClusterId is a globally unique proprietary identifier assigned by the MessageSender to the specific cluster being communicated. Depending on the dialogue, the same identifier may subsequently appear as a RequestedClusterId or a ClusterCreatorClusterId in a response message.
A ClusterId is expressed as a ProprietaryId composite comprising:
An optional
Namespace, andA mandatory
Value.
The ClusterId is a ProprietaryId composite, used to uniquely identify an individual cluster as sent by the message sender. The ClusterId, in combination with the message sender’s DdexPartyId (DPID), shall be globally unique. A message sender shall never re-use a ClusterId once assigned.
RequestedClusterId
RequestedClusterId is a ProprietaryId composite that carries the cluster identifier originally assigned by the sender of a request message. It is only required when the notification message explicitly responds to a request message, enabling the recipient to correlate the response with a specific, previously communicated cluster.
ClusterCreatorClusterId
ClusterCreatorClusterId is a ProprietaryId composite included in a notification message to reference a cluster identifier originally assigned by the creator of the cluster. It is required only when a notification is sent in response to another notification message. In that case, the ClusterId of the initial notification message shall be repeated in the ClusterCreatorClusterId to maintain a robust linkage between related cluster messages.
