History:Style Guideline: Difference between revisions

From MusicBrainz Wiki
Jump to navigationJump to search
(MoreLinks and reformatting (Imported from MoinMoin))
(plural s (Imported from MoinMoin))
Line 9: Line 9:


The following guidelines are available:
The following guidelines are available:
* [[Official Style Guidelines|OfficialStyleGuidelines]]
* [[Official Style Guideline|OfficialStyleGuideline]]<code><nowiki></nowiki></code>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.
<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.
</ul>
</ul>
Line 18: Line 18:
<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><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>
</ul>
* [[Proposed Style Guidelines|ProposedStyleGuidelines]]
* [[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><li style="list-style-type:none">This is a place for new style guidelines to be proposed and discussed.
</ul>
</ul>

Revision as of 23:04, 7 October 2005

Style Guidelines

MusicBrainz has a lot of formalized data. But in all these formalized fields you still type plain text. In order for the database to be in a good consistent shape, we have agreed on a certain style in which to write this text.

Note that the StylePrinciples of MusicBrainz state:

  1. Follow ArtistIntent.
  2. If 1 is not applicable, use ConsistentOriginalData.
  3. If both 1 and 2 are not applicable, follow the StyleGuidelines.

The following guidelines are available:

  • This is a Wiki version of the OfficialStyleGuidelines on the website which outline how the data in MusicBrainz should be formatted and organized. Being a WikiPage it is more detailed and contains discussion, questions (and answers :-). It is also more up to date than the version on the website.
  • How to capitalize album and track titles. Since June 2004 we are working towards InterNationalization. This will give us language specific standards. CapitalizationStandard lists all available standards for different languages.
  • This is a place for new style guidelines to be proposed and discussed.

More

  • If you have a question regarding an OddRelease you might want to look for it in AdditionalMetadata. If you find it there your question might already been answered. If you do not find it, you can ask on the UsersMailingList. When your problem has been solved, please list your solution there to help others that come after you.
  • You might also want to look at the EditingGuidelines and at InformationOnEditing which explains how different edits work etc.
  • The MisencodingFAQ deals with data where something went wrong with the CharacterEncodings and what to do about it.