This is an old revision of this page, as edited by MiszaBot II (talk | contribs) at 06:51, 10 September 2013 (Robot: Archiving 1 thread (older than 14d) to Misplaced Pages talk:Verifiability/Archive 61.). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Revision as of 06:51, 10 September 2013 by MiszaBot II (talk | contribs) (Robot: Archiving 1 thread (older than 14d) to Misplaced Pages talk:Verifiability/Archive 61.)(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)| This is the talk page for discussing improvements to the Verifiability page. |
|
 | This page is not a forum for general discussion about "verifiability" as a concept. Any such comments may be removed or refactored. Please limit discussion to improvement of this page. You may wish to ask factual questions about "verifiability" as a concept at the Reference desk. |
 view · edit Frequently asked questions
Questions
|
 | The project page associated with this talk page is an official policy on Misplaced Pages. Policies have wide acceptance among editors and are considered a standard for all users to follow. Please review policy editing recommendations before making any substantive change to this page. Always remember to keep cool when editing, and don't panic. |
 | See WP:PROPOSAL for Misplaced Pages's procedural policy on the creation of new guidelines and policies. See how to contribute to Misplaced Pages guidance for recommendations regarding the creation and updating of policy and guideline pages. |
| The Verifiability page is frequently reverted in good faith. Don't be offended if your edit is reverted: try it out on the Workshop page, then offer it for consensus here, before editing the actual project page. |
| There has been a great deal of discussion about the lead section of the verifiability policy over the years. If you want to discuss changing its wording, please first read the 2012 request for comments and the previous discussion about the first sentence. Thank you for your cooperation. |
 Archives |
