DDEX Standard

Skip to end of metadata
Go to start of metadata

7.4.1  Purpose

This command can be used by a Release Distributor to request receipt of a Resource file. The web service address for this call is the URL for the specific instance of the file as indicated in the NewReleaseMessage.

The GET ERN Resource method only applies if the Release Creator has used an HTTP link when communicating the location of the Resources in the NewReleaseMessage. Therefore, if the URI in the NewReleaseMessage uses a scheme other than http:// or https:// (or any protocol agreed by the parties), the Release Distributor may not be able to the use web services to obtain this Resource. This approach allows the combination of the web service delivery approach defined herein for Release metadata with an (S)FTP or local file delivery for Resource files.

7.4.2 Syntax of Reply

The web server shall return one of the following standard HTTP status codes with their standard HTTP response code semantics:

  • 200 (OK);
  • 301 (Moved permanently);
  • 400 (Bad request);
  • 401 (Unauthorised);
  • 404 (Not Found); and
  • 500 (Internal server error); and
  • 503 (Service unavailable due to a temporary overloading or maintenance of the server).

Other standard HTTP status codes may be used on bilateral agreement between the Release Creator and the Release Distributor.

If the status code is 200, the Web server shall also return to the calling web service client the Resource file.

If the status code is 301, the Web server shall also return the updated URL of the resource. If the Resource itself (i.e. not just its URL) has changed, the Release Creator shall add a new NewReleaseMessage into its feed(s) and the Release Distributor shall regard the entire NewReleaseMessage as invalid.


  • No labels