History:Style Guideline: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
m (13 revision(s))
mNo edit summary
Line 1: Line 1:
[[MusicBrainz]] has a lot of relational data. But you still have to type plain text in all the database fields. In order for the database to be in a good consistent shape, the [[Style Council]] has agreed on a certain ''style'' according to which such text should be entered.
=Style Guidelines=


'''Note that the [[Style Principle]]s of [[MusicBrainz]] state:'''
[[MusicBrainz]] has a lot of relational data. But you still have to type plain text in all the database fields. In order for the database to be in a good consistent shape, the [[Style Council|StyleCouncil]] has agreed on a certain ''style'' according to which such text should be entered.
# '''Follow [[Artist Intent]].'''

# '''If 1 is not applicable, use [[Consistent Original Data]].'''
'''Note that the [[Style Principle|StylePrinciple]]s of [[MusicBrainz]] state:'''
# '''If both 1 and 2 are not applicable, follow the StyleGuidelines.'''
# '''Follow [[Artist Intent|ArtistIntent]].'''
# '''If 1 is not applicable, use [[Consistent Original Data|ConsistentOriginalData]].'''
# '''If both 1 and 2 are not applicable, follow the StyleGuideline<code><nowiki></nowiki></code>s.'''


==Principal Guidelines==
==Principal Guidelines==


