11.2 Classical profile variant
Notwithstanding rules expressed elsewhere in this part of the ERN standard, a release in the classical profile variant shall contain at least one Primary Resource of type SoundRecording or Video with the ApplyClassicalProfileVariant flag set to true. This flag may be set to true not only for western classical music but also for other music where the structure of the title of the recording is comparatively complex and would benefit from communication as detailed in the rules below. For these resources the following rules apply:
The record company or distributor creating the
NewReleaseMessageshould ensure that its DSP partners are able to ingest such data.An opus number for the musical work contained in the sound recording shall be provided in the
OpusNumberfield within theWorkIdcomposite in theSoundRecordingorVideocomposite, if available (e.g. Op. 8). This field may also be used for musical works without opus numbers (this is usually done using an abbreviation of the German “Werk ohne Opusnummer”, e.g. WoO 59).A composer catalogue number for the musical work contained in the sound recording or video shall be provided in the
ComposerCatalogNumberwithin theWorkIdcomposite in theSoundRecordingorVideocomposite, if available.A
DisplayTitleandDisplayTitleTextshall be provided in accordance with Clause 7.2 of this part of the ERN standard. There are no specific rules about how these tags should be formed, only what they should contain.For hierarchical classical works the record company or distributor should consider using a string comprising:
The name of the composer;
A colon;
The name of the parent work;
A colon; and
The name of the movement including a sequence number.
For example, "Vivaldi: Concerto No. 1 in E major, Op. 8, RV 269, Spring: 1. Allegro". However, informal names, for example "Allegro from the Vivaldi’s Spring" are also permissible.
For non-hierarchical classical works the record company or distributor should consider using a string comprising:
The name of the composer;
A colon; and
The name of the work.
For example, "Beethoven: Bagatelle No. 25 in A minor for solo piano, WoO 59". However, informal names, for example "Beethoven: Für Elise" are also permissible.
A
FormalTitleshall be provided.For hierarchical classical works this would be the title of the movement, for example, "1. Allegro".
For non-hierarchical classical works this would usually just be the name of the work. For example, "Bagatelle No. 25 in A minor for solo piano, WoO 59".
A
GroupingTitleshall be provided for all hierarchical classical works containing the title of the parent classical work, for example "Concerto No. 1 in E major, Op. 8, RV 269, Spring".The
DisplayArtistNamemust be provided.
It usually contains a combination of conductor(s), orchestra(s), choir(s) and soloist(s). TheDisplayArtistNameusually does not include the composer(s).All groups and individuals listed in the
DisplayArtistNametag shall also be provided asDisplayArtists.All composers shall also be communicated in the
DisplayArtistcomposite with aDisplayArtistRoleofDisplayComposer. The flagIsDisplayedInTitlemay be set totrueto indicate that the composer name should be displayed as part of the title.The
PartyNametag in thePartycomposite should ideally contain aKeyName(e.g. Beethoven) and aFullName(e.g. Ludwig van Beethoven).All parties listed as
DisplayArtistsshall also be listed asContributors.When displaying information about classical works to consumers the DSP should use the
DisplayTitleorDisplayTitleText.
This may, however, not always be possible especially when catering for devices with limited space to display long titles. In that case, the DSP should, subject to any contractual obligations, combine the information from the various title tags with the composer data from theDisplayArtistcomposite. In that case the DSP should concatenate them and separate them suitably, for example by adding colons between theDisplayArtist's name and theGroupingTitleas well as between theGroupingTitleand theFormalTitle.