Solution for use in MLC 1.4

The PartyID/ProprietaryId element within the ConflictingParty composite can be used to communicate the contact details such as an email address or other contact details for an individual or a business division in the conflicting party organisation. This is in addition to being able to communicate a proprietary identifier that organisation itself.

(RDR-N 1.5 supports this requirement and RDR-RCC was developed to provide a standardised mechanism for communicating rights claim conflicts between parties using MLC 1.4, including the exchange of contact details for the parties involved. However, RCSUM of MLC 1.4 does not.)

The following rules should be observed when making use of this feature in MLC 1.4:

  • Contact identifiers for individual people should be grouped into a dedicated PartyId composite and should not be mixed with organisational identifiers within the same ConflictingParty composite;

  • Each person within the same organisation (e.g., Paul Brown and Christiana Oster in the example below) should have their own distinct PartyId composite containing their contact details;

  • If contact information is provided by different organisations (e.g., sender vs. recipient), use separate PartyId composites (as for COMPANY AB in the example below) — unless it is confirmed that both data sources refer to the same person (as for ORG XY in the example);

  • Always prefix contact information with the namespace corresponding to the DPID of the organization that provided it (as shown by the placeholders PADPIDASENDER or PADPIDARECIPIENT); and

  • To specify the form of contact the following IETF-defined tokens should be used:

    • For an email use mailto:john.doe@company.com (not: email:john.doe@company.com); and

    • For a web site use: http://company.com or https://company.com (and not web:company.com).

 

While the approach is acknowledged as a workaround, it remains fully compliant with the existing MLC 1.4 schema and does not introduce any structural changes. This workaround standardises the approach among organisations actively using RDx, ensuring consistent implementation and improved interoperability until broader adoption of newer RDR standards is achieved.

Search