Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

DDEX does not standardise genres. Every so often a new proposal is made to attempt genre specification – and each time, DDEX experts have determined that this would be not a good idea. Some of the reasons are:

  • Genres differ from territory to territory ("World Music" in the US differs from "World Music" in Germany);
  • Genres differ from language to language ("Neue Deutsche Welle" is a genre unlikely to be used in non-German speaking countries);
  • Genres are of varying specificity (An on-line retailer focusing on rock music might have one genre for all classical music whereas a classical retailer would want to distinguish between different types of classical music).

DDEX's Genre composite allows the communication of a genre and one sub-genre. DDEX also allows including more than one such Genre composite for each sound recording, video or Release:

Float
border0pt
sideright
width33%
Note

If more than one Genre composite is included in a DDEX message for a specific sound recording, video or Release, no order or hierarchy should be implied.

Code Block
<Genre>
	<GenreText>Blues</GenreText>
	<SubGenre>Bluesrock</SubGenre>
</Genre>
<Genre>
	<GenreText>R&B</GenreText>
</Genre>

 

No Hierarchy

There is no hierarchy of genres if multiple instances of the Genre composite are used for one creation and that it is recommended to not use the genre information to drive business logic