History:Reader Relationship Type Proposal: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(arty: stop messing page footers, please - it can't be that hard! (Imported from MoinMoin))
 
m (CallerNo6 moved page Proposal:Reader Relationship Type to History:Reader Relationship Type Proposal: https://chatlogs.metabrainz.org/brainzbot/metabrainz/msg/3675767/)
 
(7 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Template:proposal
=Relationship Type "Reader"=
|proposal=39
|discussion=
|champion=
|rfc=
|rfv=
|status=Abandoned?
|ar=true
|style=
|trac=1730
}}


'''Status:''' [[Image:Alert.png]] ''This is a [[Proposed Advanced Relationship Type|ProposedAdvancedRelationshipType]] and hasn't been implemented, yet! It is part of [[Performance Restructuring Proposal|PerformanceRestructuringProposal]].''
This proposal is part of [[Performance Restructuring Proposal|PerformanceRestructuringProposal]].''


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


* '''artist''' ''read'' '''album''' or '''track'''
* '''artist''' ''read'' '''release''' or '''track'''
* '''album''' or '''track''' ''was read by'' '''artist'''
* '''release''' or '''track''' ''was read by'' '''artist'''


==Description==
==Description==


This describes speech done on whole albums or just tracks that is done by a reader. A reader simply reads texts. Normally this applies to [[Audio Book|AudioBook]]<code><nowiki></nowiki></code>s. Note that this is different from a narrator who narrates a story. A reader reads the spoken parts of stories whereas in a narration they are normally spoken by others. For a narrator use [[Narrator Relationship Type|NarratorRelationshipType]].
This describes speech done on whole releases or just tracks that is done by a reader. A reader simply reads texts. Normally this applies to [[Audio Book]]s. Note that this is different from a narrator who narrates a story. A reader reads the spoken parts of stories whereas in a narration they are normally spoken by others. For a narrator use [[Narrator Relationship Type]].
<ul><li style="list-style-type:none">This part is confusing... Obviously, narrations can be done by one person only, so, IMO the number of "readers" hardly qualifies the difference... Also, a narration certainly consists of a text "read" by somebody... All in all, I don't really get the difference - and it certainly deserve a better explanation... -- [[User:dmppanda|dmppanda]] 07:03, 03 June 2007 (UTC)
</ul>


This [[Advanced Relationship Type|AdvancedRelationshipType]] is part of the [[Performance Relationship Class|PerformanceRelationshipClass]]. It is a special case of [[Speaker Relationship Type|SpeakerRelationshipType]].
This [[Advanced Relationship Type]] is part of the [[Performance Relationship Class]]. It is a special case of [[Speaker Relationship Type]].


==Relationship Attributes==
==Relationship Attributes==
Line 20: Line 28:
==="additional" and "guest"===
==="additional" and "guest"===


There is no guideline yet how the additional and the guest flag might be used for "read" relationships. ([[Additional Relationship Attribute|AdditionalRelationshipAttribute]] and [[Guest Relationship Attribute|GuestRelationshipAttribute]])
There is no guideline yet how the additional and the guest flag might be used for "read" relationships. ([[Additional Relationship Attribute]] and [[Guest Relationship Attribute]])


==Examples==
==Examples==
Line 40: Line 48:
</pre>
</pre>


And for album--artist:
And for release-artist:


<pre> reader (1)
<pre> reader (1)
Line 49: Line 57:
* attributes: additional=0-1 guest=0-1
* attributes: additional=0-1 guest=0-1
</pre>
</pre>

==Discussion==

I'm not sure if my opinion has any worth, but I support this suggestion wholeheartedly. --artysmokes
<ul><li style="list-style-type:none">Support messages and encouragements are certainly better fit into the mailing-list thread for example ;) [[Delete When Cooked|DeleteWhenCooked]]. Now, can I ask you (again!) not to mess page footers? -- [[User:dmppanda|dmppanda]] 07:03, 03 June 2007 (UTC)
</ul>

[[Category:To Be Reviewed]] [[Category:Relationship Type]] [[Category:Proposed Advanced Relationship Type]]

Latest revision as of 13:59, 28 August 2016


Status: This page describes an active advanced relationship proposal and is not official.



Proposal number: RFC-39
Champion: None
Current status: Abandoned?


Trac ticket # 1730

This proposal is part of PerformanceRestructuringProposal.

Link Phrases

  • artist read release or track
  • release or track was read by artist

Description

This describes speech done on whole releases or just tracks that is done by a reader. A reader simply reads texts. Normally this applies to Audio Books. Note that this is different from a narrator who narrates a story. A reader reads the spoken parts of stories whereas in a narration they are normally spoken by others. For a narrator use Narrator Relationship Type.

This Advanced Relationship Type is part of the Performance Relationship Class. It is a special case of Speaker Relationship Type.

Relationship Attributes

"additional" and "guest"

There is no guideline yet how the additional and the guest flag might be used for "read" relationships. (Additional Relationship Attribute and Guest Relationship Attribute)

Examples

Jim Dale read Harry Potter and the Chamber of Secrets (feat. reader: Jim Dale) (disc 1)

Monty Arnold read Dunkel (feat. reader: Monty Arnold) (disc 1)

Proposed Definition

This is how it would be implemented for artist--track:

 reader (1)

    * forward: {additional:additionally} {guest} read
    * reverse: was {additional:additionally} {guest} read by
    * description: Indicates an artist reading a text on this work.
    * attributes: additional=0-1 guest=0-1

And for release-artist:

 reader (1)

    * forward: was {additional:additionally} {guest} read by
    * reverse: {additional:additionally} {guest} read
    * description: Indicates an artist reading a text on this work.
    * attributes: additional=0-1 guest=0-1