Version 1.8 has generalised this part of the ERN standard to all types of cloud-based data storage servers whereas the versions up to version 1.7 supported SFTP only. Version 1.8 also removes support for the hard disk delivery profile and changes the file naming convention to support multiple resource files for a single Primary Resource.

Version 1.7 harmonised the communication of acknowledgements and release status between the SFTP and web service choreographies.

Version 1.6.1 fixed a bug in the description of the file naming convention.

Version 1.6 split the choreography for the communication of ERN messages (originally in one part of the ERN standard) into an SFTP profile (defined in this part of the ERN standard) and a web service profile (defined in Part 4 of the ERN standard). The SFTP profile now also supports the signalling of priority deliveries on file-system level. It also removes the provision that permits the communication of release information using insecure FTP servers.

Version 1.5 introduced small changes to the file naming convention and aligned it with current practice across all DDEX standards.

Version 1.4 simplified the process of acknowledging the ingestion of a release or batch of releases using the FTP profile by providing a simplified acknowledgement message. It also added error codes and makes sending acknowledgements mandatory. It also changed the file name convention for acknowledgements to better support the newly introduced limited life-span of acknowledgements.

Version 1.3 supported hard disk deliveries and corrected the naming convention for the manifest file, indicating that the batch is complete from Manifest_* to batch_complete_*.

Version 1.2 enabled the InformationAboutDeliveredAndAvailableReleasesMessageCall (previously known as InformationAboutAvailableReleasesMessageCall) to be used by a record company or distributor as an audit tool. It also allowed error messages be communicated to a web service caller and enables a DSP to ask for the “next release” without specifying what release that should be. Version 1.2 also added a MessageActionType into the InformationAboutAvailableReleasesReportMessage and made the MessageType, in the same composite, optional. In addition, some clarifications were added and unnecessary clauses were removed.

Version 1.1 enabled the ability for humans to intervene, when needed, into a feed. Other changes were made to enable a more streamlined machine-to-machine communication. However, since DDEX is not aware of any implementation of the ECHO version 1.0 standard (as this part of the ERN standard was previously known), the details of these changes are not listed here.