|
Index 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 21, 22, 23, 24, 25, 26, 27, 28, 29, 30 31, 32, 33, 34, 35, 36, 37, 38, 39, 40 41, 42, 43, 44, 45, 46, 47, 48, 49, 50 51, 52, 53, 54, 55, 56, 57, 58, 59, 60 61, 62, 63, 64, 65, 66, 67, 68, 69, 70 71, 72, 73, 74, 75, 76, 77, 78, 79, 80 81, 82, 83 |
|
Archives by topic First sentence (Nov 2010–March 2011 |
|
This page has archives. Sections older than 14 days may be automatically archived by Lowercase sigmabot III when more than 1 section is present. |
Proposal for new policy
(This proposal was originally posted at Misplaced Pages talk:Policies and guidelines#Limitations of RS+NOR, with a solution, but I was asked to post it at WT:RS and WT:NOR, and, by implication, here.)
Limitations of RS+NOR+VERIFY, with a solution (Rev. 1):
The motivation for this discussion is my frequent annoyance over the years with articles that don't explain things well, or don't give enough information, because experts can't simply write what they know, due to NOR and the need for RS.
An example is Sailing faster than the wind, where section "BOLD EDIT NOTICE" of its Talk page presents an excellent explanation (the analogy of a geared transmission) that couldn't be included in the article due to NOR and lack of RS. I personally believe that this explanation is actually correct, making this a very nice example, but it doesn't actually matter if this explanation is correct or not, just as we can rarely be sure that any information in any article is complete and correct, even when lots of RS have been cited. And, while I'm providing this as a motivational example, I want to discuss WP policies and guidelines here, not details of this example.
Now to get to the proposal: reliance on the availability of good RSs leads to a good encyclopedia, but this technique has limitations. Once in a while a Talk page provides some OR explanation that is clearer that the explanation given in the article. This example, I believe, is such a case. While this isn't the purpose of a Talk page, it is a very valuable service for WP readers who read the Talk pages as well the articles, as I do.
It also shows an inherent limitation of the RS+NOR policies, as applied to articles. An improved WP policy, and the solution I'm offering for discussion here, would be to allow OR explanations or knowledge in articles and Talk pages, without a reference, until someone provides a good OR reason to object to them, or an RS is found that supports a good replacement. Note that this implies that the information added without RS must be uncontroversial. Any unresolved argument among editors cancels this new policy and falls back to requiring RSs.
This new policy also applies to the large percentage of (mostly old) articles that contain no references or insufficient references. That means that presumably correct information in these many articles cannot simply be deleted by any editor. There must be an objection to it, with the opportunity to discuss the deletion on the Talk page. This allows some protection for old yet correct information.
This would be an additional policy, modifying the RS, NOR, and VERIFY policies, or would be a modification of the RS, NOR, and VERIFY policies themselves (I'm not specifying which here).
In addition to the above, this proposal affects the VERIFY policy by requiring modification to explain the situations in which OR without RS will be allowed. These situations are explained above. I will be happy to provide explicit revisions to all affected policies if this discussion eventually results in agreement. David Spector (talk) 13:26, 18 August 2013 (UTC)
- Oppose: WP is intended for a general readership. Editors should not be placed in a position where they can be told that they can't remove unsourced information because someone allegedly versed in the technical areas covered by the article knows better than they do. I find it antithetical to existing WP policy to espouse a policy that renders unsourced and potentially unverifiable information inviolate. Editors have already faced difficult situations in some cases where they removed unsourced information, even information that had been challenged for months before they did anything more serious about it. If editors cannot or will not source information, especially information that has been challenged long-term, than they should not be able to prevent its removal by claiming nothing more than, "We know this is true and we don't think it's controversial." In fact, I think once information has been challenged it should effectively be considered controversial. Given that you say any unresolved argument among editors cancels this policy, does this not basically boil down to, "You must challenge the information via a method that does not involve its removal before you may proceed with removing it?" DonIago (talk) 16:51, 18 August 2013 (UTC)
- Oppose. Misplaced Pages is not an appropriate place for the publication of original research, regardless of whether other contributors think that it is 'uncontroversial'. This proposal radically alters the whole ethos of Misplaced Pages, and could only ever lead to a reduction in article quality. AndyTheGrump (talk) 17:12, 18 August 2013 (UTC)
- If a piece of OR really is absolutely uncontroversial (i.e. not "challenged or likely to be challenged") then in fact policy already allows this. What triggers the effect of policy is the act of disputing something (e.g. by changing or removing it). At that point we resolve the dispute by reference to sources. But if nobody challenges it and nobody is likely to challenge it, then whatever you've written can stand unchallenged forever. I would be opposed to altering the wording of the policy because it's unnecessary to achieve what you want.—S Marshall T/C 17:30, 18 August 2013 (UTC)
- This idea has also gotten a less than welcoming reception at the long discussion at Misplaced Pages talk:Identifying reliable sources. Nothing you have written changes the gist of my response: if you cannot find a cite to support adding content, then sorry -- out of luck on the Pedia -- or not enough work has been done to find the cite. The reason a source is important beyond the information itself, is because they serve an important function in vetting the information for its acceptance and reliability. Alanscottwalker (talk) 18:12, 18 August 2013 (UTC)
- Support - I understand the proposer to be introducing a new class of material - "Tutorial material" - material which is useful in Misplaced Pages, but comes under class (B) in
- Oppose – This is a recipe for disaster. The ban on original research is the main reason Misplaced Pages is such a useful resource and weakening it has to be done only with very great care. But no such care is visible here and no suitable proposed wording has been presented. Zero 23:34, 18 August 2013 (UTC)
- Oppose per Zero and Andy. This should not have been posted at the other talk page or even at this talk page. The suggestion on the other talk page was to post it here or at WP:VPP. For a change of this kind, VPP would be a better place. Why David thinks it's "too informal" is beyond me.--Bbb23 (talk) 23:47, 18 August 2013 (UTC)
- Oppose per BBB23. Misplaced Pages is not Citizendium. Indeed, WP would not even be as good as Citizendium because it would not have CD's equivalent of peer review. People who use Misplaced Pages need to be able to confirm what they read here and not have to depend on self-appointed experts. — TransporterMan (TALK) 00:05, 19 August 2013 (UTC)
- Lets look at an example - the editors the article Complex number introduced the subject with this example. I don't know if this example was the creation of the author in question or if (s)he copied it from a text book. In either respect, it is hardly cutting-edge science - any maths undergraduate can confirm that it is correct. Where does this stand in terms of WP:VER and of WP:OR? BTW, the page in question gets between 1000 and 2000 hits a day and is ranked at about 7000 in terms of numbers of visitors. Martinvl (talk) 00:27, 19 August 2013 (UTC)
- Without looking at the article, if anybody who understands the subject can tell you that the example is accurate, then it's fine. What we might need is a statement directly about the acceptability of giving obviously correct examples, comparisons, etc. We do have a small but dedicated number of editors who apparently believe that if it's not what the rest of us call plagiarism, then it's a NOR violation. I assume that this proposal is born out of long experience with such editors. WhatamIdoing (talk) 04:56, 19 August 2013 (UTC)
- I was going to provide a tldr reply, but I can't say it better than what Doniago said at 12:31, 19 August 2013, and Monty845 said at 13:42, 19 August 2013, both just below. — TransporterMan (TALK) 14:23, 19 August 2013 (UTC)
- Without looking at the article, if anybody who understands the subject can tell you that the example is accurate, then it's fine. What we might need is a statement directly about the acceptability of giving obviously correct examples, comparisons, etc. We do have a small but dedicated number of editors who apparently believe that if it's not what the rest of us call plagiarism, then it's a NOR violation. I assume that this proposal is born out of long experience with such editors. WhatamIdoing (talk) 04:56, 19 August 2013 (UTC)
- Lets look at an example - the editors the article Complex number introduced the subject with this example. I don't know if this example was the creation of the author in question or if (s)he copied it from a text book. In either respect, it is hardly cutting-edge science - any maths undergraduate can confirm that it is correct. Where does this stand in terms of WP:VER and of WP:OR? BTW, the page in question gets between 1000 and 2000 hits a day and is ranked at about 7000 in terms of numbers of visitors. Martinvl (talk) 00:27, 19 August 2013 (UTC)
- Oppose, but with some sympathy for the types of problems that I think are causing this proposal. The thing is that I think editing suggestions which put things nicely are either blocked by other editors because their is a controversial amount of non-obvious originality or else because of a misunderstanding of the policies we already have. As per WhatamIdoing, I can perhaps imagine that some wording tweaks in policy might be possible, but I think openly calling for originality will not work.--Andrew Lancaster (talk) 09:35, 19 August 2013 (UTC)
- A good deal of the problem is caused by the sentence "must be able to cite reliable, published sources that are directly related to the topic of the article, and directly support the material being presented". Editors who might not understand the subject often look for in-line citations when in fact they are not necessary, or when "being able to cite" material is a matter of the expert saying "Here is a list of text books, all of which discuss the subject. Which one do you want?". Martinvl (talk) 10:06, 19 August 2013 (UTC)
- This seems a bit misleading to me. In my experience the easiest way to resolve these situations, not to mention satisfy WP:BURDEN is to provide a source, not to get into a debate over the issue. An expert on the subject should be able to provide a source, and ideally should recognize that arguing over it wastes far more time and effort on the part of all parties. Why ask which source should be provided rather than simply choosing one and providing it? If the expert provides a source and the source itself is then challenged, then there's grounds for a more serious discussion of the matter.
- That said, I question the use of the term "expert" in any case. I certainly don't know who here is an expert on what subject matter, and unless there are procedures for official recognition of "expert" status on WP...if there are I've never seen it come up...then nobody should wield the "expert" stick because it should be abundantly obvious that anyone can claim they're an expert on anything without that actually being the case. DonIago (talk) 12:31, 19 August 2013 (UTC)
- Moral Support/Practical Oppose I wish there was a way for this to work, but as a practical matter, I just don't seen a standard to apply that gives more leeway then WP:Burden that wouldn't do more collateral damage then good. Requiring the opponent of inclusion to come up with a source to disprove something is simply unreasonable, if its hard to find a reference that provides a specific example, it will be far harder/impossible to find a reference that disproves it. What we really would need is editors to only invoke burden if they really do have a strong, good faith belief that the material is not accurate, and otherwise leave the material in. But the problem is that basing a decision on the subjective motive of an editor, rather an objective standard of what RS provides is just asking for Drama and baseless accusations of bad faith. I just don't see a way for the idea to work in practice. Monty845 13:42, 19 August 2013 (UTC)
- Support (sort of) This is an important problem which has caused Misplaced Pages to plateau out in several areas. But it really doesn't need a new policy. It just needs:
- An important tweak in current policy to bring the mechanics of the policy in line with (rather than conflicting with) the spirit defined by "challenged or likely to be challenged". So it would remain just as easy to knock out unsourced questioned material, but harder to knock out unquestioned material for bad reasons.
- Explanation (maybe a guideline) to kill some immensely rampant-in-Misplaced Pages destructive urban legends which have no basis in policy. Namely that verifiability is a force for inclusion rather than just a requirement for inclusion.
- Together these two would enable expertise in editing without weakening wp:ver North8000 (talk) 13:52, 19 August 2013 (UTC)
- Oppose At least, not here on WP. We have other projects where this might make sense and be more welcome, such as Wikiversity. WP cannot have a mechanism that could make this work without abandoning the principle of "anyone can edit", without which WP would die a slow and painful death. LeadSongDog come howl! 18:30, 19 August 2013 (UTC)
- I don't see where their proposal (vague as it is) would affect that. North8000 (talk) 11:48, 20 August 2013 (UTC)
- Oppose. An expert's unsourced opinion might (but not always!) be more reliable than some non-expert's citation of random sources, but the proposal says nothing about expert qualifications; this proposal would allow all kinds of junk from anyone that "knows" something to be true. If there is a problem regarding the scope an editor has in formulating examples (etc.) that should be discussed at NOR. ~ J. Johnson (JJ) (talk) 18:42, 22 August 2013 (UTC)
Thank you. I did not see any insurmountable objections to my proposal. Here are my responses to these responses. Interspersing them would interfere with their flow, so I've grouped them all here. Please feel free to continue the discussion. David Spector (talk) 17:16, 23 August 2013 (UTC)
- DonIago, "WP is intended for a general readership. Editors should not be placed in a position where they can be told that they can't remove unsourced information because someone allegedly versed in the technical areas covered by the article knows better than they do." WP is not all intended for a general readership, by your implied definition. Many of the mathematics articles simply cannot be understood by your general readers, because they may not be educated in that technical area. The same is true of physics, and many other topics. You may have misinterpreted my frequent use of the word expert. I don't mean it to refer to someone who is highly educated in some specialty. A person who has played with toys called Beyblades may only be a teenager, yet may be an expert in that subject. She may meaningfully contribute correct information about the toy's operation, even though no one can find a single RS corroborating that information. Assuming that the toy itself is NOTABLE, the new information improves WP coverage of it. My proposal would protect that information until either a source can be found, or someone else corrects it. My proposal helps WP to grow organically, as it is meant to do. "I find it antithetical to existing WP policy to espouse a policy that renders unsourced and potentially unverifiable information inviolate." My proposal shows confidence in the editors. This is a good thing, and follows WP principles. Also, you are actually incorrect. My proposal only protects information until it is challenged. As soon as it is challenged and the challenge seems to hold, my proposal no longer applies. "Editors have already faced difficult situations in some cases where they removed unsourced information, even information that had been challenged for months before they did anything more serious about it." I'm not sure what your point is here. Please explain. "If editors cannot or will not source information, especially information that has been challenged long-term, than they should not be able to prevent its removal by claiming nothing more than, "We know this is true and we don't think it's controversial." If you mean that one editor claims the change is controversial and another claims it isn't, then it's controversial and the proposed policy no longer applies. If one of the editors is unhappy with the resulting situation, they are free to make use of the existing mechanisms for resolving disputes about policy. "In fact, I think once information has been challenged it should effectively be considered controversial." Exactly, that's correct. "does this not basically boil down to, 'You must challenge the information via a method that does not involve its removal before you may proceed with removing it?'" Yes, that is part of the implication. The proposal delays removal until there is a reasonable challenge (a wild claim with no rationale by an IP editor would not be reasonable). The proposed policy provides explicit protection for information currently at the mercy of anyone to delete.
- AndyTheGrump, "Misplaced Pages is not an appropriate place for the publication of original research..." I agree. The proposal should not be interpreted as establishing WP as a place for first publication of academic research. However, if someone knows something valuable about a subject, that will improve understanding of it, something that ought to have an RS but for some reason does not yet seem to have one, this proposed policy would allow that "expert" to share her knowledge with us. The safety in doing so is that another "expert" can claim that this alleged knowledge is highly unlikely, and explain why. Such a reasoned response cancels "OR without RS" instantly. "This proposal radically alters the whole ethos of Misplaced Pages, and could only ever lead to a reduction in article quality." I'm not sure what "ethos" means, but could you explain how my proposal, in allowing experts to contribute, will always reduce article quality? That would seem to be a contradiction, since WP has always benefitted from experts in all fields.
- S Marshall, "If a piece of OR really is absolutely uncontroversial (i.e. not "challenged or likely to be challenged") then in fact policy already allows this." Sorry, no. WP:NOR forbids adding information known by the editor, no matter how sure the editor is. WP:RS forbids adding anything for which a RS cannot be found. "What triggers the effect of policy is the act of disputing something (e.g. by changing or removing it)." It may look that way, but it is not so. An editor is allowed to remove text when it violates policy--the editor is not permitted to "dispute" policy by doing removals of text anywhere she pleases. On the other hand, she is permitted to dispute any text on the Talk page for the article. "But if nobody challenges it and nobody is likely to challenge it, then whatever you've written can stand unchallenged forever." In practice, this is exactly what happens, especially in older articles. My proposal modifies policy to allow this common case. "I would be opposed to altering the wording of the policy because it's unnecessary to achieve what you want." Currently, anyone can delete up to 25% of WP, because is consists of statements having no references. And many of those statements are true, but there are no RSs that will support them. My proposal will achieve protection and a rationale for keeping all this valuable information in WP until corroboration (or dis-corroboration) is found.
- Alanscottwalker, "This idea has also gotten a less than welcoming reception at..." I have responded to all comments there, as here. So far, I have seen little true understanding of my proposal and no objection that could not be easily countered. I think my proposal is doing very well so far, considering the experience of the long-term editors who are contributing to this discusssion. "...if you cannot find a cite to support adding content, then sorry -- out of luck on the Pedia -- or not enough work has been done to find the cite." Yes, that is the current policy, you're simply repeating it. Repeating it doesn't argue for it. "The reason a source is important beyond the information itself, is because they serve an important function in vetting the information for its acceptance and reliability." I fully agree with you. RSs are the cornerstone of the integrity and reliability of WP, such as it has. However, the reality is that 25% (or whatever) of WP consists of old articles that have no RSs at all. You can ignore them, but they're there. They are tolerated because deleting them would empoverish WP. Full enforcement of your statement would ruin WP. And, besides that, allowing better and more intuitive explanations in articles (my primary example) would clearly improve WP.
- Martinvl, I appreciate your proposal, which weakens mine so that it only applies to certain articles. I reject that. My proposal should apply to all articles, allowing people who know to contribute what they know, even when RSs cannot easily be found.
- Zero, I agree that WP should not be used to present major new research or new ideas. Yet I want to protect probably-true information and useful explanations. I believe I have done so using language that respects the importance of the NOR policy. If you can offer "suitable wording" to clarify this distinction, I would undoubtedly accept it.
- Bbb23, Please explain why a proposed change in three policies should not be presented on their Talk pages, or on the Talk page for all the policies and guidelines, for that matter. It's not obvious to me. WT pages are for discussion of WP articles. I felt that Village Pump would not be the place for this discussion, but I'm willing to move it there if others agree with you.
- TransporterMan, WP has a very different strategy from Citizendium. WP's strategy is more successful. The difference is that WP gives up some authority and reliability in return for allowing anyone to edit its articles. WP believes almost everyone has something valuable to contribute. As a result, our older articles are sometimes entirely lacking in references. We have so many articles that peer-review is haphazard, and many articles "fall through the cracks" year after year, remaining without RSs. As WP editors we accept our strategy and the policies that govern it. But many editors see flaws in those policies. One flaw is that one cannot always find a RS for a good and true statement that one would like to add to an article. My example was an attempt to illustrate this. I'm not asking WP to move in the direction of Citizendium. Their policies have not proven the right ones for growth, only the right ones for providing good information (and maybe not even that, I don't know).
- WhatamIdoing, "We do have a small but dedicated number of editors who apparently believe that if it's not what the rest of us call plagiarism, then it's a NOR violation. I assume that this proposal is born out of long experience with such editors." Well, er, no. I did not have that in mind. However, that looks like another area that would benefit from my proposed modification of policies. Of course, you're employing hyperbole here--plagiarism is forbidden by WP policy.
- Andrew Lancaster, I don't understand your points. You seem to be supporting the proposal.
- Martinvl, I'm not following your response to Andrew. I don't see how this relates to the proposal.
- DonIago, Your arguments make sense only when a RS can be found. But my proposal deals with the many situations in which a RS cannot be found, such as in the example I gave.
- Monty845, "I just don't see a way for the idea to work in practice." Fine, but you don't seem to be exploring the proposal, but instead the application of BURDEN. I'm not seeing why you find the proposal impractical.
- North8000, Your first suggestion is intruiging. I'd like to see more about it. Your second appears to be incorrect. Any statement in an article can be removed when it has no RS or even inadquate RS. Please point me to policy if I'm wrong. I don't see any real objection to my proposal, though.
- LeadSongDog, "WP cannot have a mechanism that could make this work without abandoning the principle of 'anyone can edit', without which WP would die a slow and painful death." My proposal allows anyone with certain knowledge to add it to WP without having the bad experience of seeing it instantly be deleted before they can even add RSs. This supports the principle of anyone can edit in a very direct way. You must provide proof if you seriously wish to claim that my proposal will make WP "die a slow and painful death." That is a sweeping and dramatic claim, one which even other opponents of my proposal have not made so far in this discussion.
- J. Johnson (JJ), I have deliberately not brought in the need to evidence the expertise of an editor. Sometimes an editor will know a lot (which they can contribute to make WP better), sometimes an editor will know little or nothing about the article. In the spirit of WP's strategy of allowing edits to converge to something good, I worded the proposal so that editing and editor discussion would resolve most issues, as it does under the current policies. My proposal does not require anyone to be an expert in some academic way, just to have some information that they wish to contribute to the article. If it is false, other editors will remove it right away. If it is true, other editors will respect that, and allow it to stand. But my proposed policy explicitly allows such contributions to stand even though they have no references yet. It is a way to allow anyone to contribute what they know, and at the same time conserve the 25% (or whatever) of existing unsourced information in WP.
David Spector (talk) 17:16, 23 August 2013 (UTC)
- While your response improves my understanding of your proposal, I still feel it ultimately makes it more difficult for editors to remove unsourced information that does not belong here without sourcing. It's my experience that a desire/willingness to remove unsourced information is already not something found in great abundance among editors here (indeed, I've been commended on occasion for my willingness to get in the trenches to defend the removal of unsourced material...which I don't think should have needed to happen in the first place), and I believe there are sufficient protections governing the removal of such material. I don't feel we need more pressure placed on editors to leave added material alone. Bluntly - We have WP:BURDEN for a reason, and if an editor objects to material being removed then they should be able to satisfy said policy and consequently reinsert their material. If they can't, or worse won't satisfy said policy, then I don't believe the material should be published here. DonIago (talk) 18:10, 23 August 2013 (UTC)
- David we agree that "RSs are the cornerstone of the integrity and reliability of WP, such as it has". But you've missed my point because you've misdiagnosed the full reason why that '25% or whatever,' unsourced exists. Sourcing can be hard and requires work. Policy should continue to encourage that which we all would rather not do but need to for integrity and reliability -- more work. The rather-not-do impulse does not need reenforcement; it does well enough on its own. The insistence on sources also has important systemic benefits for collaboration in this anyone can edit model. It encourages discussion about content not persons, and increases trust and communication in the know what we're all talking about vein -- sources literally serve as the common point of reference (internally, as well as externally). Alanscottwalker (talk) 23:34, 23 August 2013 (UTC)
Thank you, all. Again, I did not see any insurmountable objections to my proposal. Here are my responses to these new responses. Interspersing them would interfere with their flow, so I've grouped them all here. Please feel free to continue the discussion here. David Spector (talk) 19:39, 28 August 2013 (UTC)
- DonIago, "I still feel it ultimately makes it more difficult for editors to remove unsourced information that does not belong here without sourcing." Henry, the idea that unsourced information does not belong here is part of the current policy, not my proposal. My proposal is orthogonal to the question of providing references to sources. My proposal allows uncontroversial unsourced information until such time as RSs can be found. The great benefit of removing unsourced information is that, especially in the early days of WP or of most editors, there was a tendency to add incorrect information (for example, information that was remembered incorrectly). I do not oppose eliminating incorrect information. My proposal may add incorrect information, but it will also add correct information, benefiting WP by encouraging editors to add what they know to be correct. They will sometimes also make mistakes. My proposal does not prevent mistakes, but it does allow correct information to be added and does encourage editors to contribute to WP. "I don't feel we need more pressure placed on editors to leave added material alone." I'm not clear on how my proposal increases pressure on editors. It merely allows situations where RSs have not yet been found to stand instead of be deleted. We have entirely too much deletion on WP--frequently good information is deleted just as quickly as bad. BURDEN states, "Any material lacking a reliable source directly supporting it may be removed." My policy modifies this; it preserves useful material until RSs can be found. To the extent that we trust editors to grow and to do a good job, this will improve the quality of articles. Editors will be encouraged to contribute information they know to be true. Not guess, but know for sure. Maybe this should be added to the proposal. But, while RS and BURDEN certainly improve WP in the absence of true experts, my proposal would further improve WP. (Encyclopedia Brittanica is an example of an encyclopedia whose philosophy is to collate the contributions of recognized experts. WP has a different philosophy.) "Bluntly - We have WP:BURDEN for a reason, and if an editor objects to material being removed then they should be able to satisfy said policy and consequently reinsert their material." Blunt or not, this is simply a statement of current policy. Do you believe that current policy has evolved to the point that it cannot be improved? "If they can't, or worse won't satisfy said policy, then I don't believe the material should be published here." Okay, so it seems that your arguments pivot on this final statement, which is simply a belief in the current policy. Belief is not a good enough rationale. Yes, I agree that the current policies are excellent; the quality of many WP articles, developed through the work of dozens of "non-expert" editors, is excellent. But pay attention, too, to the many articles that have no references at all. Pay attention to the editors who leave WP because they find it difficult to face continual arguments over policy. And pay attention to the many new editors who leave after editing just one or a few articles, either because they were criticized by other editors who know the policies inside and out, or because they found it difficult to spend so much time on research when they actually know the few pieces of information they contributed.
- Alanscottwalker, You make a good point: "Sourcing can be hard and requires work. Policy should continue to encourage that which we all would rather not do but need to for integrity and reliability -- more work." My proposal is not meant to eliminate the need for sourcing. I wouldn't want to open floodgates of adding garbage that then could never be removed. The proposal would merely make WP more lively, providing a way for editors who have good knowledge to contribute it. If even one editor, reading a new addition, sees that it is garbage, they can give a concrete objection to it and later delete it for lack of RS. The point is that at WP we trust "ordinary folks" to edit. We don't assume that they are idiots who can only contribute garbage. We welcome them, and my policy encourages this. Besides, there are many cases where RSs either haven't been found (older articles), or where RSs are difficult or impossible to find (my example of explaining how it is possible to sail faster than the wind). It is in these cases where my proposal really helps. It doesn't avoid work, but it does allow spreading it out instead of insisting that anyone can remove material lacking a RS. Finally, as to avoiding work, all editors should be encouraged to add references to older articles that have none. It may not be glamorous, but it can be fun, and satisfying to confirm correct information.
David Spector (talk) 19:39, 28 August 2013 (UTC)
- "My proposal allows uncontroversial unsourced information until such time as RSs can be found."
- And this is why I'm opposed to your proposal; you're prohibiting the removal of information indefinitely, even if it is unsourced. As I stated previously, my feeling is that if the information has been challenged then it is no longer uncontroversial.
- "in the early days of WP or of most editors, there was a tendency to add incorrect information"
- Some editors might argue that this is an ongoing tendency.
- " I do not oppose eliminating incorrect information."
- But your policy would make it more difficult to remove such information because an editor could claim they had the right to retain it until an RS is located. Or are you saying it should be incumbent on the challenging editor to prove that the information is untrue? If so, how would they do that?
- "My proposal may add incorrect information, but it will also add correct information, benefiting WP by encouraging editors to add what they know to be correct."
- I don't believe we need to make it easier for editors to add correct information, especially if it means they're adding information that may be correct but also is unverifiable.
- " My proposal does not prevent mistakes, but it does allow correct information to be added and does encourage editors to contribute to WP"
- I'm not aware of issues preventing editors to contribute to WP. IMO the requirement that information be sourced or face potential deletion is not a significant challenge to contributing.
- " I'm not clear on how my proposal increases pressure on editors. It merely allows situations where RSs have not yet been found to stand instead of be deleted."
- Which increases pressure on editors to let information stand instead of deleting it, because an editor who takes issue with the deletion can obstruct the process by claiming they need an indefinite amount of time to locate sources. I've already played the "Just give me another week to locate a source" game, and it doesn't work. Either the editor doesn't provide a source, or I move on to other things and the unsourced and potentially erroneous information remains. Where's the harm in saying, "Please re-add this information when you can provide a source"?
- "We have entirely too much deletion on WP--frequently good information is deleted just as quickly as bad."
- I don't believe that unsourced information should be called "good" information. It should be called "information that should be sourced". As for your opinion that there's too much deletion on WP - that's your opinion, and I haven't seen anything to support it.
- " My policy modifies this; it preserves useful material until RSs can be found."
- At what point are we allowed to conclude that they can't be found?
- "Editors will be encouraged to contribute information they know to be true. Not guess, but know for sure. "
- How are we supposed to know whether an editor knows information is true, is guessing that it's true, or is deliberately adding incorrect information knowing they'll later be able to claim they just need time to locate a reliable source?
- "Do you believe that current policy has evolved to the point that it cannot be improved?"
- There may be room for improvement within the current policy; I simply don't see how your proposal improves the current policy; rather I see it as weakening current policy.
- "Pay attention to the editors who leave WP because they find it difficult to face continual arguments over policy."
- In my experience most arguments over this particular policy could be averted if the editor desiring to include information would spend more energy locating a source than arguing for the inclusion of unsourced material. Also I'd like evidence that this is why editors are leaving...have you conducted exit interviews, or is this a guess on your part?
- "And pay attention to the many new editors who leave after editing just one or a few articles, either because they were criticized by other editors who know the policies inside and out, or because they found it difficult to spend so much time on research when they actually know the few pieces of information they contributed."
- It's my opinion that contributing to WP shouldn't just be about adding what you know to be true; it should be about what you know to be true and can provide a reference for such that other readers can determine from whence your information originated.
- In short, I don't doubt that you're passionate about this, but I don't see how your proposal ultimately does anything to improve the project. As near as I can determine, at best it restates information that is already true ("Editors can add unsourced information") while at worst it undermines verifiability and gives obstructionist editors the defense of "I know my information is true and I promise to add a source...sometime."
- If you opt to respond I would appreciate it if you did so directly after my comment to make it easier to follow the conversation, rather than your current technique,which makees the flow of conversation less clear. Thank you.
- Who's Henry? DonIago (talk) 20:36, 28 August 2013 (UTC)
- Oppose. (I voted likewise at WT:RS.) The problems are probably fatal but it's worth considering whether they can be solved.
- In answer mainly to editor David Spector at WT:RS (the editor suggested replying here) and at this topic/section:
- I agree that experts usually agree on a given statement in a field in which they're expert. But most of those statements would be sourceable. When they're not, disagreement becomes likelier, because being in print or on the Web attracts scrutiny about the certainty of the statement, so that the lack of print or bytes reduces scrutiny and lessens weight for certainty. While knowledge development tends to reinforce the core of a given body of knowledge, because the development of new edges challenges the core so that if a challenge fails the core is reinforced (e.g., perhaps gravity does not exist but the known data is so vast it's likely to overwhelm any attempt to come up with a contradictory explanation that accounts for all the known data), if a core statement is not sourceable then developers at the edges are less likely to know of the core statement and therefore may not either agree or disagree with it, thus may not either reinforce or discredit it.
- Active bodies of knowledge that are neither very recent nor very old are more likely sourceable; inactive bodies of knowledge (like on how to repair a Macintosh 128K) are those that have not lately been much developed (as far as most of would know) and thus have not lately faced known challenges to their validity, so if they're not sourceable there's also probably less agreement among its experts as to a given statement.
- Any editor adding unsourceable content is presumably implicitly claiming to be an expert. (Exceptions include vandals and the mistaken (e.g., grammar correctors who inadvertently alter substantive information).) By claiming x is true without a source, one is presumably asking to be believed without citing an authority other than oneself, and that probably defines a claim of expertise.
- Regarding the statement by David Spector, "my proposal would rapidly have had no effect in this example , since experts differed. WP has no way to prevent erroneous information from being added, but its virtue is that such errors are rapidly eliminated, as soon as someone with better knowledge comes along." Yes, but that means either that a second expert's unsourced view could replace a first expert's unsourced view or that replacement would not be allowed unless sourced which would mean that the first view would stay although unsourced while a second expert searched in vain for a source. So we'd either have battling experts (and we don't have a system for designating or recognizing experts so we'd really be dealing with battling editors who may or may not be experts), a pretender to expertise getting in first who stymies any expert trying to clear a matter up but has no source, or a relative success (an expert able to stop editing by a nonexpert who came afterwards); two out of three of those results are especially undesirable.
- My other examples that may not have been clear have these properties: On string theory and the disagreement with it, on an unsourced disagreement, whether a string theorist or a nonstring theorist should be the editor permitted to add unsourced content is the question; both can't be that editor. Between archaeology and Egyptology as separate disciplines, each could be the dissenter from the other, so that a point of disagreement regarding archaeology in Egypt can't be resolved be turning to the mainstream, since there are two mainstreams; the same is true of political scientists and sociologists (I think sociologists) with respect to mass movements; the same is true of scholars debating who discovered America, with even more mainstreams. The theological case had that property and also the property of applicability to a great many nontheological articles in Misplaced Pages, which risks that battles between experts would not occur as often but mainly because the second experts would probably not know that a first expert had posted somewhere that was secular (e.g., on voting) and so probably wouldn't edit or counter-edit there.
- I may have misunderstood in thinking that your proposal was for experts in particular (not just any editors) to gain a degree of preservation of their unsourced edits. If it is for nonexperts too and therefore anyone to edit so that other editors should assume that any unsourced edit is the product of expertise, making reverting harder, that amounts to weakening the RS and NOR requirements without, in my opinion, enough compensating gain. I have a thought about when a baseball batter has to decide whether to swing relative to a pitch's start but I have no source and I'm not a sports expert; if I add it to Misplaced Pages my view might be read by thousands of readers because no one could delete it without first gaining consensus that my view is controversial or finding a contrary source, if there is one. Maybe I should post it at a baseball discussion forum where reliable baseball experts could weigh in or possibly unreliable commenters could refer me to a reliable source one way or the other, since most readers of Misplaced Pages are not expert in the subjects they're reading about. Misplaced Pages is heavily used by nonexperts, most of whom don't edit it at all (I tried to persuade a public librarian who found an error and had a source to edit WP herself but she wasn't willing). I frequently edit unsourced edits on the basis of my sourceable expertise; if I had to bring all of them to the talk page to gain consensus instead of being bold I'd probably soon give up for most of them, as would most editors for reasons of time and productivity, and the result would be lower editorial quality across WP (unless those with the initiative to edit first tend to be inherently more expert than those who correct them, which I doubt).
- What I was talking about regarding adding OR to other media is that OR should be submitted to subject-relevant websites or other subject-relevant media which have experts in the relevant subjects and that are RS and then, after the other media have vetted the OR, a WP editor should paraphrase from the other media into WP. It's not your proposal but it may be a solution to the problem you outline, a solution that preserves existing policies and avoids the problem of awaiting consensus before deleting wrong information because perhaps it was added on the basis of unsourceable expertise.
- When new non-BLP content is rapidly deleted for want of sourcing when sourcing could have been found, the solution now is to re-add the content but this time with sourcing.
- The plagiarism-vs.-NOR issue is not hyperbole, because it was describing what some editors call plagiarism and other editors don't when the latter editors demand what the former would call plagiarism because they don't trust the quality of the paraphrasing they see and so think they see OR. Arguments of that kind come up now and then.
- I was not concerned that you have a hidden agenda. Something like this is not much affected by hidden agendas.
- WP:BLP requires immediate deletion of contentious content. I don't know if you propose that that policy be changed, but changing it could expose the Wikimedia Foundation to legal risks.
- Wikiversity is not a site I know well. Wikiversity:Reliable sources, Wikiversity:Original research (a proposal), and Wikiversity:Adding content seem relevant. At first glance, I'm not sure that OR is allowed there.
- Crafting specific language is advantageous at some point in the discussion (and I think that's now because of already-open disagreements between you and some other editors about what your proposal actually is), posted in a way that lets it be updated before finalization as debaters raise issues you can resolve by fine-tuning the specific proposal. Crafting what a template would say is also helpful but it's not important to program one (unless you have a fancy one in mind and one could question whether it technically can be created, but what's been so far mentioned is not technologically fancy). Your proposal that if one of these cases of unsourceable expertise goes to arbitration the tradition of requiring RS and deleting OR would take over for the case is a simplifying approach; if this includes not just arbitration (a term normally used only for ArbCom proceedings) but any dispute resolution mechanism, your proposal essentially would end when an editor requested dispute resolution, but that means that consensus that an edit is controversial would be unnecessary because a single editor could seek dispute resolution. This would lead to more disputes at the dispute resolution level and less posting to article talk pages seeking consensus. If you want to preserve the tradition that dispute resolution only follow an attempt at talk page discussion, then you should craft language so that as a result each relevant dispute resolution forum requires (or continues to require) that a consensus have been arrived at on the article's talk page (assuming it's not a sham consensus) or that a failure to achieve consensus be invalidated.
- Nick Levinson (talk) 16:53, 30 August 2013 (UTC) (Edited generally: 17:14, 30 August 2013 (UTC))
DonIago and Nick Levinson, thank you for your many points. I thought of replying to them individually as I have been doing here so far (many of them have simple answers based on simply understanding the proposal with an open mind), but realized that at this point, with mostly Oppose votes, that my continued defense is not worthwhile. If I'm seeing value in the proposal, but no one else is, the probability is that I'm wrong and everyone else is right. I therefore yield to the vast majority and sincerely thank everyone for considering my ideas. I know that present policies are not quite good enough to encourage some with good personal knowledge to offer it, so maybe I'll be back here again someday with a better and less objectionable proposal. David Spector (talk) 21:50, 9 September 2013 (UTC)
Proposal - sources in english on ENWP
Time to time discover english readers the sources of the articles in languages other than English. What is the point of these? You read articles on ENWP and would love to have sources written in English, it is natural. Many times I have come across articles where most sources, written in a language other than English. If English readers do not understand what is written in the source then the source is meaningless. All parties would benefit if all sources on ENWP were in English. Lifeglider (talk) 17:46, 28 August 2013 (UTC)
- No. AndyTheGrump (talk) 17:47, 28 August 2013 (UTC)
- That may be the ideal, but should not be a rule that would exclude sources. There are many things that would make a source more difficult to "access" (off line, behind a paywall, obscure, a different language) but they should not be grounds for excluding them. North8000 (talk) 17:52, 28 August 2013 (UTC)
- On the other hand, since English is one of the major world languages, the English language Misplaced Pages opens up the subject to readers whose home language is neither English nor the language of the original source. For example, assume that most of the sources regarding a particular subject that is related to country A are written in the language A. A reader from country B wishes to know about the subject, but can only read his own language, language B and English. In this case the English Misplaced Pages will open up the subject to him. Of course, Wikipedians who read both English and language A will ensure that the article accurately represents the sources. Martinvl (talk) 23:17, 28 August 2013 (UTC)
- When there are quality English language sources to support the information in our articles, our policy favors using them over non-english sources. However, many of topic don't have quality sources in English. We still want the articles, and we still want the articles to be well sourced... even if the sources aren't in English. Blueboar (talk) 01:16, 29 August 2013 (UTC)
- Absolutely oppose. If I'm writing about Germany or a German person, it's utterly insane to use out-of-date English sources when there are quality, up-to-date German-language sources that are easily accessible and, usually, more comprehensive.—S Marshall T/C 10:00, 29 August 2013 (UTC)
- I agree with S Marhsall. In the other direction, I've cited English-language sources on de.wikipedia, when writing articles about North American plants. Of course, I think it's helpful to both quote and translate the relevant excerpts of the sources. -sche (talk) 17:45, 30 August 2013 (UTC)
- Agree with S Marshall. One option, which I don't think is currently sufficiently utilized, is to translate articles into English on WikiSource, which would make it easier for editors in any language to use sources which are primarily if not exclusively non-English. I think that this would apply most strongly to material in foreign language reference books, particularly on topics which seem to more directly relate to that language than English. Here I'm thinking of, for instance, encyclopedias in the Russian language which give wonderful articles about significant Russian historical developments or culture, but which aren't as regularly discussed in foreign language sources. If anyone knows of any way to stimulate development of such translations, I and I think others would love to see them. John Carter (talk) 16:57, 6 September 2013 (UTC)
- While that may not be wildly known, even native English speakers are neither structurally unable to nor legally forbidden from learning other languages. Or from commissioning a translation. Restricting ourselves to English sources would increase systemic bias, decrease quality, and leave us overall much poorer. Also, arguably it's easier to learn (say) Persian as a language than to learn enough math or physics or computer science to understand many academic sources in English. Just because one can read the words does not mean one understands the source. --Stephan Schulz (talk) 17:15, 6 September 2013 (UTC)
- Je suis très opposé à cette proposition. Sławomir Biały (talk) 18:11, 6 September 2013 (UTC)
- Absolutely oppose. That material must be verifiable does not mean that it must be verifiable by any given reader no matter how limited his or her competency. ~ J. Johnson (JJ) (talk) 22:42, 6 September 2013 (UTC)
wp:Verifiability and retroactive use of new names
On several occasions in the past, and in a certain recent discussion, some people have made the argument that using a person's new name when discussing periods of their life during which they were known by another name violates wp:Verifiability, wp:No original research and/or wp:Synthesis. (If need be, I can dig up examples of people making this argument.) I'd like to start a discussion of whether or not that is the case. I appreciate your help in ensuring that this remains a discussion of that specific question and does not become a discussion of whether or not retroactive use of a new name violates any other policy and/or is a good idea. I would also appreciate your suggestions of a better forum for this discussion, if you can think of one.
Say we're writing an article about someone who was born 'Pat Xyz', discovered foobarium as 'Pat Xyz', then started going by 'Lou Zyx'. Say we have reliable sources confirming each of those things. Say, for purposes of this discussion, that our article on this person is at ]. If we have sources saying "Xyz discovered foobarium", is it a violation of VERIFY, NOR and/or SYNTH for us to write "Zyx discovered foobarium"?
For my part, I contend that it is not, because we have sources verifying that Pat Xyz = Lou Zyx. I don't think anyone would ever argue that it was a violation of any of those policies to write "foobarium is water-soluble" in our article on foobarium, even if the only available references said "foobarium is soluble in H2O", so I admit that I can't even discern what the argument to the contrary is.
I've posted notices of this discussion to WT:NOR and WT:MOS; if this discussion is moved, those notices should be updated. -sche (talk) 17:34, 30 August 2013 (UTC)
- None of WP:V, WP.NOR or WP:SYNTH apply to a case where the change of name is documented by reliable sources and not challenged by any. It is only a matter of writing style. If someone is very well known under one name, the "principle of least surprise" may mean using that name for a longer period (together with a brief explanation). For example, former Israeli prime-minister Yitzhak Shamir was called Icchak Jeziernicky for his first 35 years at least, yet the article uses "Shamir" throughout. That is fairly typical. Perhaps the correct place for this discussion is some talk page associated with WP:MOS. Zero 00:04, 31 August 2013 (UTC)
- Could you clarify what you mean by "the change of name is not challenged by any "? If one source says Pat started using the name Lou, but another source calls that "a persistent myth", then it's clearly necessary to verify whether or not the name change occurred. But say all sources acknowledge that Pat started going by Lou (and thus acknowledge that references to "Lou" are references to Pat), but some sources dispute that it was (legally/morally/etc) appropriate/valid for Pat/Lou to change names. (This is the scenario in which people typically make the arguments I'm asking about the validity of.) If enough reliable sources accept the name change as valid that Misplaced Pages has decided to use "Lou" in reference to the person's post-name-change actions, does there need to be a separate, additional discussion of whether or not using "Lou" in reference to the person's pre-name-change actions is verifiable? -sche (talk) 07:58, 31 August 2013 (UTC)
- To me, the WP:V question is, "can we verify they changed their name," not "can we verify everyone else follows our style about the retroactive use of names" or whatever, for the reason that as you said the two names mean the same thing. Really, you could ask the same thing about anything in the MOS. For instance, we had a whole super duper long discussion about whether changing a hyphen to a dash, per MOS dash rules, in the comet hale–bopp article raised verifiability or OR concerns because seemingly all astronomers use a hyphen, but then really the outcome was that we follow the MOS over styling even if on a particular matter our styling is out of synch with RSs. I don't think it's that different here, really. There is no substantive change being made in this situation because the two names refer to the same person, so it's a styling matter not a substance matter. Ymmv. AgnosticAphid talk 14:37, 31 August 2013 (UTC)
- Could you clarify what you mean by "the change of name is not challenged by any "? If one source says Pat started using the name Lou, but another source calls that "a persistent myth", then it's clearly necessary to verify whether or not the name change occurred. But say all sources acknowledge that Pat started going by Lou (and thus acknowledge that references to "Lou" are references to Pat), but some sources dispute that it was (legally/morally/etc) appropriate/valid for Pat/Lou to change names. (This is the scenario in which people typically make the arguments I'm asking about the validity of.) If enough reliable sources accept the name change as valid that Misplaced Pages has decided to use "Lou" in reference to the person's post-name-change actions, does there need to be a separate, additional discussion of whether or not using "Lou" in reference to the person's pre-name-change actions is verifiable? -sche (talk) 07:58, 31 August 2013 (UTC)
- To give an example of when we use a person's old name (and all but ignore a name change)... we have William Pitt, 1st Earl of Chatham... in this article we consistently refer to the subject as "Pitt" (and down play "Chatham") throughout the text. It really does depend on the specific person and what name readers will expect to see presented. Blueboar (talk) 15:31, 31 August 2013 (UTC)
- I agree that whether to make retroactive use of a later name, continue using an earlier name, or use both names is something to be decided on a case-by-case basis. It occurred to me earlier that I hadn't noted (so I will now note) that if Misplaced Pages decided to use "Pat" throughout the article on my hypothetical "Pat Xyz"/"Lou Zyx", even when discussing periods of their life after which they'd come to be known as "Lou", that would also not violate WP:V, IMO. (And one would logically expect that the people who do think using "Lou" when discussing "Pat"'s childhood violates WP:V must also think that using "Pat" when discussing "Lou"'s adulthood violates WP:V. But what I'm suggesting is that any anachronistic use of a personal name, while it might be good or bad for other reasons, does not violate WP:V. And everyone here seems to agree on that point.) -sche (talk) 22:49, 31 August 2013 (UTC)
- This reminds me of the movie Stripes. "My name is Francis but everyone calls me Psycho. Call me Francis and I'll kill you." There are two issues that conflate this. One is a simple name change and discerning its scope, notability, verifiability, etc. For example, if someone has a nickname and it becomes well-known, it may be appropriate to use it in the lead along with the proper legal name. Other organizations where names are part of a uniform, they require legal name changes (i.e. Metta World Peace was Ron Artest and had to legally change his name, Chad Johnson wanted his uniform to reflect "Ochocinco" and it was denied by the NFL until he legally changed his name.) I think it serves the encyclopedia to use the legal name, then common name and nickname as part of the name. It is still a case by case basis though because some pet names like "sweetypie" might not be appropriate whereas Bess Truman is an example of the pet name becoming the common name, article title and lede. Case by case is appropriate in less contentious articles. But the 2nd issue which is Wikidrama of the week is a name and gender change when neither has legally or anatomically been changed and all the notability came under the previous identity. Even if we accept they are the same person and there is no confusion (H2O and water analogy), there are very real differences in pronouns and the equivalence breaks down. The use of one name or the other is perceived as the declaration of gender, rather than the person. Misplaced Pages has to balance the preference of the person with the legal status of that person (both name and gender) in regard to past, present and future. Our sources generally don't redact their articles to reflect a change. Even if they are all electronic (i.e. Slate), the article doesn't search/replace every reference and neither should WP especially if the change isn't particularly relevant to the notability of the subject and the change has not been recognized legally or anatomically. In the present drama, Manning is the topic of debate. His notability was for an illegal act (personally, I don't even know why he has an article as his life is not particularly notable outside the single event). Manning recently said he was female and his name was now "Chelsea" instead of "Bradley." All fine and dandy except no body of authority recognizes it. Nor will he use his new name and gender in future litigation or incarceration. The court is the authority over his name, the Army is the authority of his rank and the examining doctor will determine his gender. It is acceptable to note Manning's preference or declaration but the wholesale change of every reference to Manning to reflect his preference is not supported by reliable sources. If Michael Phelps came out and said he was female, the Olympic committee would not suddenly acquiesce and allow him to compete as a woman nor would the record book redact all references to his accomplishments in Men's swimming and change it to Women's swimming. There is an authoritative physical exam to determine gender (and yes, there have been intersexual athletes that have been barred from participating as the gender they identify with) and the name engraved on the trophies is the name at the time. In the case of Manning, all of his notable acts occurred when he was "Bradley." That may be very relevant to his username for the systems he compromised, it's certainly on all the charging documents and his enlistment in the Army. He was certainly notable under the name "Bradley." The next phase of his life will be prison. A doctor will examine him and determine his gender to assign him to the appropriate barracks including whether he should start a gender reassignment medical regimen. That is the authoritative source of his gender. Manning's self-identity as female is currently not supported by any medical exam and is simply his own belief. There is a difference in recognizing his personal identity while also recognizing it is not presently supported by professionals that would be considered reliable sources. We have seen many people claim an identity (i.e. Native American, African American, Hispanic) that is challenged by reliable sources (or not proven by outside sources). Only a doctor with transgender training would be able to prescribe or perform any reassignment surgeries and I personally doubt that doctor would make that determination while Manning is under a tremendous amount of stress. Gay, transsexual and transvestite are not the same and only one would be a condition diagnosed and treated by a physician. Therefore, self-identification as gay, bisexual or transvestite has a much lower threshold than transsexual where a medical diagnosis would be required to start a gender reassignment regimen. Manning may very well be female and eligible for gender reassignment treatment but he isn't going to attain that until a doctor says so. That's the reliable source standard. When that happens, the gender of the sourced reference should be maintained either chronologically or for notability. If the real world operated solely on the basis of self-identification of gender, there would be no male criminals. They would just declare themselves female and expect society to accept it and house them in female prisons. If they declared they were gay, transvestite or bisexual, no one would care and they would still go to a male prison. The bar for claiming a medical condition has a necessarily higher standard for sources. --DHeyward (talk) 23:56, 31 August 2013 (UTC)
- I apologise if my original post wasn't clear... if you re-read it, I think you'll see that you haven't addressed it. Your argument for why Manning's name and gender change isn't 'valid' is well thought-out (though I disagree with it); you clearly think that Manning shouldn't be referred to as Chelsea at all. However, this is a discussion of something different, something specific: several people, including you, suggested that using a name or pronoun retroactively — or using a source that said "(name A) did X" or "he did X" to support a sentence in an article that "(name B) did X" or "she did X" — raised verifiability concerns; other people suggested it raised synthesis concerns. Those are the concerns I'm addressing at the moment. -sche (talk) 06:38, 1 September 2013 (UTC)
- I understood it, and for the record my preferred name in the lede is Bradley Edward "Chelsea Elizabeth" Manning. I also note he used "Breanna" previously as well. My concern is that editors believe that the pronouns used in an article become hostile when someone self-adopts a gender change but apparently only hostile when Misplaced Pages uses them. No one has "Slate" redo all their articles to reflect the latest incarnation. We didn't do it when Manning used his "Breanna" persona, nor did our sources. I don't consider the pronouns hostile, however, as they accurately reflect his identity when it was sourced. To avoid battleground issues, it would be best to leave the pronouns and gender as they are found in sources. WP isn't in the gender identity business so pronouns should generally reflect the sources unless there is high bar (i.e. reliable source other than just the persons wishes). Manning, so far, doesn't appear to have done anything notable as "Chelsea". There is a stronger argument that s/he became notable when s/he was using the name "Breanna." If we look at Manning through his Gender Identity Disorder defense arguments for mitigation, he blamed GID for emotional instability, assaulting a female superior officer and leaking classified documents. The wholesale acceptance of that, without 3rd party reliable sources, stigmatizes people that have GID as being emotionally unstable, potentially violent and untrustworthy for a security clearance. I don't have a particular problem with revising an article that reflects a reliably sourced gender change (i.e. medical, legal, etc). But prior to that, I am inclined to mention the gender claim while still reflecting the gender status in the sources because otherwise it implies we accept GID on the claim by the person at face value. I don't think that is fair to people that have been diagnosed, treated, and taken medical and legal steps to become who they are. Transexual issues have a higher bar than other LGBT issues simply because it is classified as a medical condition. No one blinks an eye at pronouns like "His husband" for two males that marry. Gay is not a medical condition. Manning however said a DSM psychological disorder (GID) caused him to do illegal things. Understandably, for those that also have GID, the bar should be pretty high for that claim. Imagine a hypothetical case 40 years ago, a married man was caught molesting children and used a DSM classification of homosexuality as a medical disorder that caused him to commit those acts. Would we rush to make sure that every reference to him reflected his sexual preference? It would not be tolerated to replace "The married father molested three children..." with "The gay father molested three children..." if he tried to mitigate his crime with the now outdated DSM disorder. Today, I hope we would see that it's not particularly relevant to the bio or the crime. Manning mitigated his crime with the GID defense and we should be very reluctant to simply accept it. It's worth mentioning what he wishes to be called and what he considers himself to be, but a wholesale retroactive change based on his press release, seems premature and unenlightened until/unless he takes steps that others take (including diagnoses, medication, surgery, name change, etc). If the Army doctor for Leavenworth, for example, said he can't be housed there because Manning is female, I'd have no problem with changing pronoun references. --DHeyward (talk) 22:25, 1 September 2013 (UTC)
- The name issue cannot possibly be a problem. Take, for example Metta World Peace. He lived most of his life as "Ron Artest" and most of the sources for information on his page are to publications that pre-date his name change, and thus refer to him as "Ron" and "Artest" with no mention of his current name. The section on the Pacers–Pistons brawl, for example, uses sources from 2004, 7 years before the name change. But if we are going to take seriously the worry about name changes and verifiability, then we have to ask why is information about a brawl that a source says involved "Ron Artest" on a page for a person whose name is "Metta World Peace". The answer is because we have some reliable sources that Artest was involved in the brawl and other reliable sources that Ron Artest is the same person as Metta World Peace. We do not need to find some new source that says "Metta World Peace was involved in a brawl in 2004". The idea that there is a verifiability issue here is absurd.
- For gender, take the following real example: 11 year old future singer Robin Thicke was being babysat by hockey legend Wayne Gretzky on the day that Gretzky was traded from Edmonton to Los Angeles. This quirky fact has been deemed interesting enough to be included on Thicke's page. The source that is cited for the information uses a male pronoun when mentioning Robin Thicke twice in a throwaway comment. The only other indication in that source that the source believes that Thicke is male are two uses of the word "son" (to define his relationship to Alan Thicke). But it is easy to imagine the same article without these mentions of gender. If it had been written with no male pronouns and no uses of the word "son" for Robin Thicke, someone who took the gender verifiability question as seriously as some have would be forced to say that we cannot conclude that the source believed that Robin Thicke was male and so the Misplaced Pages page cannot say, as it does right now, "Wayne Gretzky had been babysitting him while his father was on vacation...." That's also absurd. 99.192.79.173 (talk) 15:59, 1 September 2013 (UTC) (99.192....)
- I've seen two comments made elsewhere which I think inform discussion of this issue: this opinion about why names and pronouns are used, and this opinion that retroactive use of names violates WP:SYN. I have asked the author of the latter post to copy the post over here, so it can be better discussed in this central place. -sche (talk) 20:20, 1 September 2013 (UTC)
Proposal - Valuing some sources over others
Right now, WP:SOURCEACCESS holds that
- "Do not reject sources just because they are hard or costly to access."
However, since the WP:NOT holds that Misplaced Pages Encyclopedia is an 'online community of individuals,' suggest that a priority should be given to sources that are more easily accessible to the majority of editors; e.g. online articles, famous journals, instead of obscure books. This will solve any problems that are caused by subjective interpretations of such sources.
In the same way, while WP:RSUE prefers English-language sources more than non-English ones
- "English-language sources are preferred over non-English ones"
It is not too explicit and there are instances of non-English sources being used when English ones could be used instead. With such sources, English-only editors have trouble editing materials based on such sources, even if they can contribute to the topic in question.
So, in short - propose that "Sources more easily accessible and written in English should be valued over their counterparts, and editors are encouraged to replace inaccessible and non-English sources if they can, with more accessible ones." kkj11210 (talk) 03:54, 31 August 2013 (UTC)
- That would privilege bad sources over good ones. The policy already says that English sources should be preferred when "of equal quality and relevance". Your suggestion would give preference to an article in The Daily Mail over an article in a highly-respected German history journal. --Hegvald (talk) 16:13, 31 August 2013 (UTC)
- Other editors' ignorance of foreign languages is not, and has never been, the article writer's problem. If you can't check a source because it's in a language you never learned, ask an editor who can for help.—S Marshall T/C 18:48, 31 August 2013 (UTC)
- I would definitely oppose favoring on-line sources over hard copy "dead tree" sources. Quality is more important than ease of access when it comes to sources. Blueboar (talk) 22:13, 31 August 2013 (UTC)
- Like Blueboard says: quality (and reliability?) should be the paramount consideration. This should not be weakened simply for convenience. ~ J. Johnson (JJ) (talk) 22:55, 31 August 2013 (UTC)
- I agree entirely, a weak easily accessible English source should not be preferred over a high quality foreign language source that is harder to access simply because the English source is ease of access.--64.229.165.126 (talk) 23:07, 4 September 2013 (UTC)
- Nope, I oppose, too. While this would make our lives easier in some ways, we're not trying to be the easiest encyclopedia to write for in the world, but the best. Regards, TransporterMan (TALK) 13:21, 5 September 2013 (UTC)