DDEX Standard

Skip to end of metadata
Go to start of metadata

The NewReleaseMessage shall be named as follows:

ReleaseId.Ext

Each Resource file shall be named as follows:

Label_ReleaseId_TechnicalResourceId_ResourceType_Hierarchy.Ext

The  ErnAcknowledgementStatusMessage shall be named as follows:

 

ACK_ErnMessageId_YYYYMMDDhhmmssnnn.Ext

With:

  • ReleaseId being the identifier used in the NewReleaseMessage to uniquely identify the Release.
  • Label being an optional, mnemonic token to identify the company compiling the Release. This element is primarily for human intervention and may only contain letters, digits and dashes (“-“).
  • TechnicalResourceId being an optional string, starting with the letter “T”, that is used in the NewReleaseMessage' s relevant XML tag of the same name to uniquely identify the Resource.
  • ResourceType being an optional element to indicate the type of resource (typically where this is not clear from the Ext element). This may be a generic value such as "SoundRecording" or it may be used to designate a more specific type such as CoverArt or even an abbreviation such as WP for a wallpaper Resource. This element is primarily for human intervention.
  • Hierarchy being an optional element to indicate where, in the hierarchy of the Release the Resource fits. This element should comprise of a sequence of three-digit, zero padded numbers separated by underscores (e.g. 008_015 for the 15th Resource in the 8th Resource Group). This Hierarchy element should correspond to the ResourceGroup composite in the NewReleaseMessage.
  • YYYYMMDDhhmmssnnn being the date and time that the Release is placed on the ftp server.
  • ErnMessageId being the ID used in the ReleaseNotificationMessage being acknowledged.
  • Ext being the typical file extension for the Resource type (or .xml for the NewReleaseMessage, PurgeReleaseMessage or ErnAcknowledgementStatusMessage).

The Resource file name in accordance with this clause is only guaranteed to be unique and useful for the duration of the Release delivery (i.e until an acknowledgement has been sent).

This naming convention is not necessary for machine-to-machine communication but adherence to this convention will aid human intervention for cases where such intervention is necessary.

  • No labels