Wikipedia talk:Manual of Style: Difference between revisions
collapse (not collape) |
|||
Line 29: | Line 29: | ||
[Note: The commented out line with "16:29, 9 October 2022" needs to be deleted when the discussion in "[[#RfC: Internal consistency versus consistency across articles]]" ends so that this section does not stay here for 10 years] - [[User:Apteva|Apteva]] ([[User talk:Apteva|talk]]) 17:06, 11 October 2012 (UTC) |
[Note: The commented out line with "16:29, 9 October 2022" needs to be deleted when the discussion in "[[#RfC: Internal consistency versus consistency across articles]]" ends so that this section does not stay here for 10 years] - [[User:Apteva|Apteva]] ([[User talk:Apteva|talk]]) 17:06, 11 October 2012 (UTC) |
||
{{collapse top}} |
|||
Noetica removed these words [''See correction below.–Noetica ☺''] – "though not necessarily throughout Wikipedia as a whole" – from this lead sentence: |
Noetica removed these words [''See correction below.–Noetica ☺''] – "though not necessarily throughout Wikipedia as a whole" – from this lead sentence: |
||
Line 204: | Line 204: | ||
* '''Comment''': It's obvious to anyone who thinks about it for a few seconds that this entire "intra- vs. inter-article consistency" thing is a false dichotomy. There is absolutely no conflict between the two ideas, except that which is purposefully manufactured by people who refuse to write in a way that is consistent between articles, just to [[WP:SSF|satisfy their own personal stylistic preferences at everyone else's expense]]. The "versus" that is latent in this discussion is entirely artificial. It's what the British call a load of bollocks, and Americans refer to as total bullshit. — <font face="Trebuchet MS">'''[[User:SMcCandlish|SMcCandlish]]''' <span style="white-space:nowrap;">[[User talk:SMcCandlish|Talk⇒]] ɖ∘¿<font color="red">¤</font>þ </span> <small>[[Special:Contributions/SMcCandlish|Contrib.]]</small></font> 23:38, 8 September 2012 (UTC) |
* '''Comment''': It's obvious to anyone who thinks about it for a few seconds that this entire "intra- vs. inter-article consistency" thing is a false dichotomy. There is absolutely no conflict between the two ideas, except that which is purposefully manufactured by people who refuse to write in a way that is consistent between articles, just to [[WP:SSF|satisfy their own personal stylistic preferences at everyone else's expense]]. The "versus" that is latent in this discussion is entirely artificial. It's what the British call a load of bollocks, and Americans refer to as total bullshit. — <font face="Trebuchet MS">'''[[User:SMcCandlish|SMcCandlish]]''' <span style="white-space:nowrap;">[[User talk:SMcCandlish|Talk⇒]] ɖ∘¿<font color="red">¤</font>þ </span> <small>[[Special:Contributions/SMcCandlish|Contrib.]]</small></font> 23:38, 8 September 2012 (UTC) |
||
{{ |
{{collapse bottom}} |
||
== RfC: Internal consistency versus consistency across articles == |
== RfC: Internal consistency versus consistency across articles == |
Revision as of 17:13, 11 October 2012
File:Yellow warning.png | This page (along with all other MOS pages and WP:TITLE) is subject to Arbitration Committee discretionary sanctions. See this remedy. |
![]() | For a list of suggested abbreviations for referring to style guides , see this page. |
Internal consistency v consistency across articles
[I have restored this section just after it was archived; it includes argument that is relevant to the current RFC (see just below), which explicitly makes reference to it.–NoeticaTea? 08:10, 16 September 2012 (UTC)
Restored again, for the same reason.–NoeticaTea? 08:22, 11 October 2012 (UTC)]
[Note: The commented out line with "16:29, 9 October 2022" needs to be deleted when the discussion in "#RfC: Internal consistency versus consistency across articles" ends so that this section does not stay here for 10 years] - Apteva (talk) 17:06, 11 October 2012 (UTC)
Extended content
|
---|
Noetica removed these words [See correction below.–Noetica ☺] – "though not necessarily throughout Wikipedia as a whole" – from this lead sentence:
As the lead already mentions internal consistency, this sentence is arguably repetitive without the juxtaposition. More importantly, we don't require consistency across articles, and it's important to stress that. The lead currently implies that we do, or at least does not make clear that we don't:
Therefore, the addition of "though not necessarily throughout Wikipedia as a whole" (or similar) is needed. SlimVirgin (talk) 02:38, 22 August 2012 (UTC) The first sentence of this section inadvertently misrepresents what happened. The sequence of events (all on 12 August 2012):
Slim, would you please amend that first sentence? Best to keep the account accurate. ♥ [Note: I have exhausted my reserves of time for dealing with this issue. I see that Slim did not make the factual correction I requested (see immediately above). For the RFC on this page (#RfC: Internal consistency versus consistency across articles), please refer to the detail in all of my submissions in this earlier section. I explain my temporary absence in that RFC. ☺NoeticaTea? 03:43, 7 September 2012 (UTC)]
I disagree with "In groups of articles on similar topics, similar styling is better than an unprincipled or random selection of styles." this has never been a requirement. The problem is what is a group? For example it could be argued that all articles about any subject within the countries of the EU should use British English/Irish English because the EU does. Or all articles on NATO (except those specifically about Britain and Canada) should use American English because the US is by far the largest contributor to NATO and therefore most articles about NATO are about American topics, and As NATO is deployed in Kosovo and Kosovo is not a member of th EU all articles about Kosova should be in American English. This type of argument has never been accepted. One can see the fun one can have with arguments such as if its in a category its grouped in that category therefore it has to be consistent with all the other articles that appear in that category (An editor at the moment is using that as a justification for using his preferred spellings and ignoring usage in reliable sources). When an article appears in two categories then in which "group" does it belong? This is why the MOS has only ever agreed that consistency should within an article, not across "groups" of articles. I am with SV, EN and Darkfrog24 on this one. If as has been said "SlimVirgin restored some wording that had been long absent from MOS" then as it is a sentence that sums up a lot of Arbcom decisions, when was it deleted who deleted it and what was the justification given on this talk page for the deletion? -- PBS (talk) 10:15, 25 August 2012 (UTC)
There seems to be agreement to restore "though not necessarily throughout Wikipedia as a whole." Enric Naval, Darkfrog, PBS and I are in favour; Noetica and Curb Chain are opposed; Mirokado wants consistency between closely related articles, but not necessarily across WP. I think the more people we ask, the greater the consensus will be against requiring cross-WP consistency, so I'll go ahead and restore those words. I think the lead could use some general tweaking too, but I'll address that separately. SlimVirgin (talk) 16:13, 31 August 2012 (UTC)
BreakThe problem is that the second and third paragraphs contradict each other. The second says we have a house style; the third says we do not. Both have redirects (WP:CLARITY redirects to the second, and WP:Stability and WP:STYLEVAR to the third), so anyone reading those in isolation would be misled.
SlimVirgin (talk) 16:30, 31 August 2012 (UTC)
Additional discussionI just want to note that I agree that User:Noetica was correct in removing the discussion that User:SlimVirgin started by pulling the archive instead of linking it, but some comments had been added when she restarted the discussion:[1]Curb Chain (talk) 03:05, 25 August 2012 (UTC)
Reversion of non-consensual edits concerning inter-article consistencyI have reverted (see diff) two edits by SlimVirgin. The change in question clearly has no consensus. Editing and discussion for this page are subject to ArbCom discretionary sanctions (see the note at the top of this talkpage); so a high standard of conduct and respect for due process applies. Please discuss more, and if necessary initiate a neutral RFC. If any RFC is not set up in neutral terms, according to the provisions of WP:RFC, I will call for its immediate closure and refer the matter to WP:AE. Please note especially: This is not intended as inimical to any good-faith development of the page; but experience has shown how these things can escalate, and how they can wear away people's time and patience. ♥
As Noetica continues to object, I've opened an RfC below. Apologies if it ends up being largely repetitive, but it might attract fresh eyes and we can request a formal closure to avoid arguments. SlimVirgin (talk) 01:17, 1 September 2012 (UTC)
|
RfC: Internal consistency versus consistency across articles
[Here I have reverted the irregular closure of part of the material that constitutes the RFC (simply by removing the template markers that added the heading "The following discussion is closed. Please do not modify it."). That closure was executed by SlimVirgin, the RFC's proposer. Please wait for an admin to sort out this unholy mess, rather than adding even more irregularities to an RFC that was mismanaged from the start. ☺ NoeticaTea? 22:18, 8 October 2012 (UTC)]
The RfC was opened on 1 September. It asked whether the words "though not necessarily throughout Wikipedia as a whole" should be removed from the lead sentence: "An overriding principle is that style and formatting choices should be consistent within an article, though not necessarily throughout Wikipedia as a whole."
The RfC was closed on 4 October by an uninvolved editor, Nathan Johnson, following a request at AN/RFC. He concluded: "The consensus of the discussion was to oppose the removal of the phrase." Noetica reverted his closure twice, [2] [3] asking that it be closed by an admin. I am therefore going to ask an uninvolved admin to endorse or overturn the closure. SlimVirgin (talk) 16:21, 8 October 2012 (UTC)
RfC
This sentence had been in the MoS for some time: "An overriding principle is that style and formatting choices should be consistent within an article, though not necessarily throughout Wikipedia as a whole." The whole sentence was removed 12 months ago, [4] then restored, [5] then it was changed so that it read: "An overriding principle is that style and formatting choices should be consistent within an article." [6] [7]
Should the words "though not necessarily throughout Wikipedia as a whole" be removed from that sentence? SlimVirgin (talk) 01:00, 1 September 2012 (UTC)
- [Correction by Noetica: The sentence in question had been absent from MOS for over 12 months, till Slim Virgin reinstated it a few days ago. It was then removed by an editor, and then restored in part by Noetica.]
Replies
- [no threaded discussion here, please]
- Oppose removal. There has always been an understanding that internal consistency is required when it comes to style issues, but not consistency across articles. There are formatting issues that are applied across the board (the general layout, for example). But when it comes to language variations, punctuation, and a host of other issues, we allow the editors on the page to decide, sometimes governed by personal preference, sometimes by whether a particular English-language variant ought to be dominant. The words "not necessarily throughout Wikipedia as a whole" signal that cross-article consistency is sometimes expected, but not always, and I feel it's important to retain that point. SlimVirgin (talk) 01:14, 1 September 2012 (UTC)
- I am opposing the removal because style consistency across articles has always been discouraged since the "date delinking" edit wars years ago. It's clear and concise. The removal leaves room for other interpretations. --Enric Naval (talk) 14:12, 1 September 2012 (UTC)
- Oppose removal. per SlimVirgin and Enric. (Maybe we can get "Description not prescription" added back to wherever it was, too, eventually...) Time is not especially relevant, the detail/context that the sentence contains, is. -- Quiddity (talk) 19:40, 1 September 2012 (UTC)
- Oppose removal. I think it's important to include a phrase that underscores the point that we have options for styles. Otherwise MOS would require, say, American English and SI units and common date formats across all articles. The MOS is not a prescription to be applied slavishly to all articles. A short phrase serves as a useful reminder of that fact, and its removal, as Enric Naval pointed out, leaves room for other interpretations, contributing to wasted time in needless debates about inter-article consistency. ~Amatulić (talk) 04:00, 2 September 2012 (UTC)
- Oppose removal. The sentiment expressed by the phrase in question is essential to preventing disputes over English spelling style, comma style, referencing style, etc. "The wonderful thing about standards is that there are so many of them to choose from." <grin> We should emphasize that we are not here to make everybody toe the same line. If somebody's formatting can be traced to a practice that is accepted in a particular venue, then that formatting should be allowed. Binksternet (talk) 04:35, 2 September 2012 (UTC)
- Oppose removal. It must be understood that an absolute consistency across articles is not possible with the diverse population we have and hope to have. This lack of rigid consistency must be explicitly permitted, along with the wish expressed that styles be referenced and adhered to when possible. But when the permissiveness disappears
silentlyquietlywithout much notice to the common editor, the appearances are chilling.
- Which brings up two issues on my own mind. Noetica, do you really think that 12 months is a long time, for pages which nominally are to be used to guide the entire 'pedia? You've been here since 2005, seven years. The lapse of one year before even active editors discover a misjudged edit is not unreasonable. It would seem from your strong surprise that a year could possibly be called 'recent' that you must be far too familiar with these environs to tell on that particular.
- These pages are not welcoming, quite dense, often confounding, and I am not surprised that editors would not often make themselves available to review proposed changes. Saying that "see talk" is sufficient for changes to MOS would seem to me to be entirely insufficient for the average non-MOS-wonk editor.
- Removing the explicit allowance for editors to not be required to conform to the tittle of MOS, through a change by the MOS-most editors, is troubling on multiple levels. Shenme (talk) 06:27, 2 September 2012 (UTC)
- Support the removal of text that was done twelve months ago. The stress on intra-article consistency is fine, of course. So is motherhood. But why labour to include what many editors have unfortunately misread as a licence for chaos? Groups of articles on similar themes benefit enormously from similar styling (where MOS allows for a choice). Why bend over backwards against such efforts? They are clearly in readers' interests. MOS was, till a few days ago, silent on such laudable efforts. What benefit is there in it making a statement that is bound to be misused by those who favour complete independence of styling, at each of 4,000,000 articles? No one is suggesting that a contrary statement be made; just that it is not the business of MOS inadvertently to counter worthwhile efforts to improve the readability of closely associated articles.
- NoeticaTea? 08:51, 2 September 2012 (UTC)
- [NOTE: As I explain below in "Threaded discussion", I am tied up with matters in real life. I have said all I need to say for this RFC, in the discussion earlier on this page: #Internal consistency v consistency across articles. The question facing us is important, and I advise people not to conflate consistency of style for Wikipedia in general (the very essence of MOS) and consistency of style where choices are allowed in MOS (and there are very few such choices, at least in WP:MOS itself). Misreadings we observe in this RFC illustrate the very problem that such carelessly added wording introduces: people do not read accurately, nor discriminate as we expect they will. ♥ NoeticaTea? 03:52, 7 September 2012 (UTC)]
- Oppose removal by which I really mean "support re-insertion." Wikipedia is not like other encyclopedias. It requires on the unpaid service of editors from many disparate backgrounds and it has no chain of command. There's no one who can legitimately say, "Do it this way because I'm the boss and I've earned my authority." Inter- but not intra-article consistency strikes a balance between neatness and the diversity of opinion among our editors. If it is "bound to be misused," then show at least one case in which that has happened. Has an editor ever claimed "We are not allowed to make these articles match each other; the MoS says so"? Darkfrog24 (talk) 13:31, 2 September 2012 (UTC)
- Oppose removal/retain - This would also seem to fall afoul of WP:ENGVAR, among other things... - jc37 20:04, 2 September 2012 (UTC)
- I think the sentence should be re-inserted. It's good for readers of the MOS to see a reminder that it is meant to include only a minimal amount of standardization, and that there are many reasons why different articles will have different styles. Where some see chaos in numerous styles, I see a field of wildflowers. — Carl (CBM · talk) 21:25, 2 September 2012 (UTC)
- Comment. In my opinion, style and formatting inconsistencies across articles within English Wikipedia should be viewed as unavoidable exceptions to a general ambition that Wikipedia should be as consistent as possible throughout. Inconsistency should not be tacitly encouraged or presented as part of a "principle". 86.160.221.242 (talk) 16:40, 3 September 2012 (UTC)
- Support re-removal per Noetica, and per the fact that the removal has been stable for a long time, and the fact that we do not need to repeat everything ever said in every guideline and policy on the system. It's already implicit in MoS's mandate as a guideline that it operates in juxtaposition and compromise with other forms of guidance here. Reiterating that a guideline can have exceptions, or that any particular guideline is not an ironclad policy, is not what we do here. Also, it really has been misinterpreted as a license for chaos. It was removed for a reason.
Furthermore, there's an underlying assumption (one that is often advanced by the sort of editorial misprioritization addressed by WP:SSF, and WP:NOTHERE before it) that inter-article consistency is not desirable, and is immediately trumped by narrow, even personal preferences. Yet, obviously it is desirable to the extent that it can happen without raising intractable problems (like those addressed by WP:ENGVAR). If it were not desirable MOS would be very short, as the bulk of it and its subpages is style advice for dealing with English-language prose across all articles here. Material is not being broken out of MoS into small, topic-specific WikiProject "guidelines"; rather, the exact opposite is happening: Good advice from projects is making its way steadily into MoS so that it is applied consistently in articles on other topics.
— SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 08:24, 4 September 2012 (UTC) - Support re-removal When one says 'consistent within an article' and is mute on what happens outside, lack of consistency between articles is unambiguous as implied in the guideline. There is no ambiguity in its absence, and I find the deleted half superfluous and repetitive. --Ohconfucius ¡digame! 08:49, 4 September 2012 (UTC)
- Support removal. The main purpose of the MoS , like other guidelines, is to achieve a level of consistency above the level of the individual article. Even in the case of the exceptions which prove the rule, like WP:ENGVAR we strive for consistency with things like WP:COMMONALITY. It is not required, but within the context of the Manual of Style we should not stress that it is unnecessary, thus giving the impression that it not desired. I think we achieve a reasonable balance by not mentioning it at all in this sentence.--Boson (talk) 09:04, 4 September 2012 (UTC)
- Remove to reduce chaos – "though not necessarily throughout Wikipedia as a whole" sounds like the opposite of what MOS is about, which is to encourage some consistency of style across WP. Dicklyon (talk) 05:02, 5 September 2012 (UTC)
- Support removal.—It's unnecessary to confuse editors on this point, when the whole of MoS concerns stylistic consistency on en.WP. The absence of this text in no way suggests that articles have to be consistent with each other where a choice is allowed (engvar, em vs en dashes as interruptors, etc). Tony (talk) 06:57, 5 September 2012 (UTC)
- Oppose removal (of "though not necessarily throughout Wikipedia as a whole.") This is another case where discussion of wording changes gets confused with discussion of policy changes. "An overriding principle is that style and formatting choices should be consistent within an article" of itself implies that between articles consistency of such choices is not of "overriding" importance, so if we were only discussing wording, I don't see the need for "though not necessarily throughout Wikipedia as a whole." That there is no overriding requirement for consistency throughout Wikipedia as a whole is clear from many other places (ENGVAR, choice of citation styles, etc.). If on the other hand those who don't want to include "though not necessarily throughout Wikipedia as a whole" seek thereby to change policy (as some comments above imply), so that consistency between articles becomes an "overriding principle", then these words should certainly be present, otherwise the implication is that consistency overrides ENGVAR, etc. Peter coxhead (talk) 09:23, 5 September 2012 (UTC)
- Retain/oppose removal' - The key words being "not necessarily". On those formatting issues about which broad community-wide discussion arrives at a consensus, consistency can and should be enforced, but about those the community maintains a more laissez-faire attitude, editors should have the leeway to improve articles as they see fit, given the specific needs of the specific article, without having to answer to those who try to enforce a non-existing consensus. The very most important thing, which it is best that we put our energies to, is to give our readers good, accurate information, well presented, rather than that every article have every tiny formatting aspect be exactly the same. Such "fooliosh consistency" is, in Emerson's words "the hobgoblin of little minds", in Shaw's words "the enemy of enterprise", and in Wilde's words "the last refuge of the unimaginative." Surely our editors are just the opposite: enterprising, imaginative and open to the world. Beyond My Ken (talk) 01:37, 6 September 2012 (UTC)
- Oppose Though they certainly are superfluous these few words can serve as a reminder to people of how we do things here. It would be much easier to point a misguided editor to this phrase than to the absence of words to the contrary. There may not be a lot of benefit but the cost is nanofarthings. JIMp talk·cont 09:25, 6 September 2012 (UTC)
- Support removal. Of course the Manual of Style applies to the whole of Wikipedia. That's what it's for. Are we now to have local consensus for commas? Em-dash wars breaking out in Birds? Apostrophe wars in Composers? WP:BEANS Neotarf (talk) 06:49, 11 September 2012 (UTC)
- Support removal. The extra words seem to be encouraging inconsistency far too strongly.
, indeed one responder says "consistency across articles has always been discouraged" which seems a good example of a rule which should always be ignored: should I look for ways of making every article I edit inconsistent with every other article?The wording chosen should not give anybody an excuse to be uncooperative, whether they wish to apply something too widely or ignore interrelationships between articles. Although readers must accept that Wikipedia's articles follow no single strict house style, they are not well served if, for example, individual articles covering the six books of a series have corresponding content distributed differently across sections, perhaps in a different order or with different names. The work of adding related information to several such articles could be doubled or trebled depending on how they were inconsistent and such barriers to editing cannot contribute to content improvement. Not even in a single article do we revert constructive additions merely because a wrong sort of dash has been used, so I do not see consistency within an appropriate scope, maintained tactfully, as stifling new content. Neither would any expectation of consistency remove the necessity for having consensus to maintain it: I would expect the ease of finding consensus to correspond to the closeness of the relationship in a self-limiting way. --Mirokado (talk) 14:00, 11 September 2012 (UTC) - Oppose removal. It is kind of silly for a project that uses four different flavours of English and can't decide what it thinks about the usage of diacritics to try and pretend that internal consistency is really all that important. When you get right down to it, Wikipedia is the informational equivalent of a quilt. It is a patchwork design that comes together into a single pattern despite the differences found on each tile. I see no reason to replace that with a unitarian attitude. Resolute 01:18, 14 September 2012 (UTC)
- Meh. Should talking about the other part; there is far too much different-as-hell but internally-consistent going on. Consistency across the project is needful, with any variations being on a level vastly larger than individual articles. And no, don't talk to me about WikiProjects taking any lead, here. Br'er Rabbit (talk) 04:32, 14 September 2012 (UTC)
- Oppose removal and reinstate the words per Slim, Resolute and Peter Coxhead. It's how we do things, and policies and guidance describe how we do things. Hiding T 11:00, 14 September 2012 (UTC)
- Oppose removal Editors should be allowed to edit, to create articles. No one wants to see WP become an homogeneous blob. Part of its charm is that the best articles do bear the stamp of their creator. The phrase should be retained. It's not tautological. It makes explicit an import aspect of WP's ethos. 87.112.91.134 (talk) 14:39, 14 September 2012 (UTC)
- Oppose removal/Support retaining the bit that says that we don't need to be consistant across all of Wikipedia. --Jayron32 00:44, 15 September 2012 (UTC)
- Meh, seems to make little difference either way. I would prefer to argue over something juicier like diacritics or nested quotation marks ;) Kaldari (talk) 04:43, 15 September 2012 (UTC)
- Support Removal per the smart people above. 128.127.107.10 (talk) 05:26, 16 September 2012 (UTC)
- Support removal, per Special:Contributions/86.160.221.242: In my opinion, style and formatting inconsistencies across articles within English Wikipedia should be viewed as unavoidable exceptions to a general ambition that Wikipedia should be as consistent as possible throughout. Inconsistency should not be tacitly encouraged or presented as part of a "principle". -- Strongest point made in this discussion, bar none. We strive to present a consistent and consistently formatted encyclopedia to the public. A reminder to watch consistency first on the level of the individual article is perfectly fine, but the words "though not necessarily throughout Wikipedia as a whole" explicitly defy the purpose of having a Manual of Style in the first place. --87.79.226.106 (talk) 00:32, 17 September 2012 (UTC)
- Support removal. Overall consistency in formatting and style across the entire English Wikipedia is an important goal also. Certainly exceptions can exist, but that language implies that broader consistency is of little importance. Rreagan007 (talk) 17:41, 17 September 2012 (UTC)
- Oppose removal/support replacing that phrase, unless I'm the person who gets to decide what that applies-to-all-articles style is going to be. We need more live and let live where style is concerned, and less time wasted in discussions about whose style of spelling, citing, image formatting, etc. is the one true way. WhatamIdoing (talk) 22:27, 17 September 2012 (UTC)
Threaded discussion
Some questions
- Question - How does this apply to an issue like "The" v. "the Beatles"? Could/should we have our article about the Beatles use "The" while those about John, Paul, George and Ringo use "the"? ~ GabeMc (talk|contribs) 03:56, 7 September 2012 (UTC)
- In my opinion, no. Wikipedia should have a global view on that (unless the different camps become so entrenched and intractable that people just give up trying). 86.128.4.124 (talk) —Preceding undated comment added 11:36, 7 September 2012 (UTC)
- And if that happens, go with MoS's default position, which is inter- as well as intra-article consistency. Those who would make weird exceptions have the burden on them to demonstrate a need for it. — SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 23:19, 8 September 2012 (UTC)
- The MoS does not have a default position for inter-article consistency. Darkfrog24 (talk) 14:12, 9 September 2012 (UTC)
- Come on guys, don't descend into slipshod language again and again. See my admonishments to distinguish what are quite distinct issues, above. Sheesh! If we at this talkpage don't read with care, how do we expect readers of MOS to get the message? That is the core problem in this discussion.
- SMcCandlish refers to "MoS's default position, which is inter- as well as intra-article consistency". Of course. That's the purpose of a manual of style!
- If anyone (Enric Naval? Darkfrog?) thinks Wikipedia should not have a genuine, effective MOS, let them go to the village pump and argue their case. Or mount a self-contained RFC. Here, however, the business is to develop a manual of style that functions as one. It now qualifies as a major manual of style in its own right, and there is nothing remotely approaching it on the web – or for the web – in quality and coverage. You doubt that? Show us a better one! If anyone thinks MOS includes whims or foibles, let them argue here for particular improvements. That's the core purpose here.
- So finally, for now: Do not spread confusion. Do not conflate these two issues:
- Consistency of style generally
(the purpose of MOS) - Consistent application of styles where MOS provides for a choice
(a much smaller concern, the details of which are the present topic; it can only apply to groups of related articles, otherwise MOS would not provide for choices at all)
- Consistency of style generally
- It is grossly irresponsible to hijack an RFC concerned with 2 to further one's agenda with 1.
- ♫♪
- NoeticaTea? 23:51, 9 September 2012 (UTC)
- Take your own advice, Noetica. No one said that Wikipedia should not have an effective MoS. The MoS does (or used to and should again) state that intra-article consistency is its purpose. It does not state that inter-article consistency is. One can imagine a default position, but no true one is given. Darkfrog24 (talk) 02:53, 10 September 2012 (UTC)
- Obdurate obfuscation. I have no time for this, as I have said. You write: "It does not state that inter-article consistency is [its purpose]." What? Inter-article consistency is the blindingly obvious plain supposition behind every manual of style. You wonder why I go on at length, repeating what I have already plainly stated in a few words? Think afresh; actually read what I write, and you might get it. You utterly, repeatedly, and apparently wilfully fail to see the crucial distinction that I have marked out several times already. Do better.
- ♥
- NoeticaTea? 03:27, 10 September 2012 (UTC)
- In other words, you looked at what the MoS said, and you drew your own inference about what it meant. Don't complain when other people do the same thing. I might read Hamlet and think that it's "blindingly obvious" that Hamlet's insane, but someone else might think that he's faking. I'm not "willfully failing" to listen to you. I just don't agree with you.
- What we know for certain is that the MoS does explicitly state that intra-article consistency is a goal and does not explicitly state that inter-article consistency is. Darkfrog24 (talk) 18:41, 10 September 2012 (UTC)
- A recklessly inept response, and unworthy. To mimic your analogy, missing the fact that MOS is about general consistency between all articles would be like reading Hamlet and missing the fact that it is a play. Hamlet is very evidently a play, even though there is no declaration like "this is a play, and is to be acted by actors in front of an audience". Its proper title: The Tragedy of Hamlet, Prince of Denmark. You have to know: in those days especially, a tragedy is a play. It has a list of dramatis personae, it is divided into acts and scenes, it is set up in standard dialogue format, and has stage directions. Now, the proper title for MOS: Wikipedia:Manual of Style. Kind of gives the game away, doesn't it? And what is a manual of style, that applies to 6,872,482 articles? It is necessarily a guide to elements of consistency, for and across all those articles. You continue to confuse the issue. Yes, MOS provides for some variation. But yes, MOS rightly stresses especially consistency within any given article. What is here under dispute, though you steadily refuse to acknowledge it, is the extent to which those few variable elements might vary across related articles. The issue could not rationally be anything else. You just don't read that; it seems to suit your agenda (and Enric Naval's, and sockpuppeting campaigner PMAnderson's) to insist instead on making MOS ineffectual. You would prefer that it have less influence, and that it not work toward general uniformity of style, across four million articles. But that is not what this RFC is about. Nor is it what the contested wording is about. Stop pretending that it is. Yet again: people will misread the wording that SlimVirgin inserted in MOS, which she now wants restored. You misread that wording, and you are a regular here. So it is even more likely that those less familiar with MOS will misread it. Where has this been a problem, you ask? I have answered: the best example I know is the life-wasting wrangling over Mexican–American War, in which you, Enric Naval, and PMAnderson pushed the same anti-MOS agenda, with the same perverse appeal to Slim's ill-advised and misleading words in MOS. Get it.
- ☺
- NoeticaTea? 01:08, 11 September 2012 (UTC)
- What this means, Noetica, is that you and I looked at the same document and came to different conclusions about it. That does not make me unworthy in any way or designate you as fit to give anyone orders. You have an agenda yourself: You don't want people to be allowed to do things in ways that you don't like, regardless of whether they can be proven to be correct or incorrect English.
- Just because I don't think that pushing inter-article consistency or whims like WP:LQ is a good idea doesn't mean I don't want the MoS to be followed. Removing stupid and arbitrary rules from the MoS makes people less likely to disregard the sensible ones.
- This conversation is in response to SmC's assertion that inter-article consistency is the MoS's default setting. I responded "The MoS does not have a default setting for inter-article consistency." The RfC is about whether the MoS should have a statement stating that its purpose is int
erra-article consistency, so that comment is relevant. - So, because I disagree with you, I must have misread the wording? Actually, my understanding is that you think that the fact that the MoS exists is proof that it must exist for the purpose of inter-article consistency, and that is what I don't accept.
- Your comments seem to have a recurring theme of "The fact that you disagree with me is proof that you don't understand the issue." That's not a very logical argument. Darkfrog24 (talk) 01:59, 11 September 2012 (UTC)
- Palpable misrepresentations, Darkfrog.
- I did not say you were unworthy. I said: "A recklessly inept response, and unworthy." It was unworthy of you, as a committed contributor at this talkpage.
- You have no ground for the claim that I "don't want people to be allowed to do things in ways that [I] don't like". That is an irresponsible accusation. I am not forcing anyone to do anything; nor is MOS. MOS includes many provisions that I think are absurd; but I choose to respect MOS, and I hope other editors will do the same (as WP:POLICY says they should).
- What you prejudicially characterise as "pushing inter-article consistency" is the very purpose of MOS. Again and again you fail to make the elementary distinction that I have again and again invited you to grasp.
- WP:LQ is not "a whim". If it were, it could easily be exposed as one; and it could be removed. Your failure to achieve that removal does not prove that it is a whim. Quite the contrary.
- You write: "The RfC is about whether the MoS should have a statement stating that its purpose is inter-article consistency, ...". Inaccurate to the point of being straight-out false.
- You write: "Removing stupid and arbitrary rules from the MoS makes people less likely to disregard the sensible ones." So what? I want to remove those also! We all want to. Keep working on it, by all means. But don't weaken the standing of MOS in the meantime.
- Your "understanding" shows that you do indeed miss the points that I have made. Because of your missing them, I repeat them; and still you miss them. If you have an alternative account of what a manual of style is, please share it. I have spelt out my account (which is the almost universal account, note). Let's see yours.
- You wrongly apprehend the recurring theme of my posts. It is not your disagreeing with me that I find unacceptable; it is that you do not address the evidence and the arguments that I present.
- It is a cheap and transparent tactic to ignore the arguments as actually given, present a straw man in their place, and then finish with the judgement "That's not a very logical argument."
- NoeticaTea? 05:47, 11 September 2012 (UTC)
- That "inter" was a typo for "intra." I meant to say "This is about whether the MoS should state that intra-article consistency is its purpose."
- So if I said "These posts are full of drama queen histrionics," you wouldn't think that I was calling you a drama queen? You wouldn't be insulted or consider it a personal attack? Because I think you would.
- The difference seems to be that you think that just because the MoS says something doesn't mean people have to do it, so it doesn't matter if it contains unnecessary rules (and those rules might as well match your own preferences). However, people can be censured and punished for disobeying the MoS, so we must be more careful.
- WP:LQ is a whim in that people like it but it offers Wikipedia no real benefit. It is not my failure to have it removed that proves that it's a whim. It's the fact that it contradicts established sources and that no one has been able to point to even one incident of American English punctuation causing any problems that proves this. It takes more than logic and the sources to get a popular problem out of the MoS. It would be great if it didn't work that way, but it does.
- There is a difference between most manuals of style and the Wikipedia manual of style. That difference is that the WP:MoS is meant for Wikipedia, which is 1. crowdsourced and 2. dependent on the donated service of editors from around the world. The difference in skill, training and range of expertise is immense. Because they are not being compensated, we shouldn't expect them to take orders the same way we could expect paid employees to and we shouldn't expect every article to be exactly the same the way we could expect articles in Britannica to be. If we want to keep our contributors, we need to make compromises, and accepting that consistency has its limits is one of them.
- My idea of a strong MoS is one that is obeyed. Not requiring inter-article consistency or a serial comma or any given point does not make people less likely to do what the MoS does tell them to do. Think of two teachers in a grammar school: One of them has a million rules about how the kids' legs should be positioned when they sit and exactly how far apart their coats should be on the rack. The other teacher has fewer rules but they're more about safety and schoolwork. Which one are the students less likely to disregard as a control freak or jerk? Which one is likely to have students who think that rules in general are made to be broken?
- Noetica, you haven't presented any evidence in this thread ("Questions"). You've only repeated your opinions. You sound like you think I should take your word as proof. Darkfrog24 (talk) 14:53, 11 September 2012 (UTC)
- Palpable misrepresentations, Darkfrog.
- Take your own advice, Noetica. No one said that Wikipedia should not have an effective MoS. The MoS does (or used to and should again) state that intra-article consistency is its purpose. It does not state that inter-article consistency is. One can imagine a default position, but no true one is given. Darkfrog24 (talk) 02:53, 10 September 2012 (UTC)
- The MoS does not have a default position for inter-article consistency. Darkfrog24 (talk) 14:12, 9 September 2012 (UTC)
- And if that happens, go with MoS's default position, which is inter- as well as intra-article consistency. Those who would make weird exceptions have the burden on them to demonstrate a need for it. — SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 23:19, 8 September 2012 (UTC)
- In my opinion, no. Wikipedia should have a global view on that (unless the different camps become so entrenched and intractable that people just give up trying). 86.128.4.124 (talk) —Preceding undated comment added 11:36, 7 September 2012 (UTC)
- Concur with anon. Where something is clearly incorrect English and can be shown through sources to be incorrect English, like capitalizing "the" mid-sentence, then the MoS should not allow people to use it. This is a separate issue, dealing with optional matters, like whether or not to use the serial comma. As for "The Beatles," its my understanding that their fans kept shouting until the opposition was too tired to object any more. Darkfrog24 (talk) 17:05, 8 September 2012 (UTC)
Break 1
- An RFC should not be advertised misleadingly to the community. I have therefore added a factual correction that will appear on the relevant RFC listings. If Slim Virgin would like to amend her text to incorporate that correction, fine. Otherwise, please let it stand. ♥ NoeticaTea? 11:55, 1 September 2012 (UTC)
- If you want to write underneath my posts to correct or add an interpretation, that's fine of course, but please don't post inside them (this is the second time it has happened). In any event, none of these details – when it was restored, who partially restored it – matter. The question is simply whether we (now) want these words or not. SlimVirgin (talk) 17:15, 1 September 2012 (UTC)
- Slim, I am the last person to want irregular procedure at this talkpage. But you posted misleadingly so that the RFC is not advertised honestly to the community; and your rewording is still misleading. An RFC is, as I clearly reminded people here recently, required to be presented neutrally (see WP:RFC). Please now reword accurately. I'm sure you will understand: if you do not fix the advertised portion of your text, my proper but reluctant next move might be to seek a remedy from ArbCom. NoeticaTea? 23:09, 1 September 2012 (UTC)
- I assume you are asking SlimVirgin to alter the text at Wikipedia:Requests for comment/Wikipedia policies and guidelines, presumably to include the text you added above in the "Correction from Noetica" section? (Your request is unclear, and bringing up arbcom is .... [insert eyeroll insinuating-word here].)
- I suggest a simple addition, there and above (SlimVirgin only, please): just add the list of relevant diffs, and let people come to their own conclusions based on the evidence.
- [8], [9], [10], [11]
- It's not complicated, don't make it more so. -- Quiddity (talk) 02:52, 2 September 2012 (UTC)
- Thanks for the diffs, Quiddity. I've added them. SlimVirgin (talk) 21:27, 2 September 2012 (UTC)
- Indeed: it may not be complicated at all, Quiddity. Ask SlimVirgin who inserted the contested words in the first place, and with what consensus, and with what signalling in an edit summary. That might be relevant here, don't we all think?
- When the extra words were removed, a year ago, there was reference to an ongoing discussion on the talkpage, where everything was out in the open. The edit summary (see Quiddity's links just above here): "Rationalise unruly bunch of mini-sections ('principles'). Reduce negative angle. Rm repetition and redundancy. See talk page." Now, let SlimVirgin show how the original insertion of the text she favours was managed. And by whom. I'm all for transparency. ☺!
- As for referrals to ArbCom, of course I mean through WP:AE (ArbCom enforcement). My purpose is not to impugn SlimVirgin's motives or good faith; but recent cases have left this page under ArbCom discretionary sanctions, and as a regular here I am very concerned to avoid deficiencies in process that have wasted months of editors' time, and reserves of goodwill. We have to be especially careful. False advertising at an RFC notification, editing unilaterally without establishing consensus, chaotic discussion – none of that helps. Let's work collegially to maintain an excellent manual of style for Wikipedia.
- NoeticaTea? 08:42, 2 September 2012 (UTC)
- Mentioning AE has a chilling effect, and comes across (in this low-stress situation) as tactical. I'm not going to belabor the point, because it's plausibly deniable, and hence not worth debating. But everyone reading is aware, and most are rolling eyes.
- Don't just insinuate, show the fracking evidence. Why are you asking others to do the legwork? ("Ask SlimVirgin who ...") Here's some relevant diffs, that led from its initial to final form: [12], [13], [14], [15], [16], [17], [18], [19], [20], [21] (And yes, SlimVirgin added it). It's not hard; Open the history, search for "consistency". With the time spent on crafting your polite wikilawyeresque statement, you could have been researching that, or doing something else useful. Grumblegrumble. [Addendum: Having trawled years of the history, I've seen how much work you do, and I do appreciate that. I'm just trying to point out that some of your sentences here are coming across quite badly.] -- Quiddity (talk) 21:31, 2 September 2012 (UTC)
- Slim, I am the last person to want irregular procedure at this talkpage. But you posted misleadingly so that the RFC is not advertised honestly to the community; and your rewording is still misleading. An RFC is, as I clearly reminded people here recently, required to be presented neutrally (see WP:RFC). Please now reword accurately. I'm sure you will understand: if you do not fix the advertised portion of your text, my proper but reluctant next move might be to seek a remedy from ArbCom. NoeticaTea? 23:09, 1 September 2012 (UTC)
- If you want to write underneath my posts to correct or add an interpretation, that's fine of course, but please don't post inside them (this is the second time it has happened). In any event, none of these details – when it was restored, who partially restored it – matter. The question is simply whether we (now) want these words or not. SlimVirgin (talk) 17:15, 1 September 2012 (UTC)
- Posted with difficulty, away from my usual place, from an iPad, immersed in real-world concerns involving the care of an 89-year-old woman 18,000 km from where I am: References to WP:AE may be "chilling", but the mechanism is there for a reason, and MOS has a role and a history that mean we must exercise special care. It is not my fault if people edit it disrupively, or discuss without observing the protocols, or without revealing their involvements. If my objections when people do that are seen as unpleasant, consider dispassionately what chaos we must guard against repeating.
- Look above on the page, Quiddity, and see how much effort I have already put into this discussion. Thank you for coming in now and doing some more of the necessary work, and for revealing what SlimVirgin really ought to hve made plain from the start. I genuinely have no time to do any more on this for a while. My opinions, and my rather closely articulated reasons for them, are all laid out clearly above this RFC.
- Best wishes to all!
- NoeticaTea? 22:19, 2 September 2012 (UTC)
- I don't want to take part in a meta discussion, but I'd like to add that I didn't know before starting this discussion who had first added that sentence and who had first removed it, because there was a lot of history to look through and it didn't really matter. All I knew was that it had been there for a while, and had been removed relatively recently, so that's what I wrote. I don't like the implication that I knew I was the original author and for some reason wanted to hide that (why would I?). I also wonder what the point is of not saying directly: "Slim, did you realize you first added that sentence a few years ago?".
- Anyway, enough said. I hope we can now focus on the substance. SlimVirgin (talk) 22:37, 2 September 2012 (UTC)
I am not sure if Noetica is still amazed, (21:00, 25 August 2012). But there is a possibility of arguing that while a consistent style may not be desirable across all articles, a consistent style in groups of articles may be desirable. This argument has been advanced in the past for the articles Orange (colour) and Grey because they are both articles about colour. It has also been advanced for the articles in featured topics.
My problem with arguing for consistence in "groups" of articles is what is obvious a group to one person is not necessarily obviously a group to another (and what to do with articles that are obviously in two groups with differing styles). I suspect that while the argument about obvious groups is superficially attractive, due to the problems lack of clarity in defining a group, it will eventual lead inexorably towards harmonisation of style over large parts of Wikipedia. -- PBS (talk) 08:52, 6 September 2012 (UTC)
- And then you have overlapping. There are many articles that belong to more that one group. What will happen when those groups have conflicting styles? --Enric Naval (talk) 16:12, 6 September 2012 (UTC)
Break 2
- [Note: Some of the threaded responses in this section were moved out of the Replies section above, and the initial posts copied to preserve context. SlimVirgin (talk) 23:26, 17 September 2012 (UTC)]
*Oppose removal. per SlimVirgin and Enric. (Maybe we can get "Description not prescription" added back to wherever it was, too, eventually...) Time is not especially relevant, the detail/context that the sentence contains, is. -- Quiddity (talk) 19:40, 1 September 2012 (UTC)
- Not taking sides in the RfC (haven't thought it through yet); but I want to point out now that all manuals of style are both prescriptive and descriptive. Tony (talk) 06:21, 2 September 2012 (UTC)
- I don't remember exactly where it was, but I think it was originally in WP:NOT or WP:PG or similar (not a MOS page). Pointers appreciated though. -- Quiddity (talk) 19:27, 2 September 2012 (UTC)
- Not taking sides in the RfC (haven't thought it through yet); but I want to point out now that all manuals of style are both prescriptive and descriptive. Tony (talk) 06:21, 2 September 2012 (UTC)
[Noetica's vote, quoted from above:] Support the removal of text that was done twelve months ago. The stress on intra-article consistency is fine, of course. So is motherhood. But why labour to include what many editors have unfortunately misread as a licence for chaos? Groups of articles on similar themes benefit enormously from similar styling (where MOS allows for a choice). Why bend over backwards against such efforts? They are clearly in readers' interests. MOS was, till a few days ago, silent on such laudable efforts. What benefit is there in it making a statement that is bound to be misused by those who favour complete independence of styling, at each of 4,000,000 articles? No one is suggesting that a contrary statement be made; just that it is not the business of MOS inadvertently to counter worthwhile efforts to improve the readability of closely associated articles.
- NoeticaTea? 08:51, 2 September 2012 (UTC)
[NOTE: As I explain below in "Threaded discussion", I am tied up with matters in real life. I have said all I need to say for this RFC, in the discussion earlier on this page: #Internal consistency v consistency across articles. The question facing us is important, and I advise people not to conflate consistency of style for Wikipedia in general (the very essence of MOS) and consistency of style where choices are allowed in MOS (and there are very few such choices, at least in WP:MOS itself). Misreadings we observe in this RFC illustrate the very problem that such carefleesly added wording introduces: people do not read accurately, nor discriminate as we expect they will. ♥ NoeticaTea? 03:52, 7 September 2012 (UTC)]- By "what many editors have misread as a license for chaos," what do you mean? What happened, specifically, and when? Darkfrog24 (talk) 03:55, 4 September 2012 (UTC)
*Oppose removal by which I really mean "support re-insertion." Wikipedia is not like other encyclopedias. It requires on the unpaid service of editors from many disparate backgrounds and it has no chain of command. There's no one who can legitimately say, "Do it this way because I'm the boss and I've earned my authority." Inter- but not intra-article consistency strikes a balance between neatness and the diversity of opinion among our editors. If it is "bound to be misused," then show at least one case in which that has happened. Has an editor ever claimed "We are not allowed to make these articles match each other; the MoS says so"? Darkfrog24 (talk) 13:31, 2 September 2012 (UTC)
- I've already addressed this fallacious "we're volunteers so we should be able to do whatever we want for personal reasons, and consistency can go screw itself" meme at WP:SSF. Lack of payment has nothing to do with anything; there's no logical connection. It's like saying "I have blonde hair, so I should be allowed to eat small children", or "my dog is old, so I shouldn't have to pay the water bill". — SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 22:36, 8 September 2012 (UTC)
- I'm not saying that volunteers get to do whatever they want, and you know that perfectly well, but anyone who's worked in a volunteer organization can tell you that it's not the same type of dynamic as a workplace. On Wikipedia, no one volunteer outranks another. "Do X because I'm your boss" holds no weight here. "Do X because the majority of sources say that X is right and Y is wrong" does. People don't pull rank; sources do. When the sources cannot show that one way is better than another, no one person or small group of people should get to order the others around. Darkfrog24 (talk) 14:18, 9 September 2012 (UTC)
- I've already addressed this fallacious "we're volunteers so we should be able to do whatever we want for personal reasons, and consistency can go screw itself" meme at WP:SSF. Lack of payment has nothing to do with anything; there's no logical connection. It's like saying "I have blonde hair, so I should be allowed to eat small children", or "my dog is old, so I shouldn't have to pay the water bill". — SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 22:36, 8 September 2012 (UTC)
[SMcCandlish's vote, quoted from above:] *Support re-removal per Noetica, and per the fact that the removal has been stable for a long time, and the fact that we do not need to repeat everything ever said in every guideline and policy on the system. It's already implicit in MoS's mandate as a guideline that it operates in juxtaposition and compromise with other forms of guidance here. Reiterating that a guideline can have exceptions, or that any particular guideline is not an ironclad policy, is not what we do here. Also, it really has been misinterpreted as a license for chaos. It was removed for a reason.
Furthermore, there's an underlying assumption (one that is often advanced by the sort of editorial misprioritization addressed by WP:SSF, and WP:NOTHERE before it) that inter-article consistency is not desirable, and is immediately trumped by narrow, even personal preferences. Yet, obviously it is desirable to the extent that it can happen without raising intractable problems (like those addressed by WP:ENGVAR). If it were not desirable MOS would be very short, as the bulk of it and its subpages is style advice for dealing with English-language prose across all articles here. Material is not being broken out of MoS into small, topic-specific WikiProject "guidelines"; rather, the exact opposite is happening: Good advice from projects is making its way steadily into MoS so that it is applied consistently in articles on other topics.
— SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 08:24, 4 September 2012 (UTC)
- You said "It was removed for a reason.", but what? The only clues I can find are the original edit summary, and the archived thread Wikipedia talk:Manual of Style/Archive 124#Extraneous clutter at the top - neither of which discuss the sentence/section in question at all. Is there anything else to look at, that makes you (and Noetica) consider it a license for chaos? (I'm assuming this is related to some sub-battle about date or titles or dashes or engvar or etc, but I'm not familiar with what/when/where/who :/ If I/we have more information, we can give better input. It is an RFC, after all; lots of non-regulars who need context...). Here's the talkpage history from 4/5 Aug 2011, in case that helps. -- Quiddity (talk) 20:55, 4 September 2012 (UTC)
- I second Quiddity's request. You are the second person to say that this rule has been "misinterpreted as a license for chaos." What happened, specifically, and when? Was it only once or many times? We've seen some evidence that this text prevents problems, but if we can prove that this text causes more problems than it prevents, then it should stay out. Darkfrog24 (talk) 23:43, 4 September 2012 (UTC)
- Please do not fixate on the idea that only a specific, major event is important; there was no Great Wiki Disaster of 2011. What there has been in response to this "rule" and various other kowtowing to intractable special interests who refuse to write consistent, encyclopedic prose for a general audience, is such editors taking license to do the exact opposite, and write articles on "their" topic as if intended for and published by professionals in their field instead of, well, everyone else in the entire world, which is what Wikipedia is actually here for, not regurgitating precious nitpicks from academia. It leads to wikiprojects acting as if they are sovereign states that own entire ranges of topics, and has led to enormous amounts of entrenched editwarring over the last 8+ years, threats of editorial boycotts, wikidiva resignations by editors, and other childish nonsense of massive proportions, all because some people are not here to write an encyclopedia but rather to spread their sub-sub-sub-field's particular stylistic peccadilloes and force everyone else to use them. Enough of that idiocy. It's been nothing but destructive. — SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 22:36, 8 September 2012 (UTC)
- Actually, problems attributable to this phrase would be more relevant to the MoS if they happened more than once. If it was a lot of little incidents rather than one big incident, then point to a good example or two. However, it's not immediately obvious what "not necessarily throughout Wikipedia as a whole" has to do with the issue of writing for a general vs. a specialized audience.
- Encyclopedic tone seems to be a separate issue from intra- vs. inter-article consistency, and it is covered elsewhere in the MoS. All of Wikipedia should be written for a general audience. Can you show or tell us how the phrase "but not necessarily across Wikipedia as a whole" has caused these problems? Can you point to one or more talk page discussions in which someone cited that phrase as a reason to write articles in a Wikiproject in an inappropriate manner? Did it happen in WP:BIRDS? Those guys are pretty big on writing articles for a specialized audience. Darkfrog24 (talk) 14:26, 9 September 2012 (UTC)
- Please do not fixate on the idea that only a specific, major event is important; there was no Great Wiki Disaster of 2011. What there has been in response to this "rule" and various other kowtowing to intractable special interests who refuse to write consistent, encyclopedic prose for a general audience, is such editors taking license to do the exact opposite, and write articles on "their" topic as if intended for and published by professionals in their field instead of, well, everyone else in the entire world, which is what Wikipedia is actually here for, not regurgitating precious nitpicks from academia. It leads to wikiprojects acting as if they are sovereign states that own entire ranges of topics, and has led to enormous amounts of entrenched editwarring over the last 8+ years, threats of editorial boycotts, wikidiva resignations by editors, and other childish nonsense of massive proportions, all because some people are not here to write an encyclopedia but rather to spread their sub-sub-sub-field's particular stylistic peccadilloes and force everyone else to use them. Enough of that idiocy. It's been nothing but destructive. — SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 22:36, 8 September 2012 (UTC)
- I second Quiddity's request. You are the second person to say that this rule has been "misinterpreted as a license for chaos." What happened, specifically, and when? Was it only once or many times? We've seen some evidence that this text prevents problems, but if we can prove that this text causes more problems than it prevents, then it should stay out. Darkfrog24 (talk) 23:43, 4 September 2012 (UTC)
*Retain/oppose removal' - The key words being "not necessarily". On those formatting issues about which broad community-wide discussion arrives at a consensus, consistency can and should be enforced, but about those the community maintains a more laissez-faire attitude, editors should have the leeway to improve articles as they see fit, given the specific needs of the specific article, without having to answer to those who try to enforce a non-existing consensus. The very most important thing, which it is best that we put our energies to, is to give our readers good, accurate information, well presented, rather than that every article have every tiny formatting aspect be exactly the same. Such "fooliosh consistency" is, in Emerson's words "the hobgoblin of little minds", in Shaw's words "the enemy of enterprise", and in Wilde's words "the last refuge of the unimaginative." Surely our editors are just the opposite: enterprising, imaginative and open to the world. Beyond My Ken (talk) 01:37, 6 September 2012 (UTC)
- Misquotation, and skewed quotation out of context that misconstrues the intent of the original, is the hobgoblin of people whose arguments are too weak to stand on their own. Emerson actually said "A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers...", which is very, very different, and his message was about radical philosophy and the advancement of novel ideas, which Wikipedia absolutely does not do. Just one example. By way of contrast, see the old aphorism "Consistency, thou art a jewel." Its origin is lost, but uses the virtue-as-jewel metaphor of the Elizabethan era, so it's at least as old as Shakespeare (cursorily searching, I've found it in print in the 1800s, but Bartlett suggests it's much older).
What you're missing is that Emerson, Shaw and Wilde were all writing about the negative effects of conformity on new, creative output such as literature, fashion and other forms of artistic expression, as well as the propounding of new theories. That is not what Wikipedia is. We are not permitted to engage in original research or even novel synthesis. And WP is not creative writing. It is necessarily dry, strictly informative prose that serves a purpose. It is formal, technical communication, not art. It serves this function best when it does not confuse the readership or make them mentally work hard to figure out what we are trying to convey. Emerson is worth quoting in more detail here: "To be great is to be misunderstood." Emerson argues for being confusing and self-contradictory! That's fine if you are a philosopher refining your outlook over time. It's a disaster in an encyclopedia. Inconsistency between articles here, for no reason other than to suit the in-house preferences of (mostly) academics, government people and fandom obsessives (the three most common sources of WP:SSF problems around here), is directly inimical to Wikipedia's actual goals, which are in service to readers, not editors. Consistency between articles, where it does not create novel problems like conflict between English dialects, is a sensible and necessary consistency in our context, not a foolish one. More recently, Tim Robbins (again writing of creative not technical/formal educational output) said "only logicians and cretins are consistent", and that's important: Consistency in art is certainly cretinous and yawn-inducing. But encyclopedia writing is by definition the work of logicians.
In closing, see the other quotations at http://en.wikiquote.org/wiki/Consistency, and notice that all of them that are in opposition to consistency are about either a) art and other creative output, or b) are about individuals changing their mind (i.e., a completely different meaning of the world "consistency" that isn't relevant to this discussion at all, and Cicero even suggests it's a misuse of the concept). I dare you to find a single exception. Even Larry Wall's quip that "the essence of sanity is to be inconsistently inconsistent" is directly applicable here, as it suggests that exceptions to consistency in human relation to reality (which is what WP is a tool for) should be rare; an insistent lack of consistency in such a context – what he calls "consistent inconsistency" – is, he suggests, a working definition of insane.
— SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 23:19, 8 September 2012 (UTC)
- Misquotation, and skewed quotation out of context that misconstrues the intent of the original, is the hobgoblin of people whose arguments are too weak to stand on their own. Emerson actually said "A foolish consistency is the hobgoblin of little minds, adored by little statesmen and philosophers...", which is very, very different, and his message was about radical philosophy and the advancement of novel ideas, which Wikipedia absolutely does not do. Just one example. By way of contrast, see the old aphorism "Consistency, thou art a jewel." Its origin is lost, but uses the virtue-as-jewel metaphor of the Elizabethan era, so it's at least as old as Shakespeare (cursorily searching, I've found it in print in the 1800s, but Bartlett suggests it's much older).
*Support removal. The extra words seem to be encouraging inconsistency far too strongly.
, indeed one responder says "consistency across articles has always been discouraged" which seems a good example of a rule which should always be ignored: should I look for ways of making every article I edit inconsistent with every other article?The wording chosen should not give anybody an excuse to be uncooperative, whether they wish to apply something too widely or ignore interrelationships between articles. Although readers must accept that Wikipedia's articles follow no single strict house style, they are not well served if, for example, individual articles covering the six books of a series have corresponding content distributed differently across sections, perhaps in a different order or with different names. The work of adding related information to several such articles could be doubled or trebled depending on how they were inconsistent and such barriers to editing cannot contribute to content improvement. Not even in a single article do we revert constructive additions merely because a wrong sort of dash has been used, so I do not see consistency within an appropriate scope, maintained tactfully, as stifling new content. Neither would any expectation of consistency remove the necessity for having consensus to maintain it: I would expect the ease of finding consensus to correspond to the closeness of the relationship in a self-limiting way. --Mirokado (talk) 14:00, 11 September 2012 (UTC)- Hum, my bad. A better wording: "enforcing consistency across articles has always been discouraged". As in "changing articles from one MOS-approved to another MOS-approved style, just because you would like all articles in an arbitrary group to have the same style." People won't complain if you are actually working in a group of articles and you need to do changes in order to work better, and you only change articles that you are working in, or at most the odd article that is closely related. Now, if one was to land in a group of articles for the first time, then change the style to one's personal preference, then edit war when people complain that specific articles have a different style for a reason, etc, ..... --Enric Naval (talk) 18:49, 11 September 2012 (UTC)
- Thanks, Enric. Striking some of my response. I do agree with what you say just above, but not every editor is as sensible as we are and I'm still concerned that the proposed wording will encourage uncooperative behaviour, so I will stick with supporting removal. --Mirokado (talk) 21:15, 11 September 2012 (UTC)
- Ideally nothing would depend on such a fine balance of words, but experience of Wikipedia editing suggests to me that either wording will be used by those who cherry-pick the MOS to support a prior position. "Sensible" editors already understand that intra-article consistency is a priority, and that inter-article consistency is highly desirable, and that both kinds of consistency are subject to consensus, not ownership. Unfortunately many editors are not "sensible". I guess that preference here may depend on which kind of uncooperative behaviour you've mostly encountered. I'm concerned that removing the wording will encourage uncooperative behaviour, namely editors trying to change styles which have consensus in one area of Wikipedia to those which have consensus in another, because this is the kind of edit-warring I've mostly encountered. Peter coxhead (talk) 08:31, 12 September 2012 (UTC)
- Thanks, Enric. Striking some of my response. I do agree with what you say just above, but not every editor is as sensible as we are and I'm still concerned that the proposed wording will encourage uncooperative behaviour, so I will stick with supporting removal. --Mirokado (talk) 21:15, 11 September 2012 (UTC)
- Look at that post. When I keep asking about evidence, this is what I mean. What kinds of edit wars have you seen, what fights on talk pages, what poorly worded articles, what bad reader experiences have you seen and how do you think changing/keeping this wording would fix it? Peter, can you drop us a link to any of these edit wars? Darkfrog24 (talk) 13:47, 12 September 2012 (UTC)
- Hum, my bad. A better wording: "enforcing consistency across articles has always been discouraged". As in "changing articles from one MOS-approved to another MOS-approved style, just because you would like all articles in an arbitrary group to have the same style." People won't complain if you are actually working in a group of articles and you need to do changes in order to work better, and you only change articles that you are working in, or at most the odd article that is closely related. Now, if one was to land in a group of articles for the first time, then change the style to one's personal preference, then edit war when people complain that specific articles have a different style for a reason, etc, ..... --Enric Naval (talk) 18:49, 11 September 2012 (UTC)
Well since the proposed addition has been absent for a year or so I can't point to any recent problems it has caused. I can however point to responsible and constructive activities that this wording appears to target and wonder why anyone would expend so much effort to try to prevent them:
- the List of horror films extends over 70 other pages. My attention was drawn to these lists by an obviously incorrect entry while I was checking links from a stub I had created (Amy B. Harris) for general quality issues (which does not mean that I expected all those links to be consistent). These lists were in an appalling state with lots of redlinks and lots of incorrect entries. I noticed that because I naturally checked the other lists as well as the original one, something which would be pointless if consistency between related articles is to be discouraged. Although the lists generally had the same number of columns and the same column headings, in detail there were random differences between them as well as formatting inconsistencies within some articles. The only practicable way to fix these problems was to apply a uniform structure to all the articles and then check progressively for problems and correct them. The more subtle the problems, the more the growing consistency helped to reveal them. The end result is that (with content improvements mainly due to contributions from other editors) the lists are much more correct and better sourced. Citations needed on more than one list can be copied and pasted without alteration as can the occasional entry allocated to the wrong year. The fatuous entries from drive-by editors have almost disappeared. All the changes were discussed on talk pages, often with an announcement and progress report accompanying each set of changes.
If the MOS allows an editor to insist that some of these lists can have a different table structure, or be a bulleted list instead of tables, or have a different citation format, or whatever, because "consistency between articles is not necessarily required", then I presume I would either have to let some articles rot, ignore the problems completely or start an RFC. I certainly would not do the work twice over to accommodate what I would regard as obstruction. - cooperation on the works of Anne McCaffrey is relatively easy because, generally, the articles on her books have a common format. We can refine changes to one article including discussions on the talk page knowing that the corresponding updates can be made with reasonable effort and reliably to the other articles. There have been disagreements which have been resolved on talk pages. New ideas are not stifled, very much the reverse, we are currently discussing a new set of improvements. As far as I know, nobody has been made to feel unable to make changes to the pages. I don't think anybody is saying "therefore every article about a book by a particular author must have the same format", simply that the MOS should not set out to prevent such cooperation.
- it seems in practice unlikely that editors will often challenge these sorts of scenario, but that indicates that this proposed addition is in fact pointless. If anybody were to make use of it, the result would be more discussion not less, resulting in RFCs if necessary.
- in cases like date linking which has been mentioned, nobody is going to prevent such an activity by saying "articles do not have to be consistent", that is far to vague to counter someone's conviction that the world can only be saved by linking (or delinking) every date. The lines of defence are already quite adequate, with a requirement for consensus in advance for extensive systematic changes, blocks for editors who do not accept that (we can all think of cases where that has happened) and specific criteria determining when a particular disposition is appropriate. Nobody prepared to be blocked rather than achieve consensus is going to take the slightest notice of this text even if it is adopted. --Mirokado (talk) 23:04, 13 September 2012 (UTC)
- To summarize, Mirokado seems to be saying the following 1. Inter-article consistency can make some improvements easier to make. 2. Mirokado describes one set of articles that happens to be written consistently and is working out well. To these two points, I respond that just because inter-article consistency is not required doesn't mean it's not permitted. Consistency alone isn't reason enough to change format, but my opinion is that effecting repairs is. 3. Mirokado thinks that the wording is extra/unnecessary. 4. Mirokado provides an argument against the date delinking example, which was previously offered as evidence by Enric N. Mirokado has not listed any edit wars or other nonhypothetical events attributable to the inclusion of the phrase "not necessarily across Wikipedia as a whole" in the MoS. Let me know if I've misinterpreted any of that. Darkfrog24 (talk) 04:34, 14 September 2012 (UTC)
- That is a pretty fair summary. It seems clear from your response that your concerns are not intended to impact the sorts of activity I have mentioned. As far as "consistency alone" is concerned, there will pretty well always be other benefits. I have already given examples from the editor's perspective. Readers benefit if they can easily understand where to find information in article Y if they have just been looking at the corresponding information in article X. Readers' expectations will be stronger the more closely they perceive the articles to be related.
- Responding to "just because inter-article consistency is not required doesn't mean it's not permitted": if the MOS says anything at all about this it should acknowledge, as well, that although not required across the whole project substantial consistency is essential among many sets of articles in order to provide a satisfactory user experience and highly desirable, again among relevant articles, to support effective collaboration between editors. If it does not then it is encouraging a substandard user experience and article ownership in various forms, both of which are totally unacceptable. --Mirokado (talk) 20:49, 14 September 2012 (UTC)
- To summarize, Mirokado seems to be saying the following 1. Inter-article consistency can make some improvements easier to make. 2. Mirokado describes one set of articles that happens to be written consistently and is working out well. To these two points, I respond that just because inter-article consistency is not required doesn't mean it's not permitted. Consistency alone isn't reason enough to change format, but my opinion is that effecting repairs is. 3. Mirokado thinks that the wording is extra/unnecessary. 4. Mirokado provides an argument against the date delinking example, which was previously offered as evidence by Enric N. Mirokado has not listed any edit wars or other nonhypothetical events attributable to the inclusion of the phrase "not necessarily across Wikipedia as a whole" in the MoS. Let me know if I've misinterpreted any of that. Darkfrog24 (talk) 04:34, 14 September 2012 (UTC)
- Hi Mirokado, no one is saying consistency across articles, or groups of articles, must be opposed. The point is simply that just because an editor punctuates in a certain way in Holocaust in Poland doesn't mean editors must punctuate the same way in Holocaust in Romania. The sentence at issue is: "An overriding principle is that style and formatting choices should be consistent within an article, though not necessarily throughout Wikipedia as a whole." The word "necessarily" is important here. It signals that consistency across articles may sometimes, or regularly, be appropriate, but not invariably, and that some style issues are left to the editors on the page to decide. SlimVirgin (talk) 21:27, 14 September 2012 (UTC)
- I believe that the MoS should not state that any sort of cross-article consistency is desirable because that statement will be taken as law. 1. We should give our editors freedom where correct English allows. 2. Some articles may logically belong to more than one group. Darkfrog24 (talk) 23:13, 14 September 2012 (UTC)
- Some things are the same across pages (e.g. the general appearance), and there have been style practices that were so odd that I was glad to see cross-article consistency applied (e.g. overlinking). But generally I agree that internal consistency is the aim, and agree too about the groups. SlimVirgin (talk) 03:49, 15 September 2012 (UTC)
Break 3
This isn't a race or about numbers alone, so I'm closing the running tally. SlimVirgin (talk) 18:44, 14 September 2012 (UTC) |
---|
The following discussion has been closed. Please do not modify it. |
As of now, responses are 2:1 in opposition of removal (AKA support of reinsertion). Would anyone like to offer or summarize evidence or change his or her position? Darkfrog24 (talk) 03:18, 11 September 2012 (UTC)
Oppose removal
Support removal
[Updated by NoeticaTea? 12:17, 14 September 2012 (UTC)] |
Counting votes
- I have reinstated the tally (see subsection below). No one should think that numbers alone count; but the voting has become diffused or replicated by quotation in various subsections. Quite confusing for newcomers, I might add! These lists serve an index of contributions so people can find them and evaluate their arguments. NoeticaTea? 22:11, 14 September 2012 (UTC)
- And I have closed it again. If you want to open your own RfC later you're welcome to do that, but keeping a running tally of numbers is pointless at best, so please allow this RfC to run its course without it. SlimVirgin (talk) 03:33, 15 September 2012 (UTC)
- I have no view one way or the other on the above discussion about including or not including the sentence about Wikipedia as a whole other than to comment that you might as well reverse the two words not and necessarily if it is included - just a comment... Apteva (talk) 09:27, 19 September 2012 (UTC)
Presentation of evidence for and against "not necessarily throughout Wikipedia as a whole"
I think this discussion might benefit from a summary of the evidence presented. Please limit discussions to things that can be verified (rather than discussing reasoning alone). I have paraphrased four other editors below and I invite them to replace my words with their own as they see fit. Darkfrog24 (talk) 04:47, 2 October 2012 (UTC)
Non-hypothetical evidence for and against "not necessarily throughout Wikipedia as a whole"
This section is for listing problems, such as fights and edit conflicts, that have actually happened. Practical experience falls under this category. Please show how the wording "not necessarily throughout Wikipedia as a whole" caused the problem or would have prevented it. Contributors, please post links to the relevant changes, talk pages and archives whenever possible. Darkfrog24 (talk) 04:47, 2 October 2012 (UTC)
- Enric Naval cited arbcom case "Findings of fact" (Enric N, please feel free to replace these lines with a brief explanation of why you think this discussion is relevant and why you think the inclusion of these words would have prevented problems.)[22]
- Enric Naval cited arbcom case "Date delinking" (Enric N, please feel free to replace these lines with a brief explanation of why you think this discussion is relevant and why you think the inclusion of these words would have prevented problems.)[23]
- Noetica said that the Mexican-American war page has to do with this issue. (Noetica, please feel free to replace these lines with a brief explanation of why you think this discussion is relevant and why you think the exclusion of these words would have prevented problems.) [24]
- Quiddity cited the infobox discussion below as evidence that the absence of the words "not necessarily..." from the MoS can cause fights. (Quiddity, please feel free to replace these lines with a brief explanation of why you think this discussion is relevant and why you think the inclusion of these words would have prevented problems.) [25]
Hypothetical evidence for and against "not necessarily throughout Wikipedia as a whole"
This section is for listing problems or advantages that you believe would or could happen but haven't witnessed. PLEASE BE SPECIFIC. Don't say "this wording will be misused" or "this wording will keep Wikipedia running smoothly"; say how you think it will be misused or keep things running smoothly and why. Contributors, please include links where relevant. Darkfrog24 (talk) 04:47, 2 October 2012 (UTC)
- Mirokado is concerned that inconsistency between articles that a reader regards as closely related will deliver an inferior reader experience (for example not knowing where to find corresponding information in each article). --Mirokado (talk) 00:01, 5 October 2012 (UTC)
- This view is shared by many who oppose re-insertion of the contested wording. Darkfrog24 (talk) 01:22, 6 October 2012 (UTC)
- Mikorado cited many articles dealing with the works of Anne McCaffrey and said that inter-article consistency facilitated making repairs and improvements by saving the editors' time and making any remaining issues more visible. --Mirokado (talk) 00:01, 5 October 2012 (UTC)
- Mikorado expressed a concern that reinsertion of the wording might cause some editors to render the articles inconsistent and therefore harder to repair and improve. (Feel free to reword or correct the previous sentence and attribute to yourself if you see fit to do so.) No specific case has been cited. Move this point to non-hypothetical if even one such case can be found. Darkfrog24 (talk) 01:22, 6 October 2012 (UTC)
- Mikorado cited many articles within List of Horror Films and said that inter-article consistency facilitated making repairs and improvements by saving the editors' time and making any remaining issues more visible. --Mirokado (talk) 00:01, 5 October 2012 (UTC)
- Mikorado expressed a concern that reinsertion of the wording might cause some editors to render the articles inconsistent and therefore harder to repair and improve. (Feel free to reword or correct the previous sentence and attribute to yourself if you see fit to do so.) No specific case case has been cited. Move this point to non-hypothetical if even one such case can be found. Darkfrog24 (talk) 01:22, 6 October 2012 (UTC)
Summary of RfC: “Internal consistency versus consistency across articles”
A request for closure has been made, and the bot has removed the RFC tag, and in the meantime the thread has been archived. I have unarchived it and attempted to summarize the issues as follows.
Wording:
It is proposed to add the following sentence to the fourth paragraph of the introduction: “An overriding principle is that style and formatting choices should be consistent within an article, though not necessarily throughout Wikipedia as a whole.” There is a consensus, or at least no opposition, to adding the first part of the sentence, but the second part of the sentence is contested.
Issues:
- Those who wish to add “though not necessarily throughout Wikipedia as a whole” say it is needed in order to discourage those who want to use similar format for similar articles, and that style issues should be determined by personal preference.
- Those who do not wish to add “though not necessarily throughout Wikipedia as a whole” say it will discourage similar styling in groups of articles on similar topics, that the phrase is confusing and has been used for pointless argument, and that consistency across the Wikipedia as a whole is the purpose of having a Manual of Style in the first place
Survey:
- Support adding “though not necessarily throughout Wikipedia as a whole”: SlimVirgin, Enric Naval, Quiddity, Amatulić, Binksternet, Shenme, Darkfrog24, jc37, Beyond My Ken, Jimp, Peter coxhead, CBM [derived from a reading of the contribution], Resolute, Hiding, 87.112.91.134, Jayron32, WhatamIdoing
- Oppose adding “though not necessarily throughout Wikipedia as a whole”: Noetica, SMcCandlish, Ohconfucius, Boson, Dicklyon, Tony, 86.160.221.242 [derived from a reading of the contribution], Neotarf, Mirokado, Br’er Rabbit [derived from a reading of the contribution], 128.127.107.10, 87.79.226.106, Rreagan007
Neotarf (talk) 21:09, 28 September 2012 (UTC)
- We should probably add that this is a restoration vs. endorsement of removal rather than an add. The words "not necessarily throughout Wikipedia as a whole" were originally in the MoS. This is about whether to put them back, not whether to add them for the first time.
- Ideally, disagreements on Wikipedia are supposed to be decided by the preponderance of sources and evidence rather than by the preponderance of proponents. So far, only one person has offered real evidence that having or not having this phrase in the MoS would make any material difference in the reader or editor experience, and that is Eric N, who cited disputes in which the idea of internal consistency was involved. Mirokado cited a few hypothetical problems but nothing has actually happened. A lot of the opposition to re-adding these words has been "this is unnecessary" rather than "this would cause problems." Most of the support for re-adding these words has been "the absence of these words can cause problems." Darkfrog24 (talk) 19:43, 29 September 2012 (UTC)
- Just to clarify, while there may or may not have been a request to close the RfC, it is my understanding that the bot would have removed the tag tomorrow but when the thread got archived with the tag in it the RFCbot removed the tag from the archive. In any case, in closing an RfC what is important is not a tally of votes, but a summary of arguments. In my view, I have already commented that a consistent style is necessarily not possible across WP as a whole, and was not expressing any view one way or the other about the inclusion or exclusion of that or any other part of the sentence. I would also like to add that the words "An overriding principle" are a bit over the top, as that would tend to indicate that there were other principles that were not as important. This RfC reminds me of the problem of drafting anything by committee. What actually works is for one person to go off and write a proposal, and then have the committee edit and improve it, or even reject that wording. When a committee tries to write something it takes forever to discuss each word. Apteva (talk) 20:48, 29 September 2012 (UTC)
- Note that Apteva has changed the archiving time to 60 days [26] and has also altered various other archiving parameters. [27][28] Apteva also notes on my talk page that "There are about three copies of one of the RfC's in one of the archives left over from other times that RfC was un-archived, and they can all be simply deleted from the archive, but that has not reached the top of my to do list."
- Neotarf (talk) 08:08, 30 September 2012 (UTC)
- Those are technical changes. The bot has already moved on to /Archive130, and when the archive was unarchived the internal bot counter was inadvertently changed back to 129 which would have meant that new archives would go back on /Archive129 instead of where they belonged, on /Archive130. 600k is in my opinion horrendously large for archive pages. Mostly this page had been manually archived, and many of the archive pages are on the order of 25k, not even 200k. An edit summary noted that the archive was being split into smaller archives. The bot automatically archives any thread with no response in 7 days, and the RfC was split into sections that are getting replies and those with no responses, so it seemed easier to just tell the bot to slow down until the RfC is closed, particularly because there were two of them open at the time. In another 5 days both will have expired and the archiving can go back to 7 days. Apteva (talk) 05:10, 2 October 2012 (UTC)
- (edit conflict) Actually, Darkfrog24, if you check the links, and I did, the contested words are not present on the page, awaiting possible removal. They were removed last year. And SMcCandlish and Noetica both presented specific examples of problems that had been caused by that phrase before it was changed. On the other hand, no one has shown anything negative that has actually happened in the last year without the contested phrase. Neotarf (talk) 20:59, 29 September 2012 (UTC)
- I didn't say that they were currently on the page and that we were discussing their removal. I said that they used to be on the page and we were discussing reinserting them vs. endorsing their removal after the fact: "This is about whether to put them back, not whether to add them for the first time." As someone pointed out, a year is not so long for the MoS. If the person who removed it had discussed it on the talk page first (not required, but on this page it often helps), then the change probably wouldn't have gone through, if this discussion is any example.
- I read SMC's and Noetica's posts and I didn't see any specific examples of anything, but they do both go on and it's possible that things got buried in the rhetoric. What evidence did they present? Noetica said "Look at this Mexican-American War discussion" but didn't say what he thought that discussion had to do with this one. Darkfrog24 (talk) 05:05, 30 September 2012 (UTC)
- And the contested words used to be *NOT* on this page. Rather you should be asking with what discussion they were inserted in the first place, and with what edit summary.
- You didn't seem to have any trouble finding the evidence presented by SMcCandlish and Noetica when you argued against it in the above discussion. But this is not summary material, it is just a repetition of arguments already in the (rather long and unorganized) discussion section. You were invited before to make a summary of why this material should be added, and you did not do so.
- Neotarf (talk) 07:45, 30 September 2012 (UTC)
- Neotarf, I most certainly did and do have trouble finding the evidence that Noetica and SMC may or may not have presented: [29]. They both said "inter-article consistency is desirable" but didn't cite any cases in which the wording in question caused any problems with the possible exception that Noetica said "read the Mex-Am war page" but didn't say why. That's not an argument against evidence. It's a request for evidence. You seem to have missed this the first time, so I'll be more explicit: If you saw something that I did not, please point it out to me.
- Maybe you and I aren't using the word "evidence" the same way. I would consider what Enric and Mikorado did to be evidence. Enric cited disputes that actually happened, with a link. Mikorado referred to specific articles and events and said why those articles might be threatened. It was hypothetical, but it made sense. Noetica and SMC both expressed a bunch of opinions, but I don't consider that to be evidence.
- Neotarf, you will note that I said, "This is about whether to put them back, not whether to add them for the first time." I am not trying to trick anyone. I feel that there is a difference between restoring wording that used to be there and proposing new wording. Technically, the whole MoS used to not be there.
- I actually did give a summary of why I think the wording should be restored. It's a few threads up under "oppose removal."[30]
- As for "what discussion and with what edit summary," Quiddity dug that stuff up a couple weeks ago. Hit CTRL-F for "legwork" and you'll see a bunch of links. [31] Darkfrog24 (talk) 18:47, 30 September 2012 (UTC)
- Re: "no one has shown anything negative" - see the huge thread about infoboxes below! (and all the grumbling about it in many elsewheres, where the rubber meets the road). Site-wide-Consistency is one of the main arguments in favour of "infoboxes everywhere, regardless of objections".
- See WP:ENGVAR. See WP:DATES ("Consistency in style and formatting promotes clarity and cohesion; this is especially important within an article"). See the very strong opinions that different groups with different priorities bring to other xVAR discussions. See WP:RETAIN.
- We clearly still hold the value of “though not necessarily throughout Wikipedia as a whole”, but removing that phrase from this MoS page removes the explicit mention, and makes it merely implicit in the minds of those who follow it in various circumstances. Removing it moves us closer to being a bureaucracy. It should be retained (replaced), for the same reasons that IAR needs to be stated explicitly and also repeated in many places. —Quiddity (talk) 21:21, 1 October 2012 (UTC)
- Just to clarify, while there may or may not have been a request to close the RfC, it is my understanding that the bot would have removed the tag tomorrow but when the thread got archived with the tag in it the RFCbot removed the tag from the archive. In any case, in closing an RfC what is important is not a tally of votes, but a summary of arguments. In my view, I have already commented that a consistent style is necessarily not possible across WP as a whole, and was not expressing any view one way or the other about the inclusion or exclusion of that or any other part of the sentence. I would also like to add that the words "An overriding principle" are a bit over the top, as that would tend to indicate that there were other principles that were not as important. This RfC reminds me of the problem of drafting anything by committee. What actually works is for one person to go off and write a proposal, and then have the committee edit and improve it, or even reject that wording. When a committee tries to write something it takes forever to discuss each word. Apteva (talk) 20:48, 29 September 2012 (UTC)
Premature closure reversed
With this edit I reversed a non-admin closure of the RFC. Clearly there is no consensus, so the RFC should be closed by an admin. The editor (User:Nathan Johnson) erred in not realising this, and by less than competent summation of the issues. In particular, he completely failed to distinguish consistency in general (the purpose of all manuals of style, including MOS) and consistency where MOS allows choices. This distinction is crucial among the issues confronting us in the RFC, in a number of ways.
As a central participant, concerned at least as much about due process as about the outcome of the RFC, I have been absent from Wikipedia for the last week for personal reasons. I mentioned one reason on this talkpage, and put a note at my talkpage. Meanwhile, Darkfrog wanted some summation from each side. I will be able to provide my summation within the next 24 hours. I ask to be given a chance to do that.
If this RFC results in insertion of the contested wording, I will consider issuing a new RFC to address the genuine issues that have been aired in the course of this one. The conflation of utterly separate types of consistency has seen a great deal of time wasted. The proposer of this RFC should have known better, and so should a number of participants. An RFC should be framed, and discussed, in a way that keeps separate issues separate – from start to finish. ☺
Addition: Even as I wrote, the editor reverted my reversion. I have reverted that reversion, but will not do so again.
NoeticaTea? 23:05, 4 October 2012 (UTC)
- I concur that this discussion is not finished yet. Noetica did right in reverting the closure.
- Yes things would be simpler if certain ideas were kept separate. The biggest example of this is that, as can be seen on other WP: pages, Wikipedia favors intra-article consistency and not necessarily inter-article consistency. The issue that SlimV raised was whether or not WP: MoS should say so, not whether the rule should be changed, but both issues have been discussed in this thread. Darkfrog24 (talk) 23:14, 4 October 2012 (UTC)
- Noetica is simply incompetent. There is nothing special about admins closing RfC. -Nathan Johnson (talk) 14:58, 5 October 2012 (UTC)
- Noetica is many, many things (I could tell you stories) but he has not shown himself to be incompetent. If you believe that Noetica has broken a rule or acted improperly, then explain yourself or file a complaint. There's no need to use insults. Darkfrog24 (talk) 01:35, 6 October 2012 (UTC)
- Thank you Nathan. And thank you for not caring (see my talkpage). Surely it is appreciated when non-admins step in to clear backlogs of work that admins normally do; but I think you misjudged, this time. NoeticaTea? 21:54, 5 October 2012 (UTC)
- Agree to keep discussion open. Darkfrog has done some framing of the policy problem and Noetica has returned and wishes to respond. Since there is no consensus, perhaps further discussion will help clarify the issue. It would certainly save time in the long run if the issue could be dispensed with. Neotarf (talk) 18:12, 5 October 2012 (UTC)
- I am a little delayed (beyond the 24 hours I had expected). I will submit a summary later today. In Australia, that is; so let's say on 6 October by UTC. NoeticaTea? 21:54, 5 October 2012 (UTC)
Noetica, you seem to be making this up as you go along. There is absolutely nothing in the policy which prefers an admin closure over a non-admin closure. Any RFC "can be formally closed by any uninvolved editor". I suggest you undo your reversions, and start to play by the same rules as the rest of us. 146.90.43.8 (talk) 18:20, 8 October 2012 (UTC)
- No, Safely Anonymous. I am acting in good faith to preserve due process. See remarks I have just posted below. There is nothing in policy or anywhere else to preclude my actions, prompted by wild irregularities in the conduct of this RFC. (It was already closed by the BOT, note!)
- NoeticaTea? 22:49, 8 October 2012 (UTC)
- You didn't "preserve due process". You reverted the closure, which was made by an uninvolved editor, because you, an involved editor, disagreed with his assessment. What kind of chaos would result if every editor did that "in good faith" whenever they disagreed with the result of an RFC? 23:07, 8 October 2012 (UTC) — Preceding unsigned comment added by 146.90.43.8 (talk)
Noetica's RFC summation
[This is my final systematic statement in the RFC. I request that no one post comments or questions within it, only after it.–NoeticaTea? 14:26, 6 October 2012 (UTC)]
- Procedural problems
There have been problems with this RFC from the start, and they have obscured the issues most unproductively, as I will show below. Procedural problems include these:
- Biased wording in the advertising of the RFC. Some of that was fixed at my insistence, though reluctantly (on evidence from refusals to reword things for accuracy at my request before the formal RFC). At the head of the RFC my correction can be seen.
- Poor oversight by the proposer of the RFC. SlimVirgin has done little to keep things on track, except twice to hide my own efforts at recording the state of the voting (though all acknowledge that this count is not the sole or main consideration in an RFC).
- Replication of entire votes, including prohibited copying of signatures. My attempts to rectify that chaotic development were also reverted in part by SlimVirgin. They are what prompted me to register the votes in one place; but in an apparent assertion of ownership, I was overruled. I gave up such attempts. The RFC remains sprawling and barely navigable.
- Loss of the RFC tagging. The RFC was archived, but SlimVirgin did nothing to rectify this. It was left to Neotarf (a far less experienced editor) to sort the mess out. Neotarf did well, but the status of the discussion as a legitimate RFC has been left uncertain.
- History of the text in question (November 2008; August 2011)
- SlimVirgin was the editor who originally inserted the contested wording ("... though not necessarily throughout the encyclopedia as a whole"), with this edit of 21 November 2008.
- SlimVirgin's edit summary does not reveal in any way that she added it, or even which point she was addressing exactly: "(→Consistency: created new header to emphasize this point; removed sentence from previous section that seemed to contradict it)". The intent of the edit cannot be determined from that summary.
- No evidence has been adduced in this RFC that SlimVirgin's edit was discussed first, or had any sort of consensual backing.
- Tony edited to rationalise the early part of the page, with this edit of 4 August 2011.
- Tony's edit summary did reveal the intent and effects of his edit: "(Rationalise unruly bunch of mini-sections ('principles'). Reduce negative angle. Rm repetition and redundancy. See talk page.)".
- Tony's edit did refer to discussion on the talkpage.
- The section on the talkpage that Tony initiated ("Extraneous clutter at the top") drew considerable participation. The discussion Tony started runs to just under 4,000 words (about eight A4 pages).
- The discussion Tony started did make reference, with a diff, specifically to SlimVirgin's text:
And the "general principles" section that these were stuck into had its start in this diff by SlimVirgin. Probably, in retrospect, saying "General Principles" made it a magnet for people with an agenda to sneak things into. [Dicklyon (talk) 06:13, 3 August 2011 (UTC)]
Well, Slim's good with this stuff, but probably didn't envisage that it would become the unruly forest we now see. [Tony (talk) 06:40, 3 August 2011 (UTC)]
- Tony's removal of the contested wording was unchallenged for more than twelve months (till a few weeks ago).
- My position
- The central purpose of Wikipedia's Manual of Style (MOS, with WP:MOS as its main page) is to present style guidelines for all Wikipedia articles. As discussion above shows, this natural account of manual of styles in general has been endorsed by ArbCom, and no one has offered any plausible alternative purpose for having MOS at all.
- The great majority of MOS provisions are what I call singular guidelines. That is, they recommend just one option among possible alternative style choices. This follows naturally from its central purpose; to the extent that it does not select form the range of possible alternatives, it fails as a manual of style.
- In just very few areas, more than one option is allowed for. These MOS-permitted alternatives include systematic variations in English (like US or British), variation in choice of dash for sentence punctuation (spaced en dash or unspaced em dash), management of possessives ending with an /s/ or /z/ sound, and so on.
- The contested wording fails to make clear the crucial difference between singular guidelines and MOS-permitted alternatives.
- The crucial difference can be extracted from wording that comes immediately after (like this, in MOS as it stands right now: "Where more than one style is acceptable, editors should not change an article from one of those styles to another without a substantial reason. Revert-warring over optional styles is unacceptable.") But in practice, such a continuation is not cited at article talkpages: just the text finishing with the contested wording.
- The best evidence for this and related confusions can be found in this very RFC and the discussion leading up to it (all underlining is mine):
- "I am opposing the removal because style consistency across articles has always been discouraged since the 'date delinking' edit wars years ago. It's clear and concise."
- [Enric Naval. An alarming misrepresentation of the very purpose of MOS. "Clear and concise"? Concise, but on the evidence here it is not at all clear.]
- "[After a challenge from Mirokado:] Hum, my bad. A better wording: 'enforcing consistency across articles has always been discouraged'."
- [Enric's correction is still inaccurate, since the purpose of MOS's singular guidelines (see above) is indeed consistency across 4,000,000 articles. Enric's continuation can be read above on this talkpage; but it reveals no clear conception of MOS guidelines, instead showing that he perhaps wavers in his attitude to the contested wording.]
- " 'I feel like it, I raised it on the talk page, and no one objected within a reasonable time frame,' is sufficient reason [for a change in style]".
...
"People should need a reason to make such changes. That reason need not be big. It can be 'I feel like it, I raised it on the talk page, and no one objected.' However, 'We have to make these articles match because they're closely related in subject!' is false."
- [Darkfrog. These are bizarre priorities, according to which consistency between even related articles takes lowest place of all; they suggest a misunderstanding of provisions of MOS itself, and of WP:CONSENSUS.]
- " 'I feel like it, I raised it on the talk page, and no one objected within a reasonable time frame,' is sufficient reason [for a change in style]".
- "I do not believe that we should add P3 to the MoS"
"We shouldn't add more rules without a good, non-hypothetical reason."
- [Darkfrog. P3 was an abstract proposition I put forward (see above on the page); no one suggests that it ought to be included. But then, the contested wording is itself in the category of "more rules"; so how can its inclusion be supported without "a good, non-hypothetical reason"? No one has demonstrated that its loss was felt over the last twelve months!]
- "I do not believe that we should add P3 to the MoS"
- "We should assume that anything written down in the MoS will be cited as gospel on article talk pages."
- [Darkfrog. But then, gospel can be interpreted many ways – especially when it includes words like "not necessarily" (which caused some difficulty for Enric as I have shown just above), and is turned to political purposes (see citations of "gospel" in the archives of Talk:Mexican–American War, where Enric and Darkfrog are among those who insist on conflating singular guidelines and MOS-permitted alternatives for crusading purposes).]
- "The MoS may be only a guideline in theory, but in practice, it's a set of hard rules. That means that we should treat any new additions to the MoS as if they will be cited as gospel on talk pages."
- [Darkfrog. Again dealing with singular guidelines and MOS-permitted alternatives as if there were no distinction; and ignoring the explicit directive at the head of every MOS page: "Use common sense in applying it; it will have occasional exceptions." This is a confusion about a confusion. MOS explicitly does the opposite of claiming to be "a set of hard rules"; and it is the responsibility of its readers to ... read it!]
- "The policy is that cross-article consistency is permitted but not required."
- [Darkfrog. But note that MOS is not policy. The nearest relevant policy is at WT:TITLE, which by the way includes inter-article consistency as a basic principle.]
- "The MoS does not have a default position for inter-article consistency."
- [Darkfrog. Yet again confusing MOS-permitted alternatives (inter-article consistency not called for) and singular guidelines (inter-article consistency definitely intended).]
- "The MoS does (or used to and should again) state that intra-article consistency is its purpose."
- [Darkfrog. Plainly not a fair reading of the contested wording, and opposed to the very purpose of any manual of style.]
- "Inter- but not intra-article consistency strikes a balance between neatness and the diversity of opinion among our editors."
- [Darkfrog. Just muddled. Is it what was meant, in fact? Even reversing "inter-" and "intra-" here, it yet again ignores the distinction between singular guidelines and MOS-permitted alternatives.]
- "I disagree with 'In groups of articles on similar topics, similar styling is better than an unprincipled or random selection of styles.' [T]his has never been a requirement."
- [PBS. Again, it is astonishing to see the priorities here – as if there were not many projects within Wikipedia that see the value of treating their articles with extra consistency, beyond what MOS calls for. And of course this is a non sequitur: "[T]his has never been a requirement." Of course there is no explicit and particular "requirement" that one should avoid what is random and unprincipled in style choices. But if we appeal to common sense at the head of MOS pages, that would seem to include orderly and principled decision-making.]
- "The problem is what is a group?"
- [PBS, and elsewhere Enric Naval and Darkfrog. But this can hardly be the problem, in efforts toward harmonising thematically related articles. There are others, like Which style choice is apt for that theme? And even if it were the problem, that does not preclude the finding of solutions, or workarounds; and it cannot be shown to apply in every situation. For an obvious example, the articles on the chemical elements form a perfectly natural grouping, and it naturally trumps any competing grouping that might intersect with it like "common substances", "valuable substances", or "dangerous substances".]
- "I suspect that while the argument about obvious groups is superficially attractive, due to the problems lack of clarity in defining a group, it will eventual[ly] lead inexorably towards harmonisation of style over large parts of Wikipedia."
- [PBS. Some of us will struggle to see how that could be a problem!]
- "There has never been style consistency across articles on WP, ..."
- [SlimVirgin. Confusing, yet again, singular guidelines and MOS-permitted alternatives.]
- "There has never been consensus to introduce style consistency across articles; on the contrary, there has always been opposition to it."
...
"There has always been an understanding that internal consistency is required when it comes to style issues, but not consistency across articles."
- [SlimVirgin. Confusing, once more, singular guidelines and MOS-permitted alternatives. And ignoring the very reason for MOS to exist.]
- "There has never been consensus to introduce style consistency across articles; on the contrary, there has always been opposition to it."
- "The problem is that the second and third paragraphs contradict each other. The second says we have a house style; the third says we do not."
...
"The second paragraph says there is a house style, but the third paragraph says there isn't, so there's a contradiction right there. It matters less if the two paragraphs are read together, but the separate anchors mean they might not be. The question is: to what extent does Wikipedia have a house style, or to what extent does it allow contributors to choose a style so long as there is internal consistency?"
- [SlimVirgin. No, that was never the case. Same confusion. And "the question" rests on that confusion of singular guidelines and MOS-permitted alternatives.]
- "The problem is that the second and third paragraphs contradict each other. The second says we have a house style; the third says we do not."
- "The words in question were in the MoS for quite some time, and were removed without discussion."
- [SlimVirgin. Wrong. See diffs above, and the link to an archived 4,000-word discussion.]
- "The word 'necessarily' is important here. It signals that consistency across articles may sometimes, or regularly, be appropriate, but not invariably, and that some style issues are left to the editors on the page to decide."
- [SlimVirgin. But the word 'necessarily' is one of the most confusing and misread elements in all of this. See misreadings cited above, including statements by SlimVirgin herself.]
- "The MOS is not a prescription to be applied slavishly to all articles."
- [Amatulić. This is not what the RFC is about, though many have assumed that it must be. The same muddying of issues that we see above. The level of authoritative status that the community accords to MOS is one matter; MOS's varying recommendations in singular guidelines and MOS-permitted alternatives is another.]
- "A short phrase serves as a useful reminder of that fact, and its removal, as Enric Naval pointed out, leaves room for other interpretations, contributing to wasted time in needless debates about inter-article consistency."
- [Amatulić's continuation. But as we see abundantly from the quotes above, it is the inclusion of the contested words that brings confusion! Has there been confusion over the last twelve months, while it was absent?]
- "We should emphasize that we are not here to make everybody toe the same line. If somebody's formatting can be traced to a practice that is accepted in a particular venue, then that formatting should be allowed."
- [Binksternet. But the contested wording does not emphasize that; or at least, if it is interpreted most reasonably in the light of what should follow it (about MOS-permitted alternatives), then that emphasis is very slight. The second sentence here leaves room for speculation; it seems to appeal to efforts toward inter-article consistency, but it could amount to a rejection even of MOS's singular guidelines! On either reading, there is confusion of issues.]
- "Removing the explicit allowance for editors to not be required to conform to the tittle of MOS, through a change by the MOS-most editors, is troubling on multiple levels."
- [Shenme. But that is not what the contested wording is about at all; and not what this RFC is about!]
- "Oppose removal/retain - This would also seem to fall afoul of WP:ENGVAR, among other things..."
- [jc37. How? Why? The editor does not say. Has the force of ENGVAR somehow appeared diminished over the last twelve months?]
- "Ideally nothing would depend on such a fine balance of words, but experience of Wikipedia editing suggests to me that either wording will be used by those who cherry-pick the MOS to support a prior position. 'Sensible' editors already understand that intra-article consistency is a priority, and that inter-article consistency is highly desirable, and that both kinds of consistency are subject to consensus, not ownership. Unfortunately many editors are not 'sensible'."
...
"I'm concerned that removing the wording will encourage uncooperative behaviour, ..."
- [Peter Coxhead. And I will close with his very thoughtful words, which ought to be studied in their entirety above. In my own experience, almost any wording can be perverted to uncooperative ends. We have to draft Wikipedia guidelines and policy with skill, diligence, and goodwill to minimise that. Where I disagree with Peter is on the inclusion of the contested wording, which in my experience, and from the evidence of the quotes above, is spectacularly subject to misreading, misrepresentation, and all manner of abuse.]
- "Ideally nothing would depend on such a fine balance of words, but experience of Wikipedia editing suggests to me that either wording will be used by those who cherry-pick the MOS to support a prior position. 'Sensible' editors already understand that intra-article consistency is a priority, and that inter-article consistency is highly desirable, and that both kinds of consistency are subject to consensus, not ownership. Unfortunately many editors are not 'sensible'."
- In light of the evidence just given, I oppose any simple patchwork solution to optimising the wording of MOS's lead: especially the restoration of wording that brings such serious and counterproductive confusion.
- I propose that the contested wording remain excluded from MOS, and that there be a new discussion toward accommodating all points of view about the status of MOS within Wikipedia. That seems to be the issue to which most of those wanting the wording restored have gravitated, rather than what it actually says.
- If somehow this chaotic and compromised RFC were to succeed, anyone should feel free to start another one on more rational principles to address what remains totally muddled in this one (including in the proposal the removal of wording discussed here). I might do that myself, if I can find the time.
NoeticaTea? 14:26, 6 October 2012 (UTC)
- Noetica, I think you are overestimating the level or order that is required of an RfC and the specificity of the actions required of the person who starts it. Is it nice if things have a clear structure? A lot of the time. Did SlimV break some rule or act irresponsibly by not enforcing such a structure (and is controlling other people in that way even reasonably possible)? No.
- Maybe Eric N and those others whom you cite were not misunderstanding the MoS. Maybe you have misunderstood it. The only thing that we know for sure is that you and they (and I) do not agree. The fact that someone disagrees with you is not evidence that you are right and they are wrong.
- The statement "We have to make these articles match because they're closely related in subject" is false. I'm referring to rules, to what the MoS requires, which is why I chose the words "have to." Does the MoS require inter-article consistency? No it does not. But it doesn't forbid it either. That is why I find "I like it. I raised it on the talk page and no one objected within a reasonable amount of time" to be a good defense of optional changes.
- By "cited as gospel," I mean "taken as a rule that is not open to exception or deviation," not "treated as one would treat a religious text."
- When I say, "In practice, the MoS is a set of hard rules," I mean that people can be censured and punished for disobeying it. "The MoS is just a guideline, so I can ignore it if I feel my changes make the article better" is no defense at all to an AN/I.
- The MoS does not have a default setting for inter-article consistency. No part of it says "inter-article consistency is required." It explicitly permits editors to make their own choices with respect to British and American English, the serial comma, etc. etc.
- What evidence? Noetica, you have not presented any evidence. You've only presented opinions: some of your own, and some of others, many of which you seem to have misunderstood.
- You mentioned the Mex-Am War talk page again. What exactly do you think that that event has to do with the inclusion or exclusion of this wording? No, it is not obvious from looking at that talk page. (And the word "gospel" does not appear on it.)
- Maybe the reason why "everyone has failed to mention the distinction between singular guideline and MoS-permitted alternatives" is because allowing people to use incorrect English isn't the issue. This entire discussion has been about what you call MoS-permitted alternatives from the start.
Darkfrog24 (talk) 20:40, 6 October 2012 (UTC)
Time to close this (RfC for re-insertion of "not necessarily throughout Wikipedia as a whole")
The RfC had been open for 33 days, and it was closed by an uninvolved editor, [32] so I can't see any reason not to respect the closure. Restoring a sentence to a guideline shouldn't require this level of meta discussion. SlimVirgin (talk) 16:02, 8 October 2012 (UTC)
- It obviously does because the added text is wholly inadequate to address the issues it purports to deal with. The only way of closing the rfc at present would be "no consensus" which would mean restoring the text which had been stable for a year or so. Actually I would be quite happy with that... And I will not accept a non-admin closure of this either, it is far too contentious. --Mirokado (talk)
- Why wouldn't you accept a non-admin closure? What is special about administrators that means they, and only they, can close this?!? --Jayron32 19:07, 8 October 2012 (UTC)
- Administrators adjudicate policy disputes, and hence are solely authorized to close, say, contested Afds. There is nothing in WP policy or guidelines which says uninvolved editors cannot close contested RFCs, since they are not binding. Noetica's idea of closing the discussion with Noetica's own lengthy summary (an involved editor's summary) seems not ok. Asking for an administrator to arbiter what is essentially an editorial dispute is not ok either. Reverting an uninvolved editor's closure is acceptable on grounds the summary is incorrect, but not on the grounds he (specific case here) is a non-admin. Churn and change (talk) 21:14, 8 October 2012 (UTC)
- I made a summation for the side that opposes insertion of the contested wording. Did you miss where there was discussion of each side doing such a thing? I clearly labelled it as my summation. Surely anyone is welcome to do one of those. Make your own, if you like. But stick to facts – and opinions that are supported by evidence and argument. As I do, right?
And this is not simply an "editorial dispute", as you call it. As if we were dealing with a mere article! No: we are dealing with Wikipedia's core style resource, affecting 4,000,000 articles. Spot the difference.
NoeticaTea? 09:19, 9 October 2012 (UTC)- A highly flawed and misleading summation in which you consistently if unintentionally misrepresent the meanings of other editors' statements and present no evidence in favor of your position. Darkfrog24 (talk) 15:01, 9 October 2012 (UTC)
- Clearly we disagree about that. But remember: it was my summation, of the sort that I believe you had called for, some time back. You replied to it, as you were entitled to. And I let your reply stand, giving you the last word (as things stand). Good enough? If you make a similar summation of your own, I will reply to it. Will you give me the last word, when I do so?
NoeticaTea? 22:10, 9 October 2012 (UTC)- No I didn't ask you to do that. I invited you to present and explain evidence, specifically your comment that the discussion o Mex-Am page has to do with this discussion.
- You are not being gracious by not removing other people's comments. That is required of you. Darkfrog24 (talk) 00:37, 10 October 2012 (UTC)
- You made a summation, Darkfrog. And you invited others to participate in such a process: "I think this discussion might benefit from a summary of the evidence presented. Please limit discussions to things that can be verified (rather than discussing reasoning alone)." Neotarf independently made a summary. I too chose not to proceed in the exact way the way you had set up, because I regarded it as skewed and disorganised. After announcing clearly that I would do so, I gave a summation from my point of view. I labelled my summary clearly: as mine. You did not do such a thing. I now invite you to make a summation that overtly presents things as you see them (not purporting to be a summary for all sides). Forgive me if I misunderstood: I thought you were in favour of people presenting such epitomes from the various points of view. You answered my summation, and I then let you have the last word. How long would you like this to drag on?
- You write: "You are not being gracious by not removing other people's comments" [sic]. Sorting through others' dirty work, one gets dirty hands. This RFC was a disgrace from the beginning – from before the beginning, in fact. I have a particular interest in due process. Quibble selectively as you like; and I will act as I see fit in accord with policy and guidelines, in the interest of MOS as I see it. And therefore in the interest of Wikipedia, as I see it.
- NoeticaTea? 01:50, 10 October 2012 (UTC)
- Yes, a summary of the evidence as opposed to the previous parts of the discussion, which had focused primarily on opinions and hypothetical reasoning. No, the summation that you gave was not what I asked you to do. I'm not saying that you have to do exactly what I tell you to, but then you don't get to say that this was "of a sort that I believe you had asked for," as you do above.
- Disorganized? It was divided up by subject and then by chronology. It might not have been set up the way you would have done it, but it was not disorganized.
- I've already presented things as I see them. The participants in this discussion have already read and responded to everyone's opinions. That's why I thought a new angle, evidence, might be more productive. More than half of the participants support reinsertion of the wording, but that's not how consensus is supposed to work. More than half of the evidence would be another matter.
- Refraining from removing other people's comments is not due process. You don't get to pat yourself on the back for not doing something that you're not supposed to do anyway.
- And there is no need for an sic next to my words. My usage is correct. Informality does not require an sic. Darkfrog24 (talk) 02:10, 10 October 2012 (UTC)
- First, I put "an sic" next to my quotation of your words because I would not want anyone to think I introduced an error into them. Look again: "You are not being gracious by not removing other people's comments." It struck me, and it may strike others, as a strange construction that possibly has one "not" too many. So a "sic" is justified and normal. Assume good faith.
Second, I am not obliged to do what you asked me to do, as (obviously!) neither you nor anyone else has an obligation to do what I want.
Third, I explicitly chose to narrow my evidence to the copious misunderstandings that are evident on this page. That is potent evidence, and easily checked in one place. You ask for more? Sorry, I have given all that is needed, and spent far more time than I can justify on this RFC (if indeed it is still an RFC).
Fourth, I wrote: "I regarded it as skewed and disorganised." So yes: as you rightly diagnosed, we disagree. Surprised? I made my own solution, neatly labelling it.
Fifth, move on now?
NoeticaTea? 03:46, 10 October 2012 (UTC)- Strange construction does not merit an sic. And no it does not have too many nots. I am not being a saint by not stealing from you. You are not being gracious by not deleting other people's comments. Count before you sic. As for assuming good faith, don't push your gosh darn luck; you've already had plenty of benefit of the doubt from me.
- Noetica, I just said that you aren't obliged to do what I tell you. I also said, "If you don't do what I tell you, you don't get to say 'I'm only doing what you told me!'" No, I didn't ask you to post a long list of your own arbitrary opinions peppered with misinterpretations of other contributors. Again, you can do your own thing, but then you don't get to claim that it's my thing.
- If you didn't have time to post, you wouldn't be posting. My guess? You're having a grand old time. Darkfrog24 (talk) 04:50, 10 October 2012 (UTC)
- Keep guessing, Darkfrog. I find all of this most unpleasant, and a serious intrusion into things that I have to get on with, to meet real-life obligations and deadlines. You could simply drop the business of "an sic". I wish you would! I used "sic" in good faith, and I explained why I used it; but you refuse to leave it at that. Do just leave it at that, OK? You said that I misinterpret others' comments; I chose to let you have the last word, when you alleged that in answer to my extended submission above. Happy? I say you misinterpret me; but I really want not to dwell on any of that now. Enough!
NoeticaTea? 05:58, 10 October 2012 (UTC)- There actually is a way to get people to stop replying to you on a thread. Instead of telling other people to shut up or complaining that you have a million other things to do, all of which are more important than the discussion or the people who've been talking to you, you stop posting on it yourself. Darkfrog24 (talk) 13:39, 10 October 2012 (UTC)
- Keep guessing, Darkfrog. I find all of this most unpleasant, and a serious intrusion into things that I have to get on with, to meet real-life obligations and deadlines. You could simply drop the business of "an sic". I wish you would! I used "sic" in good faith, and I explained why I used it; but you refuse to leave it at that. Do just leave it at that, OK? You said that I misinterpret others' comments; I chose to let you have the last word, when you alleged that in answer to my extended submission above. Happy? I say you misinterpret me; but I really want not to dwell on any of that now. Enough!
- First, I put "an sic" next to my quotation of your words because I would not want anyone to think I introduced an error into them. Look again: "You are not being gracious by not removing other people's comments." It struck me, and it may strike others, as a strange construction that possibly has one "not" too many. So a "sic" is justified and normal. Assume good faith.
- Clearly we disagree about that. But remember: it was my summation, of the sort that I believe you had called for, some time back. You replied to it, as you were entitled to. And I let your reply stand, giving you the last word (as things stand). Good enough? If you make a similar summation of your own, I will reply to it. Will you give me the last word, when I do so?
- A highly flawed and misleading summation in which you consistently if unintentionally misrepresent the meanings of other editors' statements and present no evidence in favor of your position. Darkfrog24 (talk) 15:01, 9 October 2012 (UTC)
- I made a summation for the side that opposes insertion of the contested wording. Did you miss where there was discussion of each side doing such a thing? I clearly labelled it as my summation. Surely anyone is welcome to do one of those. Make your own, if you like. But stick to facts – and opinions that are supported by evidence and argument. As I do, right?
- Administrators adjudicate policy disputes, and hence are solely authorized to close, say, contested Afds. There is nothing in WP policy or guidelines which says uninvolved editors cannot close contested RFCs, since they are not binding. Noetica's idea of closing the discussion with Noetica's own lengthy summary (an involved editor's summary) seems not ok. Asking for an administrator to arbiter what is essentially an editorial dispute is not ok either. Reverting an uninvolved editor's closure is acceptable on grounds the summary is incorrect, but not on the grounds he (specific case here) is a non-admin. Churn and change (talk) 21:14, 8 October 2012 (UTC)
- Noetica reverted Nathan Johnson's closure twice, [33] [34] with the edit summary: "Revert closure of RFC by User:Nathan Johnson; controversial RFCs should be closed by admins; this was premature: actions had been asked for and were pending; failed to distinguish points about consistency 1. where choices were allowed and 2. generally)".
- The RfC had been open for 33 days, so there was nothing premature about the closure. There's also nothing controversial about the RfC. Nathan has closed RfCs before and the request for closure was made on AN/RFC, so it all seemed to be in order. I've requested an uninvolved admin to endorse or overturn the closure, but it really shouldn't be necessary. SlimVirgin (talk) 21:52, 8 October 2012 (UTC)
- Noetica is now reverting my explanation for the closing admin. [35] SlimVirgin (talk) 22:27, 8 October 2012 (UTC)
- Yes Slim; and I have in good faith reverted your reversion of my action.
- In fact the RFC was already ended, by the BOT. Before Nathan got to it. From WP:RFC:
There are several ways an RfC can end: the bot can automatically delist the RfC, the RfC participants can agree to end it, or it can be formally closed by any uninvolved editor.
- That can be read as final; or it can be read as just one element in the disruptive and irregular trajectory of the RFC from the start. And that can be read as an excellent reason for abandoning the proposal in the RFC – on procedural grounds alone.
- Yes, I reverted Nathan's closure: twice, because he reverted my reversion. There is nothing at WP:RFC to preclude my doing so – as an experienced editor in good standing, deeply concerned about due process and the calm and consensual development of MOS. I gave my reasons, and I have just now given more reasons. I did not revert the action of an unvinvolved admin, note.
- My reversion was endorsed by Darkfrog, the most vigorous proponent of the views that I reject in the RFC.
- The best solution: leave it. Start again, if anyone wants to. But let any future RFC be conducted fairly, honestly, without the appearance of ownership by any party, and with a question that is transparent in its intent and useful in its scope.
- ♥
- NoeticaTea? 22:44, 8 October 2012 (UTC)
- He has reverted again. [36] This is one of a series of reverts and clarifications from Noetica during this RfC, and editing other people's posts, adding his own opinion in bold, attempts to keep a running tally of votes, reverting when it was removed, topped off by twice reverting an uninvolved editor's closure, and now twice reverting my explanation for the closing admin -- which I have had to request only because of his reverting. It has been really unacceptable behaviour. SlimVirgin (talk) 22:49, 8 October 2012 (UTC)
- What Nathan "closed" was not an RFC any more. The RFC had been ended by a bot (see WP:RFC).
- My use of bold, and other devices, has been in response to your own faulty presentation and later inadequate management of an RFC that you initiated, Slim. That was disruptive, on your part. I am entitled to keep things readable, and to work toward an orderly structure and process where you did not.
- You are involved, I am involved. If you act in a partisan way, or against the provisions of WP:RFC or WP:OWNERSHIP, someone ought to counteract that. You are an admin, with very high standing in the community; I am not an admin, and am in an extremely vulnerable position. But I will defend due process here, and I will explain my actions and meet the requirements of policy and guidelines to the best of my ability – in the face of abuses by others. It is a great pity that uninvolved parties do not intervene similarly, so far. It has been left to my own good-faith efforts.
- NoeticaTea? 23:23, 8 October 2012 (UTC)
This should be evaluated by someone who is "sufficiently experienced", "impartial", and "familiar with all of the policies and guidelines that relate to the proposal". (see WP:PROPOSAL) This is a policy page, not a wikilove kitten page, and IMHO needs to be closed by an admin, and not someone who is helping out with the backlog but "doesn't care" (see Noetica's talk page). The boxing and summary should be done by the closing admin, not the person bring the RfC.
One of the troubling things about this RfC is that no one really understands what it is supposed to do. That was clear enough from the extensive comments. The first time the wording was introduced, there was no explanation or edit summary, at least not that was brought out in the rather confused discussion above. Likewise when this RfC was introduced, the new language was just inserted without much of a rationale. Maybe that's where any new attempt at a consensus should start. --Neotarf (talk) 00:16, 9 October 2012 (UTC)
- Well, yes. Except that it is not a policy page but a guideline page. One of the most important we have, in fact.
- I say it again: the RFC was delisted by the bot, and according to WP:RFC, that ends it. Just like a similar one at WT:TITLE, which simply fell of the edge due to neglect, intractably bad management – and eventually, despairing lack of interest. But then, we have grown accustomed to RFCs running counter to the provisions at WP:RFC. A shame.
- NoeticaTea? 00:31, 9 October 2012 (UTC)
- Guideline, yes, sorry, I was going to double check before I posted. At any rate WP:PROPOSAL applies to both policy and guideline. --Neotarf (talk) 01:30, 9 October 2012 (UTC)
- I really wish people would void themselves of this idea that any tricky closure, or anything in any way related to policy, should be handled by an admin. That is absolutely not the case. Wikipedia content and policy is built by editors. Secondly, are you not embarrassed to pull a quote that far out of context? You're making the case that an admin should close this, so you use this quote, "sufficiently experienced", "impartial", and "familiar with all of the policies and guidelines that relate to the proposal". The sentence that you pulled that from is this: "This does not require the intervention of an administrator, but may be done by any sufficiently experienced independent editor (an impartial editor not involved in the discussion) who is familiar with all of the policies and guidelines that relate to the proposal." 146.90.43.8 (talk) 00:48, 9 October 2012 (UTC)
- But Nathan was clearly out of his depth, and unfamiliar with the many complex procedural and other niceties in the case; and the RFC had already been delisted by the bot. Nothing tricky about that, right? It's clear from WP:RFC. If the proposer of an RFC is so negligent as to let it slip away into the archives, that should tell us something about its merits.
NoeticaTea? 01:12, 9 October 2012 (UTC)
- You didn't like the way Nathan closed it, so you called him incompetent and reverted him. That's no way to carry on. You were far too heavily involved to revert the closure. Do you really think it was helpful, let alone pleasant, to start tossing "incompetent" around? People disagree with RfC closures all the time. It's in the nature of the thing. Rather than reverting, you should have brought it up on talk, or gone to one of those 3rd opinion noticeboards, or just taken your lumps. Regarding the bot's intervention, that seems to be something you've picked up on tonight. You certainly didn't mention it when you reverted. What did the bot say? Is it a competent bot? Whatever it said, I think that to attempt to overturn Nathan's closure on a technicality goes against the spirit of what we're trying to achieve here. 146.90.43.8 (talk) 02:08, 9 October 2012 (UTC)
- Actually, Nathan called Noetica incompetent. If Noetica said anything like that to Nathan, then he didn't do it here. Darkfrog24 (talk) 03:55, 9 October 2012 (UTC)
- More exactly, Noetica didn't say "incompetent", but he did say "anything like that to Nathan": "less than competent summation of the issues" etc. Nathan's response escalated that comment a little further (the edit vs. editor distinction). Art LaPella (talk) 04:20, 9 October 2012 (UTC)
- Ah, I see. That certainly amounts to insults on both sides. Darkfrog24 (talk) 15:01, 9 October 2012 (UTC)
- No, it does not. I commented on Nathan's actions; Nathan issued a judgement concerning me (with which you disagreed, in fact). There was no further escalation from me. I wrote: "Thank you Nathan. And thank you for not caring (see my talkpage). Surely it is appreciated when non-admins step in to clear backlogs of work that admins normally do; but I think you misjudged, this time."
NoeticaTea? 22:10, 9 October 2012 (UTC)- Note that "Thank you for not caring" sounds like obvious sarcasm, but it wasn't. Art LaPella (talk) 01:51, 10 October 2012 (UTC)
- Noetica, if I were to say, "your actions are those of a big fat drama queen," wouldn't you think I was calling you a drama queen? If you leave sarcastic comments, you don't get to say that you didn't escalate. Darkfrog24 (talk) 04:57, 10 October 2012 (UTC)
- "Sounds like obvious sarcasm, but it wasn't." Want to know what I would think? I would think you were for the second time in this sprawling discussion resurrecting old, old material in an especially provocative way. The last person borrowing that particular trope of yours for political effect is now enduring a one-year block, and an indefinite topic ban from all MOS and TITLE matters. Take care. And move on.
NoeticaTea? 05:58, 10 October 2012 (UTC)
- "Sounds like obvious sarcasm, but it wasn't." Want to know what I would think? I would think you were for the second time in this sprawling discussion resurrecting old, old material in an especially provocative way. The last person borrowing that particular trope of yours for political effect is now enduring a one-year block, and an indefinite topic ban from all MOS and TITLE matters. Take care. And move on.
- Noetica, if I were to say, "your actions are those of a big fat drama queen," wouldn't you think I was calling you a drama queen? If you leave sarcastic comments, you don't get to say that you didn't escalate. Darkfrog24 (talk) 04:57, 10 October 2012 (UTC)
- Note that "Thank you for not caring" sounds like obvious sarcasm, but it wasn't. Art LaPella (talk) 01:51, 10 October 2012 (UTC)
- No, it does not. I commented on Nathan's actions; Nathan issued a judgement concerning me (with which you disagreed, in fact). There was no further escalation from me. I wrote: "Thank you Nathan. And thank you for not caring (see my talkpage). Surely it is appreciated when non-admins step in to clear backlogs of work that admins normally do; but I think you misjudged, this time."
- Ah, I see. That certainly amounts to insults on both sides. Darkfrog24 (talk) 15:01, 9 October 2012 (UTC)
- More exactly, Noetica didn't say "incompetent", but he did say "anything like that to Nathan": "less than competent summation of the issues" etc. Nathan's response escalated that comment a little further (the edit vs. editor distinction). Art LaPella (talk) 04:20, 9 October 2012 (UTC)
- Actually, Nathan called Noetica incompetent. If Noetica said anything like that to Nathan, then he didn't do it here. Darkfrog24 (talk) 03:55, 9 October 2012 (UTC)
- But Nathan was clearly out of his depth, and unfamiliar with the many complex procedural and other niceties in the case; and the RFC had already been delisted by the bot. Nothing tricky about that, right? It's clear from WP:RFC. If the proposer of an RFC is so negligent as to let it slip away into the archives, that should tell us something about its merits.
- Do you say the same about Darkfrog's endorsement of my reversion? He would have liked the close, but he agreed that it was flawed and he had no problem with my action. To his credit!
Your assumption about my motives is against WP:AGF. I was ready to let things take a different course; but if people want to go by the wikilawyering letter of the law, I must resort to the details in WP:RFC and other provisions – where, by the way, there is nothing said against such actions as I have taken. Unlike the actions of some others involved here.
I do not toss "incompetent" around. It's not something I would bring in lightly. But I now give the facts as I read them. So do you – anonymously, of course. ☺
NoeticaTea? 02:20, 9 October 2012 (UTC)
- Why would I have liked the conversation to have been ended by an outside party? People were still talking and new voices were still welcome. Does the closer get to decide the issue or something? Darkfrog24 (talk) 03:55, 9 October 2012 (UTC)
- To be clear, Darkfrog: that outcome would have suited you, I thought. But not the means by which Nathan sought to produce it. As I have said, it is to your credit that you responded as you did in the circumstances. I am glad that there are some of us who want due process and wise judgements, even if we disagree about how those judgements end up. The quality of RFCs is declining. That should be of concern to us all, regardless of our more particular opinions.
NoeticaTea? 09:10, 9 October 2012 (UTC)
- To be clear, Darkfrog: that outcome would have suited you, I thought. But not the means by which Nathan sought to produce it. As I have said, it is to your credit that you responded as you did in the circumstances. I am glad that there are some of us who want due process and wise judgements, even if we disagree about how those judgements end up. The quality of RFCs is declining. That should be of concern to us all, regardless of our more particular opinions.
- I shouldn't have put incompetent in quotes, and I'm sorry for that, but it's essentially what you said. I'm not going to get into a discussion about who did what after you reverted. or about your motives. You were a heavily involved editor who reverted an RfC closure because he didn't like the result. That's the crux. You keep going on about "due process" as though you have some great wrong to right, but don't you think every editor on the wrong side of an RfC closure feels that way? Due process, if that means anything at all within the context of WP, would have been to let the decision stand, and to enter into discussion about your reservations. 146.90.43.8 (talk) 11:11, 9 October 2012 (UTC)
- I believe reinserting the contested wording to be right and proper, but why would closing the RfC have resulted in said reinsertion? Sure, the preponderance of evidence is in favor, but how often does that matter around here?
- People should continue to discuss this matter if they aren't finished and new voices should still be welcome. I don't think you and I have the same ideas about proper procedure and due process, Noetica. Darkfrog24 (talk) 15:01, 9 October 2012 (UTC)
- Fine! I do not withdraw my compliment to you, Darkfrog: it is to your credit that you endorsed my reversion of a closure, even though the closure favoured your position. Apply what gloss you will. NoeticaTea? 22:40, 9 October 2012 (UTC)
- Why would I have liked the conversation to have been ended by an outside party? People were still talking and new voices were still welcome. Does the closer get to decide the issue or something? Darkfrog24 (talk) 03:55, 9 October 2012 (UTC)
- Do you say the same about Darkfrog's endorsement of my reversion? He would have liked the close, but he agreed that it was flawed and he had no problem with my action. To his credit!
- It is my understanding that, besides the bot ending it, the participants can also just agree among themselves. In fact, WP:RFC also says "Deciding how long to leave an RfC open depends on how much interest there is in the issue, and whether editors are continuing to comment." It's probably better to leave it open for too long than to close it too early. Clearly the disputed wording was being interpreted in at least two ways, and further discussion may be able to unravel that. --Neotarf (talk) 01:42, 9 October 2012 (UTC)
- Well, they might agree on various things among themselves – with difficulty, of course, if the proposer comes in and closes parts of it that she doesn't like, which happened in the present case at least three times. But this is not a simple question of "deciding how long to leave an RfC open". It was not open, after the bot delisted it. So it could not be "left" open. That's in accord with WP:RFC; and it makes sense. If there's so little happening that it gets archived and delisted, something is not useful or fathomable about the RFC. A new one should then be started, along better and fairer lines.
NoeticaTea? 02:05, 9 October 2012 (UTC)
- Well, they might agree on various things among themselves – with difficulty, of course, if the proposer comes in and closes parts of it that she doesn't like, which happened in the present case at least three times. But this is not a simple question of "deciding how long to leave an RfC open". It was not open, after the bot delisted it. So it could not be "left" open. That's in accord with WP:RFC; and it makes sense. If there's so little happening that it gets archived and delisted, something is not useful or fathomable about the RFC. A new one should then be started, along better and fairer lines.
- It is my understanding that, besides the bot ending it, the participants can also just agree among themselves. In fact, WP:RFC also says "Deciding how long to leave an RfC open depends on how much interest there is in the issue, and whether editors are continuing to comment." It's probably better to leave it open for too long than to close it too early. Clearly the disputed wording was being interpreted in at least two ways, and further discussion may be able to unravel that. --Neotarf (talk) 01:42, 9 October 2012 (UTC)
- Goodness gracious. There's a lot of people here who keep insisting that admins have special privileges in closing RFCs. Quite simply, and with all due respect, this idea is total and complete bullshit, and I'm not sure where it gets into the mindset here, but it really has never been a standard. Admins do not have any special powers in declaring consensus on any matter; in cases where Admins are granted priority, is always in cases where doing so potentially requires the use of an administrator tool (blocking, deleting, or protecting) and even in those cases, it is sufficient for a non-admin to close the discussion and evaluate it, and get an admin to enact the results. There is absolutely no requirement or mandate for any discussion which doesn't even need an administrator to enact the results of, to involve an administrator at all. Now, admins may, as experienced editors, often close discussions, but a discussion closed by any uninvolved and sufficiently experienced editor is perfectly legitimate, and doesn't need confirmation by an administrator. At all. Stop trying to make Administrators out to be more than they are. There's no policy page, no guideline, and no requirement written ANYWHERE on Wikipedia that non-admins can't close discussions like this one. See Wikipedia:ADMIN#Administrators.27_abilities, and note the lack of "only admins can close RFCs". Stop it already. --Jayron32 04:34, 9 October 2012 (UTC)
- You misrepresent what is said, Jayron. And I will thank you to restrain your language in your "fucking" edit summaries, all right? (And you're an admin?)
I agree with you that admins are not absolutely required for closing these things; but we are entitled to expect better judgement in closing contested RFCs, and there is some hope of that from admins, who have higher standing for a good reason. That's the theory, anyway. In practice, the admin who started the RFC on such a shaky footing then left it to tumble into a mess. So there you go.
Just as there is nothing anywhere requiring admins to do such a closure, there is nothing anywhere to stop me from reverting a premature closure that showed poor judgement. I acted in good faith, and Darkfrog (holding opposing views) endorsed my action. You have a problem with that? Think about it then; and if after that you still have a problem, with me or my actions, take it to my talkpage. But please: keep a civil demeanour chez moi. ♥
NoeticaTea? 09:10, 9 October 2012 (UTC)
- I've not mentioned you by name. Feeling guilty? --Jayron32 17:07, 9 October 2012 (UTC)
- Guilty? Not in the slightest. Make your meanings clearer, and you will get even clearer answers.
NoeticaTea? 22:40, 9 October 2012 (UTC)
- Guilty? Not in the slightest. Make your meanings clearer, and you will get even clearer answers.
- That might be your theory, but it's not mine; it's not in the policy, nor is part of the WP ethos. Why do you think the admin icon is a mop and bucket? You're asserting that an admin typically has better judgement than his non-admin homologue. If that were the case, it would be reasonable to go the whole hog and give admins primacy in all content disputes. And wouldn't that be fun! 146.90.43.8 (talk) 11:11, 9 October 2012 (UTC)
- Well, here is an example of a user requesting an admin closure of an rfc. Two admins responded favourably to the request, both contributed to the closure and nobody seems to have objected. My apologies if that is not as routine as I had assumed. Even if formally admins have no "special privileges" it is common practice to ask them to help when peer interactions are making no progress. A closure by an uninvolved admin once discussion has died down (or is merely going in circles) would be helpful in this case. --Mirokado (talk) 12:33, 10 October 2012 (UTC)
- That's fair enough, Mirokado. If people want to post there ask an admin to close an RfC, that's up to them. Personally, I don't like that idea at all, but if others do, good luck to them. But this is something completely different. This is overturning an existing closure because it was not made by an admin, and that really is not on. Surely, you can't support that. The argument that admins are in some way more competent to deal with matters of content than non-admins runs counter to everything that WP is about. And if you've ever glanced at RfA, I'm sure you'll have seen that ability to contribute to the content side of WP is not high on the list of prerequisites. 146.90.43.8 (talk) 13:19, 10 October 2012 (UTC)
- You misrepresent what is said, Jayron. And I will thank you to restrain your language in your "fucking" edit summaries, all right? (And you're an admin?)
- Noetica, by your own argument, summations should not be removed from the talk page; in general, something on-topic should never be removed from the talk page, except for archiving. So you should put back Nathan's summary and SlimVirgin's summary of summary, probably at the tail end of the discussion. You have the right to overturn a closure (admin or non-admin), so you don't need to put back either closure. Beyond that, I don't think it makes any sense to ask for admin help here when there is no editorial consensus. If an admin hands down a specific judgment, it will just be an imposed one. If it sticks in spite of that, we would have set a wrong precedent for WP. The "no-consensus" summary (probably about right) would not work because there is the question of what it means: to keep current wording, wording as it was a month ago, a year ago, four years ago? I see debates on all those issues. I suggest you close the discussion (a purely technical procedure, with no summary or evaluation added) and start a new thread asking explicitly whether the part-in-question should be 1. included or 2. removed. This means we don't need to worry about what was in the article when. I would say every line in an article should have justification for being there, and so the onus of consensus is on those wanting inclusion. That last part, I realize, is the crux of the practical side of the issue.
- One point on the theory and practice of admins closing such discussions. The theory is that admins are the same as the rest except for policy decisions on Afds, user blocks and so on. The practice is that their opinions carry a tad bit more weight because they, on average, have more editing experience than others. But here we have plenty of experienced editors already contributing to the debate, and taking an admin's word as the final one is just elevating them to a position WP policy doesn't entitle them to, and, in all fairness, one I haven't seen any admin asking for. Churn and change (talk) 20:09, 9 October 2012 (UTC)
- I don't think I agree that anyone has the right to overturn a closure after 33 days. If it's closed prematurely, then yes, but 30 days is the default, and no one had commented for some time. So the closure was valid and the closing editor was uninvolved. Starting yet another RfC with the same question seems like overkill. We already had a discussion before this RfC, where there was consensus to include the words in question; that was on 31 August (see here). Noetica would not accept that consensus, so I started the RfC on 1 September. He did his best throughout it to turn it into a mess, then he overturned the closure on 4 October. To open yet another RfC to please just one person makes no sense. SlimVirgin (talk) 20:35, 9 October 2012 (UTC)
- By "right" I meant a procedural right in the sense such a revert would not attract sanctions (short of being 3RR). RFCs, including closing summaries, aren't binding. If a closing summary is unacceptable to an editor (in this case, to two editors) then the dispute is still on.
- There is the issue several experienced editors did oppose inclusion, even though they were a minority (as per the list you posted, and which Noetica edited out of present existence). To me, content of an article should be justified by consensus; if there is no consensus it should be there, it shouldn't be there. Churn and change (talk) 21:27, 9 October 2012 (UTC)
- Yes, but the rationale for refusing to recognize the closing summary is invalid. Claiming to not recognize the validity of the closure because the person doing the closing wasn't an admin is a non-reason. It would be like claiming that because it wasn't closed on a Wednesday, it can't be valid. If there's a real reason to oppose beyond "It didn't close the way I voted" or "It wasn't closed by an admin", then I don't see what the actual objection is. Can you bring up a problem, beyond either of those two reasons? --Jayron32 21:35, 9 October 2012 (UTC)
- I agree the admin/non-admin thing is nonsense. After all, most of the admins voting here actually voted for the proposal to begin with (you, jc37, the proposer, and, I think PBS), so the closure accorded with their views. No point asking me about the objection to the closure; I think the closure should probably be discussed standalone, if there is consensus, not necessarily unanimous, that the summary should be respected, the issue is done. The objection closure was too early seems strange if the thread had gone into the archives because of inactivity. But I can't speak for the two editors who objected to it. Churn and change (talk) 21:55, 9 October 2012 (UTC)
- Yes, but the rationale for refusing to recognize the closing summary is invalid. Claiming to not recognize the validity of the closure because the person doing the closing wasn't an admin is a non-reason. It would be like claiming that because it wasn't closed on a Wednesday, it can't be valid. If there's a real reason to oppose beyond "It didn't close the way I voted" or "It wasn't closed by an admin", then I don't see what the actual objection is. Can you bring up a problem, beyond either of those two reasons? --Jayron32 21:35, 9 October 2012 (UTC)
- I don't think I agree that anyone has the right to overturn a closure after 33 days. If it's closed prematurely, then yes, but 30 days is the default, and no one had commented for some time. So the closure was valid and the closing editor was uninvolved. Starting yet another RfC with the same question seems like overkill. We already had a discussion before this RfC, where there was consensus to include the words in question; that was on 31 August (see here). Noetica would not accept that consensus, so I started the RfC on 1 September. He did his best throughout it to turn it into a mess, then he overturned the closure on 4 October. To open yet another RfC to please just one person makes no sense. SlimVirgin (talk) 20:35, 9 October 2012 (UTC)
- Churn, if you look at the sorry history of this RFC, you will find me preserving what others had written: keeping everything open and visible, and explaining my actions to keep the RFC in conformity with settled procedures. You will find SlimVirgin, in her occasional entries here, hiding and reverting such attempts to keep order. You will find her, as the proposer of the RFC, selecting a portion of it and declaring it to be closed discussion, and attempting to draw administrative attention to that selection. If I have once or twice, in reverting grossly anomalous actions here, left some remarks off the page, that was not my intention. It is how reversions work though, isn't it? I have no problem with any such remarks being restored. Please go ahead and do that, if it's important to anyone.
I think it is clear: the appropriate closure would be, or will be, "no consensus". That should not itself be controversial. We can hope that an admin, or indeed a suitably experienced and impartial editor, can see that pretty clearly. It is in a way inevitable. The sooner we get such a closure, if the RFC is not deemed to have simply lapsed on closure by the bot (according to explicit provisions at WP:RFC), the better. Then we might move on, having learned that such thoroughly flawed RFCs will encounter resistance for their serious procedural shortcomings. The stakes are too high for such RFCs to become the norm at vital policy and guideline talkpages.
NoeticaTea? 22:40, 9 October 2012 (UTC)
- Slim:
- I am not surprised that you find Nathan's "closure" acceptable. But I contrast your attitude with Darkfrog's, who endorsed my overturning it even though he supports your proposal and therefore might have been pleased with the content of Nathan's judgement. You speak of "rights"? I question your "right" to start an RFC with non-neutral and inaccurate advertisement to the community, against the explicit provisions at WP:RFC. I question your "right" to assert ownership of the RFC, censoring well-explained efforts to document its course when you had simply gone missing. I definitely question your characterisation of my orderly efforts to remedy the disorderly actions of others. Or wanton inactions, which were also a problem. And I question a great deal more; but we have to move on. Let's all learn from this, yes? Another RFC might well be justified: properly and fairly conducted, and with a proposal that truly addresses concerns unearthed in the one we should now be abandoning.
- Churn:
- You speak of "the list [SlimVirgin] posted, and which Noetica edited out of present existence". That is fully explained above. That's how reversions work; but let any remarks be restored. I would welcome that. Don't expect me to do all the work, though! Now, do you speak also of Slim's suppression of my earlier list? Did you track that also, as you selectively track my actions? Your count of who might be displeased by Nathan's "closure" is also rather wayward. If you want to avoid interminable churning of issues here, don't make careless statements that cry out for correction. Move on?
- Jayron:
- There was a complex of reasons for opposing Nathan's "closure". Don't simplify unreasonably, or you will just prolong pointless to-and-fro when we ought to be doing something more productive, now.
- NoeticaTea? 23:08, 9 October 2012 (UTC)
- But the whole point is you should have reverted what you disagreed with, the closure, and moved the summary comments to the end. You removed those comments, don't you think you should restore them as a courtesy? Is the argument others have done it a justification, even if true? Yes, I did read the running-poll debate, and the final disposition, of collapsed but present, seems good. I am focusing specifically on your actions not because of non-neutrality but because your actions are the latest ones and hence are more visible. Where did I count who might be displeased by Nathan's closure? I said two people have objected to it; is that a wrong statement? Are you reading an implication "just two" there? I maintain, of the three reasons you gave, the non-admin and too-early aren't valid because of policy and because discussion had been inactive long enough for thread to be archived; the third, incorrect summary, would be valid if there are others agreeing with you. If there are, I would say the dispute continues, with present disposition 'no consensus.' To me, 'no consensus' means 'no consensus to include.' That conclusion depends rather strongly on how you justify your overturning of the RFC closure, and how much support you have on that. Churn and change (talk) 23:42, 9 October 2012 (UTC)
- It may be your "whole point", Churn. That does not make it the whole point. I have already explained my actions to put things back on track according to the provisions for RFCs at WP:RFC, and said that if they are imperfect, others can do some of the work too. By all means, restore any remarks that were incidentally removed. You still ignore or excuse, interestingly, some of the much larger anomalies to which I have adverted. If my actions are "the latest", ask yourself why I resorted to those actions. Or better, read and fully absorb the reasons I have already given you for those. Where are Slim's reasons for her actions, anyway? Including in the discussions that preceded the RFC. Let's just leave it all behind, as an unredeemable mess. There is clearly no consensus to insert confusing text that was removed, with accompanying discussion, more than a year ago. Address the real underlying issues, fairly and collegially, and we'll all be better off. So will MOS; so will Wikipedia; so will the readers, ultimately. That's what it's about – not maintaining one's cherished text in MOS at all costs.
Can we move on now, really?
NoeticaTea? 00:06, 10 October 2012 (UTC) - Noetica, you are not the angelic defender of order. You are the defender of your own personal preferences and your own ideas about how RfCs should work. There is more than one right way to hear everyone out. Absolutely no one but yourself has said anything about procedural shortcomings. All objections to Slim's proposal except yours have had to do with its substance.
- As for "clearly no consensus," chuck the "clearly" and one could argue either way. More than half of the participants supported it and far more than half of the evidence supports it. Darkfrog24 (talk) 00:45, 10 October 2012 (UTC)
- Not invariably angelic. Who is? But I am a staunch defender of order, in the best ways that I know.
- Personal preferences? Hardly. Not unargued ones, at least. There is much in MOS that I think is ridiculous, but I leave it alone. And I defend it against arbitrary removal.
- My ideas of how RFCs should work are the community's ideas, as captured in WP:RFC. If people here don't like that, let them take it up at WT:RFC. Or the village pump, maybe. Don't blame someone who stands out for insisting on those consensually derived provisions.
- There is clearly no consensus either way. If we discount merely confused votes that mix up two kinds of provisions in MOS (see my detailed account of this in my summation subsection, above), there is not even a numerical majority in favour of the misunderstood wording. When there is no consensus either way, accept it. And work on the underlying issues, which really need to be articulated in an honest RFC, conducted as the community expects. The sooner the better.
- NoeticaTea? 01:50, 10 October 2012 (UTC)
- WP:RFC does not contain the large number of formal rules that you are acting as if it contains. If there is something in WP:RFC outlining the specific structure that an RFC must have or stating that the person who initiates the RFC has very specific duties which Slim has failed to perform, then point to the line. If your ideas came from the community, then the community is something other than WP:RFC.
- No numerical majority? There's been a numerical majority in every single count. You'd have to do some serious cherry-picking to get an even split. Darkfrog24 (talk) 02:18, 10 October 2012 (UTC)
- Did you read what I wrote, a few lines above? It was this: "If we discount merely confused votes that mix up two kinds of provisions in MOS (see my detailed account of this in my summation subsection, above), there is not even a numerical majority in favour of the misunderstood wording." Keep misreading and misrepresenting, and we'll be here forever. Can we put it all behind us, and in future work according to WP:RFC? For a start read the bits about neutrality and delisting by the bot; note the omission of any prohibition on reverting incompetent closures; read the whole thing, preferably. And read what the community says at WP:TALK, also. Both Slim and I edited at others' contributions; I have explained my own reversions, and I have twice said that I have not the slightest objection if anyone will undertake the work of restoring anything incidentally removed along the way. Do it yourself, if it bothers you! The intent was plainly not to stifle comment. Then compare Slim's actions; and note for example how signed votes (including actual signatures) on this page are still replicated, misleadingly, through her intervention.
Give it a rest. I will when you will! Move on.
NoeticaTea? 03:46, 10 October 2012 (UTC)- Of course I read what you write. I just don't agree with you. Cutting out the contributions of everyone whose votes displease you, perhaps because you would prefer to believe that they didn't understand the issue, would be cherry-picking. You consistently claim that people who don't agree with you must have misunderstood something.
- And of course I have read WP:RFC. It doesn't contain the content that you claim it contains. You've accused Slim of doing wrong by not enforcing a strictly structured RfC, but WP:RFC doesn't say that anyone has to. It doesn't outline a strict RfC structure at all. This idea of a "proper" RfC structure is not coming from WP:RFC. It's coming from you. Darkfrog24 (talk) 04:50, 10 October 2012 (UTC)
- Laughable and entirely unsupportable misrepresentation of my actions, if doing that were not a serious departure from productive talkpage behaviour. Tell you what: I will resist the inclination to refute it in detail. This has to stop somewhere.
NoeticaTea? 06:07, 10 October 2012 (UTC)- "Entirely unsupportable"? You do know that your posts are recorded, right? Darkfrog24 (talk) 13:39, 10 October 2012 (UTC)
- Laughable and entirely unsupportable misrepresentation of my actions, if doing that were not a serious departure from productive talkpage behaviour. Tell you what: I will resist the inclination to refute it in detail. This has to stop somewhere.
- Did you read what I wrote, a few lines above? It was this: "If we discount merely confused votes that mix up two kinds of provisions in MOS (see my detailed account of this in my summation subsection, above), there is not even a numerical majority in favour of the misunderstood wording." Keep misreading and misrepresenting, and we'll be here forever. Can we put it all behind us, and in future work according to WP:RFC? For a start read the bits about neutrality and delisting by the bot; note the omission of any prohibition on reverting incompetent closures; read the whole thing, preferably. And read what the community says at WP:TALK, also. Both Slim and I edited at others' contributions; I have explained my own reversions, and I have twice said that I have not the slightest objection if anyone will undertake the work of restoring anything incidentally removed along the way. Do it yourself, if it bothers you! The intent was plainly not to stifle comment. Then compare Slim's actions; and note for example how signed votes (including actual signatures) on this page are still replicated, misleadingly, through her intervention.
- It may be your "whole point", Churn. That does not make it the whole point. I have already explained my actions to put things back on track according to the provisions for RFCs at WP:RFC, and said that if they are imperfect, others can do some of the work too. By all means, restore any remarks that were incidentally removed. You still ignore or excuse, interestingly, some of the much larger anomalies to which I have adverted. If my actions are "the latest", ask yourself why I resorted to those actions. Or better, read and fully absorb the reasons I have already given you for those. Where are Slim's reasons for her actions, anyway? Including in the discussions that preceded the RFC. Let's just leave it all behind, as an unredeemable mess. There is clearly no consensus to insert confusing text that was removed, with accompanying discussion, more than a year ago. Address the real underlying issues, fairly and collegially, and we'll all be better off. So will MOS; so will Wikipedia; so will the readers, ultimately. That's what it's about – not maintaining one's cherished text in MOS at all costs.
- But the whole point is you should have reverted what you disagreed with, the closure, and moved the summary comments to the end. You removed those comments, don't you think you should restore them as a courtesy? Is the argument others have done it a justification, even if true? Yes, I did read the running-poll debate, and the final disposition, of collapsed but present, seems good. I am focusing specifically on your actions not because of non-neutrality but because your actions are the latest ones and hence are more visible. Where did I count who might be displeased by Nathan's closure? I said two people have objected to it; is that a wrong statement? Are you reading an implication "just two" there? I maintain, of the three reasons you gave, the non-admin and too-early aren't valid because of policy and because discussion had been inactive long enough for thread to be archived; the third, incorrect summary, would be valid if there are others agreeing with you. If there are, I would say the dispute continues, with present disposition 'no consensus.' To me, 'no consensus' means 'no consensus to include.' That conclusion depends rather strongly on how you justify your overturning of the RFC closure, and how much support you have on that. Churn and change (talk) 23:42, 9 October 2012 (UTC)
- Churn, if you look at the sorry history of this RFC, you will find me preserving what others had written: keeping everything open and visible, and explaining my actions to keep the RFC in conformity with settled procedures. You will find SlimVirgin, in her occasional entries here, hiding and reverting such attempts to keep order. You will find her, as the proposer of the RFC, selecting a portion of it and declaring it to be closed discussion, and attempting to draw administrative attention to that selection. If I have once or twice, in reverting grossly anomalous actions here, left some remarks off the page, that was not my intention. It is how reversions work though, isn't it? I have no problem with any such remarks being restored. Please go ahead and do that, if it's important to anyone.
I step away from the keyboard for a moment, and look what happens to this thread! The subthreads have become impossible to follow; I will put my points all together.
- I don't know if it was me Jayron was cursing out with the F-bomb in the edit summary, or someone else, but at the risk of being hectored about "feelings", I will respond to the issue of who should close that Jayron seems to be upset about. True, there have been non-admins close discussions, but they are the type you will see a few months later with an RfA where everyone votes to support because "I already thought they were an admin". The same with admins who close the discussions. Although admins are expected to know something about different areas of the Wikipedia, the editors who follow these pages are used to seeing certain admins participate in the discussions and have an idea about whether they have clue or are familiar with the issues.
- Is Darkfrog (sic)? No, the usage sounds perfectly normal to my version of AmE. The way it is phrased I interpret to be a way to soften a criticism. But Noetica should be humored since he uses OzEng, and as I understand it, they do things a little differently; I have even heard that in the antipodal lands, they walk upside down. But Darkfrog has not introduced an error.
- Did Darkfrog make a summation? No. I'm afraid I was the only one who tried to summarize the rationale for the proposal, and it was the same as the first rationale against the proposal. The so-called summation was a comment added after the ivote, and was more of a rhetorical question. If comment was seriously expected, you would think it would have been presented in the discussion section. I suspect the real problem isn't lack of understanding, but lack of agreement.
- It's clear there is no consensus, and advertising in additional forums just produced the same result on a larger scale. If the original requester still wants to pursue the idea, perhaps it should be reworked to address the issues that were brought up, and a new discussion should focus on something like "Should the MoS be ignored for all articles?" or "Should projects be able to opt out of MOS?" Or "Should projects be encouraged to set requirements for articles in one category in the areas where variations are permitted?" or whatever.
--Neotarf (talk) 01:40, 11 October 2012 (UTC)
Does anyone agree with the reasons given for reverting Nathan's closure?
Noetica's primary reason for reverting was that a "controversial RfC should be closed by an admin". The above discussion shows that he is a minority of one in that opinion. Noetica has argued, at length, that the validity of the votes should be decided according his own criteria. Jason's "failure" to use Noetica's criteria was another reason that Noetica gave for reverting him. It seems to me self-evident that Jason is not obliged to use Noetica's criteria, any more than he's obliged to use mine or any other participant's. Jason's job was to assess the opinions and thought processes of all participants, which he did. Subsequent to his revert, Noetica has mentioned that the bot had delisted the RfC before Jason closed it. Well, the bot did exactly that, it delisted it; it removed it from the list. It didn't declare that all bets were now off, and we must start again. The RfC was open for 33 days. All interested parties must already have seen the listing. The hours between the delisting and the closure made no difference at all.
I don't feel that Noetica, a heavily involved editor, should have reverted Nathan, an uninvolved editor. I don't feel that Noetica has found any support for the reasons he gave for the revert: it should have been an admin, Jason didn't use Noetica's criteria, a bot had delisted the RfC. Noetica's cri de guerre throughout all of this has been "due process". Surely due process now is that Nathan's closure stand, and the text be included in the article. 146.90.43.8 (talk) 12:09, 10 October 2012 (UTC)
- It's my understanding that an RfC tag is a request for new voices and new participants. Because the conversation is ongoing (or was before we all got sidetracked into a discussion of whether or not the RfC tag should be removed), I believe that it is still proper to invite new participants.
- The rules do not seem to require that the person who closes the RfC be an administrator.
- As for deciding the issue, more than half of the participants support re-inserting the contested wording, but that's not how consensus is supposed to work (it's often how it does work, but that's another matter). I'd like to look at the evidence of the practical consequences of this wording. Four different contributors claim to have seen problems that they attribute to the presence or absence of this wording, and I'd love to hear from them again or from anyone who's witnessed something similar. Darkfrog24 (talk) 13:46, 10 October 2012 (UTC)
- That's reasonable Darkfrog,but I think there's a limit to how many new participants we can attract. I'd also be interested to see concrete examples. How about we a drop a line to those four and see what they come up with; then, after that, if nothing's changed within the RfC, we go with Nathan's closure? Consensus is always the thorniest issue. At some point, someone has to make a decision, even if it's to declare no consensus. In this instance it was Nathan who made the call, and he was fully qualified to do so. 146.90.43.8 (talk) 14:07, 10 October 2012 (UTC)
- The point of an RfC is to create a framework within which a decision can be made, however imperfectly. The framework is "30 days discussion as the default maximum (can be closed earlier if there are no objections), with closure by an uninvolved editor." People can revert a closure if it happens before the 30 days is up, or if the closer has previously taken a side and therefore shouldn't be the closer, or if there has been inappropriate canvassing or inadequate publicizing, but otherwise closures are respected. There would be no point in holding RfCs otherwise.
- This RfC was held according to the normal standards for a guideline RfC. It was publicized on the usual bot pages and on the PUMP, GA and FA pages. It was left open for 33 days. Someone requested closure on AN/RFC, and an uninvolved editor weighed up the consensus, which reflected the consensus of the previous discussion. It also reflected reality (namely that cross-article consistency is not, as a matter of fact, required). There is therefore no reason not to respect Nathan's closure. SlimVirgin (talk) 16:57, 10 October 2012 (UTC)
- I couldn't agree more. The problem is that Nathan's closure was not respected, so we have to decide where to go from here. 146.90.43.8 (talk) 22:32, 10 October 2012 (UTC)
- There's nothing to stop us from re-respecting it. The only alternative is another RfC. Given that I started this one by apologizing for being repetitive (an informal discussion had already established a consensus on August 31, but Noetica objected), it would be absurd to start a third one just because Noetica has objected again. SlimVirgin (talk) 22:55, 10 October 2012 (UTC)
- Again from WP:PROPOSAL: "If consensus for broad community support has not developed after a reasonable time period, the proposal is considered failed. If consensus is neutral or unclear on the issue and unlikely to improve, the proposal has likewise failed." Also: "It is typically more productive to rewrite a failed proposal from scratch to address problems than to re-nominate a proposal."
- That's about proposing new guidelines or policies. It has nothing to do with RfCs. SlimVirgin (talk) 00:30, 11 October 2012 (UTC)
This closure was premature.
The original discussion died down about halfway through, and the initiator of the proposal made a request for early closure. But there was some disagreement about the early closure. This request was postponed, and in the meantime, notices were placed on various pages. This drew in a few more votes and comments, about equally divided, as before. Again the discussion died down. At this point, I wrote a summary of the positions and started a new section for tallies, since the the discussion seemed to be finished and the tallies had not been updated. This triggered a new round of discussion. At the time of the latest attempt at closure, several questions had been asked, and the problem reframed in several ways, but responses were still being awaited.
I don't think it's too fair to dump on the editor who attempted the closure, since it was done in good faith, although evidently without being familiar with WP:CONLIMITED, which states "Wikipedia has a higher standard of participation and consensus for changes to policies and guidelines than to other types of articles" or with WP:PROPOSALs for policies and guidelines, that asks that a closing editor be "familiar with all of the policies and guidelines that relate to the proposal", consider whether "major concerns raised during the community discussion been addressed", and whether "the proposal contradict(s) any existing guidelines or policies". The editor's statement "The closure was neither premature nor incompetent, but you've cleverly exploited my not caring. You may continue arguing about something that no readers actually care about."[37] should pretty much answer any questions about that individual's level of attention to nuances of policy and guideline. It is admirable that they responded to a request to help out with the backlog, especially on these pages that seem to have so many hidden landmines for the unsuspecting newcomer, but they didn't seem to have noticed that the discussion had indeed started up again. --Neotarf (talk) 23:26, 10 October 2012 (UTC)
- The RfC was over. The bot had archived it because no one had commented for seven days. You unarchived it but prematurely removed the bot tag (on 28 September). [38] Then a few of you started discussing whether the words to be restored had ever been in the MoS (yes, they had). But there was no new discussion, no new issues. That discussion petered out too. Nathan then came along on October 4 (33 days after the RfC had opened) formally closed it, and summed up consensus. Then suddenly Noetica claimed (a) that an admin had to close it, which is not correct; and (b) that the closure was premature, which is clearly also not correct. SlimVirgin (talk) 00:41, 11 October 2012 (UTC)
- No I did not "prematurely remove the bot tag", the bot removed the bot tag with the edit summary "Removing expired RFC template." [39] I had to revert the removal later in order to take the discussion out of the archive, but I restored it as the last step. --Neotarf (talk) 01:58, 11 October 2012 (UTC)
- I don't agree that the closure was premature, Neotarf. There was no on-going substantive discussion at the time of the closure, and there hasn't been any since. It's true that Nathan's response to Noetica's insulting remarks was somewhat petulant, but that has no bearing on the closure itself. Anything said after the revert clearly could have not been used as justification for the revert. I can't accept that this RfC has to be closed by someone familiar with the minutia of the MoS. The question in the RfC is not one that requires any particular specialist knowledge. It deals with a concept that pretty much every editor is familiar with. And let's not forget that it's the job of the closing editor to assess the consensus among the arguments put forward within the RfC itself, nothing more. 146.90.43.8 (talk) 11:54, 11 October 2012 (UTC)
- I believe that rearranging the issue so that we could view it from the POV of evidence rather than by the number of people who agreed with one side or the other (not that that can't work too) counts as new material for the purposes of this thread.
- I do believe that the closure was premature but I do not believe that an admin has to do the closing. My only objection to Nathan specifically was that he resorted to name-calling. Darkfrog24 (talk) 00:56, 11 October 2012 (UTC)
- What is your suggestion now, Darkfrog? I noticed on August 11 that these words had been removed and I restored them. I was reverted. I began this discussion on August 12. The bot archived it and Noetica objected to me unarchiving it, so I had to restart it on August 22. We achieved a majority to restore the words on August 31. Noetica reverted. I therefore started the RfC on 1 September. On October 4 Noetica twice reverted Nathan's closure.
- As a result it has now been two months to discuss a sentence that we all know is demonstrably true -- Wikipedia does not as a matter of fact require style consistency across articles. If you're not going to support Nathan's closure, what do you suggest? SlimVirgin (talk) 01:31, 11 October 2012 (UTC)
- Of course it does, and there are probably some bots operating on that premise. You should probably go back and read the comments everyone gave with their ivote. You may think you know what you wrote, but does everyone interpret it the way you do? Proofreading is more than looking for typos. --Neotarf (talk) 02:09, 11 October 2012 (UTC)
- As a result it has now been two months to discuss a sentence that we all know is demonstrably true -- Wikipedia does not as a matter of fact require style consistency across articles. If you're not going to support Nathan's closure, what do you suggest? SlimVirgin (talk) 01:31, 11 October 2012 (UTC)
- Darkfrog, you've mentioned a couple of times that one side of the debate has a numerical majority and that the same side has put forward by far the strongest arguments. That, essentially, is consensus. If we don't act now and implement the proposal, then we are left with the version supported by a numerical minority and by far the weakest arguments. You've also mentioned that some editors were going to provide examples which will shed new light on the issue. I feel that if they were going to do that, they would have done so by now. We can't wait for ever. If such examples do exist they will surface at some point, and we'll all face-palm and make the appropriate adjustment to the article. 146.90.43.8 (talk) 11:54, 11 October 2012 (UTC)
- I see multiple editors objecting to the closure on grounds discussion wasn't over. Almost by definition, that means there is no consensus to accept the closure. Debating whether they are right becomes a debate over a debate over a debate.
- Another point. On WP, if an edit sticks, it is assumed to represent consensus. Per WP:CONSENSUS: " Any edit that is not disputed or reverted by another editor can be assumed to have consensus." That means SlimVirgin's addition of the wording four years ago was per consensus. It also means the removal a year ago also reflected a consensus, a new one changed from the old one. From the very next sentence on WP:CONSENSUS: "Should that edit later be revised by another editor without dispute, it can be assumed that a new consensus has been reached." The latest addition by SlimVirgin was disputed, so the existing consensus before the RFC was not to have the material there. The RFC, in my opinion, has ended in no consensus, since the "include" group doesn't have an overwhelming majority of votes, and the subjective weight of arguments is strong on both sides. That means the existing consensus from before the RFC, not to include, stands. Churn and change (talk) 01:37, 11 October 2012 (UTC)
- This is why we have RfCs with a default 30-day closure, rules about publicizing, rules against canvassing, and uninvolved editors to close them. So that someone makes a decision regarding current consensus (not four years ago, or one year ago), based on arguments and based on numbers, and then we move on. The problem with this page is that the normal decision-making processes seem not to apply. I'm not talking only about this RfC but apparently right across the board. It's in everyone's interests to get that sorted out, whether you agree or disagree about any particular issue. SlimVirgin (talk) 01:48, 11 October 2012 (UTC)
- I rather agree with Churn and change, and I think I would even if I wanted the addition. If there are any further attempts to add this text before a proper closure in favour of doing so, I think we should escalate this somehow. I will be commenting further, I hope later this evening European time, but real life calls for a while... --Mirokado (talk) 13:28, 11 October 2012 (UTC)
I'm going to add the text back into the article, per the RfC
I'm going to add the text back into the article. From the section above, the only remaining justification for the revert appears to be that the closure was premature. I'd say that is demonstrably not the case. The only discussions we've had in the last few days have been meta discussions about the closure, about the nature of consensus, and so on. At the time Nathan closed the RfC there had been no substantive discussion of the question in the RfC for several days and there has been none since. The RfC ran its course, and consensus was assessed by an uninvolved editor. To anyone considering reverting my change, I would ask that you point out here where the on-going discussion is. For the record, I commented within the RfC as 87.112.91.134. 146.90.43.8 (talk) 11:54, 11 October 2012 (UTC)
- Obviously jumping the gun. I will revert. --Mirokado (talk) 13:16, 11 October 2012 (UTC)
- "Obviously jumping the gun" is no argument at all. I've put it back in. 146.90.43.8 (talk) 14:28, 11 October 2012 (UTC)
- IP 146, what do you regard as a "substantive" discussion of the question? Why do you say that it's not "substantive"? --Neotarf (talk) 16:22, 11 October 2012 (UTC)
- "Obviously jumping the gun" is no argument at all. I've put it back in. 146.90.43.8 (talk) 14:28, 11 October 2012 (UTC)
Resolving the underlying infobox "ownership" issue
The fact that "first major contributor gets to arbitrarily decided" idea proposed above isn't workable is only half the problem here, and not the root one. The other, which this proposal also tried to address, is that wikiprojects by and large do appear to believe that they have the authority to tell the entire editorship "thou must" or "thou shalt not" put an infobox on any article We the Project consider within our Holy Scope. They need to be rapidly and unmistakably disabused of this notion before this situation gets any worse. So, the underlying issue this proposal tried to address is a real problem and remains unaddressed with this proposal's failure (because it reached too far in the opposite direction).
I propose that we add a statement to the effect that no editor or group of editors can force this issue, and that it's up to a consensus of the editors at the article, on a per-article basis, just like almost all other editorial decisions on Wikipedia.
(PS: I rather wish we'd scrap the entire WikiProject system and replace it with something that forbids any kind of "club"-like model - no "members" or "participants", no "projects", just pages of recommendations arrived at by a consensus of editors who care, on how to address particular topics. But that's another issue for another time and place.)
— SMcCandlish Talk⇒ ɖ∘¿¤þ Contrib. 22:55, 13 September 2012 (UTC)
- Can you provide links to places where this has happened? (I'm not doubting you, I'm just interested in reading what the debate looked like in those instances.) Tdslk (talk) 00:54, 14 September 2012 (UTC)
- See Classical music, and preceding comments in First major contributor, above. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:17, 14 September 2012 (UTC)
- We already have WP:LOCALCONSENSUS. A link to that should suffice; though the problem is not that we don't have a policy, but that some editors are allowed to ignore it, for the sake of a quiet life. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:22, 14 September 2012 (UTC)
- The rule you want already exists, or nearly does: "If discussion cannot determine which style to use in an article, defer to the style used by the first major contributor." The first choice is a consensus of editors at the individual article. WhatamIdoing (talk) 01:21, 21 September 2012 (UTC)
- I was asked to comment again. That is not the consensus. The consensus that is followed in practice in WP is that once it is decided to use infoboxes on a particular type of article then the decision stands until consensus changes, and affects every article in scope. It does not go article by article. In particular, there is general consensus throughout WP to use infoboxes for people in as standardized and generalized a way as possible across all the relevant wikiprojects; that nobody is compelled to make such an infobox when writing an article, but that if they do not, someone will add it. (I understood the original proposal here to be challenging that, and I understand that challenge to be rejected. If the wording of the MOS needs to be changed to make it clear that they are not optional, I make such a proposal.) DGG ( talk ) 15:44, 22 September 2012 (UTC)
- Thats way off - I hope others dont see things this way as conflict will only issue - Wiki projects don't own articles in anyway and it does go article by article as seen at Using infoboxes in articles. We have tried to fix this ownership problem many times over the years, but still have statements like "should not be used without first obtaining consensus on the article's talk page" that is a clear violation of our Editing policy and Be bold. To think our editor will see some odd WP advice page before they edit is just crazy and has lead to many many conflicts.Moxy (talk) 17:52, 22 September 2012 (UTC)
- Not to mention in-article comments instructing people not to use infoboxes, which are a blatant defiance of the outcome of the RfC called by members of that project in a vain attempt to enforce their preference. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:08, 22 September 2012 (UTC)
- Thats way off - I hope others dont see things this way as conflict will only issue - Wiki projects don't own articles in anyway and it does go article by article as seen at Using infoboxes in articles. We have tried to fix this ownership problem many times over the years, but still have statements like "should not be used without first obtaining consensus on the article's talk page" that is a clear violation of our Editing policy and Be bold. To think our editor will see some odd WP advice page before they edit is just crazy and has lead to many many conflicts.Moxy (talk) 17:52, 22 September 2012 (UTC)
- Quote - "Whether to include an infobox, which infobox to include, and which parts of the infobox to use, is determined through discussion and consensus among the editors at each individual article". There seems to be a drive here that all articles must have infoboxes, and that the editors of an article or members of wikiprojects have no say whatsoever about what the content or format of infoboxes, which people here appear to want to be set centrally as part of MOS and be immune from all challenge. Why should MOS (effectively a Wikiproject itself) have supremacy and be allowed to dictate things if no-one else is? — Preceding unsigned comment added by Nigel Ish (talk • contribs) 18:32, 22 September 2012
- Quote =Nigel Ish "a drive here that all articles must have infoboxes" and "the editors of an article or members of wikiprojects have no say whatsoever about what the content or format of infoboxes" - All that would be the opposite of what the policy says that you have just quoted. All content and format disputes should be discussed at the individual article level first - then proceed to outside the article if not resolvable at the article level. No blanket rules by a group of editors should prevail over talking about what is best for each article at each article!Moxy (talk) 19:45, 22 September 2012 (UTC)
- The quote is what the guidance currently says - the following comments are my take on what the regulars here appear to be doing in trying to force a Wikipedia wide standard for infoboxes onto all articles, with the appearance of trying to override any objections either at the article and ignore any issues that wikiprojects raise, whether based on valid subject related reasons or not.Nigel Ish (talk) 20:18, 22 September 2012 (UTC)
- Oh sorry that was not clear to me.... but yes you are correct that the majority think infoboxes are beneficial thus an asset to our readers.Moxy (talk) 20:29, 22 September 2012 (UTC)
- The quote is what the guidance currently says - the following comments are my take on what the regulars here appear to be doing in trying to force a Wikipedia wide standard for infoboxes onto all articles, with the appearance of trying to override any objections either at the article and ignore any issues that wikiprojects raise, whether based on valid subject related reasons or not.Nigel Ish (talk) 20:18, 22 September 2012 (UTC)
- Quote =Nigel Ish "a drive here that all articles must have infoboxes" and "the editors of an article or members of wikiprojects have no say whatsoever about what the content or format of infoboxes" - All that would be the opposite of what the policy says that you have just quoted. All content and format disputes should be discussed at the individual article level first - then proceed to outside the article if not resolvable at the article level. No blanket rules by a group of editors should prevail over talking about what is best for each article at each article!Moxy (talk) 19:45, 22 September 2012 (UTC)
I just want to comment to say I agree with DGG's analysis above. The current practice is that once there is agreement that a certain type (topic) of article should have an infobox, we do indeed put infoboxes on all articles of that type. This is not the same, for example, as citations, where different articles of the same type could have different citation styles. But I also agree that the MOS is not the place to decide what infobox to use. For many topics it would be better decided by a wikiproject. For types of articles that span many wikiprojects (e.g. biographies), the discussion should be on the village pump. — Carl (CBM · talk) 14:37, 10 October 2012 (UTC)
RFC:Largest cities or city population templates
There is a Request for comment about the utility/redundancy of Largest cities/city population templates. This is an open invitation for participating in the request for comment on Wikipedia:Requests for comment/City population templates. Should you wish to respond to the invitation, your contribution to this discussion will be very much appreciated! If in doubt, please see suggestions for responding. Mrt3366(Talk?) (New thread?) 08:04, 14 September 2012 (UTC)
Three corrections
![]() |
|
Please comment if there are any questions. Apteva (talk) 19:11, 7 October 2012 (UTC)
It appears that the example "the Uganda–Tanzania War; the Roman–Syrian War; the east–west runway; the Lincoln–Douglas debates; a carbon–carbon bond" while not commenting that it is a little long (do we really need so many examples?), is in need of two corrections; in the first example, "the Uganda–Tanzania War", war should not be capitalized (see google book search), and it should be "but not the Roman–Syrian War (as Roman-Syrian War is a proper name)". The article at Uganda–Tanzania War should also be moved, to Uganda–Tanzania war, and if it is a proper name, a better example used, and it be moved to Uganda-Tanzania War. (already moved) [and now it needs to be moved, but there is an RM to decide that...] Apteva (talk) 23:08, 27 September 2012 (UTC)
- Comment. I have reverted Apteva's undiscussed move of Uganda–Tanzania War, which was apparently done to prove a point here and not in the interest of the article itself.
This section attracted no comment before Apteva elevated it to an RFC, probably because Apteva is pushing on proper names, en dashes, and hyphens at several forums at the same time – including an RM, now closed as not moved, for the long-settled Mexican–American War. I have explicitly said, on this talkpage and elsewhere, that general issues with WP:MOS guidelines should be raised as general issues, right here. Not at several locations, and not as particular sparring points. It seems to me that this RFC is yet another waste of time. I comment on one detail only: yes, obviously many examples are needed in the guideline. Even more than we have now, perhaps. Some editors are still refusing to accept the principle it is based on as consensual; and Apteva, for example, is playing hard by appeal to inconsequential differences among the present examples. If any element of the long and meticulous community consultation on dashes in 2011 needs review, let it be done in an orderly and informed way. Some recommended background reading for those interested: the article Proper noun, most of which is now accurate. (It needs a move to Proper name.)
NoeticaTea? 21:48, 7 October 2012 (UTC)- It was a correct move. Uganda–Tanzania war is not a proper noun and is not capitalized. Nor was it undiscussed. The date and time in the above discussion shows that it was pointed out on September 27 that it should be moved, and that it was not moved until October 5 (and a check of the edit history will show that I noted that it had been moved when I opened the RfC on October 7). Clearly plenty of time and some for anyone to disagree with the proposal. Seeing none, I took it as approval, not an unusual response. Should an RM to move proper noun come to my attention I would object. And I think that would be the consensus. The word phrase "proper noun" did not enter use until about 1890. The dictionary, if it contains "proper name", defines it as proper noun. The two terms are interchangeable. I have called for an RfC because I am not going to get into an edit war over the Revert. In the BRD cycle, after R comes D. There had been no response, so I am asking for a response. I do not believe that a review of a clearly embarrassing discussion needs to be reviewed. Proper names use hyphens and our MOS says so. 10,000 books use a hyphen and maybe a 100 use something else. Case closed. I would like to remind everyone to focus on the issue, not the editor, though. WP is never an authority on anything, proper nouns included. WP articles can never be used as a RS. Apteva (talk) 02:40, 8 October 2012 (UTC)
- These topics have already been the focus of much long and pointless argumentation that wasted the time of multiple editors, time that could have been spent elsewhere, like in creating content. I don't understand the point of reopening these discussions so soon after they have finally and painfully been settled by consensus. --Neotarf (talk) 08:03, 8 October 2012 (UTC)
- Congratulations to Noetica, the proper noun article has just been cited by no less an authority than Mark Liberman at Language Log. [40] --Neotarf (talk) 08:09, 8 October 2012 (UTC)
- There are still improvements that are needed - fix the misleading and incorrect examples. If someone wants to argue that proper nouns are not capitalized or that sentences do not need periods, not questions of course, then certainly their time is better spent elsewhere, but if someone insists that Roman-Syrian War is spelled with an endash they will have a very hard time supporting that premise. Is War capitalized in "Uganda-Tanzania War"? Possibly, but if it is the punctuation is a hyphen and not an appropriate example of where to use an endash. If war is not capitalized, Uganda–Tanzania war is an example of where an endash is used, and the capitalization needs to be fixed. In both cases the current article needs to be moved - either to Uganda-Tanzania War or to Uganda–Tanzania war. There are always people who misspell things, and use incorrect punctuation, and that is why there is an edit tab and a move option. Apteva (talk) 03:49, 9 October 2012 (UTC)
Comet Hale-Bopp
This example: "Comet Hale–Bopp or just Hale–Bopp (discovered by Hale and Bopp)" needs to be removed because used either with or without the word "Comet" this is still a proper noun and therefore uses a hyphen, as supported by the thousands of reliable sources that use this punctuation. According to Google Books there are 31,900 sources, the overwhelming majority of which use a hyphen. It is not even close. Apteva (talk) 22:47, 9 October 2012 (UTC)
- Nonsense. Many of those reliable sources do use the en dash, which confirms that it is simply a styling choice. The fact that many sources have a style that substitutes hyphens in the traditional role of the en dash, and that the Google books OCR can't tell the difference, does not mean that WP needs to adopt that style. There's nothing special or unique about Hale–Bopp here. Your concept of "proper noun, therefore hyphen" is unsupportable hallucination. Dicklyon (talk) 01:01, 10 October 2012 (UTC)
- Not nonsense at all. There are some sources that do use en dash, but if there were many, as in many more than use hyphen, then statistically at least one would have appeared in the first ten. Out of the first 100 how many use hyphen? Out of the first 1,000 how many? Google books has 32,900 to look through. I strongly disagree with the supposition that an OCR can not tell the difference as there are a huge number of occurrences in google books of both endashes where they are appropriate and em dashes where they are appropriate. While it is far easier to do a text search, I am completely confident in my assessment that there are no endashes in the first 10 results that I obtained. As was pointed out before, any suggestion of "many" needs to also include "out of how many", as saying there are 432 examples of using Hale-Bopp with an endash sounds impressive until you find out, say, that that was out of 32,000, with 29,000 using a hyphen and 3,000 using a space, just as a made up example. Proper noun hyphen is not fiction. It is in our MOS and I really have yet to see any example of a proper noun that does not use a hyphen. I am not saying they do not exist. I can certainly imagine that if someone named Hale-Bopp and someone named Lennard-Jones discovered a comet it could be called the "Hale-Bopp–Lennard-Jones Comet, to distinguish between one discovered by Hale and someone named Bopp-Lennard-Jones, or by one person named Hale-Bopp-Lennard and one named Jones. Normally exceptions to rules are pretty easy to find. It is academic to find them, but still interesting, and I really have not seen one. One editor perhaps looked for examples of endashes in WP article titles and came up with two that are not proper nouns and two that are using incorrect punctuation on WP. Since when has WP ever been considered a reliable source? Apteva (talk) 04:27, 10 October 2012 (UTC)
- Nonsense. Several of them DO in fact appear in the first page of 10 hits on Google Book Search (with previews). You need to actually look at the previews to see how they are styled, as the OCR does not distinguish hyphen from en dash usually (and sometimes it sees en dashes as em dashes—I was going to say like this one, but it turns out that one really did get typeset with an em dash, due to some amateur typographer's blunder). If en dashes do show up sometimes in snippets, in probably from books that they got electronically, as with this one, where you can tell they got it electronically because if you zoom way in the letters aren't blurry or pixelated; they're being rendered from text. The same effect is often seen in Google Scholar, where papers with en dashes often show up as hyphen, but not always; in spite of that, nearly half show up on the first scholar results page with en dash. It's not an usual style like you're making it out to be. Dicklyon (talk) 05:33, 10 October 2012 (UTC)
- Am I hearing an echo? 5/20 is a long way from "nearly half". It is 3 to 1 in favor of using a hyphen. Which is correct based on that information? Clearly a hyphen. Apteva (talk) 06:35, 10 October 2012 (UTC)
- Nonsense. Several of them DO in fact appear in the first page of 10 hits on Google Book Search (with previews). You need to actually look at the previews to see how they are styled, as the OCR does not distinguish hyphen from en dash usually (and sometimes it sees en dashes as em dashes—I was going to say like this one, but it turns out that one really did get typeset with an em dash, due to some amateur typographer's blunder). If en dashes do show up sometimes in snippets, in probably from books that they got electronically, as with this one, where you can tell they got it electronically because if you zoom way in the letters aren't blurry or pixelated; they're being rendered from text. The same effect is often seen in Google Scholar, where papers with en dashes often show up as hyphen, but not always; in spite of that, nearly half show up on the first scholar results page with en dash. It's not an usual style like you're making it out to be. Dicklyon (talk) 05:33, 10 October 2012 (UTC)
- Not nonsense at all. There are some sources that do use en dash, but if there were many, as in many more than use hyphen, then statistically at least one would have appeared in the first ten. Out of the first 100 how many use hyphen? Out of the first 1,000 how many? Google books has 32,900 to look through. I strongly disagree with the supposition that an OCR can not tell the difference as there are a huge number of occurrences in google books of both endashes where they are appropriate and em dashes where they are appropriate. While it is far easier to do a text search, I am completely confident in my assessment that there are no endashes in the first 10 results that I obtained. As was pointed out before, any suggestion of "many" needs to also include "out of how many", as saying there are 432 examples of using Hale-Bopp with an endash sounds impressive until you find out, say, that that was out of 32,000, with 29,000 using a hyphen and 3,000 using a space, just as a made up example. Proper noun hyphen is not fiction. It is in our MOS and I really have yet to see any example of a proper noun that does not use a hyphen. I am not saying they do not exist. I can certainly imagine that if someone named Hale-Bopp and someone named Lennard-Jones discovered a comet it could be called the "Hale-Bopp–Lennard-Jones Comet, to distinguish between one discovered by Hale and someone named Bopp-Lennard-Jones, or by one person named Hale-Bopp-Lennard and one named Jones. Normally exceptions to rules are pretty easy to find. It is academic to find them, but still interesting, and I really have not seen one. One editor perhaps looked for examples of endashes in WP article titles and came up with two that are not proper nouns and two that are using incorrect punctuation on WP. Since when has WP ever been considered a reliable source? Apteva (talk) 04:27, 10 October 2012 (UTC)
For now I have changed "Comet" to comet, per p. 48 of the New Oxford Dictionary for Scientific Writers and Editors, and per our article on the comet, which does not capitalize the word comet - hence an endash is correct as it is not treated as a proper noun. There is an open RM to move the page to Comet Hale-Bopp, treating it as a proper noun. Sources clearly favor proper noun status. Halley's comet, on the other hand, does not favor proper noun status and can also be corrected. Apteva (talk) 16:28, 11 October 2012 (UTC)
Punctuation and footnotes
I would very much like to add the following to this section:
- - - - -
In contrast to scientific articles, ref tags are not placed immediately following the name of a scientist, but following the content that is referenced.
- Example: Humanistic psychologist Carl Rogers stated that the individual needed an environment that provided them with acceptance, empathy, and approval.[11]
- - - - -
The reason is that in more and more articles (anyway, the ones that I see) the ref tags are put immediately behind the name, just as in scientific articles. The problem is that is becomes unclear where the referenced content finishes and the unreferenced content starts.
For instance, "Rogers[11] stated that the individual needed love. Love is the most important need for a human being. Without love, people can get depressed."
In this case, there is no way to know where Rogers statements finish, and the editor's opinion starts. I would like to point this out to some editors and be able to refer to the manual of style. So that's why I wrote this extra example. Lova Falk talk 08:03, 29 September 2012 (UTC)
- Too specific, and ambiguous. My impression is that by "scientific articles" you mean "articles in scientific journals, as opposed to articles in wikipedia", many of which are scientific articles. Just say references follow the facts they are referencing. If a specific editor is violating that you can {{welcome}} (subst:welcome) them and point that out. Apteva (talk) 18:22, 29 September 2012 (UTC)
- Added a section to Wikipedia:Simplified Manual of Style, though to help avoid this happening. Apteva (talk) 18:59, 29 September 2012 (UTC)
- It's a WP:CITEVAR issue. If the editors at the article in question want to use that style, they're permitted to. Your only recourse is to gently talk them out of it. WhatamIdoing (talk) 21:00, 3 October 2012 (UTC)
- I agree with WhatamIdoing. Suppose the Harvard style is being used. Then you would get something like "Rogers (2009) stated that the individual needed love. Love is the most important need for a human being. Without love, people can get depressed" (where "Rogers (2009)" would be linked). This style is perfectly acceptable in Wikipedia, but doesn't correspond to the advice that "references follow the facts they are referencing". Peter coxhead (talk) 10:56, 4 October 2012 (UTC)
- But how would we know where Rogers' statement finishes? If it is Rogers who thinks that people can get depressed or an editor who thinks so???? Lova Falk talk 17:25, 5 October 2012 (UTC)
- Which is why that style is rarely used - but as pointed out it is still a valid reference style. I am guessing that someone could find an FA that uses it - throughout. Apteva (talk) 07:05, 10 October 2012 (UTC)
- But how would we know where Rogers' statement finishes? If it is Rogers who thinks that people can get depressed or an editor who thinks so???? Lova Falk talk 17:25, 5 October 2012 (UTC)
- I agree with WhatamIdoing. Suppose the Harvard style is being used. Then you would get something like "Rogers (2009) stated that the individual needed love. Love is the most important need for a human being. Without love, people can get depressed" (where "Rogers (2009)" would be linked). This style is perfectly acceptable in Wikipedia, but doesn't correspond to the advice that "references follow the facts they are referencing". Peter coxhead (talk) 10:56, 4 October 2012 (UTC)
Maths styling and readability
I want to make a case for including, as a style guideline, that all math using symbols other then the basic arithmetic symbols, be 'transcripted' into ordinary language. I don't mean that the math be replaced by ordinary language descriptions, but that displayed math have accompanying text that reads as if the math were being spoken. The case is very simple:
1) There is a huge problem of innumeracy in the general public, even among very intelligent people.
2) Part of this problem has nothing to do with the difficulty of understanding relations of quantity and so forth, but a simple inability to *read* math. Often people's eyes glaze over at the appearance of math because they simply cannot associate any sounds or meanings to the symbols.
3) I realize that the meaning and often the pronunciation of various symbols is covered in specific entries about the symbols but... a) This is not universally the case. There are symbols without specific entries, and those that have them require either the symbol itself or its name to be found. b) Math symbols are often displayed as graphic images, thus the symbols cannot be individually selected, linked or searched unless one already knows the name of the symbol. c) People are reluctant to search lists and read about symbols when they just want to grasp the basic concept the math is expressing. Instead, they go away thinking, "this is not for me..."
4) An alternate possible solution would be to include a list of every symbol used on a page with a link to the specific entry for each, perhaps in a sidebar. But this solution is inferior because: a) Symbols often have context dependent readings. For example '—>' may read 'implies' or it may read 'goes to' or 'maps to' etc. Disambiguation has to occur in context. b) Even in the same context different mathematicians will sometimes read expressions differently. There is no one canonically correct reading for many math expressions. c) It requires people to leave the page and come back, perhaps without the information they sought. d) It is a little like telling people, "learn the math before reading this". But in some cases that is exactly why they are here... trying to learn the math!
5) The problems of reading math expressions and understanding them are related but separate problems. In some cases one does need to "learn the math" before understanding, but there are numerous cases where simply being able to read the expression conveys sufficient information to result in a satisfactory understanding of the article, including the unfamiliar math.
6) For the same reason we don't encourage highly technical articles laced with specialist jargon. The function of an encyclopedia is to transfer specialized knowledge to a general audience. We don't allow foreign language quotations to go untranslated. We oughtn't allow math expressions to remain impenetrable.
68.80.134.156 (talk) 16:52, 3 October 2012 (UTC) (sorry, thought I was logged in) Baon (talk) 17:00, 3 October 2012 (UTC)
- I think that means that at Maxwell's equations#Equations (SI units), for example,
becomes something like (this is surely wrong; I didn't bother to look anything up because the details don't matter) the dot product of the electric field with the infinitesimal change in the surface, integrated over an infinitesimal change in the volume, is equal to the electric charge of the volume divided by the electrical constant. If that is your idea, I think that is harder to understand than the equation. The article's preceding paragraphs explain the equations to some extent. The Simple English equivalent is harder to understand, not easier (perhaps because my editing over there is frustrated by the "science not babytalk" faction) because it "simplified" mainly by omitting the verbal explanation. So how would you write that? And do you really think editors would even read any further nagging about readability?Art LaPella (talk) 20:33, 3 October 2012 (UTC)
- Yes! I think that's much more useful. Let me stress again that I am not advocating this as a replacement for the equation. I can at least look up "the dot product" and I know what an infinitesimal change is and what an electric field is (and could look them up if I didn't). I can't even look up a circle with two kind-of-extended "f"s (or perhaps "s"s) drawn vertically through it and two greek subscripts that I may or may not be able to name. Looking at the equation only, I don't even know that infinitesimals are involved. But perhaps you are trying too hard to deliver the meaning of the equation. That is labor the reader must undertake. I notice your code uses the term 'partial omega' for the subscript, and if I look up "dot product" the wiki page nowhere has the circle with two function signs drawn through it. So this must be "<something>subscript partial omega". What I am asking for is what you would say if you were reading the text aloud to a companion who's comprehension of the meaning of the math was not an issue. How do you read it to yourself? Do you just say to yourself, "oh, Maxwell's equation" and then substitute your understanding of the meaning without ever referring to the symbols themselves? The explanation of the meaning must be something else again, and stand apart. For instance, I might read a differential as, "dxdt" or as "dx over dt" or as "delta x delta t". There is not one "right way" to do it. I might be reduced to "d times x divided by d times t..." and I may have no clue what it means, but at least it can be read. I am looking for analogues of readings like, "the definite integral from a to b of y with respect to x...", or "take the integral from t-nought to t...".
- As for the problems of getting consensus and editor resistance or push back... those are real problems I don't want to minimize. I think it is a matter of lobbying for the usefulness of it. Along with reminders of the purpose of an encyclopedia.. it is not to glory in one's superiority or have conversations with one's peers. I agree with the no babytalk guideline. I am not suggesting talking down to anyone. Merely providing additional verbal information that some (I think many) people would find useful. If done properly, it should not interfere with readability, but enhance it for most people. Those who see it as an unnecessary crutch can skip over it. That is not ideal, but it is, I think, preferable to skipping over the math itself, which many people currently do. In any event, thank you for entertaining the idea. Obviously it will not be an easy sell to math editors, who are the least likely to perceive a need for it, and who have much invested in their own math competency, unless they are also zealous educators. Baon (talk) 23:42, 3 October 2012 (UTC)
- P.S. I looked at the SI units page you link to above. It is very good; very clean. The table provided on the symbols and notation is great! But consider a simple example: Is this "the dot product of the divergence operator and" or "the divergence of" or "divergence times..." All the above? None of the above? Uneducated, I read "the funny down pointing triangle that is the divergence operator, not delta followed by a dot that probably means multiplication". I want to know how it is commonly read. Then I can worry about its function in the equation. We have difficulty associating meaning to symbols we can't name, I think. Baon (talk) 00:36, 4 October 2012 (UTC)
- I agree that Wikipedian editors are more driven by vanity than helpfulness, but there is no easy solution without paying them. If readers don't at least recognize that the surface integral symbol (I found the explanation in the table) is some kind of integral, then are we really doing them a favor by inviting them to look up dot product, divergence etc.? This is a physics article. We have other articles that describe multi-variable calculus. So if we're leading them into a trap they won't understand, then isn't "learn the math before reading this" more helpful? And even if a verbal description does more good than harm in this case, is that true of every case, such as the much simpler quadratic formula for instance? Or should we let editors use their discretion for individual articles? And even if we should have such verbal descriptions for all articles, what will another guideline accomplish that WP:JARGON isn't doing already, besides the familiar dangers of WP:CREEP? Most Wikipedians won't read it, and the ones who do will use it for edit wars as in the thread immediately after this one. Art LaPella (talk) 04:52, 4 October 2012 (UTC)
- Thanks again for engaging with me on this matter. I am coming around to your point of view. I have spent more time looking over the symbol lookup table, and I see that there is a column in the table for "reads as", which is pretty much what I was asking for. I can see the duplication of effort that would be entailed in making that part of every article. I guess my problem reduces to individual cases where a symbol is used that is not in the table... I started this train of thought after trying to read something on the "Affine transformations" page. I have looked at the source.. The symbol is 'varphi' and I was able to look it up. I found the page on phi discusses this. It is a varient font form of phi, found mostly in older fonts, and is deprecated for mathematics. I am content to address this on the Affine transformations page, and take it as an isolated instance. I may add it to the symbol table with a note, so others will at least have a chance of seeing it there, if I can figure out how to do it. I still think there is a problem with symbol lookup... a kind of catch 22 where you need to know the name of the symbol in order to be able to look it up efficiently. And most users won't go to the page source to read the markup. (I didn't think of it myself, initially.) But I can see my suggestion is not really a good fix to those problems. Baon (talk) 16:11, 4 October 2012 (UTC)
- Just a note here — Baon appears to have misinterpreted a remark in the phi article. There is nothing "deprecated" about . It is a perfectly normal mathematical symbol and is used quite regularly. --Trovatore (talk) 22:02, 10 October 2012 (UTC)
- Thanks again for engaging with me on this matter. I am coming around to your point of view. I have spent more time looking over the symbol lookup table, and I see that there is a column in the table for "reads as", which is pretty much what I was asking for. I can see the duplication of effort that would be entailed in making that part of every article. I guess my problem reduces to individual cases where a symbol is used that is not in the table... I started this train of thought after trying to read something on the "Affine transformations" page. I have looked at the source.. The symbol is 'varphi' and I was able to look it up. I found the page on phi discusses this. It is a varient font form of phi, found mostly in older fonts, and is deprecated for mathematics. I am content to address this on the Affine transformations page, and take it as an isolated instance. I may add it to the symbol table with a note, so others will at least have a chance of seeing it there, if I can figure out how to do it. I still think there is a problem with symbol lookup... a kind of catch 22 where you need to know the name of the symbol in order to be able to look it up efficiently. And most users won't go to the page source to read the markup. (I didn't think of it myself, initially.) But I can see my suggestion is not really a good fix to those problems. Baon (talk) 16:11, 4 October 2012 (UTC)
- Only four articles are listed at Wikipedia:Spoken articles#Mathematics (version of 22:15, 4 October 2012).
- —Wavelength (talk) 21:39, 10 October 2012 (UTC)
- A discussion about pronouncing mathematical symbols is at Learning math? | Lambda the Ultimate.
- —Wavelength (talk) 16:20, 11 October 2012 (UTC)
- If you visit the Unicode code chart index at Code Charts, and scroll down to the heading "Symbols and Punctuation", and find the subheading "Mathematical Symbols", you can select thereunder a sub-subheading or a sub-sub-subheading. For example, you can select "Supplemental Mathematical Operators", which is linked to http://www.unicode.org/charts/PDF/U2A00.pdf.
- There, below the table with a width of 16 cells, the symbols are listed, preceded by their respective hexadecimal encodings and followed by their respective official Unicode names. For example, the symbol ⨀ is encoded hexadecimally as 2A00 (
⨀
produces ⨀) and has the name "N-ARY CIRCLED DOT OPERATOR". - By reference to the names of symbols in these pages, at least in theory a person can read a mathematical formula without necessarily understanding what they mean. In some respects, the process is similar to reading a passage orally, and spelling orally an unfamiliar word whose pronunciation one does not know or can not articulate.
- —Wavelength (talk) 16:20, 11 October 2012 (UTC)
Spaced vs unspaced em dash
A certain well-intentioned user named Hydrargyrum keeps replacing unspaced em dashes in hundreds of Wikipedia articles with spaced em dashes (preceded by a non-breaking space). This is contrary to WP:DASH; still, Hydrargyrum maintains that his is the correct way because he has "completed a typing course". I recognise that there is no single way of using em dashes: The Chicago Manual of Style and the Oxford Guide to Style, for example, recommend unspaced em dashes while AP Stylebook and a few others propose that these be spaced. However, WP:Manual of Style has expressly stipulated that em dashes should not be spaced on Wikipedia. The above user argues that "the information at WP:DASH was developed by incompetent individuals operating in an information vacuum, who apparently never took a course in typing, nor are they familiar with how line wraps are handled in browsers and other software" (User_talk:Hydrargyrum#Em_dashes). What, if any, action should now be taken – either with regard to restraining Hydrargyrum or allowing other styles in WP:MOS? Thanks. kashmiri 22:48, 3 October 2012 (UTC)
- I ask such people to read User:Art LaPella/Because the guideline says so. If that doesn't work, others might try something more coercive. Art LaPella (talk) 23:29, 3 October 2012 (UTC)
- Thanks, good read, I posted the link, let's see. Little optimism remains: Hydrargyrum has been asked to stop changing dashes his way already several times in the last few months – to no effect. kashmiri 00:14, 4 October 2012 (UTC)
- Remember to advise a user (as I've done in this case) if you are going to discuss their behavior somewhere. —[AlanM1(talk)]— 04:30, 4 October 2012 (UTC)
- As often when it comes to style discussions, they seem rather overconfident that they are "right" and that everyone else, or any different punctuation style, is "wrong". The reality of course, as appears to have been pointed out to them, is that there are alternatives, which are simply a matter of choice - and that the most commonly seen and used alternatives in the real world for dashes in running prose are the unspaced emdash and the spaced endash. MOS happily allows either. Common sense and the MOS would both suggest an editor shouldn't be making mass changes between the two of them - let alone changing either to the rarely seen spaced emdash. Nor do I think there's much need to change the MOS to add that third option (and even if we did, changing to that format in individual cases from one of the other two would still be utterly pointless). N-HH talk/edits 09:28, 4 October 2012 (UTC)
- This is related to the internal consistency RfC in this same page. Some people take upon themselves to change hundreds of articles between two accepted styles in order to ensure consistency, and they refuse to take hints. The MOS needs to make really clear that this is not acceptable. If the MOS doesn't say this clearly then editors can't use the MOS to stop this sort of behaviour. --Enric Naval (talk) 09:39, 4 October 2012 (UTC)
- Not really related. This is about an editor who is changing to an unacceptable style (per the MOS). —[AlanM1(talk)]— 16:28, 4 October 2012 (UTC)
- I also find spaced emdashes preferable for setting off parentheticals. Unspaced emdashes give an unwarranted sense of connection between the two words they join; parentheticals, almost by definition, should more tightly group the words contained within them than to the words outside. Endashes, on the other hand, do not seem appropriate for parentheticals at all. I think if the MoS does not permit spaced emdashes for parentheticals, this should be changed. --Trovatore (talk) 03:39, 5 October 2012 (UTC)
- The editor appears to still be changing dashes in violation of the MoS, even though several editors have asked him to stop. I have given him a warning on his talk page. Let me know if I need to follow up on it. Cheers. Kaldari (talk) 20:58, 9 October 2012 (UTC)
- I also find spaced emdashes preferable for setting off parentheticals. Unspaced emdashes give an unwarranted sense of connection between the two words they join; parentheticals, almost by definition, should more tightly group the words contained within them than to the words outside. Endashes, on the other hand, do not seem appropriate for parentheticals at all. I think if the MoS does not permit spaced emdashes for parentheticals, this should be changed. --Trovatore (talk) 03:39, 5 October 2012 (UTC)
- Perhaps a modification of the guidelines in the MOS for use of the hyphen, en dash and em dash should be considered. There are technical reasons for doing so. By default, most browsers and text editors break text automatically after a hyphen (ASCII 45, HTML code -); I have never encountered one that doesn't, unless it is forced to display in "no-wrap" mode. This is not true of the en dash and em dash characters, however. Over the years I've encountered some software that breaks lines after these characters, but most don't. Instead, what one most often sees is a break before the en dash or em dash if it is unspaced, putting the dash in the first column of the next line. Although you will no doubt find examples in print publications where this occurs, this is generally considered bad practice in typography and typesetting. It slows down reading and comprehension. How wo
uld it feel if type
-setters interru
ted text at random places within words and used hyphens in rando
-m fashion? It would make reading such text much more time consuming, would it not? By forcing the hyphen or dash to be the last visible character before a line break, it prepares the reader's brain for what is to follow, requiring less mental effort on the reader's part.
Since we don't have any control over what browser software a visitor to Wikipedia will use, we cannot predict how that browser will handle all types of dash characters. Moreover, we don't know what type of display equipment a visitor will be using; it could range from sub-VGA to XVGA, so we can't predict where lines will end within the browser window. Moreover, not all users run their browsers maximized, so even on an XVGA display, they may be viewing Web content in a sub-VGA window. That being the case, how would you go about providing the best reading experience for the site visitor?
Since Wikipedia isn't a typesetting system, we have limited options in controlling where characters will appear in a given line of text. One way that we can control the position of en dashes and em dashes is to precede them with a non-breaking space ( or  ) and follow them with an normal space (ASCII 32, HTML code  ). This guarantees that a line break will not put those characters in in the first column of the following line. Another way of doing it is with zero-width spaces. There is a zero-width non-breaking Unicode character (⁠) and also a zero-width Unicode space character (​) that would allow en dashes and em dashes to appear unspaced, yet retain the desired control of where the line breaks.
Some have presented the argument that it doesn't matter whether one uses an en dash or an em dash. Indeed, one may find pathological examples in print where the typesetter has used en dashes in place of em dashes, particularly when text is arranged in narrow columns and an em dash might appear disproportionately wide. It's not good policy, however to do so in Web content. The technical reason for this again, we cannot predict what kind of hardware and software a Wikipedia visitor will be using. The reader may be using the default screen font, or due to "accessibility" requirements may be using a substitute font, something that one can do with most modern browsers. The hyphen, en dash and em dash can look confusingly similar, depending on the screen font. Hyphens are generally not offset by spaces, and when one uses an unspaced en dash or em dash in such a situation, it can lead to ambiguous interpretation of a line of text: Was the writer pausing and interjecting an incidental thought, or is that some strange compound word? By offsetting an en dash or em dash with spaces, it leaves no doubt in the reader's mind what the writer intended to convey.
If you enjoy abusing your readers, go ahead and insist that the present MOS must be followed without question. If, on the other hand, you care about your readers, consider what I've written here. — QuicksilverT @ 23:26, 9 October 2012 (UTC)
- Thank you for presenting your case on the proper page for it, not throughout Wikipedia. I have verified that a line break can occur before an unspaced em dash, and those who write rules here (not me; note that some people here write style manuals as their real life job, not (ahem!) as a lesser part of some other job) haven't discussed that issue, to my knowledge. And yes, an unspaced em dash could look like an unspaced hyphen depending on the font. Art LaPella (talk) 01:13, 10 October 2012 (UTC)
Modification to MOS:IDENTITY
A few weeks ago, there was a proposal at WP:VPP to modify the wording of MOS:IDENTITY, specifically Point 2; the archived discussion is here. It gained some traction, but it died down without any kind of resolution, so I want to raise it again. The specific change being sought is;
"Any person whose gender might be questioned should be referred to by the gendered nouns, pronouns, and possessive adjectives that reflect that person's gender at the time of notability as reflected within the prevalence of mainstream reliable sources. Identity changes thereafter should be dealt with chronologically but should always follow the conventions used with prevalence in mainstream sources."
Instead of copying over the rationale, the link to the archive shows Berean Hunter's rationale, and other examples are provided in the thread. If people think this would be better discussed elsewhere, that's fine, but since the waters at VPP have been tested this seems like the most logical place. The Blade of the Northern Lights (話して下さい) 17:49, 4 October 2012 (UTC)
- I made a similar proposal back in May here. I agree with Blade that we need to follow what mainstream sources say rather than get ahead of these sources by making a judgment based on an individual's statements. GabrielF (talk) 18:11, 4 October 2012 (UTC)
- Does this mean we'll have to change Template:MOS-TW?? Georgia guy (talk) 18:40, 4 October 2012 (UTC)
- Yeah, it would. The Blade of the Northern Lights (話して下さい) 18:46, 4 October 2012 (UTC)
- What would the template's words have to change to?? Georgia guy (talk) 18:48, 4 October 2012 (UTC)
- Hadn't thought about it... that'll obviously need some work. The Blade of the Northern Lights (話して下さい) 18:55, 4 October 2012 (UTC)
- What would the template's words have to change to?? Georgia guy (talk) 18:48, 4 October 2012 (UTC)
- Yeah, it would. The Blade of the Northern Lights (話して下さい) 18:46, 4 October 2012 (UTC)
- Does this mean we'll have to change Template:MOS-TW?? Georgia guy (talk) 18:40, 4 October 2012 (UTC)
Can you clear up the exact meaning of this proposed rule?? Is it any similar to the following:
Trans women who are notable for being trans women should be referred to as she/her. However, trans women notable primarily for an event before the operation of surgery for a reason that has nothing to do with being transsexual should be referred to as he/him as if they were cisgender men. Georgia guy (talk) 22:29, 4 October 2012 (UTC)
- Almost. The first sentence is right, but the idea is to refer to, say, Laura Jane Grace as "he" when he was identifying as Tom Gabel and "she" after coming out in public as a she. Make sense? The Blade of the Northern Lights (話して下さい) 00:10, 5 October 2012 (UTC)
- You mean, we should assume that trans women actually were men, not women trapped in men's bodies, before the operation?? Georgia guy (talk) 00:13, 5 October 2012 (UTC)
- To couch it in less loaded, more policy-based language, it's to avoid outright misleading revisionist history such as ""she captained her tennis team at Horace Mann" (in the article on Renée Richards); specifics are in the linked VPP conversation. We at Wikipedia aren't here to play psychologists and pass judgment on whether or not they were really men or just women all along, we're here to report facts; in the cases of Grace and Richards, among others, they were notable under different names and sexes and our articles should reflect that. And this also works the other way too; the article on Andreas Krieger should be treated the same (and as of writing is actually a good example of what I'm shooting for). The Blade of the Northern Lights (話して下さい) 01:34, 5 October 2012 (UTC)
- Notable under different names and sexes?? This phrase actually does imply the statement I was asking above whether we should assume. Georgia guy (talk) 19:14, 10 October 2012 (UTC)
- The sex the person was commonly believed to be at the time. I think this is a slam-dunk. We do not — we must not — take a position on whether a person's "real" sex is. The choice to retroactively apply a sex change to previous notable events is nothing short of advocacy of a particular point of view; it must stop. --Trovatore (talk) 20:02, 10 October 2012 (UTC)
- Notable under different names and sexes?? This phrase actually does imply the statement I was asking above whether we should assume. Georgia guy (talk) 19:14, 10 October 2012 (UTC)
- To couch it in less loaded, more policy-based language, it's to avoid outright misleading revisionist history such as ""she captained her tennis team at Horace Mann" (in the article on Renée Richards); specifics are in the linked VPP conversation. We at Wikipedia aren't here to play psychologists and pass judgment on whether or not they were really men or just women all along, we're here to report facts; in the cases of Grace and Richards, among others, they were notable under different names and sexes and our articles should reflect that. And this also works the other way too; the article on Andreas Krieger should be treated the same (and as of writing is actually a good example of what I'm shooting for). The Blade of the Northern Lights (話して下さい) 01:34, 5 October 2012 (UTC)
- You mean, we should assume that trans women actually were men, not women trapped in men's bodies, before the operation?? Georgia guy (talk) 00:13, 5 October 2012 (UTC)
This section can be archived, just like any section of a talk page. I remember from 2004-2006 the "Georgia moving poll" which was wasn't archived for a long time. (It was at Talk:Georgia; now it's in an archive.) Can we put this discussion in a similar area so that it won't be archived too quickly?? Georgia guy (talk) 17:00, 11 October 2012 (UTC)
"a" vs "an"
The word designating the unity of single items (as in the example sentences "one is a number" and "Moses made an appeal") takes variably the forms "a" and "an".
The Guide does not give guidance on the correct, or recommended, use; such guidance is needed. — Preceding unsigned comment added by 90.198.109.2 (talk) 02:54, 5 October 2012 (UTC) −
- Should we also indicate that declarative sentences end with periods? I'm all for a comprehensive MoS, but that seems like overkill. The Blade of the Northern Lights (話して下さい) 02:59, 5 October 2012 (UTC)
- I'm with TBOTL on this one. Manuals of style aren't comprehensive dictionaries or grammar guides. The MOS presumes a working knowledge of the English language, and generally only covers topics which may either be a) unclear or b) in dispute. The use of "a" and "an" is pretty straightforward and unambiguous in nearly all cases (except a few words which vary by dialect, such as "historical", which should be covered by WP:ENGVAR in any case). --Jayron32 03:04, 5 October 2012 (UTC)
- English articles#Distinction between a and an covers this issue – no need to duplicate it (or the many other rules that make up English grammar). —[AlanM1(talk)]— 20:59, 5 October 2012 (UTC)
- Putting a link to the article in the sentence might be good enough for now. Contributor, have you ever seen anyone on Wikipedia misusing a and an in a way that a MoS rule would fix? Because if nothing's broken... Darkfrog24 (talk) 01:10, 6 October 2012 (UTC)
Disclaimer
Are there any guidelines on how to include disclaimers in articles? In a separate section or a footnote, at the start/end of the article,...? I am preparing an article here and would like to add a disclaimer "section/paragraph" saying roughly the following: Most of what is known about the rebellion including the exact dates are due to a single historical source, the Shoku Nihongi. [...some critical discussion on the reliability of this source...] All exact dates in this wikipedia article should therefore be taken with a grain of salt in view of their origin. bamse (talk) 09:00, 5 October 2012 (UTC)
- There's WP:No disclaimers in articles, which should handle it. I'll have a look at your draft, but what you want to do is include somewhere in the article itself that the dates aren't certain; same thing we do with Ramanuja's purported age. The Blade of the Northern Lights (話して下さい) 17:21, 5 October 2012 (UTC)
- Thanks. So a separate section titled: "Historical source" or something like it would be fine? Should that go to the beginning or end of the article, or it does not matter? bamse (talk) 11:20, 6 October 2012 (UTC)
- Probably the first paragraph after the lede section; that's what I've seen in most articles. However, if it fits better somewhere else (c.f. Old Tom Parr), go with wherever that is. The Blade of the Northern Lights (話して下さい) 03:33, 7 October 2012 (UTC)
- Thanks. bamse (talk) 09:08, 7 October 2012 (UTC)
- Probably the first paragraph after the lede section; that's what I've seen in most articles. However, if it fits better somewhere else (c.f. Old Tom Parr), go with wherever that is. The Blade of the Northern Lights (話して下さい) 03:33, 7 October 2012 (UTC)
- Thanks. So a separate section titled: "Historical source" or something like it would be fine? Should that go to the beginning or end of the article, or it does not matter? bamse (talk) 11:20, 6 October 2012 (UTC)
MOSQUOTE vs PERCENT
WP:MOSQUOTE reads "a few purely typographical elements of quoted text should be adapted to English Wikipedia's conventions without comment" and later "Spaces before punctuation such as periods and colons: these should be removed as alien to modern English-language publishing.". In to my opinion this includes and percent numbers. For instance if a quote includes something like "15 %" it should be changed to "15%" per WP:PERCENT. Am I right? -- Magioladitis (talk) 08:30, 6 October 2012 (UTC)
- I would consider this a minor typographic change that does not involve any qualitative change to the underlying quote. -- Ohconfucius ping / poke 10:19, 6 October 2012 (UTC)
- It can also be considered as conversion to house-style. -- Magioladitis (talk) 10:46, 6 October 2012 (UTC)
- (As the editor who raised the altering of the citation
quote=
with Magioladitis) I'd be happy to see WP:PERCENT linked in WP:MOSQUOTE under the list of minor typographic changes, and preferably for WP:MOSQUOTE to explicitly make a statement on citationquote=
applicability. The general altering of citations literals intitle=
andquote=
by semi-automated/WP:MEATBOT methods can be problematic though, as can be seen by the examples in [41]. —Sladen (talk) 11:35, 6 October 2012 (UTC)
- (As the editor who raised the altering of the citation
- "Spacing in quotes can be altered to comply with WP:PERCENT and WP:TIME" would be suffice? -- Magioladitis (talk) 12:05, 6 October 2012 (UTC)
- "WP:TIME" might be too broad as it includes date-reformatting. Perhaps the test would be whether a reformatting change would prevent the locating of the original citation; so removing a space in "15 %" to get "15%" probably doesn't impair locating of a source much; but renaming the
title=
of a work from "25 October - The Romanian Armed Forces' Day" to "October 25 - The Romanian Armed Forces' Day" significantly changes the ability to find that work by that name in an alphabetical card index, or Google. The second paragraph of following WP:TIME shortlinks talks about date reformatting, so perhaps that is possibly too broad. Perhaps the simplest would be to encourage quotation reformatting when used in the main body of an article, but even to go as far as to discourage reformatting within the{{reflist}}
as the references aren't there to be read, but are there to allow the reader to locate additional reliable information easily. This would allow cases where a reformatted quotation is used inline, but the "raw material" is left untouched in thequote=
. It could even be suggested that in the case of extensive reformatting of a quotation in the body, that the original can be preserved in the{{cite}}
for clarity. —Sladen (talk) 15:54, 6 October 2012 (UTC) - Ah yes, You are right. I only meant the addition of non breaking space in 12-hour time. And In general I am referring only to addition/removal of whitespace. -- Magioladitis (talk) 16:11, 6 October 2012 (UTC)
- Since you say "Spacing in quotes" I think it is perfectly fine, and the dates stuff is not relevant. Rich Farmbrough, 22:12, 6 October 2012 (UTC).
- Please do correct the space. And commas reversed with periods in numbers, as the continental Europeans do, and currency symbols after and spaced rather than before and unspaced. Tony (talk) 03:45, 8 October 2012 (UTC)
- I disagree with making changes inside quotations. For what purpose? The advice of changing curly quotes with straight quotes and single quotes is fine, but spaces? Why? And "commas reversed with periods"? There is nothing wrong with that style, no matter how strange it may look. If the quote is really wrong [sic] can be used, but it should not be changed. Apteva (talk) 04:56, 10 October 2012 (UTC)
- So no, "Spacing in quotes can be altered to comply with WP:PERCENT and WP:TIME" should not be added for two reasons - it is bad advice and it adds nothing to the MOS. If it said "spacing in quotes can not be altered" that would be one thing, but of course spaces are sometimes altered. Saying that something "can be altered" says nothing. It implies that they can also not be altered, and if someone alters them they might have done it appropriately or might not have. So what good is it? None at all. Apteva (talk) 05:03, 10 October 2012 (UTC)
- Please do correct the space. And commas reversed with periods in numbers, as the continental Europeans do, and currency symbols after and spaced rather than before and unspaced. Tony (talk) 03:45, 8 October 2012 (UTC)
- "WP:TIME" might be too broad as it includes date-reformatting. Perhaps the test would be whether a reformatting change would prevent the locating of the original citation; so removing a space in "15 %" to get "15%" probably doesn't impair locating of a source much; but renaming the
RFC: shall changes in beginning of sentence case be allowed in quotations?
See Wikipedia talk:Manual of Style/Archive 130#RFC: shall changes in beginning of sentence case be allowed in quotations? for a post archive closure of the RFC. Apteva (talk) 03:42, 8 October 2012 (UTC) NB: The closure was done here:[42] before the archive was moved. Apteva (talk) 03:54, 8 October 2012 (UTC)
"Adaptations of The Thing" vs "The Thing (adaptations)"
Where in MOS is this discussed? I notice that there is Adaptations of The Wizard of Oz, and until a few moments ago, The Phantom of the Opera (adaptations), when it was moved to Adaptations of The Phantom of the Opera. I prefer the "Thing (adaptations)" form, because it puts the modifier last, and the name of the work first, which is of greater importance to the reader, the author, and us, IMHO. Modifier-last conforms with:
- Thing (film)
- Thing (novel)
- Thing (1987 album)
That is, the various instances or forms of a work are always parenthesized. I argue that "(adaptations)" is a superclass of instances of a work on Wikipedia, rather than an extant subject to which the works themselves are subservient. Yet somehow a creeping, "standard" has been put forth, and is being acted upon en masse, solely by User:Neelix Contributions. Discuss? --Lexein (talk) 16:40, 9 October 2012 (UTC)
- Modifier-last is used when the "correct" title cannot be used. In this case, an article listing adaptations of The Thing could not be correctly titled "The Thing", so Adaptations of The Thing (or List of adaptations of The Thing) would be correct. An article on the 1987 album would be titled "The Thing", except that it's not the primary topic for that title, so a parenthetical qualifier is tacked on to the title. -- JHunterJ (talk) 17:06, 9 October 2012 (UTC)
- Yes, Neelix linked Wikipedia:Article titles#Article title format. Trimmed too much over time, now lacking enough rationale to answer my concerns, and a rationale stretched quite thin when applied to plurals, IMHO. See discussion (my viewpoint, anyways) back at the bottom of User talk:Neelix. Reopen here if you see fit. --Lexein (talk) 18:18, 9 October 2012 (UTC)
- Reopen what here? Your question as to why the qualifier isn't needed here? -- JHunterJ (talk) 18:34, 9 October 2012 (UTC)
- This is not a MOS issue, but a title issue. I recommend discussing either on the talk page of the article or at Wikipedia talk:Article titles Apteva (talk) 00:12, 10 October 2012 (UTC)
- Well, that's unexpected. I would have thought WP:Article titles was moved out of MOS for space reasons, not for "not MOS". No? --Lexein (talk) 04:52, 10 October 2012 (UTC)
- The farther I dig into the history of "don't imply subsidiary articles" or words to that effect, the less I find. It started out as partially a technical issue (old server software would literally create subpages if a slash was in the title). Over time, the explanation and rationale has been trimmed, and its application expanded to include parentheticals, to the point that it's a nearly empty imperative, without rationale. It's depressing. At some point, I had hoped to see discussion, consensus, or precedent mentioned, but nothing so far, using Wikiblame. In case anyone wondered, that's what I've been doing in spare moments, all day.
- And yes, I'm starting to think that policies and guidelines should also have inline citations, linking to their origin discussion & consensus, precedent in other encyclopedias, or to an external manual of style, just to prevent the kind of endless spelunking I'm now forced into, just because a policy doesn't seem to make prima facie sense.--Lexein (talk) 04:52, 10 October 2012 (UTC)
- Yes, Neelix linked Wikipedia:Article titles#Article title format. Trimmed too much over time, now lacking enough rationale to answer my concerns, and a rationale stretched quite thin when applied to plurals, IMHO. See discussion (my viewpoint, anyways) back at the bottom of User talk:Neelix. Reopen here if you see fit. --Lexein (talk) 18:18, 9 October 2012 (UTC)
- Wikipedia:Manual of Style/Register is a similar idea, though far from completion. Art LaPella (talk) 05:21, 10 October 2012 (UTC)
- I see no reason for documenting changes other than is already available from the history. The basic principle of WP is that it does not matter who or why or when someone adds something as long as it is correct. In article space everything needs a reliable source, and because of the need for verifiability, needs a reference. In WP space everything only needs to make sense, and if not, that is what talk pages are for. Adding references is helpful in some cases, but in most cases they are not needed. That is what articles are for. Apteva (talk) 07:01, 10 October 2012 (UTC)
- No one's forcing you into spelunking. The distinction given above between titles and their qualifiers makes prima facie sense. -- JHunterJ (talk) 10:53, 10 October 2012 (UTC)
- Agreed. It is a detriment to the project to use parenthetical disambiguators to distinguish articles from their parent articles, both because parenthetical disambiguators have a well-established, disparate purpose and because subtopics by definition represent only a portion of the scope of the term indicated thereby. Neelix (talk) 14:42, 11 October 2012 (UTC)
- Wikipedia:Manual of Style/Register is a similar idea, though far from completion. Art LaPella (talk) 05:21, 10 October 2012 (UTC)
Article titles
This sentence
- "The Manual of Style applies to all parts of an article, including the title. See especially punctuation, below. (The policy page Wikipedia:Article titles does not determine punctuation.)"
is, to put it mildly, absurd. Policies always trump guidelines, but policies do not specify everything, that is what guidelines and common sense are for, but to say that a guideline determines punctuation of an article title is not possible, and has created the absurdity of thinking that Mexican-American War should be called "Mexican–American War" (with an endash instead of a hyphen) just because if it was not a proper noun it would be spelled with an endash. Well it is a proper noun and it is spelled with a hyphen. But really, the idea that a guideline can say that a policy does not apply is completely absurd. Which is anyone going to follow, the policy or the guideline? The policy every time. Now if it was the other way around, if a policy felt a need to say, but please ignore such and such a guideline, never mind how absurd that is, that would work, because the policy gets precedence over the guideline. Just my two cents worth. I recommend deleting the entire sentence as absurd. Apteva (talk) 02:23, 10 October 2012 (UTC)
- I lost you between "policies do not specify everything, that is what guidelines and common sense are for" and "to say that a guideline determines punctuation of an article title is not possible ... Which is anyone going to follow, the policy or the guideline? The policy every time." Distinction without a difference? Art LaPella (talk) 03:40, 10 October 2012 (UTC)
- The only word between those two quotes is "but", an unusual place to get lost. I am having a hard time figuring out what is being asked. The only question at hand is, should the above sentence be removed? Arguments for or against need to be couched not on the clarity or lack thereof of my summary of the issue, but on the merits of the sentence being in the MOS. Apteva (talk) 03:57, 10 October 2012 (UTC)
- I meant that what comes before "but" seems to contradict what comes after "but". If you recognize that policies do not specify everything, then why isn't title punctuation an example of something a policy wasn't intended to specify? Art LaPella (talk) 05:24, 10 October 2012 (UTC)
- The point is that the MOS does not over ride the policy. If someone finds a policy reason for using punctuation in a certain manner, that is what will be used regardless of what the MOS says, but I have not found any examples of that being the case, hence clearly no reason for the sentence even being in the MOS. I think it is there because someone wants a ridiculous justification for the ridiculous conclusion that Mexican-American War should be spelled with an endash, even though no one does. It is nothing more than trying to make a WP:POINT, and a waste of all of our time. Apteva (talk) 06:47, 10 October 2012 (UTC)
- The bureaucratic answer is, in your own words, "policies do not specify everything". For example, if you read MOS:ITALICS (admittedly a guideline, but the same IAR logic applies) you might think Kyrie should be in quotes as a song, but WP:MUSIC says it's "generic" (at least the words aren't; the only words you can sing to Kyrie are "Kyrie ..." or a translation). OK, so only the music guideline covers that detail.
- The practical answer is that laughing off the Mexican–American War debate, one of the biggest debates we have ever had, is completely inconsistent with complaining about wasting time. Art LaPella (talk) 18:49, 10 October 2012 (UTC)
- The point is that the MOS does not over ride the policy. If someone finds a policy reason for using punctuation in a certain manner, that is what will be used regardless of what the MOS says, but I have not found any examples of that being the case, hence clearly no reason for the sentence even being in the MOS. I think it is there because someone wants a ridiculous justification for the ridiculous conclusion that Mexican-American War should be spelled with an endash, even though no one does. It is nothing more than trying to make a WP:POINT, and a waste of all of our time. Apteva (talk) 06:47, 10 October 2012 (UTC)
- I meant that what comes before "but" seems to contradict what comes after "but". If you recognize that policies do not specify everything, then why isn't title punctuation an example of something a policy wasn't intended to specify? Art LaPella (talk) 05:24, 10 October 2012 (UTC)
- The fact that WP:TITLE is a policy and WP:MOS a guideline shouldn't be given too much weight, as it's a bit of historical anomaly. Not much of what is in WP:TITLE can really be called policy, as it's most full of guidelines. Nevertheless, if there's a conflict between them, point it out and let's talk about it. Dicklyon (talk) 04:16, 10 October 2012 (UTC)
- I find the words guideline and policy to be carefully chosen and uniformly applied - and not just an accident. A great deal of discussion goes into which items should be a policy and which should be a guideline. Apteva (talk) 06:47, 10 October 2012 (UTC)
- They are more carefully chosen now than they used to be. Early on there were few debates (as most did not consider it an important distinction) for example WP:V was turned from a guideline into a policy with this edit (I suspect with no debate on the appropriate talk page) back in April 2005. Likewise what is now Article Title received its banner in 2005 with this edit but it had been in the "Category:Wikipedia official policy" since 2004 after being "One of Wikipedia's policies and guidelines" before that. Of course since then there have been intermittent debates on whether the central MOS page and AT should be a policies or guidelines and each time the status quo has been kept. To understand the reason for the sentence you have picked out you will have to read the talk page archives, and who was in favour of what. Personally as I have stated before (in April this year) that I am in favour of removing this sentence for similar reasons to those you have given. -- PBS (talk) 16:48, 10 October 2012 (UTC)
- This appears to be part of a campaign being carried out in multiple threads and multiple forums to reopen the n-dash wars that were settled in 2011. For example, see here [43] --Neotarf (talk) 20:02, 10 October 2012 (UTC)
- They are more carefully chosen now than they used to be. Early on there were few debates (as most did not consider it an important distinction) for example WP:V was turned from a guideline into a policy with this edit (I suspect with no debate on the appropriate talk page) back in April 2005. Likewise what is now Article Title received its banner in 2005 with this edit but it had been in the "Category:Wikipedia official policy" since 2004 after being "One of Wikipedia's policies and guidelines" before that. Of course since then there have been intermittent debates on whether the central MOS page and AT should be a policies or guidelines and each time the status quo has been kept. To understand the reason for the sentence you have picked out you will have to read the talk page archives, and who was in favour of what. Personally as I have stated before (in April this year) that I am in favour of removing this sentence for similar reasons to those you have given. -- PBS (talk) 16:48, 10 October 2012 (UTC)
- I find the words guideline and policy to be carefully chosen and uniformly applied - and not just an accident. A great deal of discussion goes into which items should be a policy and which should be a guideline. Apteva (talk) 06:47, 10 October 2012 (UTC)
- The only word between those two quotes is "but", an unusual place to get lost. I am having a hard time figuring out what is being asked. The only question at hand is, should the above sentence be removed? Arguments for or against need to be couched not on the clarity or lack thereof of my summary of the issue, but on the merits of the sentence being in the MOS. Apteva (talk) 03:57, 10 October 2012 (UTC)
- I lost you between "policies do not specify everything, that is what guidelines and common sense are for" and "to say that a guideline determines punctuation of an article title is not possible ... Which is anyone going to follow, the policy or the guideline? The policy every time." Distinction without a difference? Art LaPella (talk) 03:40, 10 October 2012 (UTC)
- I stayed away from the hypen/en dash thing, but given that it's being discussed here, I also find the en dash usage odd-looking. It's often at odds with what I would write and with what I see written elsewhere. I have no examples to hand as I've not collected any. But I do wonder about the origin (the sources) of the rules we adopted. SlimVirgin (talk) 23:04, 10 October 2012 (UTC)
- It is not the rules that are being questioned, but some of the examples used that do not follow those rules. The correct use of a hyphen, endash, and emdash is relatively subtle, but I think what we have is mostly correct - other than in at least three of the examples, and in at a minimum dozens of articles that were moved in 2011 to follow the "Mexican-American War" misspelling by using an endash. According to "New Hart's Rules", style guides only address issues where more than one style is perfectly acceptable in writing, such as using "co-operate" or "cooperate", both of which are implied as valid, but the book also uses the word "bemade" to mean "be made".
- I stayed away from the hypen/en dash thing, but given that it's being discussed here, I also find the en dash usage odd-looking. It's often at odds with what I would write and with what I see written elsewhere. I have no examples to hand as I've not collected any. But I do wonder about the origin (the sources) of the rules we adopted. SlimVirgin (talk) 23:04, 10 October 2012 (UTC)
- "No appeal need be made to stylistic conventions or record kept of them where text is incorrect". That would apply to names, of which it only says that names use hyphens. I think that point has been missed by the advocates of "Mexican-American War" spelled instead with an endash.
- On hyphens is says "If an author has consistently applied a scheme of hyphenation, an editor need not alter it, although a text littered with hyphens can look fussy and dated. Editors can find the dominant form of a particular compound in a suitable current dictionary such as the New Oxford Dictionary for Writers and Editors."
- There are examples where either a hyphen or an endash could be used: "Note that in US style an en rule is used to connect a prefix and a compound (the post–World War I period)." Implying that others would use "the post-World War I period" (with a hyphen instead of an endash). Apteva (talk) 00:41, 11 October 2012 (UTC)