Rules for ERN-3

DDEX messages are explicit in all communicartins. For instance a DSP may only offer a release to its users, if an explicit Deal is provided.

Typical uses of territorial vartiants:

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

For search: use all data available (but place preference, if that is done) to the data for the locality/language of the user

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

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) TerritioryCode elements.

The same applies to ResourceDetailsByTerritory.

Rules for ERN-4

The rules for ERN-4 are significantly simpler as there is are no …ByTerritory composites any more. Instead each element that can to be "territorialised" now carries an attribute that allows signalling the language, script and/or territory it applies to. For example:

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