NewReleaseMessage shall be named as follows:
Each Resource file shall be named as follows:
ErnAcknowledgementStatusMessage shall be named as follows:
ReleaseIdbeing the identifier used in the
NewReleaseMessageto 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 (“-“).
TechnicalResourceIdbeing 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.
ResourceTypebeing 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
CoverArtor even an abbreviation such as
WPfor a wallpaper Resource. This element is primarily for human intervention.
Hierarchybeing 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
Hierarchyelement should correspond to the
ResourceGroupcomposite in the
YYYYMMDDhhmmssnnnbeing the date and time that the Release is placed on the ftp server.
ErnMessageIdbeing the ID used in the
- Ext being the typical file extension for the Resource type (or .xml for the
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.