Difference between revisions of "Proposals"

From MusicBrainz Wiki
m (Next New Proposal Number)
(Style Proposals: RFC-346 renewed 2012-01-13)
Line 333: Line 333:
 
| <!-- Affects          --> [[Style]]
 
| <!-- Affects          --> [[Style]]
 
| <!-- Status          --> RFC
 
| <!-- Status          --> RFC
| <!-- RFC              --> [http://musicbrainz.1054305.n4.nabble.com/RFC-346-Style-Language-Vietnamese-Punctuation-change-tp4226419p4226419.html 2011-12-22]
+
| <!-- RFC              --> <s>[http://musicbrainz.1054305.n4.nabble.com/RFC-346-Style-Language-Vietnamese-Punctuation-change-tp4226419p4226419.html 2011-12-22]</s> [http://musicbrainz.1054305.n4.nabble.com/RFC-346-Style-Language-Vietnamese-Punctuation-change-tp4226419p4292622.html 2012-01-13]
 
| <!-- RFV              -->  
 
| <!-- RFV              -->  
 
|-
 
|-

Revision as of 09:53, 1 February 2012

Contents

Proposals

Changes to MusicBrainz are made using this proposal process.

The process is simple. Someone has an idea, either for something new, or for a change to how something existing is done. After discussion of the idea has taken place, one person takes control of the idea. This person is then known as the Idea Champion for that proposal. The Idea Champion has the responsibility for moving the idea from a vague concept to a clear proposal, then working for Style Council passage of the proposal.

Though it is somewhat dated, Turning Your Ideas Into Reality is well worth a read.

Definitions

Idea Champion
The person who currently is handling a proposal.
Style Council
Any members of the Style mailing list who wish to take part in discussion of a proposal. There is no formal membership to the style council. If you are an interested contributor to MusicBrainz and reasonably well informed about existing Style Guidelines, MusicBrainz development, and the general culture of the project, you are welcome to subscribe to the Style mailing list and join the discussions. Also see the history of the Style Council.

Process for Idea Champions

  1. Come up with an idea for something new or something that should be changed. While somewhat out of date, the points raised on this former checklist for style changes are still worth consideration as part of your proposal.
  2. Create a new wikipage for the proposal. This should be located at http://wiki.musicbrainz.org/Proposal:(proposal name). Use Template:proposal on the page; documentation is at the template page.
  1. Send a RFC announcement to the style list.
    • The RFC should have "RFC:" at the beginning of the subject line.
    • The body of the email should contain:
    1. The expected expiration date for the RFC.
    2. A brief summary of the proposal.
    3. A link to the proposal's wikipage.
    4. Links to any previous discussion (IRC, style list, users list, forums, etc) which led to the proposal.
  2. During the period where the RFC is active, discussion of it will occur on the style list.
    • Anyone can change the proposal's wikipage, though it is encouraged that any changes which go beyond minor formatting, spelling, or example changes should be left to the Idea Champion.
    • If you are not the Idea Champion, and you have sufficient disagreement with the proposal that you feel an entirely different proposal needs to be created, a new proposal wikipage should be created, for which you would become that proposal's Idea Champion. Do not rewrite the original proposal wikipage and attempt to take over the idea from the original Idea Champion!
    • Where there is disagreement, the Idea Champion should work to find consensus.
    • On minor points, the Idea Champion maintains control of the proposal. However, for the Idea Champion, you ignore dissent at the risk of the proposal - disagreement can easily become vetos during the RFV period.
    • If discussion on a RFC is still ongoing, and there is not yet agreement that the proposal is ready to pass, the RFC period may be extended. The RFC period only defines a minimum, not a maximum, time period for debate.
  3. Before a RFC may move into RFV status, another style council member must endorse it with "+1" in an email to the style list, indicating that, in its current state, it has been reviewed and is acceptable to that member. Any changes to RFC text prior to RFV clear that +1 and reset this requirement.
  4. When the RFC's initial period has expired, the Idea Champion (or a Style Leader) will send out a RFV for the proposal.
    • The RFV email should have "RFV:" at the beginning of the subject line.
    • The body of the email should contain:
    1. The expected passage date for the RFV.
    2. A brief summary of the proposal, including a summary of any changes which have been made since the RFC.
    3. A link to the proposal's wikipage.
  5. During the RFV period, any member of the style council may veto the RFV. However, vetos must have merit (no vetos simply because "I don't like this proposal"). Vetos must be publicly cast, on the style list, and should detail what problems are believed to remain in the RFV, and what changes could be made such that the veto would be cleared. These suggested changes must be reasonable; if the changes would entail a rewrite, or rethink, of the proposal itself, then a counter-proposal wikipage should be created, and the decision as to which proposal will pass should be left to the style council.
    • If a RFV receives a veto, the proposal reverts to a RFC. There is no minimum time period at this point, but no new RFV should be attempted until the problems raised in any vetos have been discussed and/or addressed. A proposal may revert to a RFC, or have replacement RFCs sent, as many times as is needed.
  6. If the end of the RFV period is reached, and no vetos have been cast, then the proposal has passed. The Idea Champion is now responsible for ensuring that the changes described by the proposal are enacted (changing wiki pages, entering edits, creating trac or jira tickets, etc.). This includes remembering to remove the proposal template from the proposal's wikipage!
    • Note to wiki moderators: when moving a passed AR proposal from the Proposal: namespace to the main namespace, please remember to remove '|proposal = 1' from the text.

Time Periods

  • RFC: 7 days
  • RFV: 2 days

Style Leaders

Style Elder

Definitions

RFC (Request for Change)
The initial discussion period for any proposal
RFV (Request for Veto)
The decision period for any proposal
Style Leader
They guide the process and keep it from getting stuck. If the council cannot reach consensus they will make a decision. This position was previously called "secretary".
Style Elder
The benevolent dictator of MusicBrainz style issues. If the process goes off the rails, or if someone disputes the style leaders' decisions, the elder steps in.

Special Procedures

Has Cover Art At, Has Lyrics At, and Has Score At Relationship Types

These relationships each only allow links to whitelisted sites. To add any site to the whitelist for any one of these advanced relationships, the following additional procedure must be followed.

  1. Add the site to the 'in-progress' list on the relevant page for the AR.
  2. Using the normal proposal process, send a RFC requesting the addition of the site.
    • The RFC should be limited to covering only 1 site.
    • The RFC must provide rationale and evidence for why the site can reasonably be believed to have permission to contain the content to which we would be linking.
  3. The Style Council will then make sure that the site itself is legal; that it has a right/license/whatever to store the content (lyrics/scores/cover art) which which the relationships would be link.
    • If any situation arises where "legal" is questionable depending on local laws, MusicBrainz is based in California, so US/California law wins.
  4. Once the RFV has passed, permission must be obtained, in writing (email is fine), from the site which would be added to the whitelist.
    • This permission may be requested prior to the passage of the RFV.

Only when permission has been received and a RFV has passed may the site be added as a whitelisted site for the applicable relationship type(s).

Adding new instrument types

These do not go through the Style Council process. Instead, they use the instrument addition process.

Current Proposals

Next New Proposal Number

Next new proposal number: 348

Proposal numbers 112 - 200 and 206 - 250 have been reserved for RFCs to fill in holes in the guidelines and documentation.

Style Proposals

Categorized as Category:Proposed Style. Passed proposals waiting to be implemented and closed proposals are found on the talk page.

RFC Title & Wikipage Champion Affects Status RFCs RFVs

RFC-1: AudioBook Style

1

Audiobook Style Jormangeud New guideline In development

RFC-8: Capitalization Standard Swedish

8

Capitalization Standard Swedish symphonick New guideline In development

RFC-19: Game Soundtrack Style

19

Game Soundtrack Style BrianFreud New guideline In development

RFC-20: Instrumental Style

20

Instrumental Style Bogdanb ETI style for instrumental tracks In development 2006-04-20

RFC-25: Medley Style

25

Medley Style Jacobbrett New guideline In development

RFC-42: Release Artist Style

42

Release Artist Style navap New guideline In development

RFC-43: Release Country Event Style

43

Release Country Event Style (additional older page) (RFC-64 Discussion) Jacobbrett Release events RFC2 2010-03-20
2010-04-07

RFC-53: Soundtrack Style

53

Soundtrack Style BrianFreud New guideline In development

RFC-54: Soundtrack Title Style

54

Soundtrack Title Style BrianFreud New guideline In development

RFC-61: Track Title Style

61

Track Title Style warp Naming of track titles In development

RFC-62: Untitled Release Style

62

Untitled Release Style Bogdanb New guideline In development

RFC-67: Revised Classical Style Guide (aka CSGv2)

67

Revised Classical Style Guide (aka CSGv2) BrianFreud Rewrites all of CSG RFC, On hold pending NGS release 2009-02-15

RFC-202: Part Number Style rewrite

202

Part Number Style rewrite BrianFreud Part Number Style On hold pending RFC-61

RFC-109: Release Groups

109

Release Groups Jacobbrett New guideline In development

RFC-204: Decommission Don't Make Relationship Clusters

204

Decommission Don't Make Relationship Clusters BrianFreud Removes a guideline vetoed, awaiting counter-proposal 2010-03-15 2010-03-29

RFC-275: Clarify order of precedence of guidelines and principles

275

Clarify order of precedence of guidelines and principles BrianFreud Cleans up & assigns order of precedence for guidelines and principles RFC2 2010-03-27 2010-04-04

RFC-288: Capitalization Standard Japanese

288

Capitalization Standard Japanese foolip
kepstin
New caps standard guideline RFC+1 2010-06-05
2010-11-27

RFC-290: Live Bootleg Style: Link to reference list modifications

290

Live Bootleg Style: Link to reference list modifications BrianFreud Add reference list for state abbreviations RFC3 2010-09-08
2010-11-11
2010-12-05
2010-09-14
2010-11-13

RFC-299: Continuous Mix Style

299

Continuous Mix Style chancey New style guideline RFC 2010-09-22

RFC-307: Futuramerlin.com Album Artwork

307

Futuramerlin.com Album Artwork Calculator Ftvb ? ?

RFC-320: Revised Sortname Style

320

Revised Sortname Style caller#6 re-write of Sortname_Style RFC

RFC-329: Removal of CDON.COM and AMG from What not to Link to

329

Removal of CDON.COM and AMG from What not to Link to Jacobbrett Style/Relationships/URLs/What not to link to RFC 2011-07-15

RFC-332: Live Performance Relationship Dates

332

Live Performance Relationship Dates ChurruKa Performance_Relationship_Type Passed 2011-07-10

RFC-333: Unify track/recording guidelines

333

Unify track/recording guidelines User:LukasLalinsky Style RFC 2011-07-26

RFC-339: Work/Relationship Inheritance in Works Trees

339

Partial Works Relationship Inheritance Jim DeLaHunt Work RFC 2011-10-28
2011-11-01
2011-11-05

RFC-346. Style/Language/Vietnamese : Punctuation change

346

Style/Language/Vietnamese jesus2099 Style RFC 2011-12-22 2012-01-13

RFC-347. Style/Classical: Update for NGS

347

Style/Classical Hawke Style RFC [2012-01-12]

Advanced Relationship Proposals

Categorized as Category:Proposed Relationship Type. Passed proposals waiting to be implemented and closed proposals are found on the talk page.

RFC Title & Wikipage Champion Affects Status RFCs RFVs

RFC-4: Redesign of the Vocal Relationship Attribute

4

Redesign of the Vocal Relationship Attribute BrianFreud AR modification discussion, Pre-RFC

RFC-26: Miscellaneous Production Relationship Type/Artwork

26

Miscellaneous Production Relationship Type/Artwork BrianFreud In development

RFC-29: Narrator Relationship Type

29

Narrator Relationship Type symphonick New vocal role In development

RFC-35: Part Of Series Relationship Type

35

Part Of Series Relationship Type voiceinsideyou
abandoned
New release-release, or RG-RG, AR In development

RFC-39: Reader Relationship Type

39

Reader Relationship Type symphonick New vocal role In development

RFC-55: Speaker Relationship Type

55

Speaker Relationship Type symphonick New vocal role In development

RFC-68: Add Has News Coverage AR

68

Add Has News Coverage AR ruaok
BrianFreud
abandoned
New release-URL AR Tabled until post-NGS 2010-02-28
2010-03-15

RFC-69: Defining instruments and vocals for members of bands

69

Defining instruments and vocals for members of bands BrianFreud Artist-artist AR enhancement (#1141) In development

RFC-83: Add track-url Work-URL Wikipedia AR

83

Add track-url Work-URL Wikipedia AR BrianFreud New track-URL AR (#3852) In development

RFC-84: Add 'provides discographic information about' AR

84

Add 'provides discographic information about' AR BrianFreud New track-URL AR (#3734) In development

RFC-87: Add 'is a project of' AR

87

Add 'is a project of' AR abandoned New artist-artist AR (#1739) In development

RFC-260: Extend License attribute

260

Extend License attribute Murdos Adds new licenses to existing License Relationship Attribute In development

RFC-261: Clean up link phrases

261

Clean up link phrases BrianFreud Makes AR link phrases consistent and comprehensible RFV 2010-03-24 2010-04-07

RFC-106: Conductor AR Changes

106

Conductor AR Changes luks
BrianFreud
Conductor and Chorus Master Relationship Types modification discussion, RFC 2007-05-03
2010-12-06

RFC-106a: Deprecate Chorus Master Relationship Type

106a

Deprecate Chorus Master Relationship Type BrianFreud Depricates the Chorus Master Relationship Type (follow up to RFC-106) discussion, RFC 2010-12-31

RFC-264: Choirmaster Position Relationship Type

264

Choirmaster Position Relationship Type BrianFreud New artist-artist AR discussion, RFC 2010-12-06

RFC-265: Concertmaster Position Relationship Type

265

Concertmaster Position Relationship Type BrianFreud New artist-artist AR discussion, RFC 2010-12-21

RFC-265a: Concertmaster Relationship Type

265a

Concertmaster Relationship Type BrianFreud New release/track-artist AR discussion (see RFC-265)

RFC-266: Conductor Position Relationship Type

266

Conductor Position Relationship Type BrianFreud New artist-artist AR discussion, RFC 2010-12-06

RFC-319: Modify Member Of Band Relationship Type

319

Modify Member Of Band Relationship Type BrianFreud Add a guideline to the MoB AR (Split out from RFC-264 and RFC-266), discussion, RFC 2010-12-16

RFC-267: Manager Position Relationship Type

267

Manager Position Relationship Type BrianFreud New artist-artist AR discussion, RFC 2010-12-21

RFC-268: Road Crew Position Relationship Type

268

Road Crew Position Relationship Type BrianFreud New artist-artist AR discussion, RFC 2010-12-31

RFC-269: Music Director Position Relationship Type

269

Music Director Position Relationship Type BrianFreud New artist-artist AR discussion, Pre-RFC

RFC-270: Bandleader Position Relationship Type

270

Bandleader Position Relationship Type BrianFreud New artist-artist AR discussion, RFC 2010-12-31

RFC-271: Teacher Position Relationship Type

271

Teacher Position Relationship Type BrianFreud New artist-artist AR discussion, Pre-RFC

RFC-272: Vocal Coach Position Relationship Type

272

Vocal Coach Position Relationship Type BrianFreud New artist-artist AR discussion, Pre-RFC

RFC-273: Instrument Instructor Position Relationship Type

273

Instrument Instructor Position Relationship Type BrianFreud New artist-artist AR discussion, Pre-RFC

RFC-274: Supporting Musician Relationship Type enhancement

274

Supporting Musician Relationship Type enhancement BrianFreud Add attribute to existing artist-artist AR discussion, RFC 2010-12-21

RFC-278: Add label-URL to Discography Relationship Type

278

Add label-URL to Discography Relationship Type BrianFreud Adds AR RFC+1 2010-06-03 2010-06-10

RFC-279: Add label-URL to Mail Order Relationship Type

279

Add label-URL to Mail Order Relationship Type BrianFreud Adds AR Waiting for RFC

RFC-280: Add label-URL and artist-URL to Review Relationship Type

280

Add label-URL and artist-URL to Review Relationship Type BrianFreud Adds 2 ARs Waiting for RFC

RFC-281: Add artist-label to Miscellaneous Role Relationship Type

281

Add artist-label to Miscellaneous Role Relationship Type BrianFreud Adds AR Waiting for RFC

RFC-291: Jamendo Relationship Type

291

Jamendo Relationship Type navap New URL AR In development

RFC-297: Toured With Relationship Type

297

Toured With Relationship Type BrianFreud New AR In development

RFC-298: Bandcamp Relationship Type

298

Has Cover Art At Bandcamp Relationship Type VxJasonxV New Cover Art URL(s) ARs In development, RFC1 withdrawn 2010-12-11

RFC-309: Married Relationship Type enhancement

309

Married Relationship Type BrianFreud New attributes In discussion

RFC-310: Emeritus Position Relationship Attribute

310

Emeritus Position Relationship Attribute BrianFreud relationship attribute In discussion

RFC-311: Principal Position Relationship Attribute

311

Principal Position Relationship Attribute BrianFreud relationship attribute In discussion

RFC-312: Executive Committee Position Relationship Type

312

Executive Committee Position Relationship Type BrianFreud New AR In discussion

RFC-313: Principal Position Relationship Type

313

Principal Position Relationship Type BrianFreud/Symphonick New AR In discussion

RFC-314: Soloist Relationship Type

314

Soloist Relationship Type Symphonick New AR In discussion

RFC-315: Contractor Position Relationship Type

315

Contractor Position Relationship Type and Position Relationship Attribute BrianFreud New AR RFC 2010-01-02

RFC-322: Performed Relationship Type Attributes

322

Performed Relationship Type Attributes Cjk32 New Attributes RFC 2011-06-06

RFC-323: Live Attribute for Performed Relationship Type

323

Performed_Relationship_Type_Live_Attribute Bitmap Relationship attribute RFV 2011-06-08 2011-06-15

RFC-324: Official Website and Discography Entry ARs for Releases/Release Groups

324

Official Homepage Relationship Type Discography Entry Relationship Type Kepstin Official Homepage RFC

RFC-325: Cover Relationship Type

325

Cover Relationship Type Bitmap Rewrites AR RFV 2011-06-18 2011-06-26

RFC-331: CD Baby Relationship Type

331

CD Baby Relationship Type hrglgrmpf New AR RFC 2011-07-24 2011-07-27

RFC-335: Forbid arrange on non classical works

335

Forbid arrange on non classical works jesus2099 Change AR guideline text RFC 2011-09-14 _

RFC-337: Solo performer relationship attribute

337

Solo performer Hawke adds attribute RFC 2011-10-25

RFC-341: CSG Recording parts Relations

341

CSG Recording parts Relations Benji99 New Recording-Recording AR RFC 2011-11-17

RFC-345: Extend License Relationship To Recordings

345

Extend License Relationship To Recordings hrglgrmpf adds entity RFC 2011-12-21

Other Proposals

Categorized as Category:Proposal. Passed proposals waiting to be implemented and closed proposals are found on the talk page.

RFC Title & Wikipage Champion Affects Status RFCs RFVs

RFC-3: Advanced Entity

3

Advanced Entity (Post-NGS) BrianFreud Catchall for various post-NGS entity suggestions post-NGS

RFC-6: Artist Type Project

6

Artist Type Project abandoned New Artist type abandoned

RFC-11: Change Default Data Quality Proposal

11

Change Default Data Quality Proposal (Data) BrianFreud Voting, Quality, and Edit expiration discussion, post-NGS 2007-06-19

RFC-24: Location Proposal

24

Location Proposal BrianFreud New entity discussion, post-NGS

RFC-36: Performance Restructuring Proposal

36

Performance Restructuring Proposal BrianFreud In development

RFC-37: Performances And Recordings Proposal

37

Performances And Recordings Proposal BrianFreud New entity discussion, post-NGS

RFC-49: Release Type Restructuring Proposal

49

Release Type Restructuring Proposal BrianFreud In development

RFC-49a: Release Status Proposals

277

Various Release Status Proposals BrianFreud This is a catchall for Release Status proposals formerly part of RFC-49 In development

RFC-49b: Release Format Proposal

278

Release Format Proposal BrianFreud This is the Release Format proposal, formerly part of RFC-49 In development

RFC-258: How to Identify Release Details

258

How to Identify Release Details Jacobbrett Will replace How To Identify Labels Not an actual RFC

RFC-296a: Change "Release Country"

296a

Change "Release Country" BrianFreud RFC+1 2010-12-28

RFC-300: Add new release type: Production Music

300

Add new release type: Production Music BrianFreud discussion, pre-RFC

RFC-301: Add new release type: Studio/Demo

301

Add new release type: Studio/Demo BrianFreud discussion, pre-RFC

RFC-302: Add new release type: Audio Drama

302

Add new release type: Audio Drama BrianFreud discussion, pre-RFC

RFC-303: Add new release type: Multi-Album

303

Add new release type: Multi-Album BrianFreud discussion, pre-RFC

RFC-304: Add new release type: Live Compilation

304

Add new release type: Live Compilation BrianFreud discussion, pre-RFC

RFC-305: Add new release type: Soundtrack Single

305

Add new release type: Soundtrack Single BrianFreud discussion, pre-RFC

RFC-306: Add new release type: Soundtrack Compilation

306

Add new release type: Soundtrack Compilation BrianFreud discussion, pre-RFC

RFC-334: Theatre style artist collaborations

334

Theatre Style Artist Collaborations pbryan Style/Specific_types_of_releases/Theatre RFV 2011-08-10
2011-08-02
2011-08-19

RFC-343: Add

343

Add 歌詞タイム to Lyrics Whitelist kepstin Lyrics whitelist RFV 2011-11-22 2011-12-02

Pre-Reserved RFCs for cleaning up documentation and guidelines

These are all official entities, relationships, guidelines, or other things which have some minor element which is missing. Most are only a sentence or two, but need an RFC to be made official; this table lists those, and pre-reserves RFC numbers for these future RFCs. As these are intended to be truly short RFCs of only a sentence or two (in almost all cases), most won't actually have proposal pages, only proposal emails.

RFC Wikipage Hole to be filled Champion RFCs RFVs
118 What Not To Link To Needs rewrite and updating, then official status
119 (unassigned)
120 Librettist Relationship Type Guideline for use of the additional attribute
127 Orchestra Relationship Type Guideline for use of the additional attribute
132 Samples Artist Relationship Type Guideline for use of the additional attribute
133 (unassigned)
134 Samples Artist Relationship Type Guideline for use of the vocal attribute
135 Samples Artist Relationship Type Guideline for use of the instrument attribute
136 Engineer Relationship Type Guideline for use of the executive attribute
139 (unassigned)
140 (unassigned)
141 (unassigned)
142 Bonus Relationship Attribute Description
143 Chorus Master Relationship Type start date
144 Chorus Master Relationship Type end date
145 Chorus Master Relationship Type additional attribute
150 Compilation Relationship Type start date
151 Compilation Relationship Type end date
157 Co Relationship Attribute Description
158 Creative Position Relationship Type start date
159 Creative Position Relationship Type end date
160 Engineer Position Relationship Type start date
161 Engineer Position Relationship Type end date
162 (unassigned)
163 Editor Relationship Type start date
164 Editor Relationship Type end date
167 DJ Mix Relationship Type start date
168 DJ Mix Relationship Type end date
169 Liner Notes Author Relationship Type start date
170 Liner Notes Author Relationship Type end date
171 Liner Notes Author Relationship Type additional
172 Description Relationship Attribute Description
173 (unassigned)
174 (unassigned)
175 Mash-up Relationship Type start date
176 Mash-up Relationship Type end date
177 (unassigned)
178 (unassigned)
181 Member Of Band Relationship Type additional
182 Miscellaneous Role Relationship Type start date
183 Miscellaneous Role Relationship Type end date
184 (unassigned)
185 (unassigned)
186 Mix-DJ Relationship Type start date
187 Mix-DJ Relationship Type end date
188 Orchestra Relationship Type start date
189 Orchestra Relationship Type end date
194 Part Of Set Relationship Type start date
195 Part Of Set Relationship Type end date
196 Performer Relationship Type start date
197 Performer Relationship Type end date
198 Photography Relationship Type additional
199 Producer Position Relationship Type start date
200 Producer Position Relationship Type end date
206 Producer Relationship Type start date
207 Producer Relationship Type end date
210 Publisher Relationship Type start date
211 Publisher Relationship Type end date
212 (unassigned)
213 (unassigned)
214 Remaster Relationship Type start date
215 Remaster Relationship Type end date
218 (unassigned)
219 (unassigned)
222 Tribute Relationship Type start date
223 Tribute Relationship Type end date
224 Writer Relationship Type start date
225 Writer Relationship Type end date
226 Executive Relationship Attribute Description
227 Remixer Relationship Type start date
228 Remixer Relationship Type end date
229 Remixer Relationship Type additional
230 Samples Relationship Type start date
231 Samples Relationship Type end date
234 Supporting Musician Relationship Type start date
235 Supporting Musician Relationship Type end date
236 Supporting Musician Relationship Type additional
237 Supporting Musician Relationship Type guest
238 Supporting Musician Relationship Type instrument
239 Supporting Musician Relationship Type vocal
240 Transliterated Relationship Attribute Description
241 (unassigned)
242 (unassigned)
243 (unassigned)
244 (unassigned)
245 (unassigned)
246 (unassigned)
247 (unassigned)
248 (unassigned)
249 (unassigned)
250 (unassigned)

Fodder for Future Proposals