DDEX Standard

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

8.2.1 Introduction

The Atom feeds shall have follow the syntax of an Atom feed as defined in the relevant XML Schema Definition file.

The following Atom feed entry elements map to the following elements in the relevant NewReleaseMesssage:

Atom Feed entry ElementNewReleaseMessage Element
//entry/title

either

  • //ReleaseList/Release/DisplayTitleText

or

  • //ReleaseList/Release/DisplayTitle/TitleText

Which element is chosen depends on whether the Release Creator wishes to communicate subtitle information in the Atom feed.

//entry/ReleaseType/ReleaseList/Release/ReleaseType
//entry/ReleaseId/*//ReleaseList/Release/ReleaseId*

Entries should be entered into the feed sequentially, that is the oldest entry should be at the top and the latest addition should be at the bottom. A Release Creator may, however, add and remove entries at its own discretion.

The number of entry composites in the Atom feed is not prescribed by this standard. The Release Creator publishing the web service may, however, want to set a maximum number in collaboration with its Release Distributor business partner(s).

The following link types can be communicated in the //feed/link/@rel attributes:

  • self – to provide the URL of the feed itself;
  • next – to provide the URL to the next feed "page" (in the case where there is more than one feed pages available to the Release Distributor); and
  • previous – to provide the URL to the previous feed "page" (in the case where there is more than one feed pages available to the Release Distributor).

The following link types can be communicated in the //feed/entry/link/@rel attributes:

  • alternate – to provide the URL for the GET ERN Message method defined in Clause 7.2;
  • delete – to provide the URL for the DELETE ERN Message method defined in Clause 7.3; and
  • status ack – to provide the URL for the POST Release Status method defined in Clause 7.5.

8.2.4 Feed Entry Categories

The following categories may be communicated in the //entry/category element:

  • MetadataUpdate – to indicate that the relevant Release is being updated and that such an update relates to the information describing the Releases and/or Resources that make up the Release;
  • ResourceUpdate – to indicate that at least one Resource of the relevant Release is being updated;
  • DealUpdate – to indicate that at least one Deal for the relevant Release is being updated; and
  • Takedown – to indicate that the relevant Release is being globally taken down.

It is permitted to communicate multiple categories, each in one category element.

  • No labels