The following guidelines are available:
The following guidelines are available:
* [[Official Style Guideline|OfficialStyleGuideline]]<code><nowiki></nowiki></code>s
* [[Official Style Guideline]]s
<ul><li style="list-style-type:none">This is a Wiki version of the [[Official Style Guideline|OfficialStyleGuideline]]s on the [http://musicbrainz.org/style.html website] which outline how the data in [[MusicBrainz]] should be formatted and organized. Being a [[Wiki Page|WikiPage]] it is more detailed and contains discussion, questions (and answers :-). It is also more up to date than the version on the website.
** This is a Wiki version of the [[Official Style Guideline]]s on the [http://musicbrainz.org/style.html website] which outline how the data in MusicBrainz should be formatted and organized. Being a [[Wiki Page]] it is more detailed and contains discussion, questions (and answers :-). It is also more up to date than the version on the website.
* [[Capitalization Standard]]
</ul>
** How to capitalize album and track titles. Since June 2004 we are working towards [[Internationalization||internationalization]]. This will give us language specific standards. [[Capitalization Standard]] lists all available standards for different languages.
* [[Capitalization Standard|CapitalizationStandard]]
* [[Classical Style Guide]]
<ul><li style="list-style-type:none">How to capitalize album and track titles. Since June 2004 we are working towards [[Internationalization|InterNationalization]]. This will give us language specific standards. [[Capitalization Standard|CapitalizationStandard]] lists all available standards for different languages.
** For classical music (or any music, where the composer is taken as the principal artist) different style rules apply, and different problems arise. These are all addressed in this section containing [[Classical Music FAQ]], [[Classical Style Guide]] and [[Talk:Classical Style Guide|ClassicalStyleGuideDiscussion]].
</ul>
* [[Classical Style Guide|ClassicalStyleGuide]]
* [[Proposed Style Guideline]]s
** This is a place for new style guidelines to be proposed and discussed.
<ul><li style="list-style-type:none">For classical music (or any music, where the composer is taken as the principal artist) different style rules apply, and different problems arise. These are all addressed in this section containing [[Classical Music FAQ|ClassicalMusicFAQ]], [[Classical Style Guide|ClassicalStyleGuide]] and [[Talk:Classical Style Guide|ClassicalStyleGuideDiscussion]].
</ul>
* [[Proposed Style Guideline|ProposedStyleGuideline]]<code><nowiki></nowiki></code>s
<ul><li style="list-style-type:none">This is a place for new style guidelines to be proposed and discussed.
</ul>


==Other Guidelines and Help==
==Other Guidelines and Help==


* [[Series Style Guideline|SeriesStyleGuideline]]<code><nowiki></nowiki></code>s
* [[Series Style Guideline]]s
<ul><li style="list-style-type:none">These are guidelines that apply to a specific series of releases only, but not to all entities in general.
** These are guidelines that apply to a specific series of releases only, but not to all entities in general.
* If you have a question regarding an [[Odd Release]] you might want to look for it in [[Additional Metadata]]. If you find it there your question might already been answered. If you do not find it, you can ask on the [[Users Mailing List]]. When your problem has been solved, please list your solution there to help others that come after you.
</ul>
* You might also want to look at [[How Editing Works]] and the [[Editing Guideline]]s as well as [[How To Vote]].
* If you have a question regarding an [[Odd Release|OddRelease]] you might want to look for it in [[Additional Metadata|AdditionalMetadata]]. If you find it there your question might already been answered. If you do not find it, you can ask on the [[Users Mailing List|UsersMailingList]]. When your problem has been solved, please list your solution there to help others that come after you.
* The [[Misencoding FAQ]] deals with data where something went wrong with the [[Character Encodings]] and what to do about it.
* You might also want to look at [[How Editing Works|HowEditingWorks]] and the [[Editing Guideline|EditingGuideline]]<code><nowiki></nowiki></code>s as well as [[How To Vote|HowToVote]].
* The [[Misencoding FAQ|MisencodingFAQ]] deals with data where something went wrong with the [[Character Encodings|CharacterEncodings]] and what to do about it.


===Changing Guidelines===
==Changing Guidelines==


The style guidelines form a very balanced set of rules. Changing them is a slow and careful process. Since 2005-12 a new process for [[Style Change|StyleChange]]<code><nowiki></nowiki></code>s is emerging. See [http://www.nabble.com/forum/Search.jtp?forum=2885&local=y&query=style+council+thoughts these email threads], [[How To Change Style Guidelines|HowToChangeStyleGuidelines]], and also the older guide on [[How To Propose New Guidelines|HowToProposeNewGuidelines]] for details.
The style guidelines form a very balanced set of rules. Changing them is a slow and careful process. Since 2005-12 a new process for [[Style Change]]s is emerging. See [http://www.nabble.com/forum/Search.jtp?forum=2885&local=y&query=style+council+thoughts these email threads], [[How To Change Style Guidelines]], and also the older guide on [[How To Propose New Guidelines]] for details.


The [[Migration Guideline|MigrationGuideline]] requires that major changes to the StyleGuideline be tested by [[Beta Editing|BetaEditing]] on the [[Test Server|TestServer]], to figure out if it entails any major [[Soft Structure|SoftStructure]] changes.
The [[Migration Guideline]] requires that major changes to the style guidelines be tested by [[Beta Editing]] on the [[Test Server]], to figure out if it entails any major [[Soft Structure]] changes.


[[Category:To Be Reviewed]] [[Category:Style]] [[Category:Index]]
[[Category:To Be Reviewed]] [[Category:Style]] [[Category:Index]]

Revision as of 10:00, 19 March 2009

MusicBrainz has a lot of relational data. But you still have to type plain text in all the database fields. In order for the database to be in a good consistent shape, the Style Council has agreed on a certain style according to which such text should be entered.

Note that the Style Principles of MusicBrainz state:

  1. Follow Artist Intent.
  2. If 1 is not applicable, use Consistent Original Data.
  3. If both 1 and 2 are not applicable, follow the StyleGuidelines.

Principal Guidelines

The following guidelines are available:

Other Guidelines and Help

Changing Guidelines

The style guidelines form a very balanced set of rules. Changing them is a slow and careful process. Since 2005-12 a new process for Style Changes is emerging. See these email threads, How To Change Style Guidelines, and also the older guide on How To Propose New Guidelines for details.

The Migration Guideline requires that major changes to the style guidelines be tested by Beta Editing on the Test Server, to figure out if it entails any major Soft Structure changes.