Talk:Composition Relationship Class

From MusicBrainz Wiki
Revision as of 18:46, 15 March 2009 by Nikki (talk | contribs) (New page: IMHO two more relationship are needed and are proper here, please check if correct and AR syntax * AttributeToRelationshipType: ** ''release''/''track'...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

IMHO two more relationship are needed and are proper here, please check if correct and AR syntax

  • This is quite common in classical, see [here]
  • Also quite common, with a couple of famous [examples] Is different from arranged, it's a much more rework process, final work is often credited to transcriptor; so possibily a release AR "is a transcription of" could be better but classical releases are not unique. --ClutchEr2

"attributed to" can be confused with whom a release is attributed to on covers, I guess? --Shepard

"Based on a theme by"

In ClassicalMusic, it is sometimes the case that some composer writes new music based on a musical them by a second composer. The resulting work is considered a work in its own right, but it is well known to be based on the second composer's work. The phrase "on a theme by" may even be in the work's title. See, for example, Sonatina No. 6 "Kammer-Fantasie über Carmen" by Busoni based on a them from Bizet's Carmen; and Rhapsody on a Theme of Paganini, Op. 43 by Rachmaninoff based on a theme by Paganini. The conclusion of an edit #7828613 discussion for the former work was that the composer of the original theme should be connected to the track or release via an "additional composer" AdvancedRelationship . There was also talk of putting an annotation on the "additional composer" relationship to clarify the nature of their contribution, but there doesn't seem to be a way to put an annotation on the AR. The "additional" attribute for ComposerRelationshipType presently has no other meaning (q.v.), but it seems more descriptive to have a specific AR for the purpose. -- JimDeLaHunt 2007-11-24 .

This indicates that the artist wrote or composed some music which was used as the inspiration or starting point for substantial new composition by the Artist who composed the Release or Track. "Theme" is used in the ClassicalMusic sense of "based on a theme by", not in the sense of the theme song of a TV show. [Where's the right place to publish this proposal? PM me.] -- JimDeLaHunt 2007-11-24

Authored spoken (not sung) words

We don't seem to quite have a CompositionRelationshipClass for the person who rights words that are spoken, rather than sung. LyricistRelationshipType and LibrettistRelationshipType both specify they are for works of "music". But MusicBrainz does include some audio books and spoken word Releases, for example David Sedaris's "Me Talk Pretty One Day". We could just use "Lyricist" or "Librettist" for this relationship, and expect people to combine it with the Audiobook ReleaseAttribute, and get the point. But if we care enough to distinguish between "Lyricist" or "Librettist", we care enough to add "Author".

  • Proposal: new AuthorRelationshipType (here in CompositionRelationshipClass)
    • release/track has spoken words which were authored by artist

This indicates that the artist wrote or authored words which are spoken in the Release or Track. For words which are set to music, use LyricistRelationshipType and LibrettistRelationshipType instead of this. -- JimDeLaHunt 2007-12-06

LibrettistRelationshipType should apply to Track also, not just Release

LibrettistRelationshipType said that it meant artist wrote the libretto for release. I think it should also apply to tracks. Most operas fill a CD, but a Release of opera excerpts could legitimately have a different Librettist for each track. I've added the word "Track" in there. This is my notification to those who oversee such things, since they probably monitor the comments on this wiki page. -- JimDeLaHunt 2007-12-06