Forum:Proposal to Organize Bracketed Addendums in Titles: Difference between revisions

Forum:Proposal to Organize Bracketed Addendums in Titles (view source)

Revision as of 18:50, May 26, 2011

8 bytes added , 13 years ago

no edit summary

Forerunner

9,203

edits

@@ Line 1: / Line 1: @@
 Hello there Halopedia, and addressing you today is none other than Halo-343; you know, that guy. This proposal, as its lengthy title might suggest to an attentive human being, is regarding the largely unneeded usage of bracketed addendums on Halopedia. I made a [[Talk:Main Page#Usage of bracketed addendums in article titles|similar post]] regarding this several days ago, and in response to agreement from several users, I've decided to formalize my suggestion, which this explanatory introduction now introduces.
-On to the purpose of this proposal, I've recently begun to notice a large usage of illogical addendums in a sizable amount of article titles lately, particularly those with a level of the same name. To give examples of this; [[343 Guilty Spark (Monitor)]], [[Armory (Room)]], [[High Charity (Structure)]], [[Cairo Station (Platform)]], [[Gravemind (Form)]], [[Kizingo Boulevard (Location)]], [[Tsavo Highway|Tsavo Highway (Location)]], [[Arbiter (Title)]] and countless others. If several articles share the same name, the bracketed distinction should only follow the titles of those named after the primary subject. For example, there are two instances in the Halo series titled "343 Guilty Spark"; the monitor and the level. The level is named after the monitor, thus should be the only article using bracketed information in its title to distinguish it from the primary subject, with a small note at the top of the page to cover any confusion ("Were you looking for ____?"). In addition to this, real-world subjects such as levels should not hinder the titling of a primary in-canon subject. If there is more than two instances, Gravemind for instance, the same rule should apply, but with a disambiguation page made to organize the other secondarily named pages, again with a note linking to it ("For other uses of "Gravemind", see Gravemind (disambiguation)"). In addition to this, in conjunction with Dragonclaws' proposal regarding capitalization, in instances where bracketed addendums are required, such wording should be lower case, not capitalized. For example, "(level)" is correct, "(Level)" is not.
+On to the purpose of this proposal, I've recently begun to notice a large usage of illogical addendums in a sizable amount of article titles lately, particularly those with a level of the same name. To give examples of this; [[343 Guilty Spark (Monitor)]], [[Armory (Room)]], [[High Charity (Structure)]], [[Cairo Station (Platform)]], [[Gravemind (Form)]], [[Kizingo Boulevard (Location)]], [[Tsavo Highway|Tsavo Highway (Location)]], [[Arbiter|Arbiter (Title)]] and countless others. If several articles share the same name, the bracketed distinction should only follow the titles of those named after the primary subject. For example, there are two instances in the Halo series titled "343 Guilty Spark"; the monitor and the level. The level is named after the monitor, thus should be the only article using bracketed information in its title to distinguish it from the primary subject, with a small note at the top of the page to cover any confusion ("Were you looking for ____?"). In addition to this, real-world subjects such as levels should not hinder the titling of a primary in-canon subject. If there is more than two instances, Gravemind for instance, the same rule should apply, but with a disambiguation page made to organize the other secondarily named pages, again with a note linking to it ("For other uses of "Gravemind", see Gravemind (disambiguation)"). In addition to this, in conjunction with Dragonclaws' proposal regarding capitalization, in instances where bracketed addendums are required, such wording should be lower case, not capitalized. For example, "(level)" is correct, "(Level)" is not.
 This was recently, and unofficially, implemented on [[Cortana]], which had previously been titled things like "Cortana (Character)", "Cortana (AI)" and "Cortana (Artificial Intelligence)". All those previous titles were made to distinguish "Cortana" from "Cortana (Level)", ''ignoring the fact that there was a clearly visible "(Level)" in the latter's title'', making the addendum on the former pointless, as the difference had already been outlined in the title of the latter. Now that I've pointed that out, doesn't what I'm proposing make a lot more sense? In further conjunction with a suggestion by Dragonclaws, the current practice of adding "(Level)" to every level title also applies, and the distinction should only follow the titles of levels that share a name with something else, i.e. "High Charity" and "High Charity (level)". Now, I have heard mention that Manticore placed a taboo on the word "disambiguation" in the title of disambiguation pages. Let me stress that, he ''placed a taboo on the word "disambiguation" in the title of disambiguation pages.'' Respectfully, that is ludicrous; the term "disambiguation" is needed to maintain consistency on any wiki, and what I'm proposing here further proves that. I haven't full validity on this tale of Manticore's doings, but regardless, it further drives my point.