Skip to end of metadata
Go to start of metadata

All DDEX messages allow the communication of proprietary identifiers in addition to standardised and widely-used industry identifiers such as ISRCs for recordings, ISWCs for musical works and ISNIs for parties. The syntax to communicate such proprietary identifiers is described on https://kb.ddex.net/display/HBK/Proprietary+Identifiers. As indicated there, each proprietary identifier must be accompanied by a namespace that identifies the organisation that is responsible for maintenance and governance of the relevant identification system. The namespace is usually in form of a DPID.

The following snippet contains a proprietary identifier created in accordance with the system maintained by the organisation with DPID PADPIDA2014122301Q:

<ProprietaryId Namespace=”PADPIDA2014122301Q”>0815</PropriataryId> 

In some cases, a company may operate multiple identification systems. In that case it is not only essential to communicate the organisation that is responsible for maintenance and governance of these identification systems, but also the identification systems themselves. 

To indicate different proprietary identifications systems, the identifier needs to be preceded by a string identifying the identification system followed by a colon. The two snippets below provide two proprietary IDs from PADPIDA2014122301Q’s sound recording and music video identification schemes.

 <ProprietaryId Namespace=”PADPIDA2014122301Q”>video:0815</PropriataryId>

and

<ProprietaryId Namespace=”PADPIDA2014122301Q”>audio:0815</PropriataryId>

 

It is the organisation maintaining the identification systems – in this case PADPIDA2014122301Q’s – responsibility to work with its business partners to agree the appropriate prefixes.

  • No labels