History:Style Guideline: Difference between revisions
From MusicBrainz Wiki
Jump to navigationJump to search
(HowEditingWorks (Imported from MoinMoin)) |
(typo (Imported from MoinMoin)) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=Style Guidelines= |
=Style Guidelines= |
||
[[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 |
[[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. |
||
'''Note that the [[Style Principle|StylePrinciple]]s of [[MusicBrainz]] state:''' |
'''Note that the [[Style Principle|StylePrinciple]]s of [[MusicBrainz]] state:''' |
||
| Line 27: | Line 27: | ||
* 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. |
* 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. |
||
* You might also want to look at [[How Editing Works|HowEditingWorks]] and the [[Editing Guideline|EditingGuideline]]<code><nowiki></nowiki></code>s. |
* 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. |
* 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 |
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 [[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|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. |
||
Revision as of 12:38, 2 July 2006
Style Guidelines
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 StyleCouncil has agreed on a certain style according to which such text should be entered.
Note that the StylePrinciples of MusicBrainz state:
- Follow ArtistIntent.
- If 1 is not applicable, use ConsistentOriginalData.
- If both 1 and 2 are not applicable, follow the StyleGuideline
s.
Principal Guidelines
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.
- 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 ClassicalMusicFAQ, ClassicalStyleGuide and ClassicalStyleGuideDiscussion.
- This is a place for new style guidelines to be proposed and discussed.
Other Guidelines and Help
- 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 HowEditingWorks and the EditingGuideline
s as well as HowToVote. - The MisencodingFAQ deals with data where something went wrong with the CharacterEncodings and what to do about it.
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 StyleChanges is emerging. See these email threads, HowToChangeStyleGuidelines, and also the older guide on HowToProposeNewGuidelines for details.
The MigrationGuideline requires that major changes to the StyleGuideline be tested by BetaEditing on the TestServer, to figure out if it entails any major SoftStructure changes.
