Style/Principle: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
m (17 revision(s))
(Remove useless header; nowiki bits.)
Line 1: Line 1:
Users of [[MusicBrainz]] and the members of the [[Style Council|StyleCouncil]] put some great efforts in working out detailed [[Style Guideline|StyleGuideline]]s, which state how data should be formatted. Since we stress these guidelines, people often get the impression that there is a rule that says: "Always follow the style guidelines".
=Music Brainz Style Principle=

Users of [[MusicBrainz]] and the members of the [[Style Council|StyleCouncil]] put some great efforts in working out detailed [[Style Guideline|StyleGuideline]]<code><nowiki></nowiki></code>s, which state how data should be formatted. Since we stress these guidelines, people often get the impression that there is a rule that says: "Always follow the style guidelines".


'''But this is not true.''' Instead you should stick to this principle.
'''But this is not true.''' Instead you should stick to this principle.
Line 11: Line 9:
# If 1 is not applicable, '''follow [[Strong Guideline|StrongGuideline]]s.'''
# If 1 is not applicable, '''follow [[Strong Guideline|StrongGuideline]]s.'''
# If neither 1 nor 2 are applicable, '''use [[Consistent Original Data|ConsistentOriginalData]].'''
# If neither 1 nor 2 are applicable, '''use [[Consistent Original Data|ConsistentOriginalData]].'''
# If none of 1, 2 nor 3 are applicable, '''follow the [[Style Guideline|StyleGuideline]]<code><nowiki></nowiki></code>s.'''
# If none of 1, 2 nor 3 are applicable, '''follow the [[Style Guideline|StyleGuideline]]s.'''


===Alternative phrasing===
===Alternative phrasing===


This can also be explained from the bottom upwards:
This can also be explained from the bottom upwards:
* (4) Usually you stick to the [[Style Guideline|StyleGuideline]]<code><nowiki></nowiki></code>s.
* (4) Usually you stick to the [[Style Guideline|StyleGuideline]]s.
* (3) If, however, something is consistently labelled in a different style on official sources, then this classifies as [[Consistent Original Data|ConsistentOriginalData]] and overrules the [[Style Guideline|StyleGuideline]]<code><nowiki></nowiki></code>s. Note that you need to provide some evidence for [[Consistent Original Data|ConsistentOriginalData]] (ideally in the [[Edit Note|EditNote]]), or your edits will most likely be voted down.
* (3) If, however, something is consistently labelled in a different style on official sources, then this classifies as [[Consistent Original Data|ConsistentOriginalData]] and overrules the [[Style Guideline|StyleGuideline]]s. Note that you need to provide some evidence for [[Consistent Original Data|ConsistentOriginalData]] (ideally in the [[Edit Note|EditNote]]), or your edits will most likely be voted down.
* (2) There are, however, some [[Strong Guideline|StrongGuideline]]s, which overrule even such consistent official style. An example is the [[Abbreviation Style|AbbreviationStyle]], which states that most abbreviations are to be spelled out.
* (2) There are, however, some [[Strong Guideline|StrongGuideline]]s, which overrule even such consistent official style. An example is the [[Abbreviation Style|AbbreviationStyle]], which states that most abbreviations are to be spelled out.
* (1) Finally there is the notion of [[Artist Intent|ArtistIntent]]. If you can show that the artist ''intended'' something to be stylized a special way, then you should enter it like that into the database. Since it is somewhat difficult to find out what the artist intended and there might be controversial views, it is a good practice to discuss this in [[Edit Note|EditNote]]s or on the [[Users Mailing List|UsersMailingList]].
* (1) Finally there is the notion of [[Artist Intent|ArtistIntent]]. If you can show that the artist ''intended'' something to be stylized a special way, then you should enter it like that into the database. Since it is somewhat difficult to find out what the artist intended and there might be controversial views, it is a good practice to discuss this in [[Edit Note|EditNote]]s or on the [[Users Mailing List|UsersMailingList]].

Revision as of 05:53, 29 May 2009

Users of MusicBrainz and the members of the StyleCouncil put some great efforts in working out detailed StyleGuidelines, which state how data should be formatted. Since we stress these guidelines, people often get the impression that there is a rule that says: "Always follow the style guidelines".

But this is not true. Instead you should stick to this principle.

The Style Principles

If you ask yourself in what style something should be entered into MusicBrainz, the following rules apply in this order (strongest on top):

  1. Follow ArtistIntent.
  2. If 1 is not applicable, follow StrongGuidelines.
  3. If neither 1 nor 2 are applicable, use ConsistentOriginalData.
  4. If none of 1, 2 nor 3 are applicable, follow the StyleGuidelines.

Alternative phrasing

This can also be explained from the bottom upwards:

  • (4) Usually you stick to the StyleGuidelines.
  • (3) If, however, something is consistently labelled in a different style on official sources, then this classifies as ConsistentOriginalData and overrules the StyleGuidelines. Note that you need to provide some evidence for ConsistentOriginalData (ideally in the EditNote), or your edits will most likely be voted down.
  • (2) There are, however, some StrongGuidelines, which overrule even such consistent official style. An example is the AbbreviationStyle, which states that most abbreviations are to be spelled out.
  • (1) Finally there is the notion of ArtistIntent. If you can show that the artist intended something to be stylized a special way, then you should enter it like that into the database. Since it is somewhat difficult to find out what the artist intended and there might be controversial views, it is a good practice to discuss this in EditNotes or on the UsersMailingList.