History:Narrator Relationship Type Proposal: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(categories (Imported from MoinMoin))
(updated status (Imported from MoinMoin))
Line 1: Line 1:
=Relationship Type "Narrator"=
=Relationship Type "Narrator"=


'''Status:''' [[Image:Attention.png]] ''This is a [[Proposed Advanced Relationship Type|ProposedAdvancedRelationshipType]] and an [[Open Style Issue|OpenStyleIssue]]. It has not been implemented, yet!''
'''Status:''' [[Image:Alert.png]] ''This [[Proposed Advanced Relationship Type|ProposedAdvancedRelationshipType]] and [[Open Style Issue|OpenStyleIssue]] has been superceded by the '''[[Performance Restructuring Proposal|PerformanceRestructuringProposal]]'''. It has not been implemented, yet!''


==Link Phrases==
==Link Phrases==

Revision as of 12:44, 6 November 2005

Relationship Type "Narrator"

Status: Alert.png This ProposedAdvancedRelationshipType and OpenStyleIssue has been superceded by the PerformanceRestructuringProposal. It has not been implemented, yet!

Link Phrases

  • artist narrated album or track
  • album or track was narrated by artist

Description

This one could be useful for audiobooks, spoken children's stories and classical releases.

This AdvancedRelationshipType is part of the PerformanceRelationshipClass.

Relationship Attributes

"additional"

There is no guideline yet how the additional flag might be used for "narrated" relationships. (AdditionalRelationshipAttribute)

Examples

Discussion

Live albums often have introductions spoken by someone on the stage or other spoken parts. Example: Once in Agony. Should this relationship also be used for this? --Shepard

  • Maybe we can also add IntroductionRelationshipType? To answer your question: it feels a bit weird to call what you are describing "narrating", but I'd have no problem with people using the NarratorRelationshipType... (if you don't think the terminology is a bit awkward) --azertus
    • Naah, IntroductionRelationshipType would be a bit breaking a fly on the wheel. I'm just thinking if it would be better to have a more generic relationship type for this like "artist X spoke album/track Y". And also I see parallels to vocal performances so perhaps this could be all put in one class. --Shepard
    Wouldn't it be enough to change it to "speaker"? That would fit for any case, when an "artist is speaker on track/album"? --Fuchs
    • I see what you mean, but I feel narrating is a specific enough case to be a a type on its own. I propose the following: we add SpeakerRelationshipType, which can be used to ARify introductions, dialogues, etcetera. NarratorRelationshipType is then only to be used in the specific cases outlined on this page. --azertus

From an OO point of view, might it be something like "track spoken by ..." then the attribute "as introduction | as narration | as DirectorCommentary..." (Also many AudioBooks are acted out by a number of characters, not just a narrator: "as actor" or "as character N") --Chuck__Carmody

  • Dudes forget this introduction thing! It was just an example for spoken parts on live albums or for spoken parts in general. I see no way why we should have a special handling for "introduction". And also I don't think attributes would do it as "artist spoke album/track" and "artist narrated album/track" are totally different link phrases. The idea of different speaking roles in a track (similar to guest performances) might be nice but we should not forget that this site is mostly about music and not about theater plays or something so we should not stretch this too much :) --Shepard