Territorial variations in release descriptions


DDEX messages are explicit in all communications. For example, a Digital Service Provider (DSP) can offer a release only if an explicit Deal is provided.

There is one exception to this rule: the communication of territorial variations of Release descriptions. For these, the rules are:

  • The first …ByTerritory composite (in a specific Release, Resource or Work composite) communicates the default values that apply to all territories; and

  •  All subsequent …ByTerritory composites (in the same Release, Resource or Work composite) provide only those composites that are technically mandatory or differ from the default.

Identical Territorial Data Sets

If two sets of ReleaseDetailsByTerritory are the same for the a given Release, they should be communicated in a single ReleaseDetailsByTerritory composite with two or more TerritoryCode composites.

The same applies to ResourceDetailsByTerritory.

Typical uses of territorial variants are:

  • For display: the DSP should only show the data that's relevant for the user's locality. If multiple languages are provided, the one(s) appropriate to the user's preferences should be used; and

  • For search: use all the data available for the user's locality or language.


In ERN-4, there is no …ByTerritory composite anymore.

Each element that can apply to a territory carries an attribute that allows signalling the language, script or territory it applies to. For example:

<DisplayTitleText LanguageAndScriptCode="en">Small World Big Band</DisplayTitleText>
<DisplayTitleText LanguageAndScriptCode="de">Kleine Welt -- Große Band</DisplayTitleText>