6.7 Structure of the Duplicate ISRC Cluster Notification

The structure of the DuplicateIsrcClusterNotification is described in below. DuplicateIsrcClusterNotifications shall be communicated with the message exchange protocol defined in Part 1 of the ECM standard.

The DuplicateIsrcClusterNotification can be used to communicate 0-n Duplicate ISRC Clusters, and contains five sub-elements as depicted in Figure 3:

  • A mandatory @AvsVersionId communicates the version of the allowed value sets used in the message;

  • The mandatory LanguageAndScriptCode communicates the language and script for the elements of the message as defined in IETF RfC 5646. Language and script are communicated using the syntax lang[-script][-region][-variant];

  • A mandatory MessageHeader communicates general message metadata as depicted in Figure 4;

  • A mandatory PartyList with 1-n Party composites (depicted in Figure 5) describing parties related to musical works or recordings referenced from the Duplicate ISRC Clusters. Each Partymust have either a PartyName or a PartyId but may also have both; and

  • A mandatory array of IsrcClusters as depicted in Figure 6 that describes 1-n Duplicate ISRC Clusters through:

    • A mandatory ClusterId, a unique identifier of the Duplicate ISRC Cluster allocated by the message sender;

    • An optional ClusterCreatorClusterId, a unique identifier of the Duplicate ISRC Cluster allocated by the party that originally created the cluster. This 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 link between related messages.

    • An optional array of RequestedClusterId, linking the Duplicate ISRC Cluster back to DuplicateIsrcClusterRequest(s);

    • An optional ClusterCreator, referencing the Party composite describing the party that originally created the cluster;

    • A mandatory ClusterRoot, describing the resource that begets the Musical Work Cluster (see Figure 7); and

    • An optional array of ClusterMembers, describing the resources that make up the Duplicate ISRC Cluster (see Figure 8).
      Whether the ISRC designated as the ClusterRoot is also included as a ClusterMember (or not) is governed by bilateral agreements between the Message Sender and Message Recipient.

 

The ISRC specified in a DuplicateIsrcClusterRequest must be included as either the ClusterRootor a ClusterMember in the corresponding DuplicateIsrcClusterNotification, as determined by the sender of the notification. 

3.png

Figure 3 – Structure of the DuplicateIsrcClusterNotification

4.png

Figure 4 – Structure of the MessageHeader composite

5.png

Figure 5 – Structure of the Party composite

 

6.png

Figure 6 – Structure of the IsrcCluster composite

7.png

Figure 7 – Structure of the ClusterRoot composite

8.png

Figure 8 – Structure of the ClusterMember composite

Search