Wikipedia talk:Manual of Style/Biography/2023 archive
From Wikipedia, the free encyclopedia
| This is an archive of past discussions about Wikipedia talk:Manual of Style/Biography. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
GENDERID names
Regarding this edit that was reverted. There is an obvious conflict with the original wording and the WP:NOTCENSORED policy, which states, "Wikipedia may contain content that some readers consider objectionable or offensive—even exceedingly so. Attempting to ensure that articles and images will be acceptable to all readers, or will adhere to general social or religious norms, is incompatible with the purposes of an encyclopedia."
There are already guidelines and policies covering former names and privacy concerns, which is why I added links to the section. Why is there a special carveout for a transgendered person and we treat them different than any other person who changes names? Consensus doesn't get to override policy. Cuñado ☼ - Talk 01:09, 5 January 2023 (UTC)
- We've been through this over and over. Check the archives. Discussing it again is unlikely to lead to a change. —David Eppstein (talk) 01:42, 5 January 2023 (UTC)
- I've read the conclusions in the archives. The issue of former names and privacy is already addressed in BLP and on this page. GENDERID currently says to avoid the former name "even if reliable sourcing exists", which clearly violates core content policies and the MOS for former names. I have edited Wikipedia for 17 years and have never seen such an open violation of policy. Saying "go read the archives" is insufficient. If you don't want to discuss it, I'll start another RFC. Cuñado ☼ - Talk 17:38, 5 January 2023 (UTC)
- You've been an editor here for many years. Don't throw it away on a tendentious anti-woke crusade. —David Eppstein (talk) 19:42, 5 January 2023 (UTC)
- I've read the conclusions in the archives. The issue of former names and privacy is already addressed in BLP and on this page. GENDERID currently says to avoid the former name "even if reliable sourcing exists", which clearly violates core content policies and the MOS for former names. I have edited Wikipedia for 17 years and have never seen such an open violation of policy. Saying "go read the archives" is insufficient. If you don't want to discuss it, I'll start another RFC. Cuñado ☼ - Talk 17:38, 5 January 2023 (UTC)
- The answer to your question,
Why is there a special carveout for a transgendered person and we treat them different than any other person who changes names?
, is to be found in the many community processes linked at MOS:GIDINFO. - The "Coles Notes" summary of the discussions concerning former names is, primarily, that there is a concern based on BLPPRIVACY principles (WP:BLP having the weight of core policy) that is different for gender identity-related name changes than it is for other name changes. You may disagree with this, but it represents the way the community has adjudicated tension among its core policies for many years now, and with the input of many, many editors. Newimpartial (talk) 21:45, 5 January 2023 (UTC)
- So, personally I think MOS:DEADNAME is right for the wrong reasons, because I think we should in general be much more deferential to name changes. There isn't something magical about a gender-based name change that makes it more worthy of respect than other name changes; the issue is just that our community has historically sucked at respecting individuals' right to be called by the name they request, so we made a carve-out for the case where that obnoxious practice was causing the most trouble. Setting that aside, no, this is not a NOTCENSORED violation. WP:NOTCENSORED does not require us to include anything. It just says we reserve the right to show anything lawful, when doing so would be in accordance with other policies and guidelines. The actual governing guideline is Wikipedia:Offensive material, which explicitly rejects giving any "special favor to offensive content". This is why, among other things, articles on human sexuality are almost never illustrated by live-action videos; it's why the image of fresh cuts at Self-harm was replaced with an image of scars; and so on.So if someone were to argue "We should not include so-and-so's deadname because it is illegal under the laws of such-and-such foreign jurisdiction" or "because it's a sin in my religion" or any other non-PAG based argument, then NOTCENSORED is a valid rebuttal. But if someone says "We should not include so-and-so's deadname because it presents issues regarding privacy and human dignity, without there being a particular benefit to the reader in us including it", that's the regular kind of weighing of interests we do on articles all the time. And here, people have presented that argument so many times, and it's been affirmed by the community so may times, that it was enshrined in guideline. (And hey, just a guideline. I've seen IAR exceptions made here and there, usually when the subject has publicized their own deadname.) -- Tamzin[cetacean needed] (she|they|xe) 01:20, 6 January 2023 (UTC)
- Thanks Tamzin, very helpful. I think you touched on my point, that we should have a policy about former names without regard to transgender status. We have a guideline for former names, and a policy addressing privacy, and I think those make sense and already address the issue of non-notable former names. The guideline on WP:GENDERID currently censors useful and verifiable material based on the individual's personal feelings, which makes sense in a gender studies class but not an encyclopedia. I support keeping a person's sexual identity private unless there is good reason, but I don't agree with the way the guideline is worded. I think there is a way to update it that will not be unnecessarily offensive to transgender people while also not leaving a contradiction with policy that will endlessly churn out complaints.
- At some point I'll work on an RFC, unless you think something can be worked out here. Cuñado ☼ - Talk 16:58, 6 January 2023 (UTC)
- Your belief that the hundreds of editors who contributed to the current consensus against the inclusion of non-notable former names of nonbinary and trans people over the last decade will suddenly change their minds when presented with your proposal - well, to be charitable, it seems exceedingly optimistic. Newimpartial (talk) 17:30, 6 January 2023 (UTC)
- Can you point me to the RFC that you are thinking of? I did not see that issue specifically addressed as you describe. Yes I did make an effort to search the archives. Cuñado ☼ - Talk 17:58, 6 January 2023 (UTC)
- @Cuñado: Here are about 10 RfCs among the 70 or so discussions - Wikipedia:Manual_of_Style/Gender_identity#Discussion_timeline. Bluerasberry (talk) 18:29, 6 January 2023 (UTC)
- Please use MOS:IDINFO to navigate the prior discussions; that is what its timeline of discussions is for. The decision to clarify that non-notable deadlines are excluded from article space, rather than only the main biographical article, was made in 2020. The question of which deadnames should, and should not, be included in the lead of the main biographical arricle was decided back in 2015, and was revisited frequently but without significant changes until the restrictions on former names were expanded in 2020. In 2021 additional restrictions were placed on how notable former names of trans and nonbinary people should be mentioned. (All of these links are presented in the timeline section of IDINFO, with brief identifying descriptions of each discussion.) Newimpartial (talk) 18:29, 6 January 2023 (UTC)
- Can you point me to the RFC that you are thinking of? I did not see that issue specifically addressed as you describe. Yes I did make an effort to search the archives. Cuñado ☼ - Talk 17:58, 6 January 2023 (UTC)
- Your belief that the hundreds of editors who contributed to the current consensus against the inclusion of non-notable former names of nonbinary and trans people over the last decade will suddenly change their minds when presented with your proposal - well, to be charitable, it seems exceedingly optimistic. Newimpartial (talk) 17:30, 6 January 2023 (UTC)
- I've suggested before that the appropriateness of including a deadname for transgender individuals shouldn't stop there, but should extend to any name changes, such as non-English names for immigrants or pre-marriage names for married people - if the sourcing is weak or relying on primary sources, we should not include that name. This would make one policy consistent across all BLP. But this was rejected because editors felt that it was required to include things like pre-marriage names in BLP articles. Hence the conflict here. Masem (t) 18:00, 6 January 2023 (UTC)
Pronouns for transgender and non-binary people
Hi. I am a non-binary person. I have read the Wikipedia guidelines on transgender and nonbinary people (MOS:GI) and I really think they should be changed. Why does it specifically say only a living person gets the respect of being referred to by their preferred pronouns?
If a person's preferred pronouns were known why should they not be respected in death? It is high time to update these guidelines. Errlane (talk) 10:46, 16 January 2023 (UTC)
- This is the BLP policy, so its application to dead people is limited only to the short period after death. That said, I think there's room in the policy that if a dead transgender person was known to prefer a certain set of pronouns via reliable sources, we should respect that choice (and of course, if a currently living transgender person with known pronouns dies, their preference doesn't disappear after death). If we have no such idea of preference, then using "they/them" is the more respectful route. Masem (t) 13:33, 16 January 2023 (UTC)
- Are there any examples of articles where a dead person had preferred pronouns that we don't use? (Not at all saying it's not the case, I've just not encountered any.) — Czello 13:45, 16 January 2023 (UTC)
- Do you mean MOS:GID? If so, where does it "specifically say only a living person gets the respect of being referred to by their preferred pronouns"? I see "Refer to any person whose gender might be questioned with gendered words (e.g. pronouns, man/woman/person, waiter/waitress/server) that reflect the person's most recent expressed gender self-identification". EddieHugh (talk) 20:44, 16 January 2023 (UTC)
please explain (GENDERID examples)
(I noticed this on the MOS:GIDINFO page, but the content is transcluded from here)
As of this writing we offer two examples of "don't include the former name if not notable", both written in green (indicating this is how to write things):
- From Laverne Cox, not notable under prior name: Laverne Cox (born May 29, 1972) ...
- From Rachel Levine, not notable under prior name: Rachel Leland Levine (/ləˈviːn/; born October 28, 1957) ...
First off, the green text doesn't actually match what the articles (currently) say: The first article begins "Laverne Cox (born May 29, 1972) is an American actress and..." Green text should IMO be reserved for the actual words we want to teach readers to use. Plus, wouldn't it be better if the example actually contrasted what to write with what to not write (which is why we'd use a made-up example)
Why not use a made-up example, and why not write (in green) the exact phrasing we want readers to adopt:
- Jane Doe (born May 1, 1980) is an American celebrity. They are known for..."
- Jane Doe (formerly John Doe, born May 1, 1980) is an American celebrity. They are known for..."
Doe is not notable under prior name, so do not include it at all.
My question is: why did the community decide to not use this style of examples? CapnZapp (talk) 07:47, 22 January 2023 (UTC)
- I don't know, but perhaps because it's redundant. The examples are of what names to use, not pronouns. We therefore do use the exact phrasing that users should adopt. (Your examples are also contradictory: the first recommends "they" and the second, for the same person, indicates that "they" is incorrect.) I'd argue that we don't need examples of pronoun use, because it's clear from the first paragraph of MOS:GENDERID (in your example, "Doe is not notable under prior name, so do not include it at all" is required to explain which name is which, but it's merely repeating that first paragraph). EddieHugh (talk) 13:17, 22 January 2023 (UTC)
What are you talking about? Nobody is discussing pronouns. Both I and the GENDERID is discussing whether to mention the former name. My example clearly shows how to write and how to not write it.
I'm saying that this...
- Jane Doe (born May 1, 1980) is an American celebrity. They are known for..."
- Jane Doe (formerly John Doe, born May 1, 1980) is an American celebrity. They are known for..."
(obviously switching to a made-up example so we can show the incorrect way of doing it; illustrating what we're telling users NOT to do) ...is much more easily understood than whatever the current text's examples is trying to say. Unlike the current text it avoids text you're not supposed to write (in other words, no they don't contain "the exact phrasing that users should adopt"), doesn't begin with a "From" (that I don't understand the purpose of), and extremely clearly illustrates both the green do and the red don't.
That I chose Jane Doe as my example name, and my choice of example nationality, "job", and pronoun, is entirely irrelevant and beside the point. CapnZapp (talk) 22:06, 23 January 2023 (UTC)
- I thought you might be referring to pronouns because you wrote "the green text doesn't actually match what the articles (currently) say", and then included pronouns, which aren't in the examples, while the green text is exactly what's in the articles. Anyway, I think that the current text is adequately clear, if long-winded (one example for not notable and one for notable would be enough). EddieHugh (talk) 19:59, 24 January 2023 (UTC)
- I would point out that one reason to include two examples for each case is to show that there is not "one correct template" to use to follow in each case. The notable examples, for instance, give one case where the pretransition name is a "birth name" and one where it is not. Newimpartial (talk) 21:04, 24 January 2023 (UTC)
- The "From" part, intended to explain from which articles the examples have been lifted, is completely unnecessary. But if you must link to real articles, don't mess up the example to do so.
- The contrast between green and non-green text is not great enough. Better is to offer examples consisting of green (or red) text only, with no explanatory nonsense inserted mid-example.
- Sorry, but just providing examples isn't enough. The purpose of a demonstration is to be clear. I don't mind keeping the two real-life examples, but overt clarity would then be needed. In the spirit of overt clarity: if you provide an example to show how to phrase it when pretransition name is a "birth name", say so. Don't expect the reader to "just understand". These guidelines aren't written primarily for people that already know what to say and what to avoid. For many readers, this article will be the first time they even hear about terms such as "pretransition name"!
For example (feel free to write better explanatory text; copying bits from reply above just to illustrate):
When pretransition name is a "birth name" (example from Laverne Cox):
- Laverne Cox (born May 29, 1972) ...
When it is not (example from Rachel Leland Levine):
- Rachel Leland Levine (/ləˈviːn/; born October 28, 1957) ...
When pretransition name is not notable (fictional example):
- Jane Smith (formerly John Hammer, born May 1, 1980)..."
(do not include non-notable pretransition name at all)
CapnZapp (talk) 18:18, 25 January 2023 (UTC)
- I'm going to assume I have answered y'all to your satisfaction, and that we are now in agreement. CapnZapp (talk) 15:38, 30 January 2023 (UTC)
- Thank you for "preserving the presumed intention", Newimpartial. However, wouldn't you agree your edits lost the explanation of why we have two green examples? That is (with your own words) "one case where the pretransition name is a 'birth name' and one where it is not"...? At least I don't know either of Laverne Cox and Rachel Levine, and wouldn't be able to discern any functional difference between the two examples (other than "one example subject has two last names, the other has one" and "one example includes pronounciation, the other does not") CapnZapp (talk) 19:28, 30 January 2023 (UTC)
- What do you mean by Elliot Page's prior name not being a birth name? Wasn't Page christened "Ellen"? (And weren't we discussing these in the context of Cox/Laverne, not Manning/Page?) CapnZapp (talk) 19:34, 30 January 2023 (UTC)
- Prior to acting, Page's last name was a hyphenated form of his mother and father's surnames (Philpotts–Page), which was shortened for his stage name. It's a bit confusing since the hyphenated name is not in the linked article and it's not an obvious change (like from Norma Jeane Mortenson to Marilyn Monroe, for example). — Carter (Tcr25) (talk) 19:51, 30 January 2023 (UTC)
- In fact, the hyphenated name does not meet notability requirements (to my knowledge, the only sourcing for it that satisfies WP:IND is a local newspaper in South America). This has been discussed at length at Talk:Elliot Page. The consensus has therefore been consistent that "Ell*n Page" is a notable professional name, not a birth name, and this consensus was reflected in the choice of example for the MOS. Newimpartial (talk) 20:19, 30 January 2023 (UTC)
- Oh, come on. The purpose of giving examples is illustrating a point. In order to explain the point (why otherwise make it?) we need to explain an obscure detail that we have agreed to not divulge! The obvious conclusion is to use another example, where we can actually tell our readers what our example is meant to illustrate. CapnZapp (talk) 22:07, 30 January 2023 (UTC)
- To be clear, I am not saying Page is a bad example. If we clearly (in our article) explain that Page is an example of a subject whose name is not a birth name, and avoid raising further questions by explaining why this is so, then it is a great example. If, however, we use Page as an example with zero elaboration as to why we use that example, it loses all instructive value. CapnZapp (talk) 22:15, 30 January 2023 (UTC)
- Where are you suggesting that this elaboration ought to be provided. Surely not in the article text of Elliot Page? Newimpartial (talk) 22:23, 30 January 2023 (UTC)
- I don't know where the elaboration should be provided (or it if is even appropriate), but it's not clear to anyone unfamiliar with the lengthy discussions at Talk:Elliot Page why he would be used as an example for "not a birth name." It's about picking an example that makes clear the point being made, not further confusing the reader. Perhaps replacing "not a birth name" with "professional name" or "stage name" would be less confusing. — Carter (Tcr25) (talk) 00:06, 31 January 2023 (UTC)
- I have tried to reflect your suggestion in this tweak. Newimpartial (talk) 01:45, 31 January 2023 (UTC)
- I don't know where the elaboration should be provided (or it if is even appropriate), but it's not clear to anyone unfamiliar with the lengthy discussions at Talk:Elliot Page why he would be used as an example for "not a birth name." It's about picking an example that makes clear the point being made, not further confusing the reader. Perhaps replacing "not a birth name" with "professional name" or "stage name" would be less confusing. — Carter (Tcr25) (talk) 00:06, 31 January 2023 (UTC)
- Where are you suggesting that this elaboration ought to be provided. Surely not in the article text of Elliot Page? Newimpartial (talk) 22:23, 30 January 2023 (UTC)
- To be clear, I am not saying Page is a bad example. If we clearly (in our article) explain that Page is an example of a subject whose name is not a birth name, and avoid raising further questions by explaining why this is so, then it is a great example. If, however, we use Page as an example with zero elaboration as to why we use that example, it loses all instructive value. CapnZapp (talk) 22:15, 30 January 2023 (UTC)
- Oh, come on. The purpose of giving examples is illustrating a point. In order to explain the point (why otherwise make it?) we need to explain an obscure detail that we have agreed to not divulge! The obvious conclusion is to use another example, where we can actually tell our readers what our example is meant to illustrate. CapnZapp (talk) 22:07, 30 January 2023 (UTC)
- For the exclusion of pre-transition names, the difference is precisely that
"one example subject has two last names, the other has one" and "one example includes pronounciation, the other does not"
. The value in those particular examples, as I suggested above, is simply to underline the fact that there is no single formula mandated in this branch of the decision tree, either. Newimpartial (talk) 20:24, 30 January 2023 (UTC)- Thank you for explaining. But... this explanation needs to be provided to the reader of the article, because the point of the example is to convey a point. I certainly didn't understand this given only the examples - after all you needed to explain it to me! Regards, CapnZapp (talk) 22:11, 30 January 2023 (UTC)
- Does that make things clearer for the reader? The assumption I would work with is that a bio lede would follow MOS:FULLNAME and MOS:CHANGEDNAME, but with the stipulation that deadnames/prior names should only be used in very limited circumstances when the person was notable under that name. Do the multiple examples help understand this better? (And there really needs to be a pointer to MOS:GENDERID at MOS:CHANGEDNAME to make clear that pre-transition names are handled differently.) — Carter (Tcr25) (talk) 00:21, 31 January 2023 (UTC)
- I agree that the carveout for pre-transition names of trans people deserves an effective pointer at CHANGEDNAME. Newimpartial (talk) 01:46, 31 January 2023 (UTC)
Do the multiple examples help understand this better?
As explained, the point of having two examples is that they are different. To me it is obvious this needs to be explained to the audience - it isn't enough that we that write the page understand what each example illustrates. Apparently, this obviousness does not extend to everybody. (While I'm not the one suggesting having twoi examples, I have no objections to it; I'm just clarifying that, to my understanding, the purpose of having two examples isn't to help understanding the basic point, it is to illustrate "there is no single formula" when you write such a lead sentence). Regards, CapnZapp (talk) 06:32, 31 January 2023 (UTC)- For the "no notable pretransition name" case, the two examples only illustrate "no single formula", since the difference between the cases doesn’t illustrate anything specific to pretransition names.
- For the "notable pretransition name" case, the examples illustrate subtly different treatment for a birth name vs. a professional name, so they do illustrate a point that is relevant to pretransition names in particular IMO. Newimpartial (talk) 12:20, 31 January 2023 (UTC)
- Okay, I see your point and see the same thing mirrored at MOS:FULLNAME. I edited how the GENDERID examples are presented to parallel how similar examples are presented at FULLNAME and other sections of the article. This makes it clearer to me what is being described and required (and how it aligns/differs from the guidance elsewhere). — Carter (Tcr25) (talk) 13:40, 31 January 2023 (UTC)
- What do you mean by Elliot Page's prior name not being a birth name? Wasn't Page christened "Ellen"? (And weren't we discussing these in the context of Cox/Laverne, not Manning/Page?) CapnZapp (talk) 19:34, 30 January 2023 (UTC)
- Thank you for "preserving the presumed intention", Newimpartial. However, wouldn't you agree your edits lost the explanation of why we have two green examples? That is (with your own words) "one case where the pretransition name is a 'birth name' and one where it is not"...? At least I don't know either of Laverne Cox and Rachel Levine, and wouldn't be able to discern any functional difference between the two examples (other than "one example subject has two last names, the other has one" and "one example includes pronounciation, the other does not") CapnZapp (talk) 19:28, 30 January 2023 (UTC)
Specific guidelines apply to living transgender and non-binary people (see § Gender identity, below).
Late in the previous discussion, a point was raised: shouldn't CHANGEDNAME point to GENDERID?
And so it does (very last line). However, note the word "living" in the current text. Does GENDERID apply to living subjects only or equally to deceased subjects? We afford greater protections to living bio article subjects, is GENDERID one of these?
If the answer is "yes only to living" then GENDERID needs to make this distinction. If the answer is "no; to all" the above line at CHANGEDNAME needs to be edited. (To be clear: I have no opinion either way, I just want to point out this possible discrepancy)
CapnZapp (talk) 06:38, 31 January 2023 (UTC)
- MOS:GENDERID applies to living people ("If a living transgender or non-binary person..."). A large RFC about a year and a half ago found no consensus for changes relating to dead people.--Trystan (talk) 15:35, 31 January 2023 (UTC)
- Probably the existing pointer at CHANGEDNAME should be higher up in the section, perhaps after the red de Blasio example, since it creates a pretty big exception to what's stated upfront and currently falls after a section on changed surnames. — Carter (Tcr25) (talk) 16:56, 31 January 2023 (UTC)
Nationality
Out of no where this format à la "Austrian and American" comes to counter the long established tradition of the hyphen! Goodness gracious ;)
Where and when has this format been decided all of a sudden? Synotia (talk) 09:43, 24 December 2022 (UTC)
- Can you give an example. There is no nation of Austria-America, so Austrian and American or Austrian, American would be the correct way to show dual nationality. A hyphen is often used to describe ethnicity. Is that what you mean? MB 15:33, 24 December 2022 (UTC)
- We write African-American culture for example, yet there is no nation of Africa-America either?
- And has this been decided by a community consensus, or by just one single egghead? Synotia (talk) 16:00, 24 December 2022 (UTC)
- Agree with MB… if we are indicating someone’s ethnic heritage (not encouraged, per MOS:ETHNICITY) then the hyphen would be appropriate, but if we are trying to indicate dual citizenship we would need to link the two nationalities with “and” (and if we are indicating sequential citizenship - ie the person renounced one citizenship for another - I would suggest not trying to do so in one single sentence). Blueboar (talk) 16:05, 24 December 2022 (UTC)
- Note that for ethnicity, MOS:HYPHEN says not to hyphenate:
—Bagumba (talk) 17:41, 24 December 2022 (UTC)Avoid using hyphen to connect racial or ethnic descriptors, regardless of whether or not they are used attributively (Aboriginal Australians, Asian American studies, Black British people).
- Once again, I have no clue who came up with this, it goes against the established consensus on this encyclopedia. For ages people used hyphens and nobody had an issue with it. Only a very very small handful of articles use that weird format. Moreover, outside of Wikipedia I have never encountered it, making it feel made up as hell. --Synotia (moan) 12:49, 7 February 2023 (UTC)
Should MOS:GENDERID apply to a person whose sole notability is due to a heinous crime such as murder or rape?
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
Consider an individual such as Amber McLaughlin (born Scott A. McLaughlin). McLaughlin was executed for the murder and rape of a woman, committed while living as male, only transitioning to female while on death row. You will find a number of other cases of individuals who have transitioned post-incarceration for heinous crimes, although this is the only case (thus far) which has ended in execution. McLaughlin's notability is due to committing heinous crimes; although the primary source of notability is only for being executed for them, being executed for a crime can't really be separated from the crime itself (especially in a case such as this, in which nobody–to my knowledge–is suggesting this was the execution of an innocent person). (Technically MOS:GENDERID doesn't apply to McLaughlin, since it only applies to living persons–but I'm trying to raise a broader point here than just that one individual case.)
Here are some arguments why MOS:GENDERID should not apply in such cases:
- In very many cases, the victim or their family will be offended by extending recognition to the murderer/rapist's newly claimed identity
- Many victims of similar crimes will be offended – many female victims of male sexual violence (and their supporters) have expressed opposition to the recognition of such identity claims by perpetrators
- The intention behind the policy is to extend respect to transgender people; I don't think making an exception in these narrow cases exhibits any disrespect to transgender people in general. On the contrary, unequivocally accepting these individuals' claimed transgender identities may actually promote transphobia
Note, I am only suggesting we should carve out an exception for heinous crimes such as murder, rape, child abuse, etc, not for less inherently abhorrent offences. Such an exception would not apply to e.g. Chelsea Manning, since whatever your view on her criminal convictions, few would seriously suggest they are on the same level as rape or murder. I was thinking about filing an RFC on this topic, but thought it would be better to raise it informally for discussion first. SomethingForDeletion (talk) 23:46, 6 February 2023 (UTC)
- Misgendering someone – for any reason – disrespects all transgender people. Deciding it is alright to misgender someone based on crimes they did implies having your identity recognized is a privilege that can be taken away, which should not be the case.
- Furthermore (and maybe more important for Wikipedia) deadnaming and misgendering someone is factually wrong. Amber McLaughlin isn't not a woman because she is notable for committing horrible crimes. We don't misgender cis people who do horrible crimes, there is no reason this should change for trans people, unless Wikipedia decides transgender individuals are not really the gender they identify as, which is obviously incorrect. Catgirl-su (talk) 18:24, 7 February 2023 (UTC)
Disagree We at Wikipedia don't offer extrajudicial punishment by imposing a different set of standards to convicted criminals than to other people. This should be SNOWBALL closed. CapnZapp (talk) 19:50, 7 February 2023 (UTC)- I think, as with most things, it comes down to what reliable sources say, and ultimately WP:Consensus is the foundation. If the preponderance of reliable sources cease to recognise the transition as 'genuine' for some reason, then we could clearly discuss reflecting that in the article. But what you're discussing is a fringe case among fringe cases (fringe2), the MOS will never cover every single eventuality. JeffUK 21:59, 8 February 2023 (UTC)
- WP:Ignore all rules. I agree with JeffUK that we should follow how the topic is described in the preponderance of reliable sources. If the MOS guide attempting to be respectful to people with gender dysphoria means that we're helping a criminal obfuscate their crimes for posterity, then ignore the MOS. Cuñado ☼ - Talk 15:54, 9 February 2023 (UTC)
- It seems to me that a person who committed a heinous crime under their former name is de facto notable under that former name (provided of course that the crime is attested by reliable sources), and thus the mention of that former name is covered by the existing wording of GENDERID. Rosbif73 (talk) 16:15, 9 February 2023 (UTC)
- Also disagree for the same reasons everyone else does. There's no problems with the existing policy. Loki (talk) 02:47, 10 February 2023 (UTC)
Proposed GENDERID text revision redux
Per EddieHugh's request, below is proposed revised text based off what consensus here was showing, but edited to address their concerns.
When a living transgender or non-binary person's former name is not notable, that name should not be included in the article. For example:
When a living transgender or non-binary person was not notable under theirpretransistionpretransitionname, that name should not be included in the article.
For example:
- From Laverne Cox: Laverne Cox (born May 29, 1972) ...
- From Rachel Levine: Rachel Leland Levine (/ləˈviːn/; born October 28, 1957) ...
- Avoid:
Not notable, do not use:Jane Smith (formerly John Hammer, born May 1, 1980) ...
In the case of a living transgender or non-binary person who was notable under theirpriorformer name, that namemayshould be included in the lead sentence of their main biographical article. Introduce thepriorformer name with "born" if they were notable under their birth name or "formerly" if notable under apriorformer professional name, stage name, or pseudonym. For example:
In the case of a living transgender or non-binary person who was notable under their birth name or a former professional name, stage name, or pseudonym, that name should be included in the lead sentence of their main biographical article. Introduce the prior name with either "born" or "formerly". For example:
- From Chelsea Manning, notable under birth name: Chelsea Elizabeth Manning (born Bradley Edward Manning, December 17, 1987) ...
- From Elliot Page, notable under
priorformer professional name: Elliot Page (formerly Ellen Page; born February 21, 1987) ...
Thoughts, objections, concerns? CapnZapp, Newimpartial —Carter (Tcr25) (talk) 14:58, 1 February 2023 (UTC)
- I think using the old language for the first case, like "when a living ... person was not notable under a pretransition name, that name..." is more precise (and therefore better) than your proposal. The test is the notability of the person while using the name, not the "notability of the name itself" (whatever that would mean). Newimpartial (talk) 15:32, 1 February 2023 (UTC)
- Okay, adjusted above... Does using "pretransistion name" instead of "prior name" create any gray areas around gender change without a medical transition? —Carter (Tcr25) (talk) 16:09, 1 February 2023 (UTC)
- I wouldn't have thought so, since the relevant transition here is social, rather than legal or medical for example. But I would like others to weigh in. Newimpartial (talk) 16:19, 1 February 2023 (UTC)
- "pretransition" is misspelled "pretransistion"
- I would have thought that the usage of green/red text is standard and that the reader can be assumed to understand its meaning (actually, is green/red text color-blind-friendly?), but okay - if MOS generally explains examples in red as "don't actually write this, this is an example of how to do it wrong" then we should definitely repeat that here as well. If this would be an isolated case, however, I think the explanation "do not use" from "Not notable, do not use:" should be removed.
- I like how the new text avoids claiming Page's prior name is not a birth name, since we appear unwilling to actually explain that.
- I like how the new text explicitly tells us when to use "born" and when to use "formerly". (Just wanted to point out this, since the new text adds a rule that wasn't there before. Previously there wasn't an actual rule against using other words than "born" for the notable under their birth name case - we just stated editors should use "born" or "formerly". The examples hinted at which word to use where, but examples aren't rules. And to be ultra clear: I have no objections, I just want to raise awareness in case anyone missed the fact the suggested edit doesn't just change the presentation of the MOS rules, it actually changes them)
- I concur with Newimpartial's objection.
- CapnZapp (talk) 17:55, 1 February 2023 (UTC)
- Thanks. I've fixed the spelling. Looking at other examples on the page, some red text is introduced in the sentence preceding it with "do not use" or similar language. Others (particularly when paired with a green text example) it's introduced with Avoid on the same line, so changed to that. —Carter (Tcr25) (talk) 19:04, 1 February 2023 (UTC)
- Thank you for bringing the discussion back here. Comments:
- Is "When a living transgender ... For example:" needed? Most of that is in the existing "If a living transgender ... the person's current name" paragraph. Would adding "For example:" to the existing paragraph be enough?
- The current "...former name should be included in the lead sentence of their main biographical article only if they were notable under it" isn't very clear in its use of "should", but it differs significantly from the proposed "that name may be included in the lead sentence" ('should' versus 'may').
- I'm not sure about adding "pretransition name" to the list of terms used: what counts as "transition"? But then there's already "transition" in the same section. EddieHugh (talk) 23:09, 1 February 2023 (UTC)
- I agree that the first sentence of the proposed text is not needed, as it just repeats the existing "If a living transgender or non-binary person was not notable..." sentence. I also think that shifting from "should" to "may" reduces clarity and is likely to lead to unnecessary disputes about when to include the former name. The section as written establishes that by "former name" we mean a deadname. The proposed text would result in switching between "former name", "pretransition name" and "prior name", which reduces clarity. Finally, I oppose mandating that birth names be introduced with "born", as opposed to the current guidance which says both "born" and "formerly" are appropriate, leaving the choice up to the editors of a particular article.--Trystan (talk) 23:59, 1 February 2023 (UTC)
- Comment: Yes, with
Just wanted to point out this, since the new text adds a rule that wasn't there before.
above I hope to have helped made sure this change didn't fly under the radar. (Unlike you Trystan I don't mind the change, but then again, I don't have a strong opinion either way). CapnZapp (talk) 07:10, 2 February 2023 (UTC)
- Comment: Yes, with
- Okay, tried to address the seemingly repetitive first sentence, use former name throughout, and replace may with should when talking about someone notable under a former name.
- Regarding formerly vs. born. The examples as MOS:CHANGEDNAME all use born for birth names, as does MOS:NEE. The discussion of "also known as" names at CHANGEDNAME and MOS:PSEUDONYM puts a different emphasis on the professional or stage name (e.g., Timothy Alan Dick (born June 13, 1953), known professionally as Tim Allen) than I think is what's intended in GENDERID. To my mind, presenting "born" as the proper word for a birth name aligns with the rest of MOS:BIO and "formerly" covers well the instances when the notable name is something other than a birth name. Can you provide an example of a case where it makes more sense to use "formerly" for a birth name or "born" for a stage name? —Carter (Tcr25) (talk) 00:55, 2 February 2023 (UTC)
- Just to point out that examples can't make rules (or at least, shouldn't). That is, just because all examples use X doesn't mean there is a rule saying "you must use X"... unless there actually is rules text to that effect. We can't (shouldn't) expect readers to infer rules from examples. (I have no opinion either way; just want to keep the level of clarification high throughout this discussion, which I'm mostly monitoring so my proposed changes aren't lost half way) CapnZapp (talk) 07:06, 2 February 2023 (UTC)
- Can you suggest a better way to phrase things then? The existing text at GENDERID says
introduce the name with "born" or "formerly":
. MOS:BIRTHDATE saysBirth and death labels are included only when needed for clarity. When given, use full words, whether immediately preceding a date or not:
(which is referring to writing out "born" instead of using "b."). Examples may not be "rules", but they demonstrate the proper application of the rules to help aid in understanding them and almost every time a birth name is used in the examples when the person is known by a different name, "born" is used to mark the birth name. The only exception is MOS:NEE says specifically, when a birth name is given for someone who's changed their surname,Editors may denote this [the birth name] with "born" ...
or, if the surname change is due to marriage, né or née may be used instead of born. (The conditional may is used here because of the exception for when né/née might be used instead.) - CapnZapp, as I see it, it's not a new rule, just a clarification that aligns with the rest of the MOS. The current GENDERID text specifies to use either born or formerly. The only difference is the revision specifies "born" for use with (notable) birth names (which is in alignment with the rule at MOS:NEE and the examples that illustrate the rules at BIRTHDATE, CHANGEDNAME, etc.), leaving "formerly" for use with other sorts of former (notable) names. Are there any cases where this would be problematic or where an editor would reasonably choose to use the words differently? Or should "may" be being used here instead of "should" (to mirror the verbs in MOS:NEE)?— Carter (Tcr25) (talk) 14:45, 2 February 2023 (UTC)
- Can you suggest a better way to phrase things then? The existing text at GENDERID says
- Just to point out that examples can't make rules (or at least, shouldn't). That is, just because all examples use X doesn't mean there is a rule saying "you must use X"... unless there actually is rules text to that effect. We can't (shouldn't) expect readers to infer rules from examples. (I have no opinion either way; just want to keep the level of clarification high throughout this discussion, which I'm mostly monitoring so my proposed changes aren't lost half way) CapnZapp (talk) 07:06, 2 February 2023 (UTC)
- Trystan, can you elaborate on your last point (let editors choose when to use born or when to use formerly)? Is there an instance where born would be used for a stage name? Or where formerly would be more appropriate for a birth name? How do you see this deviating from the rest of MOS:BIO, such as the statement at MOS:NEE to use born, unless you're dealing with a surname change due to marriage where né/née may be used instead? I'm seeing this not as a rule change but a clarification that aligns with the rest of MOS:BIO, but if there are cases where it doesn't work I'd appreciate being educated about them. — Carter (Tcr25) (talk) 14:25, 3 February 2023 (UTC)
- The current guidance to use either born or formerly came from a compromise solution achieved in this RFC, which discussed the different connotations born can have for trans individuals. I have no objection to testing if that consensus has changed (in either direction), but I suggest it be done through an RFC.--Trystan (talk) 14:52, 3 February 2023 (UTC)
- Thanks, I hadn't located that discussion. I've revised again to reflect that RFC; however, I also went back to "prior name" in one instance here so as not to have a soft implication that "former name" was connected to use of "formerly" (which was the assumption I was working under). —Carter (Tcr25) (talk) 15:51, 3 February 2023 (UTC)
- Just so that we have everything on the table at once: yes, the 2015 RfC mandated "born" or "formerly", but it didn't mandate specific guidance about when to use one or the other, nor did it come to any particilar conclusion about the possible connotations of "born".
- Also, the most recent prior discussion of this guidance, which resulted in the status quo text and determined the current selection of examples, was this one. Newimpartial (talk) 16:20, 3 February 2023 (UTC)
- Thanks, Newimpartial, I think with the revisions above there's nothing in conflict with either of those RfCs, but the changes still add some clarity, including the Avoid example, in response to the concerns CapnZapp raised in the "please explain (GENDERID examples)" discussion. — Carter (Tcr25) (talk) 18:19, 3 February 2023 (UTC)
- I'm fine with that. Newimpartial (talk) 18:31, 3 February 2023 (UTC)
- Looks good to me as well.--Trystan (talk) 20:04, 3 February 2023 (UTC)
- Thanks, Newimpartial, I think with the revisions above there's nothing in conflict with either of those RfCs, but the changes still add some clarity, including the Avoid example, in response to the concerns CapnZapp raised in the "please explain (GENDERID examples)" discussion. — Carter (Tcr25) (talk) 18:19, 3 February 2023 (UTC)
- The current guidance to use either born or formerly came from a compromise solution achieved in this RFC, which discussed the different connotations born can have for trans individuals. I have no objection to testing if that consensus has changed (in either direction), but I suggest it be done through an RFC.--Trystan (talk) 14:52, 3 February 2023 (UTC)
- I agree that the first sentence of the proposed text is not needed, as it just repeats the existing "If a living transgender or non-binary person was not notable..." sentence. I also think that shifting from "should" to "may" reduces clarity and is likely to lead to unnecessary disputes about when to include the former name. The section as written establishes that by "former name" we mean a deadname. The proposed text would result in switching between "former name", "pretransition name" and "prior name", which reduces clarity. Finally, I oppose mandating that birth names be introduced with "born", as opposed to the current guidance which says both "born" and "formerly" are appropriate, leaving the choice up to the editors of a particular article.--Trystan (talk) 23:59, 1 February 2023 (UTC)
- Thank you for bringing the discussion back here. Comments:
- Thanks. I've fixed the spelling. Looking at other examples on the page, some red text is introduced in the sentence preceding it with "do not use" or similar language. Others (particularly when paired with a green text example) it's introduced with Avoid on the same line, so changed to that. —Carter (Tcr25) (talk) 19:04, 1 February 2023 (UTC)
- I wouldn't have thought so, since the relevant transition here is social, rather than legal or medical for example. But I would like others to weigh in. Newimpartial (talk) 16:19, 1 February 2023 (UTC)
- Okay, adjusted above... Does using "pretransistion name" instead of "prior name" create any gray areas around gender change without a medical transition? —Carter (Tcr25) (talk) 16:09, 1 February 2023 (UTC)
- Maybe I'm just slow today, but I'm struggling to understand what the strikeouts at the start are meant to communicate. What would come before "For example?" Both suggestions are struck out. What would that be an example of? - Astrophobe (talk) 17:44, 3 February 2023 (UTC)
- Sorry, those were parts of the initial draft struck in response to comments and questions. The striking of everything but "For Example:" was because others felt the proposed line was too repetitive of an existing paragraph that wasn't being considered for change. So, now "For example:" would follow the existing "
If a living transgender or non-binary person was not notable under a former name (a deadname), it should not be included in any page (including lists, redirects, disambiguation pages, category names, templates, etc.), even in quotations, even if reliable sourcing exists. Treat the pre-notability name as a privacy interest separate from (and often greater than) the person's current name.
" — Carter (Tcr25) (talk) 18:07, 3 February 2023 (UTC)
- Sorry, those were parts of the initial draft struck in response to comments and questions. The striking of everything but "For Example:" was because others felt the proposed line was too repetitive of an existing paragraph that wasn't being considered for change. So, now "For example:" would follow the existing "
Any further thoughts/concerns/edits, or does this look good to deploy? Clean (hopefully) final version (with the existing, unchanged preceding) below ... CapnZapp, EddieHugh —Carter (Tcr25) (talk) 14:17, 6 February 2023 (UTC)
If a living transgender or non-binary person was not notable under a former name (a deadname), it should not be included in any page (including lists, redirects, disambiguation pages, category names, templates, etc.), even in quotations, even if reliable sourcing exists. Treat the pre-notability name as a privacy interest separate from (and often greater than) the person's current name. For example:
- From Laverne Cox: Laverne Cox (born May 29, 1972) ...
- From Rachel Levine: Rachel Leland Levine (/ləˈviːn/; born October 28, 1957) ...
- Avoid: Jane Smith (formerly John Hammer, born May 1, 1980) ...
In the case of a living transgender or non-binary person, their birth name or former name (professional name, stage name, or pseudonym) should only be included in the lead sentence of their main biographical article if they were notable under that name. Introduce the prior name with either "born" or "formerly". For example:
- From Chelsea Manning, notable under birth name: Chelsea Elizabeth Manning (born Bradley Edward Manning, December 17, 1987) ...
- From Elliot Page, notable under former professional name: Elliot Page (formerly Ellen Page; born February 21, 1987) ...
Comment - I don't blame you for not knowing the tedious background, but many editors would regard your change to the final intro paragraph, from should only be included if
to In the case of .... should be included
as substantive and, given the background, even as requiring its own RfC. (The former only sets limits on inclusion, while the latter positively mandates inclusion when the condition is met - at least, that is how many of us read that policy language.) Newimpartial (talk) 14:28, 6 February 2023 (UTC)
- I don't read it that way. Both the existing text and the revision use "should" with the same limitation on inclusion (when the person was notable under the former name). That said, does this improve it for you? "If a living transgender or non-binary person was notable under their birth name or a former professional name, stage name, or pseudonym, only then should that name be included in the lead sentence of their main biographical article." —Carter (Tcr25) (talk) 14:44, 6 February 2023 (UTC)
- That's marginally better, but I'd be much more comfortable with, "In the case of a living transgender or non-binary person, their birth name or former name (professional name, stage name, or pseudonym) should should only be included in the lead sentence of their main biographical article if they were notable under that name." Newimpartial (talk) 15:42, 6 February 2023 (UTC)
- Thanks, that works for me (and has been inserted above). —Carter (Tcr25) (talk) 15:56, 6 February 2023 (UTC)
- Can that be changed to "in the lead" rather than specifically saying the lead sentence? For example, if someone was somewhat notable under their former name and if their lead sentence is already stuffed with more notable aspects of their life post transition then we might not want to put the former name in the very first sentence. I think it would be best to make this a "best but not mandatory" MOS practice. Springee (talk) 23:53, 6 February 2023 (UTC)
- MOS:GENDERID currently specifies "in the lead sentence." MOS:FULLNAME says "should usually be given in the lead sentence," so there is wiggle room elsewhere in MOS:BIO... What do others think? —Carter (Tcr25) (talk) 02:02, 7 February 2023 (UTC)
- Can that be changed to "in the lead" rather than specifically saying the lead sentence? For example, if someone was somewhat notable under their former name and if their lead sentence is already stuffed with more notable aspects of their life post transition then we might not want to put the former name in the very first sentence. I think it would be best to make this a "best but not mandatory" MOS practice. Springee (talk) 23:53, 6 February 2023 (UTC)
- Thanks, that works for me (and has been inserted above). —Carter (Tcr25) (talk) 15:56, 6 February 2023 (UTC)
- That's marginally better, but I'd be much more comfortable with, "In the case of a living transgender or non-binary person, their birth name or former name (professional name, stage name, or pseudonym) should should only be included in the lead sentence of their main biographical article if they were notable under that name." Newimpartial (talk) 15:42, 6 February 2023 (UTC)
User:Tcr25, I have concerns about Rachel Levine being used as an example above. She was an academic researcher into eating disorders pre-transition, and published a number of articles in medical journals under her birth name. Obviously pre-transition she was a lot less notable than now, but I'm not sure she was entirely non-notable – and I think that's a rather different situation from someone like Laverne Cox, who as far as I am aware was a complete nobody pre-transition. A person might be interested in Levine's academic career/research/publications, and a person who wants to pursue that interest would need to know what name she published much of her work in that area under. By contrast, a person's reasons for knowing Cox's birth name couldn't be anything other than interest in celebrity trivia. SomethingForDeletion (talk) 23:06, 6 February 2023 (UTC)
- Notable in the guideline links to WP:GNG, which is a specific and well-defined threshold to meet. The consensus at the subject's article seems quite stable that she was not notable under her former name, so I think the example stands.--Trystan (talk) 23:55, 6 February 2023 (UTC)
- I don't have a strong feeling either way. If there's an alternate person you can suggest who is relatively high profile and would serve equally well to illustrate things, please suggest them. That said, and as Tyrstan noted, the consensus seems to be that Levine fits the case of not notable under her prior name. (She's also one of the existing examples on the article, so she's not a new example here.) —Carter (Tcr25) (talk) 01:48, 7 February 2023 (UTC)
- I think examples in the MOS should be really clearcut cases. I agree Laverne Cox is such a case but not convinced that Rachel Levine is one. I don't think the consensus on Levine's article is necessarily dispositive as to whether it is a "clearcut case". If we can't find another example to replace it with, I think just having the Laverne Cox example is enough. SomethingForDeletion (talk) 09:37, 7 February 2023 (UTC)
- You can see the discussion above why it is desirable to have more than example to show there isn't a single set format. I'm not opposed to changing the example, but would need some suggestions about who to use instead. In the meantime, since the Levine example doesn't change what's already in the MOS, I wouldn't hold up the rest of the changes over this example. —Carter (Tcr25) (talk) 13:03, 7 February 2023 (UTC)
- Given the repeatedly-estsblished consensus at Talk:Rachel Levine that her pretransition name is not notable, and its consistent exclusion from the article, I think the example is a good one. Newimpartial (talk) 13:34, 7 February 2023 (UTC)
- You can see the discussion above why it is desirable to have more than example to show there isn't a single set format. I'm not opposed to changing the example, but would need some suggestions about who to use instead. In the meantime, since the Levine example doesn't change what's already in the MOS, I wouldn't hold up the rest of the changes over this example. —Carter (Tcr25) (talk) 13:03, 7 February 2023 (UTC)
- I think examples in the MOS should be really clearcut cases. I agree Laverne Cox is such a case but not convinced that Rachel Levine is one. I don't think the consensus on Levine's article is necessarily dispositive as to whether it is a "clearcut case". If we can't find another example to replace it with, I think just having the Laverne Cox example is enough. SomethingForDeletion (talk) 09:37, 7 February 2023 (UTC)
Given that discussion seems to have died out on this, I've moved the stable version of the examples and intro text to the MOS page. —Carter (Tcr25) (talk) 16:34, 10 February 2023 (UTC)
- "should only be included in the lead sentence of their main biographical article if they were notable" would be less ambiguous as "should be included in the lead sentence of their main biographical article only if they were notable". That would also match the previous wording. EddieHugh (talk) 17:26, 11 February 2023 (UTC)
- I find the present text less ambiguous than the prior language, for what it's worth. Newimpartial (talk) 17:37, 11 February 2023 (UTC)
- The first makes the inclusion conditional; the second highlights the condition to be met for inclusion. I think the effect are the same either way (the only reason to include a deadname is because the person was previously notable under it), just maybe a difference in which you stress. Neither feels more or less ambiguous to me. —Carter (Tcr25) (talk) 18:09, 11 February 2023 (UTC)
- The ambiguity: is inclusion to be in the lead sentence and nowhere else if the person was notable under that name ("only... in the lead sentence"), or does inclusion in the lead sentence require the person to be notable under that name ("only if... notable")? We mean the latter, I think. EddieHugh (talk) 22:12, 11 February 2023 (UTC)
- I restored this phrase to how it was ordered before the recent changes. Crossroads -talk- 00:29, 13 February 2023 (UTC)
- The ambiguity: is inclusion to be in the lead sentence and nowhere else if the person was notable under that name ("only... in the lead sentence"), or does inclusion in the lead sentence require the person to be notable under that name ("only if... notable")? We mean the latter, I think. EddieHugh (talk) 22:12, 11 February 2023 (UTC)
- The first makes the inclusion conditional; the second highlights the condition to be met for inclusion. I think the effect are the same either way (the only reason to include a deadname is because the person was previously notable under it), just maybe a difference in which you stress. Neither feels more or less ambiguous to me. —Carter (Tcr25) (talk) 18:09, 11 February 2023 (UTC)
- I find the present text less ambiguous than the prior language, for what it's worth. Newimpartial (talk) 17:37, 11 February 2023 (UTC)
Sex in CONTEXTBIO?
MOS:CONTEXTBIO doesn’t make mention of sex (or gender), but it seems like there would be no reason not to treat it the same. We don’t need to clarify someone as a “female soccer player” or “female scientist”, except in cases like “first woman to win a Nobel Prize” (and so on). Am I missing something, or is this sort of consideration so obvious to be CREEPy? — HTGS (talk) 04:16, 2 January 2023 (UTC)
We don’t need to clarify someone as a “female soccer player” or “female scientist”
— but we do categorise them (Category:Women's association football players, Category:Women scientists) and thus we should define them as such. Mitch Ames (talk) 05:06, 2 January 2023 (UTC)- @Mitch Ames I am not talking about categorization, but about the text (and specifically the lead sentence) of a biography, per MOS:CONTEXTBIO. And specifically, I am wondering out loud whether CONTEXTBIO should explicitly advise against including gender in the lead sentence. Whether or not people are put into gendered categories is of no concern to me. — HTGS (talk) 01:41, 11 February 2023 (UTC)
- Would this idea also apply to trans people? Would we no longer state “X is a trans-female soccer player” or “Y is a trans-male actor”? Blueboar (talk) 02:05, 11 February 2023 (UTC)
- I would assume that in most cases of trans athletes, their gender would be central or pertinent to their notability. This may also be true of trans people generally, but it would still align with people like Rachel Levine, who is notable (largely) independent of her gender, and whose lead paragraph currently does not mention that she is a trans woman.
- FWIW I didn’t pose the question with trans people in mind (I had just made this edit
… is a New Zealand
) so a carveout for trans bios would be fine by me. Eg, a footnote like “femalerugby union playerfor trans individuals this guideline may not always apply
”. But I do feel that CONTEXTBIO's current wording (gender … should generally not be in the lead sentence unless relevant to the subject's notability
) would cover it well enough for the good judgment of good editors. — HTGS (talk) 02:32, 14 February 2023 (UTC) - And, to be especially clear, I was (and am) posing an open question. The addition of gender seems to logically follow for me, but reasonable minds may differ. — HTGS (talk) 02:39, 14 February 2023 (UTC)
Avoiding thingies
Do you need to avoid Bill Gates III? ErceÇamurOfficial (talk) 18:41, 7 March 2023 (UTC)
- Could you please clarify the question. Do you mean that we should avoid referring to "Bill Gates III" at all, or possibly not use "William Henry Gates III" in that article"?
- Relevant MOS guidelines include MOS:NAME, MOS:FULLNAME, MOS:JR, WP:COMMONNAME.
- Mitch Ames (talk) 23:38, 7 March 2023 (UTC)
Additions to JOBTITLES
Hi, an extra paragraph was added to WP:JOBTITLES in this edit, likely a response to a dispute I had with the editor over applying JOBTITLES to position leads following the use of "The". There was no discussion over this paragraph so unsure whether it is against consensus or a worthy inclusion. Or simply put, can such addition be checked, it seems to be a rewording of the third point above the examples table but excluding the exceptions, does this paragraph now argue that it should be capped even after using "the" or "a"? Third point above, stated it can be capitalised when it is not preceded by a modifier (including a definite or indefinite article)
. DankJae 00:33, 10 March 2023 (UTC)
Changes to 'Context'
These need to be discussed. The current wording is STABLE. Changing guidelines whilst involved in a dispute related to those guidelines (see Wikipedia talk:WikiProject Football#user:Skyerise) is incredibly poor form. GiantSnowman 16:42, 11 March 2023 (UTC)
- Not providing proper nationality context when possible leaves readers confused. I proposed that several uses of "usually" be change to "where possible" to prevent intentional omission of relevant nationality (-ies) by recalcitrant editors who assume every reader is going to know the relevant football nationality rules. The way it is being done is totally unclear. Skyerise (talk) 16:47, 11 March 2023 (UTC)
- Question: is this dispute about what categories to use or about how to phrase the opening text of the article? Blueboar (talk) 17:48, 11 March 2023 (UTC)
- In a way, both. Having the nationalities clearly stated, rather than assumed from football rules (note that the players on other than national teams are treated differently and typically state the nationality up front), leaves no ambiguity about which nationality categories should be included. The way it is being presented makes it unclear where the subject is playing as a national and where they are playing as an expatriate, making it difficult to select or verify the correct categories. Skyerise (talk) 18:07, 11 March 2023 (UTC)
- Ok, so the next question is: does it matter whether a player is playing as a national or as an expatriate (and if so, why does it matter)? Blueboar (talk) 18:57, 11 March 2023 (UTC)
- Skyerise is not correct here. A player with unambiguous nationality will be described as e.g. 'English footballer', regardless whether they play at club or international level. A player born in country X but who plays for country Y due to (most often) parentage will be described as above. This is how it has been done for years, covers tens of thousands of articles, and has never caused confusion (as far as I am aware). GiantSnowman 19:29, 11 March 2023 (UTC)
- It's also perhaps worth noting that the expats almost certainly have press documenting their actual citizenship, but the players of "unambiguous nationality" (the ones for whom all documented life activities occur within some particular country) may well not, because it's so obvious that nobody feels the need to say it explicitly. Unless we have a source explicitly stating that they are a citizen of some country, or stating their birthplace in a jus soli country, all we can go on is where they flourished. So leaving it somewhat ambiguous (calling them an "English footballer" rather than a "citizen of the UK who plays football for England", say) can be an accurate reflection of our sourcing. —David Eppstein (talk) 22:40, 11 March 2023 (UTC)
- My complaint is that, contrary to what GiantSnowman has stated, is that at least some articles, no nationality is being stated before the profession as indicated by WP:CONTEXTBIO. Saying something like "born in X, plays for Y", where the subject is a citizen of both, requires that the reader know that "plays for Y" implies "is a citizen of Y". There is no logical reason for not being explicit. There is a reason for being explicit - without this even an experienced editor who happens to know nothing about football may misconstrue what categories are appropriate. Obviously, a reader who knows nothing about football will not necessarily come away with the fact that the subject holds dual citizenship. That's the whole point of WP:CONTEXTBIO - to make sure that the context is clear without assuming knowledge on the part of the reader. Reverting the clarification of nationality is edit-warring that verges on vandalism (since the OP called me a vandal for trying to improve the article). The only possible problem I see here is if they were born in a country that requires them to relinquish their citizenship when repatriating, but that can be determined from the relevant nationality law article.It's my understanding that very few countries require this in these modern times. Skyerise (talk) 17:19, 12 March 2023 (UTC)
- Does anybody besides GiantSnowman have a problem with my revisions to Kenneth Paal and Eduardos Kontogeorgakis. Is there some valid reason not to follow WP:CONTEXTBIO here? Skyerise (talk) 17:32, 12 March 2023 (UTC)
- It's also perhaps worth noting that the expats almost certainly have press documenting their actual citizenship, but the players of "unambiguous nationality" (the ones for whom all documented life activities occur within some particular country) may well not, because it's so obvious that nobody feels the need to say it explicitly. Unless we have a source explicitly stating that they are a citizen of some country, or stating their birthplace in a jus soli country, all we can go on is where they flourished. So leaving it somewhat ambiguous (calling them an "English footballer" rather than a "citizen of the UK who plays football for England", say) can be an accurate reflection of our sourcing. —David Eppstein (talk) 22:40, 11 March 2023 (UTC)
- Skyerise is not correct here. A player with unambiguous nationality will be described as e.g. 'English footballer', regardless whether they play at club or international level. A player born in country X but who plays for country Y due to (most often) parentage will be described as above. This is how it has been done for years, covers tens of thousands of articles, and has never caused confusion (as far as I am aware). GiantSnowman 19:29, 11 March 2023 (UTC)
- Ok, so the next question is: does it matter whether a player is playing as a national or as an expatriate (and if so, why does it matter)? Blueboar (talk) 18:57, 11 March 2023 (UTC)
- In a way, both. Having the nationalities clearly stated, rather than assumed from football rules (note that the players on other than national teams are treated differently and typically state the nationality up front), leaves no ambiguity about which nationality categories should be included. The way it is being presented makes it unclear where the subject is playing as a national and where they are playing as an expatriate, making it difficult to select or verify the correct categories. Skyerise (talk) 18:07, 11 March 2023 (UTC)
Nationality issues
Hi All, There are numerous discussions going on both on wiki talk pages, via wiki (near) edit wars and within the art-world and in the media regarding reclassifying Ukrainian born persons (artists, chess players etc), current labelled as Russian. This could also impact other persons subject to historic colonial, conquered and other disputed areas. I think we need some clarity and potentially some individual ruling in some cases. So, can someone provide some expert guidance on the MOS.
Example Talk:Kazimir Malevich born in Kyiv, then part of the Russian empire, to Polish parent (does not clarify where they were born), studied in Russia, calls himself Ukrainian, was part of a Russian school (style of art, not educational)
Cheers 2404:4408:638C:5E00:75C2:43D3:364F:F481 (talk) 05:11, 15 March 2023 (UTC)
- This is a complicated issue, by no means limited to Ukraine. I have ancestors in Europe whose birth places changed names as borders shifted, e.g., Gavrylyak, Polish White Russia. In such cases, should articles use the name at birth? The name at the time of writing? --Shmuel (Seymour J.) Metz Username:Chatul (talk) 12:43, 15 March 2023 (UTC)
- The article should give historical names and current names - example: “He was born in what was then Oldname, Russia (now Newname, Ukraine…”)” If necessary, explain it in more than one sentence. Blueboar (talk) 13:07, 15 March 2023 (UTC)
- This is what I would have said, if Blueboar hadn't beaten me to it. — JohnFromPinckney (talk / edits) 14:09, 15 March 2023 (UTC)
- MOS:NATIONALITY states that the opening sentence should refer to the country of which the person was a citizen when they became notable. It also says "in controversial or unclear cases, nationality is sometimes omitted."
- I looked at Kazimir Malevich and I noticed that the opening sentence says he was a Russian avant-garde artist, with the hyperlink to Russian avant-garde. While his citizenship cannot have been Ukrainian at a time that Ukraine wasn't legally a country, this does not stop him being a member of the artistic Ukrainian avant-garde. He is the first person named on the Ukrainian avant-garde page so was certainly notable for it. So for this specific example I wonder if a formulation such as
would be more informative, less contentious, and remain consistent with guidance. I don't know if a similar formulation would help for the other discussions you mention. --Mgp28 (talk) 13:22, 15 March 2023 (UTC)Kazimir Severinovich Malevich (23 February [O.S. 11 February] 1879 – 15 May 1935) was an artist in the Ukrainian avant-garde...
- Actually, reading the whole first paragraph for Kazimir Malevich it seems he is considered an artist of both the Russian avant-garde and the Ukrainian avant-garde, so what I suggested might not help. Either way, given that Russian avant-garde is a single hyperlink, the word Russian already appears to be being used as an adjective for the art movement not the artist, so changing the word order as I suggested might at least make this clearer. --Mgp28 (talk) 13:31, 15 March 2023 (UTC)
- Hi Mgp28 I am not sure at all that your statement "x wasn't legally a country", is the correct approach, forced or coercive citizenship is not necessarily what I would regard as my guide to "real" nationality or the heart is.121.98.30.202 (talk) 08:49, 16 March 2023 (UTC)
- In this case, where an artist was clearly contributory to both Russian and Ukranian avant-garde movements, those facts seem more relevant to the context of the artist's life and importance than any direct statement about the artist's citizenship and/or nationality. I think Mgp28 is therefore likely to be on the right track. Newimpartial (talk) 13:01, 27 March 2023 (UTC)
Nationality issues again
Could some outsiders please comment on what is the proper way to introduce Christopher Columbus (1451—1506) when taking into account WP:MOSBIO? On the talk page there's been a year-long continuous discussion over whether Columbus should be introduced as 'Genoese' or 'Italian', which are the two most frequently used adjectives in literature. There is a general consensus that Columbus came from the Republic of Genoa, one of the Maritime republics on the northern Italian peninsula, though his origins are sometimes disputed (see the article Origin theories of Christopher Columbus), and he later moved to Iberia working for the Crown of Castile. There's also plenty of sources that suggest the origins of Italian nationalism can be traced back to the Renaissance which was already underway in Columbus' lifetime. My position has been to introduce him by 'Genoese', and I've tried to impose a middle ground solution by removing nationality altogether, but such edits always get reverted back to 'Italian' instantly. WP:MOSBIO has been introduced to the discussion only recently, but there is ongoing discussion over the proper interpretation, with some even questioning the guideline itself. Machinarium (talk) 14:10, 26 March 2023 (UTC)
- I will take a leaf out of the long story over at Nicolaus Copernicus (go trough the talk-page archives if you want, but it's a tedious read)...and would say that labeling him as a "Renaissance explorer" might be an approach that could at least be tried (if it hasn't been tried before, I haven't looked). Lectonar (talk) 13:08, 27 March 2023 (UTC)
Native American
I'm interested in reading the discussion that led to Native American citizenships being added to CONTEXTBIO, but I can't seem to find it. Anybody know of it's location? – 2.O.Boxing 07:26, 20 March 2023 (UTC)
- It was discussed here: . Looks like there were no objections and even an approval (from me). I've restored it on the page, since it was discussed when it was added, we should have a discussion as to whether to remove it. Pretty sure it comes from a related Wikiproject's existing standards. Skyerise (talk) 11:30, 27 March 2023 (UTC)
- We just (last month) had a longer discussion about this on one of our various noticeboards … but I can’t locate which noticeboard it was on. Consensus was mixed. Blueboar (talk) 11:43, 27 March 2023 (UTC)
- I've noticed it's getting harder and harder to find old stuff. So many changes since the early days... Skyerise (talk) 12:53, 27 March 2023 (UTC)
- I found what Skyerise linked above, the proposal to upgrade it from a footnote to an example, but I can't find the discussion that lead to it being added as a footnote in the first place. Seems contradictory to the rest of CONTEXTBIO to me (and at odds with the general understanding of citizenship and nationality). I'm hoping there's some discussions I can read to get a better understanding. – 2.O.Boxing 13:30, 27 March 2023 (UTC)
- I've noticed it's getting harder and harder to find old stuff. So many changes since the early days... Skyerise (talk) 12:53, 27 March 2023 (UTC)
- We just (last month) had a longer discussion about this on one of our various noticeboards … but I can’t locate which noticeboard it was on. Consensus was mixed. Blueboar (talk) 11:43, 27 March 2023 (UTC)
- On the underlying issue (and this restoration), I would observe the following:
- (1) I agree with the argument made in the discussion Skyerise linked that indigenous identities in North America (and probably in many other places) are best understood as nationality/citizenship, not as ethnicity;
- (2) for Canada at least, I disagree that
citizenship
(as opposed to nationality) is always the relevant framing; it seems to fit better for First Nations but less well for other indigenous groups (Métis, Inuit); - (3) while the example presented is fine on its own terms, it doesn't necessarily represent a "best practice" that could be applied to other indigenous biographies (a problem that also confronts several of the other current examples with respect to other BLPs, IMO). Newimpartial (talk) 12:55, 27 March 2023 (UTC)
- I can't disagree with Native American being viewed as such in North America, but Europe doesn't recognise their nationalities or tribal citizenships. There's also the article on Native Americans in the United States, which first describes them as
Indigineous peoples
, and that link says,The Indigenous peoples of the Americas are the inhabitants of the Americas before the arrival of the European settlers in the 15th century, and the ethnic groups who now identify themselves with those peoples
(bolding mine). That pretty much fits my (and probably many others outside of North America) understanding of Native American; it primarily relates to ethnicity/descent and doesn't relate to nationality or citizenship (that would be American).That being said, I agree with the format used for Wilma Mankiller as it's directly relevant to her notability (and noting the tribe in parentheses is informative), but certainly not for Donna Nelson, a notable chemist. I think any guidance would be more apprirate as a sentence or two in the ethnicity and religion part. Whether or not people view it as ethnicity or nationality/citizenship, it's clear it isn't on the same level as citizenship to a soverign state, which I believe is the spirit of the guideline. – 2.O.Boxing 13:30, 27 March 2023 (UTC)- Tribal membership is a complex issue. But where it can be determined that the subject is a member of a a tribe which is considered a sovereign nation, they should certainly be described according to their membership in that nation. Some tribes do not have that status, see List of federally recognized tribes in the contiguous United States. I don't know whether any of this applies to First Nations. It is also my understanding that at least some nations at some times have had an open border policy with respect to indigenous peoples. My recollection is that England was one of the countries which extended this courtesy, though of course everything changed everywhere after 9/11. Skyerise (talk) 13:45, 27 March 2023 (UTC)
- Well, I will wait to hear more and probably reply again tomorrow (unless asked a direct question, per my editing restrictions), but I do think the
spirit of the guideline
is somewhat at issue here. I see two pieces of relevant text that can be used to discern this "spirit":In most modern-day cases, this will be the country, region, or territory, where the person is currently a citizen, national, or permanent resident
, andEthnicity, religion, or sexuality should generally not be in the lead unless relevant to the subject's notability
.
- I have seen editors pull back and forth over two main points of disagreement about these passages:
- some editors will gloss the first point as though it said, "place the person in the context of their country of citizenship or residence", while others take the language more literally and allow for more variety of outcomes;
- some editors will take the second point as though it established a very high bar for the mention of anything that does not correspond to a nation-state citizenship, while others do not interpret the text this way.
- While editors aren't always keen to acknowledge this, much of the resulting disagreement has to do with what editors are or aren't willing to acknowledge as "nationalities". It is clear to some editors that Welsh is a nationality meriting first-sentence mention in most cases, while not acknowledging equivalent status for Catalan or Quebecois nationality. To some New Zealand editors, it may seem evident that Maori identity should be a nearly-universal, required first-sentence mention in relevant biographies, but this might not be obvious to others. And so on.
- What I think we nearly all agree is that it is against the spirit and the letter of the MOS for editors to seek sources for family background and to insert hyphenated identities in article lead sections based on such references. But it seems obvious to me, from a Canadian perspective, that when indigenous people carry their indigineity as a highly visible aspect of their identity, that that form of national belonging should be presented in an article lead, and that any wikilawyering along the themes of "only one nationality can be included"/"it should reflect a recognized Westaphalian state" ought to be set aside as un-encyclopaedic, IMO.
- Also, I would point out to Skyerise that while First Nations in Canada have a status that is essentially similar to "Federally recognized tribes" in the US, the respective statuses of Métis and Inuit indigenous people - while also constitutionally entrenched - operate along different principles.Newimpartial (talk) 14:15, 27 March 2023 (UTC)
- That's where my issue lies, and I see it like a WP:CONLEVEL issue; the US made a local decision that the wider community doesn't agree with or recognise. Consensus is against. Tribal nations do not have absolute authority or external autonomy (as demonstrated in Tribal sovereignty in the United States). By definition, they're not sovereign nations. Now, I understand there's slightly differing definitions of a sovereign nation/state, but the ones I've seen (including the definition under international law) have included having absolute authority and the ability to enter talks with other sovereign nations (foreign powers). That's what I'm basing my stance on; if they're not legally recognised as a soverign nation/state, and nationality/citizenship relates to soverign nations/states, then there is no nationality/citizenship. Internationally, that is literally the case; the EU considers tribal passports "fantasy passports", which means at least in Europe, their US-recognised dual citizenship does not exist. The two instances I could find of international travel--which would imply some kind of legal recognition--were in reference to tribal lacrosse teams; one was refused entry in to the UK in the mid 2000s and the other travelled successfully to Ireland within the last decade, but I don't find that very convincing when looking at the context (publicly invited by a government sporting body for a competition).I think I'm in agreement with Newimpartial's point about
when indigenous people carry their indigineity as a highly visible aspect of their identity
, as long as the nationality/citizenship to the relevant sovereign nation is in the first sentence. – 2.O.Boxing 22:27, 27 March 2023 (UTC)- Well, I don't think the recognition of North American first nations by the U.S. and Canadian governments is any more of a
local decision that the wider community doesn't agree with or recognise
than the UK/FIFA decision to recognize Scotland, Wales, and Northern Ireland, as we have discussed at my Talk. I also don't think it is up to Wikipedia editors to decide who are or aren'tsovereign nations
, nor am I aware of any basis in WP policy to assign nationality exclusively by selecting among Westaphalian states. That isn't actually what the policy text in question tells us to do, it isn't what our articles do now, and I haven't seen a formal proposal here to change policy and practice to insist that this is what we should do, either. - Certain editors believe that all, or nearly all, biographical articles should provide a Westaphalian assignment of nationality of their subject, while other editors believe that the relevant
country, region or territory
is not always a national state, and that it is up to sources not editors primarily to decide which national identities are relevant to a subject's notability. But if there is a strong argument against the inclusion of Indigenous identities in the lead paragraph for biographies where they are strongly emphasized by high-quality sources, I certainly haven't seen such an argument in this section (nor does existing policy provide the basis for one, AFAICT). Newimpartial (talk) 16:23, 28 March 2023 (UTC)- Best not lump Canadian indigenous and American indigenous people together. Sovereignty is not recognized in Canada in the same way. We have guidelines at indigenous Wiki project... but these are antiquated American style views.. Moxy-
20:45, 28 March 2023 (UTC)
- No, I don't mean to
lump Canadian indigenous and American indigenous people together
. I do maintain, though, that in both cases national identities have been documented in RS that may be relevant for the lead paragraph of a biographical article. Newimpartial (talk) 20:53, 28 March 2023 (UTC)- Having nationality recognized by the country they inhabit is not the same as International recognition ( no passports) same as the Quebec nation simply National recognition with zero International implications. That said the example giving is to link Native American and or First Nation etc... then to link their tribal identity. This seems like we're linking Native American and First Nations all over the place for nothing more than a link that does not explain anything more than the tribal link would about indigenous heritage. Moxy-
21:29, 28 March 2023 (UTC) - I have to agree with Newimpartial here. As a member of the Indigenous Wikiproject, we deal pretty much daily with editors who don't understand the differences between citizenship and heritage, and who don't know how to accurately write about these things. Having the Wilma Mankiller example in this link has been very helpful. Even if the section needs to have some of the other entries compressed or removed, I am strongly advocating for putting it back. - CorbieVreccan ☊ ☼ 21:16, 30 March 2023 (UTC)
- Having nationality recognized by the country they inhabit is not the same as International recognition ( no passports) same as the Quebec nation simply National recognition with zero International implications. That said the example giving is to link Native American and or First Nation etc... then to link their tribal identity. This seems like we're linking Native American and First Nations all over the place for nothing more than a link that does not explain anything more than the tribal link would about indigenous heritage. Moxy-
- No, I don't mean to
- Best not lump Canadian indigenous and American indigenous people together. Sovereignty is not recognized in Canada in the same way. We have guidelines at indigenous Wiki project... but these are antiquated American style views.. Moxy-
- Well, I don't think the recognition of North American first nations by the U.S. and Canadian governments is any more of a
- That's where my issue lies, and I see it like a WP:CONLEVEL issue; the US made a local decision that the wider community doesn't agree with or recognise. Consensus is against. Tribal nations do not have absolute authority or external autonomy (as demonstrated in Tribal sovereignty in the United States). By definition, they're not sovereign nations. Now, I understand there's slightly differing definitions of a sovereign nation/state, but the ones I've seen (including the definition under international law) have included having absolute authority and the ability to enter talks with other sovereign nations (foreign powers). That's what I'm basing my stance on; if they're not legally recognised as a soverign nation/state, and nationality/citizenship relates to soverign nations/states, then there is no nationality/citizenship. Internationally, that is literally the case; the EU considers tribal passports "fantasy passports", which means at least in Europe, their US-recognised dual citizenship does not exist. The two instances I could find of international travel--which would imply some kind of legal recognition--were in reference to tribal lacrosse teams; one was refused entry in to the UK in the mid 2000s and the other travelled successfully to Ireland within the last decade, but I don't find that very convincing when looking at the context (publicly invited by a government sporting body for a competition).I think I'm in agreement with Newimpartial's point about
- I can't disagree with Native American being viewed as such in North America, but Europe doesn't recognise their nationalities or tribal citizenships. There's also the article on Native Americans in the United States, which first describes them as
Most living people will be described with a single nationality...
This edit adding a section on nationality include the referenced phrase. Is there any objection to adjusting that, like the other similar guidelines here, to be explicit about exceptions where the subject still has a strong connection to a previous nation? --John (User:Jwy/talk) 04:26, 26 March 2023 (UTC)
- Presumably you mean these edits by User:Skyerise. I see that Skyerise has since been using that section as a bludgeon to erase the national origin of people who grew up and were educated in one place but now work in another, making the lead give the false impression that these people were always of the nation they happen to live in, even in cases where we do not have evidence of their current citizenship. For example, Vida Dujmović, from the former Yugoslavia (if I remember correctly Herzegovina, not Croatia?), educated in Croatia, edited by Skyerise to say she is (only) Canadian. She moved to Canada as an adult and still works there. By now she may well be a Canadian citizen. But we do not have evidence of that, nor do we have evidence for what the answer would be if you asked her what nationality she has or what country she is from. If you asked the same question of me, the answer would probably be "it's complicated". A clause saying "most people have one nationality" is obviously true, in the abstract: greater than 50% of the world's population has not changed nationality, I think. But it is ridiculous to apply that clause to the minority of people to whom it is not true, as if we can only accept an oversimplified picture of the world where "most" somehow has morphed into "all".
- What I would like to see is a much more explicit policy that, for people for whom the question of nationality is in any way unclear (there is more than one country they have been associated with), we refrain from stating a nationality without explicit sourcing for that citizenship. Otherwise, we can say things like "Yugoslav-born computer scientist who works in Canada". To do anything else is to guess, and guessing is something we should avoid in biographies and especially in BLPs. —David Eppstein (talk) 05:04, 26 March 2023 (UTC)
What I would like to see is a much more explicit policy that, for people for whom the question of nationality is in any way unclear...
: Guessing on one's nationality is already covered by WP:V and WP:OR. —Bagumba (talk) 07:57, 26 March 2023 (UTC)- The whole point of WP:CONTEXTBIO, back when the shortcut used to be WP:OPENPARA, has always been worded to prefer the use of a single nationality. Back when it was at OPENPARA, it had nearly exactly the same examples as I restored. At some point the material got reorganized and the examples got lost in the reorganization. The examples I added are pretty much what was there before the reorganization. I know Asimov was used at the first example in the original examples. The other examples may use different people than the original examples... The original reason for this - yes, I was around during early discussions that led to the guideline - was that nationalists and revisionists of various stripes want to "claim" the person. Thus there were edit wars between Americans and Russians over Asimov. The short version is: there is no reason to mention a country in which the subject simply resided without becoming notable for anything. The guideline also accounts for people whose citizenship is unknown but who reside in another country at length with obvious employment. They can't do that in the US at least without a green card. And that's why the guideline states "or permanent resident". While I personally don't add nationalities where citizenship is not clear, it is completely within the guidelines to call someone who has taught at Harvard for 20 years an American - even if they were born elsewhere, retain their original citizenship, and are only a permanent resident of the US. In the original discussions, the key was: where did the work for which they are notable mostly occur? If it is predominantly in a single country, that's the context that supported them while they did the things for which they became notable. Only if notable work was done over multiple countries should we even think about adding a second nationality. The guideline only cover the first sentence. There is no bloody reason to say "Yugoslavian-born Canadian" when we can say "is a Canadian blah blah. Born in Yugoslavia, he moved to ..." The "nationality+profession" is used for both short summaries and a quick check on proper categorization, which are two reasons for preferring a single nationality in the lead sentence. Skyerise (talk) 13:18, 26 March 2023 (UTC)
- Yes there is a reason to say "Yugoslavian-born who works in Canada", in exactly the example I gave. Because we do not have sourcing for any one citizenship. So to state a citizenship we would have to guess. We should not guess and we should not encourage guessing. It is very different from the case of Asimov that you cite: for Asimov, he came to one country (the US) as a child, and we have a source for him becoming a citizen of the US as a child. —David Eppstein (talk) 15:48, 26 March 2023 (UTC)
- Ah, it seems footballers are some sort of special international citizen with different rules - or at least so said @GiantSnowman:. However, while GS claimed that there are different guidelines for footballers, they did not link to any such guideline. So I am not sure whether such an alternate guideline even exists. If it does, I'd be happy to follow it if someone would be so kind as to point it out to me. Meanwhile I'm just skipping footballer articles when they come upon 'random article' Skyerise (talk) 13:26, 26 March 2023 (UTC)
- An alternative is to NOT MENTION nationality in the first sentence - at all: “Joe Blow is a footballer, currently playing for Puddlesby United” … “Jane Doe was an acclaimed actress, best known for her staring role in the silent movie ‘Hamster Capers’.” Blueboar (talk) 13:44, 26 March 2023 (UTC)
- Why? It's much less informative and much less clear. The second example runs afoul of WP:PEACOCK - which frequently happens when the nationality is not present: then they are "famous", "prominent", or "acclaimed" rather than American or German. Skyerise (talk) 13:50, 26 March 2023 (UTC)
- Because usually a subject’s nationality has little (or nothing) to do with what makes the subject notable. The first sentence should focus on what makes the subject note worthy. It should focus on what they do or did… not where they came from. Blueboar (talk) 15:02, 26 March 2023 (UTC)
- Also because often for people who have flourished in multiple countries (as is very common in academia) we do not have sourcing for their citizenship. —David Eppstein (talk) 15:50, 26 March 2023 (UTC)
- And we don't have to per "or permanent resident". The academic born in Europe who has lived and taught in the US for decades may reasonably be described as American even without a citation for naturalization. Skyerise (talk) 17:20, 26 March 2023 (UTC)
- No. Stating a single nationality in the lead is unambiguously a claim that the person has a single nationality. In the cases we are discussing, it is often false and even more often unverifiable, and you are actively pushing for the inclusion of falsehoods and unverifiable claims in our article leads. In the case of someone who has one citizenship but works in another country, or a dual citizen, or someone who has held multiple citizenships while performing notable activities, we should not push the false narrative that they are entirely of one nationality. —David Eppstein (talk) 20:03, 26 March 2023 (UTC)
- @David Eppstein: Just as a footballer's citizenship can be determined from football rules, permanent residency in many countries can be determined from length of residency and employment, at least in the US; though residents of Commonwealth of Nations countries I think can work in any CoN country, and I don't know how the EU handles such things. If you think we should not do this, then perhaps we should start a discussion about removing "or permanent resident of" from the Context section, though its been there as long as I can remember. Skyerise (talk) 13:03, 27 March 2023 (UTC)
- That is WP:OR. Do not do it. —David Eppstein (talk) 17:32, 27 March 2023 (UTC)
- @David Eppstein: Just as a footballer's citizenship can be determined from football rules, permanent residency in many countries can be determined from length of residency and employment, at least in the US; though residents of Commonwealth of Nations countries I think can work in any CoN country, and I don't know how the EU handles such things. If you think we should not do this, then perhaps we should start a discussion about removing "or permanent resident of" from the Context section, though its been there as long as I can remember. Skyerise (talk) 13:03, 27 March 2023 (UTC)
- No. Stating a single nationality in the lead is unambiguously a claim that the person has a single nationality. In the cases we are discussing, it is often false and even more often unverifiable, and you are actively pushing for the inclusion of falsehoods and unverifiable claims in our article leads. In the case of someone who has one citizenship but works in another country, or a dual citizen, or someone who has held multiple citizenships while performing notable activities, we should not push the false narrative that they are entirely of one nationality. —David Eppstein (talk) 20:03, 26 March 2023 (UTC)
- And we don't have to per "or permanent resident". The academic born in Europe who has lived and taught in the US for decades may reasonably be described as American even without a citation for naturalization. Skyerise (talk) 17:20, 26 March 2023 (UTC)
- Also because often for people who have flourished in multiple countries (as is very common in academia) we do not have sourcing for their citizenship. —David Eppstein (talk) 15:50, 26 March 2023 (UTC)
- Because usually a subject’s nationality has little (or nothing) to do with what makes the subject notable. The first sentence should focus on what makes the subject note worthy. It should focus on what they do or did… not where they came from. Blueboar (talk) 15:02, 26 March 2023 (UTC)
- Why? It's much less informative and much less clear. The second example runs afoul of WP:PEACOCK - which frequently happens when the nationality is not present: then they are "famous", "prominent", or "acclaimed" rather than American or German. Skyerise (talk) 13:50, 26 March 2023 (UTC)
- Just to comment on footballers, I believe the real-world issue is that at any one time, players can belong to one and only one national team - they must have a passport in their national team nationality, but of course they may have passports in other nationalities and their country of residence or of work need not correspond to their national team nationality. In this instance, it would be an unfortunate surprise to readers if the national team nationality were not prominently presented in the arricle; in some cases it may he the greatest claim to significance of the player, according to the RS. Newimpartial (talk) 14:05, 26 March 2023 (UTC)
- What I am seeing is a misunderstanding between ethnicity and nationality and citizenship. Moxy-
14:25, 26 March 2023 (UTC)
- This is intented as a reply to me, so I will ask what
misunderstanding
you see. "FIFA nationality" is a strict subset of legal citizenship - it could also be understood as a subset of nationality of occupation. Obviously, nationality of residence and nationality of occupation are distinct concepts. But for people who are notable precisely in relation to a certain form of nationality (e.g., national team membership), should Wikipedia not continue to present this consistently in biographical articles? I don't know what "misunderstanding" you have detected. Newimpartial (talk) 14:36, 26 March 2023 (UTC)- Americans are unlikely to differentiate between ‘citizenship’ and nationality’ in everyday language, this is not the case in other countries. Nationality should be listed only in addition to citizenship, and only in cases where it is verifiable and relevant to the article. For most articles, place of birth denotes nationality. When it comes to the United States, U.S. citizens are U.S. nationals. Still, not all U.S. nationals are U.S. citizens. Moxy-
15:20, 26 March 2023 (UTC)
- We should not let footballers drive our guidelines for non-footballers. The fact that international footballers play for a national team, and are required by FIFA to be citizens of that nation, gives these people a definitive nationality that many other expatriates and emigrants do not have. We should not base our guidelines on the false assumption that nationality is as easy to determine for other people as it is for footballers. —David Eppstein (talk) 20:06, 26 March 2023 (UTC)
- Just to be clear, when I commented on footballers above it was only to point out a key characteristic of that case (that they may be notable for an activity that is dependent on exercising a particular nation's citizenship), not as a paradigm applicable to non-footballers. Also, I would point out to Skyerise that footballers are in fact a very specific demographic in that they may exercise another citizenship more frequently in their personal or professional lives than they do their national team citizenship - but the latter may be highly relevant and thetefore feature in the opening paragraph (q.v. Carleigh Frilles).
- As I pointed out in my recent contribution to the discussion of Native American nationality, I have seen editors disagree not only about the application of the nationality guideline but about its
spirit
as well. (Moxy's comment above,Nationality should be listed only in addition to citizenship
, is an example of what I referred to in that earlier post as agloss
, simplifying and transforming the guideline into a principle some editors support but which policy text does not actually stipulate.) - I would like to point to four biographical articles about Canadians that handle the issue differently, but each of which makes sense in the specific case: Jonathan David, René Lévesque, Mary Simon, Buffy Sainte-Marie. None of these correspond in detail to any of the examples Skyerise added to the MOS, but each seems to me to reflect the interaction between high-quality sourcing and Wikipedia policy in an appropriate way.
- TL;DR - I don't think there is "one right way" to handle the diversity of cases of nationality in biographical articles, and I'm also skeptical that the list of examples added late last year are especially exemplary. Newimpartial (talk) 16:12, 27 March 2023 (UTC)
- We should not let footballers drive our guidelines for non-footballers. The fact that international footballers play for a national team, and are required by FIFA to be citizens of that nation, gives these people a definitive nationality that many other expatriates and emigrants do not have. We should not base our guidelines on the false assumption that nationality is as easy to determine for other people as it is for footballers. —David Eppstein (talk) 20:06, 26 March 2023 (UTC)
- Americans are unlikely to differentiate between ‘citizenship’ and nationality’ in everyday language, this is not the case in other countries. Nationality should be listed only in addition to citizenship, and only in cases where it is verifiable and relevant to the article. For most articles, place of birth denotes nationality. When it comes to the United States, U.S. citizens are U.S. nationals. Still, not all U.S. nationals are U.S. citizens. Moxy-
- This is intented as a reply to me, so I will ask what
- What I am seeing is a misunderstanding between ethnicity and nationality and citizenship. Moxy-
- An alternative is to NOT MENTION nationality in the first sentence - at all: “Joe Blow is a footballer, currently playing for Puddlesby United” … “Jane Doe was an acclaimed actress, best known for her staring role in the silent movie ‘Hamster Capers’.” Blueboar (talk) 13:44, 26 March 2023 (UTC)
- The whole point of WP:CONTEXTBIO, back when the shortcut used to be WP:OPENPARA, has always been worded to prefer the use of a single nationality. Back when it was at OPENPARA, it had nearly exactly the same examples as I restored. At some point the material got reorganized and the examples got lost in the reorganization. The examples I added are pretty much what was there before the reorganization. I know Asimov was used at the first example in the original examples. The other examples may use different people than the original examples... The original reason for this - yes, I was around during early discussions that led to the guideline - was that nationalists and revisionists of various stripes want to "claim" the person. Thus there were edit wars between Americans and Russians over Asimov. The short version is: there is no reason to mention a country in which the subject simply resided without becoming notable for anything. The guideline also accounts for people whose citizenship is unknown but who reside in another country at length with obvious employment. They can't do that in the US at least without a green card. And that's why the guideline states "or permanent resident". While I personally don't add nationalities where citizenship is not clear, it is completely within the guidelines to call someone who has taught at Harvard for 20 years an American - even if they were born elsewhere, retain their original citizenship, and are only a permanent resident of the US. In the original discussions, the key was: where did the work for which they are notable mostly occur? If it is predominantly in a single country, that's the context that supported them while they did the things for which they became notable. Only if notable work was done over multiple countries should we even think about adding a second nationality. The guideline only cover the first sentence. There is no bloody reason to say "Yugoslavian-born Canadian" when we can say "is a Canadian blah blah. Born in Yugoslavia, he moved to ..." The "nationality+profession" is used for both short summaries and a quick check on proper categorization, which are two reasons for preferring a single nationality in the lead sentence. Skyerise (talk) 13:18, 26 March 2023 (UTC)
- I think that nationality can be defining for some people, ethnic origin can be defining for some people (probably fewer), and neither can be defining for others. Furthermore, for many article subjects neither of the above are verifiable. While I understand the desire for standardization, I think that neither, either or both should be included only if 1) verifiable and 2) defining for that individual. Buidhe public (talk) 07:54, 29 March 2023 (UTC)
- I agree. The original issue, as I understand it, was people claiming the subject for their side (ethnicity, nationality, whatever). For a subject that has verifiable connection to their birth country, including BirthCountry-CurrentCountry seems natural. The guideline should focus more on what fits the subject rather than defending against crusading editors - with that defense being covered as a special case "when there is serious contention." --John (User:Jwy/talk) 02:43, 1 April 2023 (UTC)
Perhaps the solution is to not use any such descriptions in the intro of BLPs or bios-in-general. GoodDay (talk) 15:44, 26 March 2023 (UTC)
- Nationality in the lede is important context for a biography. GiantSnowman 15:48, 26 March 2023 (UTC)
Consensus behind the section Skyerise added in November
I seem to have missed it, so could someone point me to the on-wiki interaction that established the consensus that was then documented in the series of edits under discussion above ()? While I see some useful clarification among those edits, I also see a good deal of confusion and an editorial preference to move further away from the sources of BLP articles than any previous consensus or community practice would require. Could someone clarify this, please? Newimpartial (talk) 14:05, 26 March 2023 (UTC)
- Can we move away from reliable sources? That seems like WP:OR and no discussion anywhere on Wikipedia can validate such an approach. Slywriter (talk) 15:26, 26 March 2023 (UTC)
- I, for one, am not suggesting that we can move away from reliable sources. I am suggesting, rather, that the added policy text encourages editors to depart from following the reliable sources in many cases. Newimpartial (talk) 15:35, 26 March 2023 (UTC)
I'm also interested in finding the discussion that lead to these additions, specifically the Native American example. I found this proposal from November with only one reply from Skyerise before it was added. It's probably worth noting that CorbieVreccan was the one who added the footnote in March 2022. I had a look in the WP:IPNA talk page archives but couldn't find any discussion there. I'm still presuming there's one thats eluding me. – 2.O.Boxing 14:31, 26 March 2023 (UTC)
- I posted on this talk page. There were no objections. Skyerise (talk) 16:36, 26 March 2023 (UTC)
- Native American wasn't in the previous examples. Considering there doesn't appear to be consensus for something so contentious, I'm going to remove that one until its been appropriately discussed. I don't really have much comment on the other examples; they're close enough to the previous ones and seem to accurately reflect the guideline. – 2.O.Boxing 08:46, 27 March 2023 (UTC)
Determining 'which' nationality to use in a bio, has at times been a thorny topic. Do we go with "birth country"? The country the person lived in most of their lives? The 'only' determining factor, would be what do reliable sources do, per individual. GoodDay (talk) 14:53, 26 March 2023 (UTC)
- Might be naive of me, but don't we just follow reliable sources? Or is the issue these are all database entries deemed notable that have no RS coverage? Slywriter (talk) 15:25, 26 March 2023 (UTC)
- Then there's the United Kingdom situation, which can certainly be thorny. Some individuals prefer to be called British, which they're called as such in reliable sources. While others prefer English, Scottish, Welsh, Northern Irish or Irish, which they're called as such, in reliable sources. But, that's another rocky area. GoodDay (talk) 15:41, 26 March 2023 (UTC)
- The problem with that is that different sources have different standards. Many sources are reporting ethnicity instead of nationality, using terms like Italian-American, which is ambiguous. We should not follow such sources, but rather follow our own Manual of Style. Skyerise (talk) 16:32, 26 March 2023 (UTC)
- Err no... we follow sources, not our MOS. If our MOS disagrees with sources, the MOS is wrong and must be corrected to conform with WP:V and WP:OR. Slywriter (talk) 17:49, 26 March 2023 (UTC)
- The MoS is not wrong. Whether to present nationality alone or combined with ethnicity is an editorial decision. Another publication's MoS may permit such constructions, or even encourage them, which is why they present the material that way. Neither our or their MoS is "wrong", they are simply incompatible. We do not "follow the sources" just to put ethnicity unnecessarily and inexplicably in the lead sentence. Better to take a whole sentence to explain it, usually in the early life section. Otherwise every black American will be described as "African-American", which conveys too little information to be clear. Were they born in America or Africa? If an African-American moves to Africa, are they now an American-African? Wouldn't white people who moved from the US to Africa also be American-Africans? It's best to unpack into ethnicity and nationality, and follow WP:ETHNICITY. Really. 20:59, 26 March 2023 (UTC)
- My issue is that I know being hyphenated-American is important to the subjects of two biographies I take an interest in. They are proud of their origin, have been back to inspire those in their country and have even attempted to play for their country-of-origin national team. The current guideline strongly discourages leading with their (well documented) hyphenated status when it is a key part of their identity. The MOS should not do so, IMO. --John (User:Jwy/talk) 20:49, 26 March 2023 (UTC)
- Ethnic pride is specifically why ethnicity is not encouraged in the lead sentence. In such a case I'd suggest detailing why they pride themselves on their ethnic heritage as an Italian-American (or whatever) later in the lead. Skyerise (talk) 20:59, 26 March 2023 (UTC)
- Why discourage it if it is key part of who they are? I can see discouraging it if the editors are using it as an expression of their own view on matters independent of the subject, but if the subject is active in their birth country (it's not necessarily ethnic) it seems a good way to help establish "who they are." --John (User:Jwy/talk) 23:40, 26 March 2023 (UTC)
- The problem is not so much people who are notable for their ethnic pride, but rather people who might possibly be of some ethnicity, maybe, if you guess by surnames, and Wikipedia editors with a lot of ethnic pride who want to highlight that supposed ethnicity everywhere they can find it. —David Eppstein (talk) 00:02, 27 March 2023 (UTC)
- Why discourage it if it is key part of who they are? I can see discouraging it if the editors are using it as an expression of their own view on matters independent of the subject, but if the subject is active in their birth country (it's not necessarily ethnic) it seems a good way to help establish "who they are." --John (User:Jwy/talk) 23:40, 26 March 2023 (UTC)
- Ethnic pride is specifically why ethnicity is not encouraged in the lead sentence. In such a case I'd suggest detailing why they pride themselves on their ethnic heritage as an Italian-American (or whatever) later in the lead. Skyerise (talk) 20:59, 26 March 2023 (UTC)
- Err no... we follow sources, not our MOS. If our MOS disagrees with sources, the MOS is wrong and must be corrected to conform with WP:V and WP:OR. Slywriter (talk) 17:49, 26 March 2023 (UTC)
@Skyerise: Your addition of nationality examples in November had the edit summary: "add examples of presentation of nationality according to the committee-written guidance". For reference, can you provide a link to the old version where these came from, or a link(s) to relevant discussion for the specific wording. Thanks.—Bagumba (talk) 12:09, 27 March 2023 (UTC)
- @Bagumba:, the MoS pages have been moved and reorganized so much that I cannot find them. I remember discussions leading to the examples being added (vaguely as I am elderly), and remember the examples being in the guideline in 2010 - 2012, when I was mostly working on New Mexico topics and Taos art colony biographies, before the whole MoS page and subpage structure got renovated. At some point during that renovation the examples got removed. I am sure they were there as I have been following these examples since about that time. At one time they were at the shortcut WP:OPENPARA, but that's been re-targeted several times and I suspect deleted at least once as I remember it existing before the current redirect was created. I continued to use it to point to the examples for some time, not realizing they weren't there anymore. Though perhaps I am just getting old and forgetful... I've also been unable to find a discussion leading to their removal, so I think the removal was probably inadvertent. I think examples are good to have, though perhaps some of the wording and intent can be improved, since I had to write them anew from memory there may be differences from the original that may need to be addressed? Skyerise (talk) 12:27, 27 March 2023 (UTC)
- If I look at WP:OPENPARA's history, the shortcut was created on 19 December 2010. The examples at the MOS on that date mostly match the examples currently at Wikipedia:Manual of Style/Biography § Opening paragraph. I didn't find an explicit set of nationality examples from before.—Bagumba (talk) 16:19, 27 March 2023 (UTC)
- I wasn't involved in the discussion before the main section was added. But for the Native American bit with Wilma Mankiller: There was a lot of dispersed discussion leading up to it, at various article talk pages where the same issues kept coming up (as I referred to above), and at the wikiproject. When it was proposed on MOS talk, there were no objections. So for Squared.Circle.Boxing to say it was "contentious" doesn't line up with what happened. - CorbieVreccan ☊ ☼ 22:48, 30 March 2023 (UTC)
- If I look at WP:OPENPARA's history, the shortcut was created on 19 December 2010. The examples at the MOS on that date mostly match the examples currently at Wikipedia:Manual of Style/Biography § Opening paragraph. I didn't find an explicit set of nationality examples from before.—Bagumba (talk) 16:19, 27 March 2023 (UTC)
Dual nationality: hypenate or "and"
In the examples added on 13:05, 15 November 2022, there's two examples for dual nationality that use "and" and discourage hyphenating:
- Arnold Schwarzenegger (born July 30, 1947) is an Austrian and American actor, film producer, businessman, retired professional bodybuilder and politician
- For a politician, dual citizenship can be a political issue, so it is important to be clear and avoid ambiguity. The lead sentence here is not about ethnicity ("Austrian-American") or the country of birth ("Austrian-born American"), but rather about dual citizenship.
- Peter Lorre (June 26, 1904 – March 23, 1964) was a Hungarian and American actor
- This is an example of a person who established a career in Europe as a Hungarian, then emigrated to the United States and was naturalized and continued his career, and is thus known as both a Hungarian actor and as an American actor. The use of and again prevents the introduction of ethnicity or birth.
However, these examples were added to the MOS only shortly after they were changed in the respective bios:
- 12:51, 15 November 2022: Schwarzenegger changed from "Austrian-born American" to "Austrian and American"
- 12:57, 15 November 2022 Lorre changed from "Hungarian-born" to "Hungarian and American"
These were not stable versions. However, per the policy WP:PROPOSAL:
Most commonly, a new policy or guideline documents existing practices, rather than proposing a change to what experienced editors already choose to do.
Do the changes reflect a standard practice? Are there examples of where this has been followed, prior to the MOS change? It seems to contradict MOS:DUALNATIONALITIES:
For people and things identifying with multiple nationalities, use a hyphen when using the combination adjectivally and a space when they are used as nouns, with the first used attributively to modify the second
The changes still might make sense, but I don't think we should rely on WP:SILENCE as consensus for this.—Bagumba (talk) 16:40, 27 March 2023 (UTC)
Tense for the dead
When describing dead people as they relate to achievements, records and currently-living people, what tense should I use? Specifically, for Puti Tipene Watene, we currently have “he is the only person to both represent the New Zealand national rugby league team and become a Member of Parliament
” and “He is the great-grandfather of rugby league player Dallin Watene-Zelezniak
” (emphasis added). If there’s general agreement on the right way to phrase these, I think it would be worth adding them to the Tense section, even if only to guide confused souls like me. — HTGS (talk) 10:54, 23 March 2023 (UTC)
- I think 'is' and 'was' respectively for the two specific examples above? GiantSnowman 21:42, 24 March 2023 (UTC)
- Right you are, GiantSnowman. Once someone "enters the record books", that part of them leaves the body to seek its fortune as a historical figure. Same name, whole other game. A grandfather is more like a lawyer or acrobat, where the sentience itself must be "in the flesh" to "do the job". Even then, though, it gets tricky. In the context of a family tree, ancestors and descendants still are exactly where they've always been, in pages like record books for relatively unimpressive accomplishments. When we start talking kings, queens and those thought to have perished in submarines, things turn drastically more convoluted and the likelihood of a short and clear way to put it for everyone to understand just ceases to exist. But yeah, think "place in history" vs "person on Earth" for a good "rule of thumb". InedibleHulk (talk) 06:48, 7 April 2023 (UTC)
- The first one could be made less inelegant by using the present perfect:
...he is the only person ever to have both represented...and become...
. (Conveniently, become is both the present tense and the past participle.) That puts the overt action in the past but is formally in the present tense, which is appropriate because the possibility of someone else doing the same thing has not closed. If the NZ team and Parliament no longer existed, then "was" would be correct. --Trovatore (talk) 07:36, 7 April 2023 (UTC)- First ever, only ever, both too wordy. Everything is always ever, by default, it's right there in the name. And "and" conveys the idea of two things just fine, forget "both", I advise. Aside from that, you might be on to something with "become". Good luck, rulemakers! InedibleHulk (talk) 04:27, 8 April 2023 (UTC)
- The first one could be made less inelegant by using the present perfect:
- Right you are, GiantSnowman. Once someone "enters the record books", that part of them leaves the body to seek its fortune as a historical figure. Same name, whole other game. A grandfather is more like a lawyer or acrobat, where the sentience itself must be "in the flesh" to "do the job". Even then, though, it gets tricky. In the context of a family tree, ancestors and descendants still are exactly where they've always been, in pages like record books for relatively unimpressive accomplishments. When we start talking kings, queens and those thought to have perished in submarines, things turn drastically more convoluted and the likelihood of a short and clear way to put it for everyone to understand just ceases to exist. But yeah, think "place in history" vs "person on Earth" for a good "rule of thumb". InedibleHulk (talk) 06:48, 7 April 2023 (UTC)
MOS:FULLNAME vs MOS:JR
At O.G. Anunoby, his full name is verifiably sourced as "Ogugua Anunoby Jr." MOS:FULLNAME reads:
While the article title should generally be the name by which the subject is most commonly known, the subject's full name, if known, should usually be given in the lead sentence (including middle names, if known, or middle initials).
However, MOS:JR says:
Using Jr., Sr., or other such distinctions, including in the lead sentence of an article, is only for cases in which the name with the suffix is commonly used in reliable sources.
Should "Jr." be included in the lead sentence's full name, if it's not part of the title i.e. WP:COMMONNAME? —Bagumba (talk) 18:46, 1 April 2023 (UTC)
- It must be used in cases cases where the name with the suffix is commonly used in reliable sources. Hence John McCain starts with "John Sidney McCain III", his father John S. McCain Jr. with "John Sidney "Jack" McCain Jr.", and John S. McCain Sr. with "John Sidney "Slew" McCain". Hawkeye7 (discuss) 19:53, 1 April 2023 (UTC)
- Is there a reason for requiring suffixes to be commonly used, a higher standard than we have for other parts of a full name, such as obscure but verifiable given names e.g. Elizabeth Stamatina Fey (Tina Fey)? —Bagumba (talk) 02:13, 2 April 2023 (UTC)
- @Wehwalt:: You recently made edits that introduced this restriction for reliably sourced full names in the lead sentence. Can you comment if this was the intended effect. Was there a wider discussion on this topic? Thanks. —Bagumba (talk) 08:39, 7 April 2023 (UTC)
- I can only view a limited portion of the article, so I can't say if that sports column is in my view a RS that the Jr is used. It certainly doesn't seem commonly used in his case. As for the edits, I simply made clearer, by changing "well-attested" to "commonly used" what was the case, that such suffixes should only be used if commonly attested to in reliable sources. That's hardly new in the MOS. There are too many cases of people throwing in a Jr. because the father had the same or a similar name and there's no reliable source saying Jr. was ever used. I think the distinction you are looking for is that the "obscure but verifiable" parts of a name are legally part of the name but the "Jr." is a disambiguator, not part of the name, used to distinguish between two people, which is generally dropped at some point without a legal change of name. Are you saying that one column by a sportswriter in the Sun makes the suffix "well-attested" but not "commonly used"?--Wehwalt (talk) 13:27, 7 April 2023 (UTC)
- Thanks for the background. The source says:
He’s actually Ogugua Anunoby Jr., son of a scholar, brother of a former NFL player.
If I understand your concern correctly, editors should not WP:OR that a person legally added Jr./Sr. to their name. I am familiar with David Arseneault Jr., whose WP:COMMONNAME is referred to with "Jr.", but where it's dubious that it's part of his legal name, since he has a different middle name than his father. With Anunoby, his father is not publicly notable, so there's no conflicting evidence that their middle names dont match, and there is no reason to believe "Jr." is dubious. In my experience, people's middle names and suffixes are not commonly referred to in reliable sources, but are generally presented on WP as their legal name if reliably verifiable. While there is reasonable doubt to not include "Jr." as part of a legal name like with Arseneault, I think "commonly used" can be too confused with COMMONNAME, setting an excessive bar, in Anunoby's case. Anunoby's page title should remain without "Jr.", but it seems reasonable that it's part of his legal name, as we would treat a source if it mentioned a middle name instead. —Bagumba (talk) 04:15, 8 April 2023 (UTC)- It seems to me that even "well-attested" is calling for something of higher magnitude than "reliably sourced". How would the "reasonable doubt" be established? Omission of the "Jr.", in Anunoby's case or generally, would prove nothing. Wehwalt (talk) 07:59, 8 April 2023 (UTC)
- An edit summary at Anunoby said "32 of the 33 references used omit the suffix" Of course it will, when it's not his COMMONNAME. The MOS change put new emphasis on the lead's full name, when MOS:JR before was only referring to a page title and the use of WP:NATURAL disambiguation. —Bagumba (talk) 10:34, 8 April 2023 (UTC)
- I would see if there is support for Jr. in sources not used in the article, especially league, team, and from networks like ESPN. If they don't use the Jr. then the single sports columnist starts to look like an outlier. I'm not sure that the parallel between middle names and Jr. is appropriate, a source is not likely to synthesize a middle name but might use a Jr. or Sr. without much thought when they're discussing the father and he has the same name as the notable son. That doesn't mean the writer's discovered what the rest have overlooked, that he uses a Jr. No matter what the wording of the MOS, a single source would seem scanty there. Wehwalt (talk) 12:45, 8 April 2023 (UTC)
- An edit summary at Anunoby said "32 of the 33 references used omit the suffix" Of course it will, when it's not his COMMONNAME. The MOS change put new emphasis on the lead's full name, when MOS:JR before was only referring to a page title and the use of WP:NATURAL disambiguation. —Bagumba (talk) 10:34, 8 April 2023 (UTC)
- It seems to me that even "well-attested" is calling for something of higher magnitude than "reliably sourced". How would the "reasonable doubt" be established? Omission of the "Jr.", in Anunoby's case or generally, would prove nothing. Wehwalt (talk) 07:59, 8 April 2023 (UTC)
- Thanks for the background. The source says:
- I can only view a limited portion of the article, so I can't say if that sports column is in my view a RS that the Jr is used. It certainly doesn't seem commonly used in his case. As for the edits, I simply made clearer, by changing "well-attested" to "commonly used" what was the case, that such suffixes should only be used if commonly attested to in reliable sources. That's hardly new in the MOS. There are too many cases of people throwing in a Jr. because the father had the same or a similar name and there's no reliable source saying Jr. was ever used. I think the distinction you are looking for is that the "obscure but verifiable" parts of a name are legally part of the name but the "Jr." is a disambiguator, not part of the name, used to distinguish between two people, which is generally dropped at some point without a legal change of name. Are you saying that one column by a sportswriter in the Sun makes the suffix "well-attested" but not "commonly used"?--Wehwalt (talk) 13:27, 7 April 2023 (UTC)
- @Wehwalt:: You recently made edits that introduced this restriction for reliably sourced full names in the lead sentence. Can you comment if this was the intended effect. Was there a wider discussion on this topic? Thanks. —Bagumba (talk) 08:39, 7 April 2023 (UTC)
- Is there a reason for requiring suffixes to be commonly used, a higher standard than we have for other parts of a full name, such as obscure but verifiable given names e.g. Elizabeth Stamatina Fey (Tina Fey)? —Bagumba (talk) 02:13, 2 April 2023 (UTC)
Proposal: Moving post-nominals from lead sentences to article bodies
Question of pronoun use for nonbinary non-caring
Should nationality be included in the lead sentence?
Request for comment: should we add nationality usage examples for lead sentences?
Reverts
Capitalization of professor
RFC re: MOS:GENDERID and the Deadnames of Deceased Trans Persons
Remove the "living" qualifier in MOS:DEADNAME
Capitalisation of titles
Conflict between JOBTITLE and SURNAME
Discussion at Talk:Celia Rose Gooding § RfC on pronouns
"Noteworthy" or "notable" roles in the first para/sentence
Excessive clutter of Gaddafi example
Remove bold for honorific titles in lead sentence
MOS:ETHNICITY
Age of person in an infobox
it's preferable a more readable form
What does notable mean for MOS:GENDERID?
GENDERID - When to include deadnames, post-RfC discussion
IAR & GENDERID
Ambiguity under PEOPLETITLES
Workshopping a second proposal
@Kornatice: and I split over the capitalization of "Florida governor Ron DeSantis"/"Florida Governor Ron DeSantis". Konatice said it should be lowercased (I think because the official title is Governor of Florida Ron DeSantis), accurately pointing out that the table includes "US president Richard Nixon
". But ... while Konatice is absolutely right ... I think the problem is that the table is wrong—not just externally wrong but internally inconsistent.
Possible error in MOS:JOBTITLE table
First, let's start with the text rules, which say to capitalize positions.
- When followed by a person's name to form a title, i.e., when they can be considered to have become part of the name: President Nixon, not president Nixon; Pope John XXIII, not pope John XXIII.
- When a title is used to refer to a specific person as a substitute for their name during their time in office, e.g., the Queen, not the queen (referring to Elizabeth II); the Pope, not the pope (referring to Francis).
- When a formal title for a specific entity (or conventional translation thereof) is addressed as a title or position in and of itself, is not plural, is not preceded by a modifier (including a definite or indefinite article), and is not a reworded description:
Now, it was my thought that the first bullet controlled. But Kornatice—consistent with the Nixon example—reads the third bullet as limiting the first bullet: and thus, we should not capitalize "a formal title for a specific entity ... [that is] addressed as a title or position in and of itself ... and is not a reworded description:"
. I have to admit, I'm pretty decent at grammar, but that third bullet throws me for a loop. Does "in and of itself" apply to title and position? Anyways ... regardless:
First, I'm not sure that's the rules are internally consistent: note that the first bullet says "President Nixon" should be capitalized ... but "President" is arguably a reworded description (shorthand) for President of the United States.
And, second, I can't help but think that the colon (which I left in) is very important there. The colon proceeds the table. And, notably, there's something a little funny about the table: Every item in the left column—showing capitalization—is not a title immediately followed by a name—it's a title that's the object of a verb."Richard Nixon was President of the United States.
"; "Theresa May became Prime Minister of the United Kingdom in 2016.
"; "Louis XVI became King of France and Navarre in 1774, later styled King of the French (1791–1792).
"
On the right column, we get a little more variation: titles that are the objects of verbs ("Theresa May was the prime minister of the United Kingdom.
") AND titles that exist independent of the name they precede—not functioning as adjectives but as subjects ("The French king, Louis XVI, was later beheaded.
"). The only example where a name immediately follows and title function is the "US president Nixon
" example. Now, what's weird about this example is that it's also not consistent with the column titles at the top of the table. The left column title is "denoting a title", but the right column title is "denoting a description". But that's a semi-baffling choice of words if the example is correct. In "Florida governor Ron DeSantis
" or "US president Richard Nixon
" ... both "Florida governor" and "US president" are literally being used as titles ... so it's a little strange to say they're denoting a description instead of a title.
I want to further add that not capitalizing Florida Governor Ron DeSantis would be inconsistent with ... every other style guide I'm aware of? (Not that we're bound by those style guides, just food for thought.) Based on that, I'd suggest modifying that third bullet to:
- When a formal title for a specific entity (or conventional translation thereof) is connected to the subject via a linking verb and addressed as a title or position in and of itself, so long as the title is not plural, is not preceded by a modifier (including a definite or indefinite article), and is not a reworded description:
-Jerome Frank Disciple 02:05, 26 June 2023 (UTC)
- I don't think this analysis is right. I think you've missed an important example:
Mitterrand was the French president
. This is the example used for the case of not capitalizing an office or title. - I also disagree that the full title for the governor of Florida is "Governor of Florida". It's just "Governor". Same way you'd refer to "Dr. Sigmund Freud" but would in a full sentence say "Sigmund Freud was a doctor". If you say "Sigmund Freud was a doctor of psychiatry" you still don't capitalize it. Nor would you if you were to refer to "psychiatric doctor Sigmund Freud". The title in this case is just "Dr." or "Doctor", and not "doctor of psychiatry" or "psychiatric doctor".
- It's the "Florida" that's causing confusion here I think, because "Florida" is itself a proper noun and so is always capitalized. Loki (talk) 04:32, 26 June 2023 (UTC)
- Uh, I don't think I did! In "
Mitterrand was the French president.
"—the title is the object of the verb ("was"). As such, the first bullet point does not apply to it, and it fits the reword I suggested. The key question here is whether the third bullet point is meant to limit the first bullet point—I think it's fairly clearly not meant to.--Jerome Frank Disciple 12:00, 26 June 2023 (UTC)- I disagree that that's the key question here. My reading of this section is that the first bullet point doesn't even apply at all to "Florida governor Ron DeSantis", the same way it would not apply to "psychiatric doctor Sigmund Freud". It only covers titles that are part of the name, not descriptions that just happen to go before the name. Loki (talk) 14:53, 26 June 2023 (UTC)
- No, that's not accurate: "
when followed by a person's name to form a title
" is the controlling description there—note that "considered to become part of the name
" is only listed after "i.e.
" ("that is"). You can't substitute "i.e." for "if and only if". (Also, how is "Florida [G]overnor Ron DeSantis" not part of the name but "President Richard Nixon" is?) - I'm ... quite skeptical of the idea that adding an adjective destroys capitalization but using shorthand for the title does not—certainly I don't think that's reflected in the current rules. For example, the official title for U.S. president is not "President" but "President of the United States". So, substituting "President" for the full title is modifying it. Yet "President Nixon" is capitalized. But, by your rule, if I said "His inability to keep his mouth shut reminded observers of loose-lipped President Nixon" ... president would be lowercased, because there's an adjective before it? (After all, by your rule, per your talk page, "French president Mitterrand" would be lowercased, but French is just an adjective. I think what you're getting at is more that the title shouldn't be capitalized if it's a standalone reference (e.g., He was joined by the French president, Mitterand") ... but that's not use as a title. --Jerome Frank Disciple 15:10, 26 June 2023 (UTC)
- No, that's not accurate: "
- I disagree that that's the key question here. My reading of this section is that the first bullet point doesn't even apply at all to "Florida governor Ron DeSantis", the same way it would not apply to "psychiatric doctor Sigmund Freud". It only covers titles that are part of the name, not descriptions that just happen to go before the name. Loki (talk) 14:53, 26 June 2023 (UTC)
- Uh, I don't think I did! In "
- As I understand it… we would write “He was joined on stage by Governor DeSantis” ("Governor DeSantis" being his title)… but “He was joined on stage by Florida governor DeSantis” (“Florida governor” being his job). Blueboar (talk) 17:18, 26 June 2023 (UTC)
- But my point is that is still using governor as a title in a grammatical sense. Perhaps you can say "Florida" is modifying "Governor" and therefore Governor shouldn't be capitalized, but that doesn't really make sense. It's also counter to every other style guide I'm aware of. In fact, I can't find a single news org that does that.
- PBS: Florida Governor Ron DeSantis
- NPR: Florida Governor Ron DeSantis
- New York Times: Florida Governor Ron DeSantis
- BBC: Florida Governor Ron DeSantis
- Reuters: Florida Governor Ron DeSantis
- Newsweek: Florida Governor Ron DeSantis
- Tampa Bay Times: Florida Governor Ron DeSantis
- Of course, we can reject every other style guide ... but why are we doing that here? The only reason that's been offered is that "Florida Governor Ron DeSantis" isn't "part of the name" like "Governor Ron DeSantis" is. ... But that's not a distinction based on any real grammatical concept.
- Further, if the modification rule really does apply to titles that are serving as adjectives (and immediately precede the name), no one has been able to explain why "President Nixon" would be capitalized, even though the official title is President of the United States, and "President" is merely a shorthand modification.
- As the first bullet accurately holds, if the title immediately precedes the name and is not independent of the name, we should capitalize it.--Jerome Frank Disciple 19:07, 26 June 2023 (UTC)
- Honestly, I've stopped fighting this one. Logically, you're right and the rule should be if the title immediately precedes the name, then it's capitalized (
Florida Governor Ron DeSantis
), but if the title is set apart from the name in some way, then it's lowercase (Ron DeSantis, the governor of Florida
orthe Florida governor, Ron DeSantis
). —Carter (Tcr25) (talk) 19:46, 26 June 2023 (UTC)- I appreciate that! For a second it felt like I was taking crazy pills.
- @Blueboar what are your thoughts? I understand what you said is above is your understanding of the policy, but do you think that's right? Or, more specifically, would either you or @Carter Tcr25 object to changing the third bullet to:
- Honestly, I've stopped fighting this one. Logically, you're right and the rule should be if the title immediately precedes the name, then it's capitalized (
- But my point is that is still using governor as a title in a grammatical sense. Perhaps you can say "Florida" is modifying "Governor" and therefore Governor shouldn't be capitalized, but that doesn't really make sense. It's also counter to every other style guide I'm aware of. In fact, I can't find a single news org that does that.
- When a formal title for a specific entity (or conventional translation thereof) is connected to the subject by a linking verb, so long as the title is not plural, is not preceded by a modifier (including a definite or indefinite article), and is not a reworded description:
- and removing the "US president Nixon" example? (which, by the way, is a hyper weird example ... because I'm not sure there's any example of a Wikipedia article saying something as weird as "US president Nixon").
- (Btw: I did consider whether it was okay to limit to "linking verbs": Specifically, I wondered whether "elected president of the United States" would be used with a capital "P" in either our articles or reliable sources. Looks to me like no: see African-American candidates for President of the United States (
Barack Obama (D-IL) was elected president of the United States.
) or this NYT story ("Joseph R. Biden Jr. was elected president of the United States on Saturday ...."
).
Stray thoughts |
|---|
|
- --Jerome Frank Disciple 21:02, 26 June 2023 (UTC)
- Agreed (except "capitalize titles when they immediately precede names" should be "capitalize titles when they immediately precede or follow names", since some titles come after) I do think a case can be made for capitalizing "Florida Governor Ron DeSantis"; I don't recall a good rationale for "Florida governor Ron DeSantis"; it's just a modifier preceding a name+title combo, like "former President Jimmy Carter" (or "former-President Jimmy Carter" if you prefer). Similarly, "then-King Edward VIII (later the duke of Windsor)". But maybe I'm forgetting some debate from back-when that did make a case for lower-casing. — SMcCandlish ☏ ¢ 😼 22:31, 23 July 2023 (UTC)
- --Jerome Frank Disciple 21:02, 26 June 2023 (UTC)
SURNAME and repeated uses
During Folly Mox's recent (very welcome) RFC on link repetition, which successfully challenged the assumption that Wikipedia articles are read from top to bottom like a regular article
(because nobody reads Wikipedia like that) and changed the policy on duplicate links from one-per-article to one-per-section, Bagumba wondered if that change Would [...] trickle over to MOS:SURNAME
as well. That question was tabled for possible discussion here.
So, let's have that discussion, because OMG yes it should! (IMHO) A repeated frustration for me, when reading articles, goes like this: (Note: The names are made up, but the frustration is real.)
- I'm reading an article about... some event, something that doesn't have a person as its subject.
- Let's pretend it's an article about the Bowling Green massacre — not Kellyanne's fake one, a real one.
- I'm reading the fifth section of the article, having skimmed over the rest, because... I don't know, because I have the attention span of a gnat on meth? Point is, it happens.
- That section opens,
On December 5, 2017, Hall released a statement condemning the attack.
Now, the obvious question here is, "Who the hell is 'Hall'!?" Oh, OK, I go back three entire sections to find out that the article's referring to Georgina Hall, then-Mayor of Bowling Green.
We can do better than that. At least once a section, any figures mentioned in the article should probably be fully re-contextualized. Even if someone does read from top to bottom like a regular article
, over that kind of distance it's really easy to forget who these people are, when they're referred to only by their surname. Writing "Mayor Hall" or "Mayor Georgina Hall" the first time she's mentioned in each section costs us little, and makes for more readable articles.
Heck, when something is vital to our understanding of their role — like our fictional Ms. Hall's Mayorship — I'd even consider supporting a policy that it should be included every time they're mentioned. When a person mentioned in an article is relevant solely or primarily due to their position, including that context ("Mayor Hall" rather than just "Hall") each time they're mentioned feels prudent. FeRDNYC (talk) 08:20, 15 July 2023 (UTC)
- Support once per section at a minimum. Weak support for the extension (
when something is vital to our understanding of [a person's] role ... it should be included every time they're mentioned
), but as guidance rather than hard rule. I agree it's frustrating to find oneself in the situation described as a reader, but I'd be weary of making re-contextualising-on-every-use a solid policy lest it cause articles to become stilted or take on a patronising tone. Better it should be encouraged, but with reasoned deviation permitted. XAM2175 (T) 10:15, 15 July 2023 (UTC)- Yeah, I'm not sure how I feel about the second part myself, it was a 'thinking out loud' sort of addition. While I feel it could be useful as "style advice", at least within the same paragraph you're right that it could read as stilted. So, you'd want to allow some leeway there, and it starts to feel like a bad fit for policy. FeRDNYC (talk) 15:43, 15 July 2023 (UTC)
- Allow but do not mandate - allowing re-contextualizing is fine, but mandating it "at least once a section" is overkill, and would result in excess verbosity. The wording of MOS:DL should probably apply to SURNAME as well (my emphasis here, not in MOS): "... may be repeated if helpful for readers ... at the first occurrence in a section".One significant and relevant difference between repeated links vs repeated title/forename is that repeated links do not take up any more space on my screen, and it's relatively easy to ignore the extra colouration of the link, but repeated title/forename does take up extra screen space, and more (unnecessary) words makes it harder to read the text (it's more cognitive load to skip over the repeated title/forename). Mitch Ames (talk) 04:10, 16 July 2023 (UTC)
- Oppose. Why would we cater to jump-around readers at the expense of an article that flows without repetition? In an article like Russo-Ukrainian War, we would have to write in full "President of Ukraine Volodymyr Zelenskyy" in every section, rather than just describing him as "Zelenskyy". That's not unlike describing Jesus in every relevant chapter of the bible, just for people who are jumping in somewhere. Our articles should have internal integrity, flow and readability, and not appear like a series of independent standalone sections cobbled together. WWGB (talk) 05:50, 16 July 2023 (UTC)
- Personally, if someone is mentioned only a few times in an article, and it's non-contiguous, and it isn't just a matter of in-text attribution for a source, I usually re-introduce them, at least briefly, usually including given name. It had never occurred to me that that violates MOS:SURNAME, and no one's ever called me on it, which is perhaps telling in itself. So, allow per Mitch. Which mirrors link repetition across sections: no one has to re-link a term every section (and in many articles that would look absurd); it's just that there's no longer a rule against it. -- Tamzin[cetacean needed] (she|they|xe) 02:00, 19 July 2023 (UTC)
- Full name repetition is something I do quite a bit – it doesn't break the flow and it makes what's going on for people like me, who skim and forget names that don't look important (particularly analysts). For mentions that are quite far apart from each other, I might do a title reintroduction. It makes for a better reading experience, it's more accessible, it doesn't throw off the look, would 100% support scrapping the no-repetition guideline. theleekycauldron (talk • contribs) (she/her) 06:23, 20 July 2023 (UTC)
- Generally oppose I understand the motivation as I sometimes read whole articles and sometimes jump into specific questions, but I think that repeatedly introducing individuals with full names and roles interrupts the flow and will generally be unnecessary. If I consider three general situations:
- The individual is a key character in the article. For example, to understand the Bowling Green massacre example you need to know who Kellyanne Conway is, so it seems reasonable to expect that the reader will read enough of the article that they don't need repeated reintroduction.
- The individual is notable enough to have a Wikipedia article. Now that we can have once-per-section hyperlinks, we can unobtrusively link to their article without breaking the flow of the text.
- The individual is not notable in the article or in Wikipedia generally. I can see that such individuals will occasionally need to be reintroduced but I generally oppose changing guidelines to recommend it, as in many cases this is best handled by not referring to the person by name at all: returning to the example posed above, the Bowling Green massacre article doesn't refer to the mayor by name, instead saying, "The mayor of Bowling Green, Kentucky, issued a statement...". --Mgp28 (talk) 11:40, 20 July 2023 (UTC)
- Reluctant weak support. In general, I don't think it's necessary to repeat full name or name and title in most instances, but I'd concede there are times where it may help the flow. I agree with WWGB's concern that we don't have articles that read like they're multiple articles just slapped together, but I think Mitch Ames has a point that we should allow (but not mandate) repetition to a limited degree when it helps the reader. —Carter (Tcr25) (talk) 12:31, 20 July 2023 (UTC)
- Comment. I'm supportive of the idea of contextualising individuals in later sections for the benefit of people who have not fully read and absorbed prior sections, but I'm not clear on what change is being proposed. The applicable bit of guidance currently reads After the initial mention, a person should generally be referred to by surname only, and then goes on to discuss a lot of edge case exceptions. I'll note that my practise to date has been that if I'm reading an article and come across an individual I don't recognise and have to root around in the upper bits of the article to identify them, I'll usually edit the section causing my confusion to add a very brief descriptor of the individual, unless it would clearly disrupt the flow of the full article, like if they were introduced at the end of the section immediately prior. I don't read this as violating should generally, and can't recall ever being reverted about it.I think the change wrought from the MOS:DL RfC actually low key weakens the need for this one, since later mentions of an individual can be uncontentiously wikilinked to their bio through their surname, allowing the reader a quick route to identification. For the examples given above,
Mayor Hall
andPresident Zelenskyy
are probably how I'd personally handle later section mentions, with or without linking as common sense indicates. So in general I'd put myself on team "allow, but don't mandate", but it would be nice if a specific change to the guidance text were proposed. Folly Mox (talk) 20:18, 20 July 2023 (UTC) - Allow but do not mandate. This proposal largely makes sense in the context of a person being mentioned as a "side subject" (e.g. mayor of the town the article is about), but it does not make much sense when it comes to inline source attribution. E.g., if the artice near the top has something like "According to Hugh Trevor-Roper (1983), [quote here][1], and then 7 sections later we have "Murray Pittock (2010) showed that the assumptions in Trevor-Roper (1983) were based on incomplete research, and left out [various important source stuff][23]", this is entirely fine. It's completely routine, and readers understand that "Trevor-Roper (1983)" is a reference to a previously-cited work that can be found in the bibliography of the article. Linking as "Trevor-Roper (1979)" in the later case does not help the reader, as the material in that specific context is about the author's written source, not the author as a biographical subject. — SMcCandlish ☏ ¢ 😼 22:45, 23 July 2023 (UTC)
GID inclarity
Complementary preferences
After names were explicitly added to the first sentence of MOS:GID, the guideline has become rather confusing; see Talk:Eddie Izzard#Semi-protected edit request on 7 June 2023. Currently it says we should use a name consistent with the most recent expressed gender identity, when I'm pretty sure the intent was that we should use the name(s) the subject most recently identified with. This leads to confusion where, like in the linked thread, it can be argued that because a nonbinary subject approves one masculine name, they can also be called by another name because that is also masculine. Thoughts? -- Maddy from Celeste (WAVEDASH) 10:58, 9 June 2023 (UTC)
- Pinging User:Actualcpscm who partook in that discussion. -- Maddy from Celeste (WAVEDASH) 11:01, 9 June 2023 (UTC)
- Thanks for the ping! I'd like to add some general questions to this:
- 1. What happens if the most recently expressed partial preferences are contradictory? For example, what if someone expresses preference for she/her pronouns and then expresses preference for an umambiguously male-identifying first name? What pronouns should an article about them use? Really, the question here is: How do editors deal with cases of multiple complementary preferences, and what is the room (if any) for interpretation and extrapolation?
- 2. How do we separate gender-related name ambiguity from other non-legal names like personas or nicknames? If a trans person who has changed their name was previously notable under a nickname, how do we treat their birth name? Is it appropriate to refer to a trans person by their birth name if their preferred name is a common hypocorism of their birth name? Actualcpscm (talk) 11:14, 9 June 2023 (UTC)
- As to the specific examples @Maddy from Celeste and @Actualcpscm brought up: Izzard is an tough case because (as I understand) she personally identifies by one name but professionally identifies by another; she's part of a class of persons who, as Actualcpscm articulately described, have "multiple complementary preferences". I actually don't think this edit addresses those situations, and I don't know that any guidance can? (I mean, I can think of a few things, but none of them would be great or have a snowball's chance in hell of getting consensus.) I think those sorts of issues are going to require page-by-page resolution.--Jerome Frank Disciple 13:32, 9 June 2023 (UTC)
- I agree that we can‘t account for every edge case of complementary preferences, but I‘d like to „codify“ the need for internal consistency in such cases. The article that triggered this discussion, Eddie Izzard, currently refers to Izzard as Eddie (short for Edward, i.e. a masculine name) in the lead sentence, but then goes on to use she/her pronouns. This accounts for the multiple preferences expressed by Izzard, but I think internal consistency is more important for readability and clarity. The fact that this naming ambiguity even exists is indicative of an ambiguous gender identity, for which I think commitment to one name and pronoun set is more important than following the letter of the expressed preferences in a meticulously literal way. I‘m not sure if this is community consensus, though; I‘m not very familiar with the RfC that resulted in MOS:GID. Actualcpscm (talk) 14:18, 9 June 2023 (UTC)
- I definitely see your point, and I definitely agree there should be intra-article consistency (and consistency across Wikipedia for one person). My concern is that the individuals preferences will be so unique that they’ll be hard to account for. for example, with Izzard we might craft a guideline that says “prioritize stage names” or “prioritize personal names” (on my phone and am not that familiar with Izzard so sorry if that’s not quite right—just working a hypo here). But how many other modern persons will that apply to? (genuinely asking)—Jerome Frank Disciple 14:23, 9 June 2023 (UTC)
- How about something along the lines of this:
„In the case of multiple complementary or contradictory preferences that have been recently expressed, either together or at the same time, articles should use only one set of name(s) and pronouns for internal consistency. Which set that is should be decided on a case-by-case basis, prioritizing the naming convention under which the individual is notable or reported on. [This priority is secondary to the individual‘s preferences and only applies in cases of ambiguity in their preferences.]“
- I‘m not quite happy with the wording, but I think you get the idea. Notability and reporting practices are relevant only when the individual has said something like „any set of pronouns is completely fine.“
- Basically, IFF the criterion of expressed preference doesn‘t yield a clear result, we default back to standard practices, i.e. Wikipedia sticks to how the reliable sources say it. Actualcpscm (talk) 15:50, 9 June 2023 (UTC)
- Re. Izzard: I‘m really not sure how to describe the Izzard situation, they have adopted a very complex gender identity that‘s linked to their performances but not exclusive to their stage persona. I‘m really not sure.
- Re. Frequency of this issue: I think we‘ll see more and more notable individuals that are gender-nonconforming, and a good bit of them will say „I like he/him and she/her equally“, or something like that. This won‘t be the last time this question comes up, and as it currently exists, MOS:GID doesn‘t account for it. Actualcpscm (talk) 15:54, 9 June 2023 (UTC)
- That's a fine point! I'm going to add just a few final thoughts before I let others take over and respond, because I do have some concerns:
- I'm, personally, a little hesitant about preemptive guidelines ... I generally think it's safer to let an issue appear, see how it's handled on an article-by-article basis, and either capture the standard practice or resolve a split by resorting to the guidelines.
- I also wonder how often "internal consistency" is going to be an issue in light of MOS:SURNAME.
- Finally, while currently handled by IAR, I suspect there are going to be a few editors who object on historical-figure grounds.
- I do think you're right that this is going to be an issue—there's a related RFC on Talk:Celia Rose Gooding, who, on her twitter profile, listed "they/she" pronouns, and, later, in a tweet, said "
I use both she and they pronouns
". In that case, the discussion seems to have focused on (1) how to determine Gooding's preference (with most users relying on which pronoun was listed first in the twitter bio) and (2) how to best avoid ambiguity (with many users supporting "she" suggesting that "they" should be subordinated by default). Oddly, few users suggesting going by what most reliable sources used (though perhaps that's because the Twitter announcement postdated most reliable sources about the person, so the question turned on recency). - This all said ... if we were to add a statement capturing what you propose, perhaps we could kill at least a few of the words?
If such a person's most recently expressed identity is unclear (or the person has simultaneously embraced multiple identities), articles should be consistent about pronoun usage and which name is treated as the person's principal name. These determinations should be made on a case-by-case basis.
- --Jerome Frank Disciple 16:11, 9 June 2023 (UTC)
- Just want to point out, at around the time Gooding put out the
I use both she and they
tweet, their social media profiles listed she/they. At some point after the tweet it was changed to the current order of they/she. Sideswipe9th (talk) 16:48, 9 June 2023 (UTC)- Oooh I somehow missed that entirely! I need to update my comment on that talk page. Thanks for pointing that out!--Jerome Frank Disciple 16:50, 9 June 2023 (UTC)
- I'd mentioned it in my !vote in the current RfC over there, but I guess a bunch of folks haven't read it. Sideswipe9th (talk) 16:53, 9 June 2023 (UTC)
- You did! Weird—I actually remember clicking on each of the external links you provided, and I very much remember the points you made in the second and third paragraph (the third, especially, led me to address that issue in a parenthetical at the end of my comment) ... I guess I somehow just glossed over the last sentence of that first paragraph?? Sorry about that!--Jerome Frank Disciple 16:56, 9 June 2023 (UTC)
- I'd mentioned it in my !vote in the current RfC over there, but I guess a bunch of folks haven't read it. Sideswipe9th (talk) 16:53, 9 June 2023 (UTC)
- Oooh I somehow missed that entirely! I need to update my comment on that talk page. Thanks for pointing that out!--Jerome Frank Disciple 16:50, 9 June 2023 (UTC)
- Good points! Going through them one by one:
- 1. I agree, we shouldn't make guidelines for issues that haven't come up yet. However, we're here because there have been cases of ambiguity, and my point was intended as "This will continue to happen into the future, these cases are not unique or limited to a specific time period."
- 2. I think your proposal resolves this; we're not saying that individuals need to be addressed by their chosen first name, just that there needs to be a consistent naming convention within articles.
- 3. Historical figures are tricky to figure out because our understanding of gender has changed so much in such a short time. Again, I think your proposed text gets around this nicely.
- I'm also quite surprised that reporting in reliable sources wasn't taken into account that much in the RfC you mention, but so be it. If that's what current practice is, it should be reflected accurately here.
- Slightly amended proposal:
If a person's most recently expressed gender identity is unclear (or the person has simultaneously expressed multiple identities), articles should be internally consistent with regards to the name that is treated as the person's principal name and the pronouns that are used to refer to them. These determinations should be made on a case-by-case basis.
- I'm also pinging @Maddy from Celeste and @ScottishFinnishRadish for feedback. If everyone feels that this reflects current community consensus, I'll go ahead and add it to MOS:GID. Yay
policymakingguideline-drafting! Actualcpscm (talk) 16:49, 9 June 2023 (UTC)- If you want to narrow it down a lot, you could just say, at the end of paragraph 1: "
Complex and ambiguous cases should be treated on a case by case basis, but articles should be internally consistent as to a person's principal name and pronouns.
" I'd like to see what others have to say about this, but I don't have a problem with it.--Jerome Frank Disciple 17:12, 9 June 2023 (UTC)- Either of these looks good to me. -- Maddy from Celeste (WAVEDASH) 16:38, 11 June 2023 (UTC)
- Implemented with minor changes! Actualcpscm (talk) 12:12, 12 June 2023 (UTC)
- I'm not entirely convinced that a clarification along these lines is needed yet. I think SFR's comment below encapsulates why I don't think we need a clarification point like this. If a person choses to use a typically masculine name with feminine pronouns, or vice versa, I don't think we need to second guess it in any way, we just need to follow how they wish to be referred to. Likewise if a person expresses themselves in a typically masculine or feminine way, and wants us to use they/them pronouns, then we should respect that.
- Izzard's case seems kinda unique to me, in that she's making a clear distinction between her public and private personas. She's maintaining use of the name Eddie Izzard for her public presence, while elsewhere she would prefer if people refer to her as Suzy. The way I would interpret her most recent statement is that Eddie is remaining her stage name, whereas Suzy is her actual name. Because our biographical articles are typically about the whole person, I lean towards using Suzy as the primary name.
- However of the two options put forward so far, I much prefer the shorter version from Jerome as I don't think we need to be as verbose as Actualpscm's proposal. Both broadly convey the same meaning, but the shorter version also allows for a little more wiggle room on what is considered a
complex or ambiguous case
. Sideswipe9th (talk) 17:15, 13 June 2023 (UTC)- I think this is a very different matter from the IAR clarification that SFR was referring to in that comment. This is a much more substantial clarification than "the general principles of reading guidelines apply to this guideline." Importantly, we're not deviating from the RfC consensus here.
- Really all we're saying is that articles should stick to one primary name and one set of pronouns, whatever they may be. In the case of someone like Izzard, it could be argued that different sections of the article should refer to Izzard in different ways (for example as Suzy in a Personal life section and as Eddie in a Performances section). I don't think that would be a good idea; as you put it, biographical articles are about the whole person. After Maddy and SFR confirmed that they agree with this clarification in principle, I added it here; what do you think about the wording? Actualcpscm (talk) 11:19, 14 June 2023 (UTC)
- Are we sure that there aren't any potential articles on genderfluid subjects where it might be appropriate to use different pronouns in different parts of the article? For any guideline, there will always be complex and ambiguous cases to be dealt with on a case-by-case basis; we can't predict exactly what they will involve. I agree that in general articles should strive to be consistent, but I'm not sure we need to specify it as a hard rule. (Specifying a rule as specifically designed for complex cases makes it very hard to justify any exceptions.) It's not the same, but I am thinking of how articles like Trixie Mattel and Conchita Wurst switch between names and pronouns when describing the drag/real-life personas, and are better for it.--Trystan (talk) 12:55, 14 June 2023 (UTC)
- I am convinced by this argument, so I retract my support for either amendment. -- Maddy from Celeste (WAVEDASH) 12:58, 14 June 2023 (UTC)
- I don't think I agree that those articles are necessarily made better by this inconsistency. In fact, it very much clashes with what we mentioned just above; biographical articles are about the person as a whole, not about their stage personas. Of course those personas need to be mentioned and accordingly referred to, but the article itself should be about the actual individual. If I were to rewrite those articles right now, I don't think I'd mix pronouns the way they currently do. However, I'm not sure what the community consensus is on biographies that extensively cover stage personas; I'd like to get some input from other editors. @Jerome Frank Disciple @ScottishFinnishRadish @Sideswipe9th, you have all been very involved in this discussion; what do you think? Should biographical articles that cover stage personas treat those personas as their subject in this way?
- I'm reverting the changes I made since they apparently don't reflect current consensus. Let's see how the debate develops. Actualcpscm (talk) 13:05, 14 June 2023 (UTC)
- Are we sure that there aren't any potential articles on genderfluid subjects where it might be appropriate to use different pronouns in different parts of the article? For any guideline, there will always be complex and ambiguous cases to be dealt with on a case-by-case basis; we can't predict exactly what they will involve. I agree that in general articles should strive to be consistent, but I'm not sure we need to specify it as a hard rule. (Specifying a rule as specifically designed for complex cases makes it very hard to justify any exceptions.) It's not the same, but I am thinking of how articles like Trixie Mattel and Conchita Wurst switch between names and pronouns when describing the drag/real-life personas, and are better for it.--Trystan (talk) 12:55, 14 June 2023 (UTC)
- I don't have much to add here, other than I don't often end up editing in these situations so I'm not sure how best to handle it, and the RFC that I closed didn't really deal with this particular wording so I don't have much to clarify on that front. ScottishFinnishRadish (talk) 11:34, 12 June 2023 (UTC)
- If you want to narrow it down a lot, you could just say, at the end of paragraph 1: "
- Just want to point out, at around the time Gooding put out the
- That's a fine point! I'm going to add just a few final thoughts before I let others take over and respond, because I do have some concerns:
- I definitely see your point, and I definitely agree there should be intra-article consistency (and consistency across Wikipedia for one person). My concern is that the individuals preferences will be so unique that they’ll be hard to account for. for example, with Izzard we might craft a guideline that says “prioritize stage names” or “prioritize personal names” (on my phone and am not that familiar with Izzard so sorry if that’s not quite right—just working a hypo here). But how many other modern persons will that apply to? (genuinely asking)—Jerome Frank Disciple 14:23, 9 June 2023 (UTC)
- I agree that we can‘t account for every edge case of complementary preferences, but I‘d like to „codify“ the need for internal consistency in such cases. The article that triggered this discussion, Eddie Izzard, currently refers to Izzard as Eddie (short for Edward, i.e. a masculine name) in the lead sentence, but then goes on to use she/her pronouns. This accounts for the multiple preferences expressed by Izzard, but I think internal consistency is more important for readability and clarity. The fact that this naming ambiguity even exists is indicative of an ambiguous gender identity, for which I think commitment to one name and pronoun set is more important than following the letter of the expressed preferences in a meticulously literal way. I‘m not sure if this is community consensus, though; I‘m not very familiar with the RfC that resulted in MOS:GID. Actualcpscm (talk) 14:18, 9 June 2023 (UTC)
Proposal to address potential ambiguity re: persons with deadnames that match their current expressed gender identity
While the above section seems to chiefly concern the persons with, borrowing language from Actualcpscm, "complementary preferences" regarding their names, I think Maddy also brought up a semi-distinct issue that can be addressed fairly easily. I suggest we remove "gender" from the phrase "gender self-identification" in paragraph one. I made that edit here, but it was reverted with a "get consensus first" message. I haven't seen anyone oppose, but I figured this separation will give them an opportunity to do so.
The paragraph in question already applies only to those "whose gender might be questioned" (though that could maybe be better phrased). Because "names" was added per the rfc, there was a possibility of some ambiguity: If a trans man originally had a masculine name (but still changed it), should we principally refer to him by his birth name, since that would be consistent with his most recent expressed "gender self-identification"? ... I think almost everyone here would say "no": Given the RFC's thematic focus on deadnaming (and the fact that such a person's birth name would still be a deadname), I think that's the most reasonable understanding of the community's position. Removing "gender" addresses the issue.
Refer to any person whose gender might be questioned with the name and gendered words (e.g. pronouns, man/woman/person, waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources, even if it does not match what is most common in sources. This holds for any phase of the person's life, unless they have indicated a preference otherwise.
--Jerome Frank Disciple 14:53, 9 June 2023 (UTC)
- That seems reasonable, and the second "gender" in that construction was redundant in the first place. I'm wracking my brain for any negative unintended outcome that could result from this edit, and nothing is coming to mind. — SMcCandlish ☏ ¢ 😼 22:13, 23 July 2023 (UTC)
- Ok, so what if the person likes to be called Jane or Helen but reliable sources doesn't state the preferred pronoun? I think referring to Jane as she/her would be assuming gender, which is what some in the LGBT+ movement find offensive. Regards, Thinker78 (talk) 22:18, 23 July 2023 (UTC)
- We wouldn't be writing about them here at all without reliable sources, and the odds of zero of those sources ever using a pronoun to refer to the person are slim to none. We can entirely reasonably construe from the recent-er RS material what pronoun(s) are appropriate. — SMcCandlish ☏ ¢ 😼 10:27, 24 July 2023 (UTC)
- Ok, so what if the person likes to be called Jane or Helen but reliable sources doesn't state the preferred pronoun? I think referring to Jane as she/her would be assuming gender, which is what some in the LGBT+ movement find offensive. Regards, Thinker78 (talk) 22:18, 23 July 2023 (UTC)
Can we stop misgendering neopronoun users?
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- This discussion has gotten quite heated for one in which most participants substantially agree. I'm going to attempt an involved close here before this devolves into something worse. If anyone desperately feels that this should continue, feel free to revert me (just please copy this comment to the discussion itself); but hear me out first.-- Tamzin[cetacean needed] (she|they|xe) 02:18, 26 July 2023 (UTC)
- There was a strong consensus in the November RfC to generally use they/them in lieu of neopronouns, and to the extent that a discussion like this can serve as a straw-poll of change in consensus, it seems that that remains by far the prevailing view in the community.
- The question of whether this constitutes misgendering is probably a red herring, but regardless most participants felt that it either doesn't at all, or only conditionally does.
- No one has identified any specific articles where they/them is used over the subject's explicit objection. No one seems to be arguing that, in such a case, we must use they/them, compared to an alternative of surname-only or even, potentially, using neopronouns as a one-off case. (A local consensus for the latter seems unlikely as of this writing, but would not contradict the guideline.)
- Concerns about editors' conduct can be raised at AN/I or AE (cf. WP:GENSEX, WP:ARBATC) as appropriate, but I'm hoping that closing at this juncture can prevent that.
- This discussion has gotten quite heated for one in which most participants substantially agree. I'm going to attempt an involved close here before this devolves into something worse. If anyone desperately feels that this should continue, feel free to revert me (just please copy this comment to the discussion itself); but hear me out first.
The current policy is to use they/them when someone uses neopronouns, which is very confusing because one of the main reasons people have to use neopronouns is that they want a gender neutral pronoun but are uncomfortable being called they/them. I think the policy should be to use whatever pronouns are requested, with the exception of satire. Example of satire: when Michelle Malkin said her pronouns are "u/s/a". Afroswordguy (talk) 09:59, 26 May 2023 (UTC)
- So we had a huge discussion about this last year, which is footnoted in the guidance. I would personally also take exception to the idea that not using a person's neopronoun in the running prose of the article constitutes misgendering. Pronouns can be representative of gender identity, but there's not a one-to-one mapping. Folly Mox (talk) 13:20, 26 May 2023 (UTC)
- This is the English language Wikipedia. Hence, it should use English words, not phantasy words. Linguistically, Pronouns are a closed word class. Str1977 (talk) 20:58, 2 July 2023 (UTC)
- This kind of statement baffles me from both the perspective of Wikipedia's mission statement and just overall the entire concept of language and its evolution. Words are not handed down to us from on high, they emerge naturally as people use them, and those words then change over time thanks to linguistic drift.
- Just because a pronoun is made up doesn't make it not a real word, for the same reason that just because the word "yeet" is made up doesn't make it not a real word. Words are words because people use them, not because some higher authority decided they are words. IcarusAvery (talk) 23:04, 8 July 2023 (UTC)
- @IcarusAvery: True in Engliish, though not in e.g. French, where there actually is a governing body (the Académie Française) that holds authority over the official definition of the language, and is responsible for deciding which words are standard French and which are not.
- You're correct, though, that the English language is entirely defined by usage. English dictionaries are reactive, not prescriptive: They document the evolving language after-the-fact, based on usage encountered "in the wild". New words enter the English language the same way every existing word did: when it becomes common usage. There is no such thing as a
closed word class
— what an utter "phantasy". - (I especially love it when people use the phrase "made-up words", like that somehow makes a word not "real". ALL words are made up!) FeRDNYC (talk) 01:18, 15 July 2023 (UTC)
- Let's not be silly. I do not believe for one second that you do not know that what is meant is "recently made up words", i.e. MOS:NEOLOGISMS. The objection is to their lack of broad acceptance in the language, not to the fact that someone coined them, because of course everything in language was ultimately coined by someone at some time. You're basically engaging in a fallacy of equivocation and a subtle form of straw man, in attacking a carefully selected meaning of a phrase when everyone here knows that it was not the intended meaning. — SMcCandlish ☏ ¢ 😼 02:31, 25 July 2023 (UTC)
- (Wikipedia's List of language regulators is quite long, and amazingly enough English appears to be the only firm "None" on the list! Though there are surely many other languages that are "None"s by omission.) FeRDNYC (talk) 01:27, 15 July 2023 (UTC)
- How do you discern which are satire and which are not? —DIYeditor (talk) 21:31, 2 July 2023 (UTC)
- @DIYeditor: how do you discern whether a public figure stating their birthday is satire? (Example of satire: James Acaster on Sunday Brunch.) WP:BLPSELFPUB with a dose of WP:IAR suffices. There's nothing special about pronouns. — Bilorv (talk) 10:53, 18 July 2023 (UTC)
- Cisgender gay male ally of transgender and nonbinary people here: To start with, using "they" instead of whatever pronoun a given nonbinary person has prescribed for use for themselves isn't misgendering them. Calling someone "they" instead of "ze" or "ter" or "xe" or any of the other forms that have been proposed over the years isn't misgendering them, it's simply failing to, or refusing to, use an idiosyncratic pronoun. "Ze" doesn't imply a different gender from "they", they both convey that the referent individual falls outside of the male-female dichotomy.
- Setting aside that terminological comment: Over the years there were various proposals for nonbinary pronouns. A long time ago I read a claim that the community seemed to be settling on "ze", "zir", "zeir". That seemed great to me. But in the end, the consensus came around to the reuse of the plural pronoun. I've always thought that was dumb, by the way, but that's the reality of it, and in English it's a fait accompli that "they" has become the nonbinary pronoun.
- Suppose that in 1950, a self-identifying cisgender man had announced that he wanted to be referred to as "zoom" instead of "he"—expecting people to remember it (and also to remember similar requests from many other people, if self-tailored pronouns were to become the fashion), and being offended if people didn't know or didn't remember or chose to ignore his preference. It would have been asking an awful lot. It would have amounted to his having unilaterally declared, based on his own preference, a transfer of pronouns out of the realm of grammar and, like people's names, into the realm of individual identification. To me, the idea seems impractical and unreasonable.
- That being my view in that scenario, it isn't different for nonbinary people. For that reason, I support uniformly using "they" for nonbinary people on Wikipedia. It's the established pronoun for that purpose. If they say they're being misgendered by that, I consider that to be an objectively false assessment of the situation. Largoplazo (talk) 22:12, 2 July 2023 (UTC)
- I don't mean to be rude - I'm sure you're arguing in good faith and don't have any malice here - but as someone who was there when using "they/them" pronouns was considered contentious (to be frank, they still are, just not as severely) hearing the phrase "if they say they're being misgendered by that, I consider that to be an objectively false assessment of the situation" feels very much like that old meme "I thought was experiencing transphobia, but thank God I had this cis person here to tell me I'm wrong."
- You (that's a general "you", not you specifically) do not get to decide if someone else isn't actually being misgendered. Using "they/them" for someone who you know uses "fae/faer" or whatever is equivalent to and just as bad as using "they/them" for someone who you know uses "she/her" or using "she/her" or "he/him" for someone who you know uses "they/them." You are actively denying someone a part of their identity. If someone uses neopronouns exclusively, those are the pronouns you use for that person.
- In the case of "this person uses multiple sets of pronouns, some neopronouns and some more traditional ones" I can see the argument being made to primarily use the more traditional ones (especially using just a single set of them) in formal writing like Wikipedia just for ease of reading, but if Jane Doe over here uses "fae/faer" and no other pronouns, using "they/them" for faer is misgendering faer unless fae comes out and says "I don't personally consider that to be misgendering me" or something along those lines. IcarusAvery (talk) 23:14, 8 July 2023 (UTC)
- I'm sorry, but - no. "They" is a perfectly acceptable neutral pronoun to use in a catch-all capacity. Wiki editors (and people in general) are not expected to remember and recite any esoteric, obscure, and even conjured neopronoun. "They" is, by its very nature, a neutral way to refer to anyone. — Czello (music) 23:24, 8 July 2023 (UTC)
- More generally, Wikipedia readers cannot be expected to be able to read and understand made-up and non-standard words. That is why MOS:NEO states that neologisms "should generally be avoided". Neopronouns are by their nature neologisms. Singular they is not; it has many centuries of history of usage. —David Eppstein (talk) 00:20, 9 July 2023 (UTC)
- I'm not sure WP:NEO should apply to neopronouns, personally, and I think the policy at MOS:NEOPRONOUN may eventually come to be seen as stuffy and behind-the-times. But, that's probably to be expected, as it's an encyclopedia's job to be a little bit stuffy, and relatively slow to react to changes in the world.
- (Because, the world is changing, in terms of its views on personal pronouns. It doesn't really matter what people of my generation think. (I'm 48.) We'll all be dead any moment now — on a geological time scale — and many younger minds have very different views on this subject in particular. Those views will likely come to dominate, eventually.)
- And TBH, I actually find it refreshing that the world at large — even the older generations, for the most part — have grown to embrace singular "they" as readily and as widely as we collectively have. There was a time, even just 10, 20 years ago, when you'd have had people arguing that the only singular pronouns are "he"/"him" and "she"/"her". All bases are covered by those two, they'd have insisted, and when in doubt just use "he"/"him" because patriarchy. We've already come a long way since then, actually, and only fairly recently. FeRDNYC (talk) 02:14, 15 July 2023 (UTC)
- As a principal editor of MoS for over a decade, I can assure you that neopronouns were definitely part of the rationale behind MOS:NEO; they are not excluded for a reason. You're possibly correct that "MOS:NEOPRONOUN may eventually come to be seen as stuffy and behind-the-times"; all of MOS:GENDERID once did, as did several other MoS passages that have since changed (including MOS:POSS and MOS:JR, etc.). They changed when real-world practice had overwhelmingly changed, and these changes were then reflected in the academic-leaning style guides that MoS is actually based on (Chicago, Garner's, Oxford/Hart's, Fowler's). That hasn't happened yet with neo-pronouns and quite possibly never will, because changing the inflectional morphology of a language, including very basic words like pronouns, is extraordinarily difficult to engineer. (It's linguistically very different from coining a new noun, verb, or phrase.) — SMcCandlish ☏ ¢ 😼 03:06, 25 July 2023 (UTC)
- I'm going to echo IcarusAvery and say that misgendering is something that's defined by the individual, not by your personal opinion on what constitutes misgendering. people use neopronouns because they want to be referred to by neopronouns. if they were okay with they/them pronouns then they would use they/them pronouns instead of or in addition to neopronouns. you may not agree that this is the case, but it is harmful to use they/them pronouns to refer to someone who, for example, comes out as a trans woman and expresses that she wants to be referred to with she/her pronouns. she's told you what her pronouns are and intentionally using different pronouns (outside of situations where you would use they/them pronouns for anyone) is probably going to feel like misgendering to her. the same goes for people who use neopronouns.
- I would support a proposal to use neopronouns for people who use neopronouns. I understand the reasons we don't do so now but I don't think it ultimately makes sense that we're drawing arbitrary lines about whose pronouns we respect. Tekrmn (talk) 05:21, 20 July 2023 (UTC)
- That means "misgendering" under your personal definition – which is clearly not the one in general use in the language, frankly – would be an idiolect matter, and WP is not and cannot be written in idiolects, or readers will not understand the material. This is very closely (via the concept of microaggressions, etc.) tied to the notion that "an attack" or "violence" is entirely defined by the alleged victim. This is a sometimes a useful notion in entirely individual contexts such as a psychotherapy session ("all trauma is trauma", "your feelings are valid", etc.) but has no applicability to more objective contexts like legal systems or encyclopedia writing; you don't get to randomly punish other people for "attacking" or "doing violence" to you that are not more objectively defined as attacks or violence by the community/society in which you are operating. — SMcCandlish ☏ ¢ 😼 03:15, 25 July 2023 (UTC)
- you brought this topic to my talk page, where you said you weren't interested in continuing to engage with me on it. I have no interest in continuing to discuss this with you either, so I'd appreciate if you would not seeking out previous comments I've made on the subject, or otherwise try to continue a discussion with me on it. Tekrmn (talk) 06:56, 25 July 2023 (UTC)
- This is a public discussion page. You cannot expect what you assert here to go unaddressed. Discussion and consensus formation does not work that way. There is no "right to speak your mind unchallenged on Wikipedia". And the behaviorial issues I raised in user-talk are completely severable from the substantive matters I am addressing above; they're barely related at all. And you directly asked me to come to your talk page about these matters, and even said "if you can clarify why you feel it [Tekrmn behavior in this topic] is any of those things [objections SMcCandlish made to that behavior] I'd be more than happy to consider any insight you might provide". I did so rather patiently, even identifying exactly which wording came across as aspersion-casting and name-calling, and how to avoid that; but then you just censored the entire thread away without comment. So, this is coming off as just a bit disingenuous, along WP:1HAND lines. — SMcCandlish ☏ ¢ 😼 07:26, 25 July 2023 (UTC)
- you've already addressed the very same assertion on this talk page, without responding to any of my other points and while accusing me of a myriad of logical fallacies and then going on to accuse me of a myriad of bad faith behavior.
- your summary of the events is pretty seriously edited. Tekrmn (talk) 17:40, 25 July 2023 (UTC)
- I don't see what point you're trying to make. Yes, my editing is usually serious. Yes, I raised a behaviorial point here, and you said you'd rather discuss it in user talk so I took it there, then after offering to engage you did the opposite. (And having said my piece I had dropped the behavioral matter entirely.) I'm now trying to address content-specific matters here, but you're dragging our attention back toward to the behavioral dispute. Is there any kind of point to doing that? — SMcCandlish ☏ ¢ 😼 21:52, 25 July 2023 (UTC)
- again, a mischaracterization of what happened, but my point is that I'd like you to stop seeking out every possible opportunity to start an argument with me. Tekrmn (talk) 22:01, 25 July 2023 (UTC)
- Thank you for clarifying that you’re unable to address SmC’s comments on your “misgendering” statements. —Locke Cole • t • c 23:02, 25 July 2023 (UTC)
- there have been points raised about the practicality of using neopronouns when many of our readers do not speak english as a first language, which I found quite compelling, so there's no reason for me to continue this discussion. being "unable to address" another editor's comments is far from the only reason one might not engage with said editor, especially when the discussions have been contentious. Tekrmn (talk) 23:11, 25 July 2023 (UTC)
- If you have nothing to add you could simply stop replying? —Locke Cole • t • c 23:16, 25 July 2023 (UTC)
- there have been points raised about the practicality of using neopronouns when many of our readers do not speak english as a first language, which I found quite compelling, so there's no reason for me to continue this discussion. being "unable to address" another editor's comments is far from the only reason one might not engage with said editor, especially when the discussions have been contentious. Tekrmn (talk) 23:11, 25 July 2023 (UTC)
- Thank you for clarifying that you’re unable to address SmC’s comments on your “misgendering” statements. —Locke Cole • t • c 23:02, 25 July 2023 (UTC)
- again, a mischaracterization of what happened, but my point is that I'd like you to stop seeking out every possible opportunity to start an argument with me. Tekrmn (talk) 22:01, 25 July 2023 (UTC)
- I don't see what point you're trying to make. Yes, my editing is usually serious. Yes, I raised a behaviorial point here, and you said you'd rather discuss it in user talk so I took it there, then after offering to engage you did the opposite. (And having said my piece I had dropped the behavioral matter entirely.) I'm now trying to address content-specific matters here, but you're dragging our attention back toward to the behavioral dispute. Is there any kind of point to doing that? — SMcCandlish ☏ ¢ 😼 21:52, 25 July 2023 (UTC)
- This is a public discussion page. You cannot expect what you assert here to go unaddressed. Discussion and consensus formation does not work that way. There is no "right to speak your mind unchallenged on Wikipedia". And the behaviorial issues I raised in user-talk are completely severable from the substantive matters I am addressing above; they're barely related at all. And you directly asked me to come to your talk page about these matters, and even said "if you can clarify why you feel it [Tekrmn behavior in this topic] is any of those things [objections SMcCandlish made to that behavior] I'd be more than happy to consider any insight you might provide". I did so rather patiently, even identifying exactly which wording came across as aspersion-casting and name-calling, and how to avoid that; but then you just censored the entire thread away without comment. So, this is coming off as just a bit disingenuous, along WP:1HAND lines. — SMcCandlish ☏ ¢ 😼 07:26, 25 July 2023 (UTC)
- you brought this topic to my talk page, where you said you weren't interested in continuing to engage with me on it. I have no interest in continuing to discuss this with you either, so I'd appreciate if you would not seeking out previous comments I've made on the subject, or otherwise try to continue a discussion with me on it. Tekrmn (talk) 06:56, 25 July 2023 (UTC)
- That means "misgendering" under your personal definition – which is clearly not the one in general use in the language, frankly – would be an idiolect matter, and WP is not and cannot be written in idiolects, or readers will not understand the material. This is very closely (via the concept of microaggressions, etc.) tied to the notion that "an attack" or "violence" is entirely defined by the alleged victim. This is a sometimes a useful notion in entirely individual contexts such as a psychotherapy session ("all trauma is trauma", "your feelings are valid", etc.) but has no applicability to more objective contexts like legal systems or encyclopedia writing; you don't get to randomly punish other people for "attacking" or "doing violence" to you that are not more objectively defined as attacks or violence by the community/society in which you are operating. — SMcCandlish ☏ ¢ 😼 03:15, 25 July 2023 (UTC)
- More generally, Wikipedia readers cannot be expected to be able to read and understand made-up and non-standard words. That is why MOS:NEO states that neologisms "should generally be avoided". Neopronouns are by their nature neologisms. Singular they is not; it has many centuries of history of usage. —David Eppstein (talk) 00:20, 9 July 2023 (UTC)
- In your argument you conflate the pronoun with the gender. If your analysis is correct, is there one gender to which all people who wish to be referred to as "they" belong, one gender to which all people who wish to be referred to as "fae" belong, and are those different genders? I suspect not. Conversely, if there is a gender (other than male or female) with which multiple people identify and, of those people, some wish to be referred to as "they" and some as "fae", then, since my premise is that they're of the same gender, how can using "they" for someone of that gender who prefers "fae", or vice versa, be misgendering them when both pronouns are in use to refer to people of that same gender?
- It's the same as the cis man I put forth in my previous remarks who wants to be referred to as "zoom". He isn't denying that he's male, a man. Therefore, no matter how upset he might get when people go right on referring to him as "he", any argument by the self-identifying male that he's being "misgendered" when he's referred to using the standard pronoun for referring to self-identifying males is counterfactual. Largoplazo (talk) 02:21, 15 July 2023 (UTC)
- Colloquially, referring to someone using the wrong pronouns, like ascribing the wrong gender identity to them, is an act of "misgendering". It's not literal, since you can't actually gender someone... how would that even work? But in languages (like English) where certain pronouns are traditionally associated with certain genders, pointing to someone and saying, "this man", or using "sir", "he", or "him" to refer to that person, when they don't identify as a male using he/him pronouns, all constitut pretty much the same offense.
- How (or whether) that extends to other pronouns that don't necessarily fall into those traditional gender divides — like singular "they" — is a topic of discussion and debate. There's no definitive answer on that, and opinions will vary. But holding up
someoneyour strawman and claiming zoom is wrong or being logically inconsistent simply because zoom's views on pronouns and gendering are different from your own feels like a losing one. FeRDNYC (talk) 07:08, 15 July 2023 (UTC) - (Already regretting not using "strawperson".) FeRDNYC (talk) 07:14, 15 July 2023 (UTC)
- If that's what "misgendering" means colloquially, then when you say I'm "misgendering" somebody by using a pronoun that isn't the one they prefer, all you're saying is that I'm using a pronoun that isn't the one they prefer, which is vastly different from what I understand that word to mean, which is to assign them to the wrong gender. The latter is to deny their gender, which is wrong; the former is simply not to go along with an idiosyncratic demand that is independent of gender. Yet your use of that word implies that I'm committing the former. That's a deception. It sounded like you were telling me I was doing something bad, but now you're telling me is that all you're doing is restating what I'd already said using in different terms.
- It reminds me of something the comedy writer Alan King once wrote (paraphrasing here): "When my lawyer found out I didn't have a will, he said, 'Alan, don't you realize that if you die without a will, you can die intestate?' He scared the hell out of me until I looked up 'intestate' in the dictionary and found out it means 'dying without leaving a will'. So this genius was telling me that if I die without leaving a will, I'm going to die without leaving a will. That gem cost me $20." (Lawyers' billing rates were much lower in 1961 than they are now.) As in Alan King's story, you used the word "misgender" in a way that implied I was doing something that should be of concern. Then it turned out it only meant that I was doing what I'd already acknowledged I was doing. Basically, this colloquial usage has rendered the word powerless, which is not really a result that you want if you also want to be able to use it to refer to actual misgendering, which I agree is a problem. If people have extended the meaning of the word in that manner, then they've shot it the foot. It should no longer be used in discourse because it can be used to mean one thing while sounding like it means something else. Avoid the word altogether and say what you actually mean. Am I saying we shouldn't feel obliged to memorize new pronouns for people who want to invent them for themselves? Yes. Am I calling a nonbinary person a man or a woman? No. Let's keep that distinction clear. Alternatively, let everyone agree to stop using "misgender" for this new, "colloquial" meaning. It's rhetorically sloppy.
- It's like calling anyone who opposes the current policies of the Israeli government (as I do) anti-Semitic. That conflates Judaism, the nation of Israel, and the current policies of the Israeli government into a single thing. I'm proudly Jewish and I support the existence of Israel. To call me anti-Semitic is absurd. To justify it by explaining to me that "colloquially, 'anti-Semitism' is used to mean anyone who opposes today's Israeli treatment of Palestinians" doesn't lessen the absurdity.
- My "zoom" example isn't a strawman, it's an analogy that's exactly on point. The rules of rational discourse apply to those of us who are in various non-privileged categories (two of which pertain to me) as much as it does to cisgender male white Christian people. Largoplazo (talk) 11:03, 15 July 2023 (UTC)
- I'm sorry, but - no. "They" is a perfectly acceptable neutral pronoun to use in a catch-all capacity. Wiki editors (and people in general) are not expected to remember and recite any esoteric, obscure, and even conjured neopronoun. "They" is, by its very nature, a neutral way to refer to anyone. — Czello (music) 23:24, 8 July 2023 (UTC)
- Using singular-they for people who use recently made-up "pronouns" isn't "misgendering", it's become normal everyday English practice for both indeterminate cases and as a socially acceptable way to avoid neopronouns. It is also the only way our material is going to be parseable by everyone. We cannot expect readers to understand completely random strings like "xe", "hirm", "fae", "tree" (yes, that's a real case), or whatever as pronouns. And writing like we're on our personal Facebook page will just bring the project into disrepute. — SMcCandlish ☏ ¢ 😼 22:07, 23 July 2023 (UTC); edited to include the obvious "recently", to put a stop to pointless "all words are made up" responses. 02:59, 25 July 2023 (UTC)
- I'd love to see a source stating that it's normal and socially acceptable to intentionally misgender people.
- I don't think it's crazy to expect our readers to comprehend the use of neopronouns if we state at the beginning of the article that the person uses neopronouns. we're not even asking them to be able to use the neopronouns themselves, they only need to recognize that any of the given 3-4 words refer to the subject. if our readers can't comprehend simple word association we have bigger issues.
- also not seeing any connection between neopronouns and the linked policy.
- I hardly think that following in the footsteps of harvard university (in 2015 for that matter), the new york times, and many other well-respected organizations and institutions would bring wikipedia to disrepute. Tekrmn (talk) 05:49, 24 July 2023 (UTC)
- I don't respond to ridiculous straw man fallacies. Try formulating an actually logical response instead of trying to insult my and everyone else's intelligence. — SMcCandlish ☏ ¢ 😼 10:29, 24 July 2023 (UTC)
- I directly responded to the points in your comment so I'm unclear on how that's a straw man fallacy. it was not my intention to attack your or anyone else's intelligence, but to point out that your argument that neopronouns are too confusing doesn't bear much weight. I apologize for the way it landed. Tekrmn (talk) 15:54, 24 July 2023 (UTC)
- Characterizing other editors and external writers as "stating that it's normal and socially acceptable to intentionally misgender people", when what they actually said is that using singular-they is acceptable as a default and as an alternative to neo-pronouns, is a raging straw man, and also a mix of circular reasoning, begging the question, argument from repetition and ipse dixit. The idea that using singular-they broadly is "misgendering" is your own proposition, which you have failed to prove to much of anyone's satisfaction, and just saying it over and over again isn't going to convince anyone. — SMcCandlish ☏ ¢ 😼 23:32, 24 July 2023 (UTC)
- feel free to refer to my answer to this same point that you posed on my talk page. Tekrmn (talk) 00:10, 25 July 2023 (UTC)
- Done, on the behavioral matters. More source research, on the substance of what you wrote above:
- Extended contentNYT doesn't routinely (or even at all so far as I've seen, and I've been looking for some time) actually use neopronouns; they just happened to have published an opinion piece about them (and publishing articles about stuff, whether the publisher agrees with it or not, is kind of what newspapers exist for). Fox News (of course) attacked them for it. NYT strategy has been to avoid using pronouns at all in cases of subjects who use neopronouns (and the publication was predictably attacked for it by activists ). Time actually did use neopronouns in one piece (can't find any evidence of later ones) and caught criticism for it, which was reported on by Daily Mail (which says "a co-founder of Wikipedia" was among the critics, which I would guess refers to Larry Sanger since it sounds out-of-character for Jimbo). Irish Times published something similar ; I've not run into any major reaction material about it (which kind of surprises me due to Ireland's majority Catholicism). NBC News published some more straightforward reporting on neopronouns and they (and notably used techniques like repeating the surname, and using they, rather than actually using the neopronouns in the publication's own voice). Other mainstream newspapers have published what amount to counter-essays (e.g. , (pushback from a civil liberties expert), and this one which indicates push-back within the LGBTQIA+ community itself (though this one is a regional not national paper). A more neutral piece from a regional NBC News affilliate covers the long history of neopronouns, which go back further than people think; the take-away from this is that attempts to institute them since the 19th century have failed. It notably also shows that even close family members of TG/NB people have lasting trouble with pronoun changes. BuzzFeed News does not use neopronouns , and quotes AP Stylebook as the "authority" for why: "[Do] not use neopronouns such as xe or zim; they are rarely used and are unrecognizable as words to general audiences." That is certainly the main WP concern. (I don't own the current edition , so I don't know if AP has changed on this in the interim.) Speaking of AP, their newswire article here addresses neopronouns without recommending them and says "They are not widely used and are unfamiliar to many people, but they do offer the benefit of grammatical clarity" versus singular-they (but WP editors already have years of practice at using they without producing confusing constructions, so we don't care about that last point, which from a linguistic perspective is extremely dubious to begin with, since there is no basis for interpreting the function or nature of a word that is not recognized as a word!). It also notes that GLAAD and NLGJA both recommend to "use the pronouns that people request" (i.e. probably including neopronouns); this is telling: both are activistic organizations, and AP is defying them, despite otherwise being often over-eager to adopt "progressive" language-reform ideas. This was published after the current edition of AP Stylebook so it probably has not changed on this matter (next edition comes out in 2025 or maybe late 2024). All that said, dredging up competing examples of "what some newspaper or news style guide is doing" is rarely actually useful to do in MoS discussions, because MoS is not based on news style, as a matter of policy (WP:NOT#NEWS, "Wikipedia is not written in news style"). However, exploring this at least demonstrates a few things: mainstream journalism is not broadly jumping on the neopronoun bandwagon, beyond just observing it as a phenomenon, and brief forays into that territory tend to result in controversy (which most news publishers that are not far-right or far-left try strenuously to avoid).On Harvard University: What I'm finding is a short backgrounder on pronouns including neopronouns, which they tellingly refer to as "personal gender pronouns" (i.e., it is a matter of idiolect as I've said elsewhere); but the page's purpose is simply "a reference that provides basic working definitions to facilitate shared discussions"; it is not a policy that Harvard is officially going to write with neopronouns or make students use them. The links on that page that go to other Harvard resources don't help your case; they don't advise neopronouns. The one here says "Commonly used pronouns include: she/her/hers, he/him/his, they/them/theirs" without any mention of neopronouns. Other links there just go to external organizations, most of them activistic about the question. Harvard's workplace inclusivity policy has a section on pronouns, but it does not address neopronouns. Their "Gender Identity and Pronouns" page makes no mention of neopronouns. Their Office for Gender Equity surprisingly has no hits for the word "pronouns" other than staff bios' declarations of particular indiviudals' preferred pronouns . Their "Equity, Diversity, Access, Inclusion, and Belonging" pamphlet mentions a couple of neopronouns, but says nothing that can be interpreted as a policy to use them by the university or to enforce their use by students or faculty. Their Employee Resource Groups subsite, which includes the Harvard LGBTQ+ Faculty and Staff (Queer Employee Resource Group), has no hits for "pronouns" or "pronoun" at all . Their "Creating Gender Inclusive Learning Environments for Transgender and Nonbinary Student" presentation mentions they several times, and mentions the existence of neopronouns without advising anytihng about them (and includes phrasing I think some people here would object to: "non-binary genders (e.g. so-called xenogenders, which do occur albeit infrequently, or neopronouns)". A page on "Creating an inclusive environment for transgender and gender-nonbinary teens" never mentions pronouns . After pretty exhaustive searching, I can find no evidence at all to suggest that Harvard is some bastion of neopronous usage. And as with news style, WP isn't based on some particular academic institution's style anyway, and MoS was not written from any of their style guides (notwithstanding that Chicago Manual of Style is published by the U. of Chicago; it's a style guide for public use, not an internal university style guide).
- Anyway, that all took a couple of hours, and I'm going back to working on article content. :-) PS: "if we state at the beginning of the article that the person uses neopronouns" presumes people read our articles from top to bottom like they're reading a book, and we know for a fact from research that this is not true, especially on mobile devices, which now account for over 50% of our usage. We just had an RfC that overhauled our MOS:DUPLINK because of these facts. — SMcCandlish ☏ ¢ 😼 09:35, 25 July 2023 (UTC)
- Done, on the behavioral matters. More source research, on the substance of what you wrote above:
- feel free to refer to my answer to this same point that you posed on my talk page. Tekrmn (talk) 00:10, 25 July 2023 (UTC)
- Characterizing other editors and external writers as "stating that it's normal and socially acceptable to intentionally misgender people", when what they actually said is that using singular-they is acceptable as a default and as an alternative to neo-pronouns, is a raging straw man, and also a mix of circular reasoning, begging the question, argument from repetition and ipse dixit. The idea that using singular-they broadly is "misgendering" is your own proposition, which you have failed to prove to much of anyone's satisfaction, and just saying it over and over again isn't going to convince anyone. — SMcCandlish ☏ ¢ 😼 23:32, 24 July 2023 (UTC)
- I directly responded to the points in your comment so I'm unclear on how that's a straw man fallacy. it was not my intention to attack your or anyone else's intelligence, but to point out that your argument that neopronouns are too confusing doesn't bear much weight. I apologize for the way it landed. Tekrmn (talk) 15:54, 24 July 2023 (UTC)
- No one has yet to bring forth evidence that each and every neopronoun maps one-to-one with a unique gender, which is the assumption upon which the charge of misgendering rests. Folly Mox (talk) 07:07, 24 July 2023 (UTC)
- "misgendering" is used to denote using the wrong pronouns for someone because mispronouning sounds unpleasant. gender is super individualized, even among cis people. not everyone who uses he/him pronouns is a man and not every man experiences their gender differently. the only thing people who use he/him pronouns necessarily have in common is that they use he/him pronouns. the same is true for any pronouns- an individual feels they fit so they use those pronouns- there's not a one to one relationship between a person's gender and the pronouns they use. it is true that many people experience their gender in ways that are pretty out of the box, which may lead them to use neopronouns. Tekrmn (talk) 16:01, 24 July 2023 (UTC)
- Saying "they" isn't intentionally misgendering anyone; it's the opposite of that. — Czello (music) 07:45, 24 July 2023 (UTC)
- To be fair, there are some traditionalists who refuse to use singular they and feel misgendered when they are called "they" rather than "he" or "she". I would still use singular they for such people in cases where I am referring to them generically or when I am trying to conceal their identity, but I think that in cases where one is referring to a specific and known person, known to have such beliefs, it would be appropriate to use "he" or "she" rather than "they".
- As for neopronouns: how about, I don't make assumptions about what gender you are and you don't insist that I use a different and unfamiliar dialect of English, with a different vocabulary, than the one I normally speak? Language is a very personal thing, maybe as personal as gender. Imposing it on other people is rude. —David Eppstein (talk) 07:55, 24 July 2023 (UTC)
- Yes, it's called idiolect, and WP is not and cannot be written in it on an article-by-article basis. People with unusual pronoun expectations cannot reasonably expect them to be followed by newspaper writers, TV news anchors, or encyclopedists, because we have an actual huge and diverse audience to deal with. Neo-pronouns are for one's self and one's close circle, who have been informed of them and what they signify. Signification is really at the core of this recurrent and kind of tiresome debate: neo-pronouns signify nothing automatically to anyone, as they are not a part of the learned semi-standardized language; they are idiolect devices that signify something only to a small "inside" crowd. They are thus akin to pet names, nicknames, and other terms of endearment. Things might be different if English adopted a set of near-univerally understood additional pronouns, but this clearly is not going to happen, and even if it did, a large number of TG/NB persons would nevertheless delight in insisting on their own alternative versions anyway. The very fact that some neopronouns were proposed in a rather organized fashion from the late 1960s yet have a) seen nearly no real-world adoption except at a very individual level, and b) led instead to an ever-grown profusion of idiolect neo-pronouns from the 2000s onward, is clear proof of this. (In my own social circle I'm exposed to dozens of neo-pronouns, and notably zero of the people they pertain to are ever offended by a singular-they because all of them are rationale people and quite well aware that there are too many neo-pronouns for anyone to be expected to remember and use them except among their closest circle.) — SMcCandlish ☏ ¢ 😼 10:39, 24 July 2023 (UTC)
- I think there is already potential confusion for many readers in articles, e.g. where "trans woman" means someone who was born/assigned as a man and may not be a term the reader understands, where "they" maybe be used as both singular and plural when there is an ambiguous referent (this is a major problem on Wikipedia), where "he" or "she" may refer to someone whom the reader does not understand in that sense, etc.
- Mightn't neo-pronouns actually be less confusing than ambiguous uses of "they"? —DIYeditor (talk) 17:23, 24 July 2023 (UTC)
- No. We resolve this problem where it exists by clarifying the prose. XAM2175 (T) 17:38, 24 July 2023 (UTC)
- So there is no case where it could be useful to have neopronouns in an article? We need to have a blanket policy against it? —DIYeditor (talk) 17:51, 24 July 2023 (UTC)
- The only example I can think of is where we make a one-off mention of their neopronouns. I cannot imagine it would make for a good article for us to use them throughout. — Czello (music) 18:09, 24 July 2023 (UTC)
- Yes. We're already doing the one-off mentioning, and it is sufficient. — SMcCandlish ☏ ¢ 😼 21:32, 24 July 2023 (UTC)
- The only example I can think of is where we make a one-off mention of their neopronouns. I cannot imagine it would make for a good article for us to use them throughout. — Czello (music) 18:09, 24 July 2023 (UTC)
- So there is no case where it could be useful to have neopronouns in an article? We need to have a blanket policy against it? —DIYeditor (talk) 17:51, 24 July 2023 (UTC)
- No. We resolve this problem where it exists by clarifying the prose. XAM2175 (T) 17:38, 24 July 2023 (UTC)
- I generally agree with this position, but such a broad generalisation as
a large number of TG/NB persons would nevertheless delight in insisting on their own alternative versions anyway
strikes me as unnecessarily pointed and derisive. XAM2175 (T) 17:37, 24 July 2023 (UTC) - @SMcCandlish please strike your derisive comment about your fellow editors (myself included). EvergreenFir (talk) 17:44, 24 July 2023 (UTC)
- I had to read it twice, and do not see anything I'd consider "derisive". Care to elaborate? Otherwise, please strike the false claim. —Locke Cole • t • c 17:47, 24 July 2023 (UTC)
- @Locke Cole - as highlighted by XAM2175, the comment "
a large number of TG/NB persons would nevertheless delight in insisting on their own alternative versions anyway
" is derisive. We don't need drawn out versions of calling people snowflakes. EvergreenFir (talk) 17:51, 24 July 2023 (UTC)- I think it's a stretch, especially considering there are new/recent users here that appear to be following the letter if not the spirit of WP:RGW and WP:NOTHERE with endless arguments about GENDERID "issues" (I put it in quotes because IMO there is no issue; follow the reliable sources and apply DUE as necessary; most of MOS:GENDERID is wholly unnecessary instruction creep as it is, adding to it is simply going to create even more potential for conflict). Maybe SMcCandlish's comment belongs in an AN/I or ARBCOM discussion, but ignoring behavior and the WP:BATTLEGROUND mentality on display is disruptive to the project. We're not here to change the world beyond providing a free and open source for knowledge. —Locke Cole • t • c 20:22, 24 July 2023 (UTC)
- I agree that this is an area with many WP:RGW folks. And I myself get annoyed with the pronoun police. But dealing with those editors is part of the "job" as admin and long term editors. That still doesn't give SMcCandlish the right to call me, fellow editors, and the many good-faith editors on this topic snowflakes who would delight in forcing people to use "made up pronouns". EvergreenFir (talk) 21:21, 24 July 2023 (UTC)
- There's nothing "derisive" in noting that people enjoy and take pride in their self-identification and activism activities. Pride Month is called that, and is a big fun affair for almost everyone concerned, for a reason. I'll remind you that I'm under the LGBTQIA+ banner myself (I just spent the last two weekend staffing booths at related events!). I don't need censorious "you're not being left the way I insist the left should be" lecturing from other people under the same tent. The far right is on the rise for a reason, and that reason is that the left keeps attacking itself over insipid, doctrinaire, language-policing squabbles, and this topic area is a nasty mire in large part because of that holier-than-thou behavior. PS: Trying hard to find offense in what other editors write is a form of assuming bad faith. — SMcCandlish ☏ ¢ 😼 21:32, 24 July 2023 (UTC)
- @EvergreenFir: And I never called anyone a "snowflake" (which is just your dog-whistle way of trying to imply that I'm a rightwinger – your attempt to cast me as some kind of socio-political ideological "enemy" to go after is unbecoming an administrator). I also never said anyting about "forcing people" to do anything. You're making up bald-faced bullshit out of nowhere. It's ad hominem and guilt by association character-assassination nonsense, and you know it. — SMcCandlish ☏ ¢ 😼 21:32, 24 July 2023 (UTC)
- Your tone and message in that original comment do not match how 2 other editors have interpreted it. I don't think I am the one trying hard for anything. Regardless, I'm clearly more on your side with the "insipid, doctrinaire, language-policing squabbles" concerns (see my comment below). EvergreenFir (talk) 22:28, 24 July 2023 (UTC)
- I agree that my actual tone and message don't agree with 2 other editors' personal interpretations. I'm not responsible for how other people bend over backwards to misinterpret things and then to cast people they disagree with on something as ideological "enemies". I will not be browbeaten into self-censoring on a matter like this. Implication and inference are not synonyms. — SMcCandlish ☏ ¢ 😼 23:38, 24 July 2023 (UTC)
- @SMcCandlish: to say that I'm unimpressed by this full-throttle descent into assumptions of bad faith would be a major understatement, and it's a ridiculously overblown response to a simple suggestion of mine that you had incorporated a single potentially offensive line into a statement of opinion that I otherwise broadly endorsed. Please consider the full sentence that you wrote:
Things might be different if English adopted a set of near-univerally understood additional pronouns, but this clearly is not going to happen, and even if it did, a large number of TG/NB persons would nevertheless delight in insisting on their own alternative versions anyway.
I suggest that this could be read as you passing judgment on trans and NB people in bulk, because their gleefully coining yet more pronouns would frustrate a resolution to the issue that you believe would otherwise be satisfactory. In such a reading, the actual meaning you've subsequently given –that people enjoy and take pride in their self-identification and activism activities
– is entirely absent; replaced by something that can be read as far more derogatory, more of a cheap drive-by shot at a group of which it could appear that you disapprove.I note with some disappointment that your response to this suggestion appears to echo that which on a previous occasion lead to no small amount of contention within the community and resulted in your publishing this lengthy explanatory essay, in which – amongst a certain number of polemical points on the same lines as your responses above – you do ultimately acknowledge that you failed to consider that your audience might not interpret your writing and understand your meaning and intent as you yourself did.I would further note that @Locke Cole also appears to have interpreted your original post as being negative in nature, as EvergreenFir and myself did. The major difference, however, is that he appears to believe that the negativity is not only defensible but perhaps even appropriate, and at the very least good enough to act as a COATRACK for his feelings on GENDERID as a whole. That he seems to view such a derisory generalisation as being proportionate in countering what he describes as a[disruptive] WP:BATTLEGROUND mentality
from a handful ofnew/recent users here
is somewhat concerning. XAM2175 (T) 21:12, 25 July 2023 (UTC)- I don't feel a compelling need to be impressed by what you're unimpressed by. "this could be read as you passing judgment on trans and NB people in bulk ... a group of which it could appear that you disapprove" is more leaping to the worst possible conclusion about what another editor wrote and basically engaging in character assassination to make a point; i.e., it's blatant assumption of bad faith at bare mimimum. I agree that it's "concerning" when people rampantly misinterpret material and bend it to toward their own prejudices; I'm just concerned about more than one editor doing it in more than one direction, while you're only apparently concerned with a single editor doing it in a direction that doesn't agree with your position. I'm more evenhanded in my dismissal of fallacious, word-twisting, and motive-assuming nonsense. — SMcCandlish ☏ ¢ 😼 21:47, 25 July 2023 (UTC)
- @SMcCandlish: to say that I'm unimpressed by this full-throttle descent into assumptions of bad faith would be a major understatement, and it's a ridiculously overblown response to a simple suggestion of mine that you had incorporated a single potentially offensive line into a statement of opinion that I otherwise broadly endorsed. Please consider the full sentence that you wrote:
- I agree that my actual tone and message don't agree with 2 other editors' personal interpretations. I'm not responsible for how other people bend over backwards to misinterpret things and then to cast people they disagree with on something as ideological "enemies". I will not be browbeaten into self-censoring on a matter like this. Implication and inference are not synonyms. — SMcCandlish ☏ ¢ 😼 23:38, 24 July 2023 (UTC)
- There's nothing "derisive" in noting that people enjoy and take pride in their self-identification and activism activities. Pride Month is called that, and is a big fun affair for almost everyone concerned, for a reason. I'll remind you that I'm under the LGBTQIA+ banner myself (I just spent the last two weekend staffing booths at related events!). I don't need censorious "you're not being left the way I insist the left should be" lecturing from other people under the same tent. The far right is on the rise for a reason, and that reason is that the left keeps attacking itself over insipid, doctrinaire, language-policing squabbles, and this topic area is a nasty mire in large part because of that holier-than-thou behavior. PS: Trying hard to find offense in what other editors write is a form of assuming bad faith. — SMcCandlish ☏ ¢ 😼 21:32, 24 July 2023 (UTC)
- I agree that this is an area with many WP:RGW folks. And I myself get annoyed with the pronoun police. But dealing with those editors is part of the "job" as admin and long term editors. That still doesn't give SMcCandlish the right to call me, fellow editors, and the many good-faith editors on this topic snowflakes who would delight in forcing people to use "made up pronouns". EvergreenFir (talk) 21:21, 24 July 2023 (UTC)
- I think it's a stretch, especially considering there are new/recent users here that appear to be following the letter if not the spirit of WP:RGW and WP:NOTHERE with endless arguments about GENDERID "issues" (I put it in quotes because IMO there is no issue; follow the reliable sources and apply DUE as necessary; most of MOS:GENDERID is wholly unnecessary instruction creep as it is, adding to it is simply going to create even more potential for conflict). Maybe SMcCandlish's comment belongs in an AN/I or ARBCOM discussion, but ignoring behavior and the WP:BATTLEGROUND mentality on display is disruptive to the project. We're not here to change the world beyond providing a free and open source for knowledge. —Locke Cole • t • c 20:22, 24 July 2023 (UTC)
- @Locke Cole - as highlighted by XAM2175, the comment "
- I had to read it twice, and do not see anything I'd consider "derisive". Care to elaborate? Otherwise, please strike the false claim. —Locke Cole • t • c 17:47, 24 July 2023 (UTC)
- Yes, it's called idiolect, and WP is not and cannot be written in it on an article-by-article basis. People with unusual pronoun expectations cannot reasonably expect them to be followed by newspaper writers, TV news anchors, or encyclopedists, because we have an actual huge and diverse audience to deal with. Neo-pronouns are for one's self and one's close circle, who have been informed of them and what they signify. Signification is really at the core of this recurrent and kind of tiresome debate: neo-pronouns signify nothing automatically to anyone, as they are not a part of the learned semi-standardized language; they are idiolect devices that signify something only to a small "inside" crowd. They are thus akin to pet names, nicknames, and other terms of endearment. Things might be different if English adopted a set of near-univerally understood additional pronouns, but this clearly is not going to happen, and even if it did, a large number of TG/NB persons would nevertheless delight in insisting on their own alternative versions anyway. The very fact that some neopronouns were proposed in a rather organized fashion from the late 1960s yet have a) seen nearly no real-world adoption except at a very individual level, and b) led instead to an ever-grown profusion of idiolect neo-pronouns from the 2000s onward, is clear proof of this. (In my own social circle I'm exposed to dozens of neo-pronouns, and notably zero of the people they pertain to are ever offended by a singular-they because all of them are rationale people and quite well aware that there are too many neo-pronouns for anyone to be expected to remember and use them except among their closest circle.) — SMcCandlish ☏ ¢ 😼 10:39, 24 July 2023 (UTC)
- I don't respond to ridiculous straw man fallacies. Try formulating an actually logical response instead of trying to insult my and everyone else's intelligence. — SMcCandlish ☏ ¢ 😼 10:29, 24 July 2023 (UTC)
- All words in English are made up words SMcCandlish, and those that eventually enter the dictionary do so because of their use by others, and not because some body has decreed them to be so. That's not really a strong argument against using neopronouns over singular they. I also don't see the relevance of WP:NOTFACEBOOK here, as we're not discussing an article or user page that's being used as a personal web page or blog.
- A stronger argument for or against using neopronouns would be by referring to relevant styleguides. It's important to remember that Wikipedia follows the sources, and doesn't lead the sources. The current edition of the AP Stylebook (sorry, no direct link to this but it is available on Kindle Unlimted) recommends against using neopronouns, and instead recommends using they/them/their. The New York Times Manual of Style and Usage hasn't been updated since 2015, and doesn't appear to include any relevant guidance on pronouns. I'm not able to access the current edition of the Reuters' Handbook. The NLGJA Association of LGBTQ Journalists stylebook states that neopronoun use is acceptable but may require additional explanations due to a lack of familiarity. GLAAD's Media Reference Guide recommends using the pronouns that the person uses, including neopronouns. The Trans Journalists Association style guide recommends using a
quick, appositive phrase mentioning their pronouns
for neopronouns at their first instance and seems to imply that it's OK to use them. The Canadian Government's language portal recommends use of neopronouns, following the guidance of the individual who uses them, even when unfamiliar. - So it seems the styleguides are split. Some recommend using neopronouns, some don't, and some don't mention them either way. Those that are more LGBT focused tend to have stronger recommendations for neopronoun usage. Back in October 2022 we had a well attended RfC on the use of neopronouns in articles, and my feelings on the use of neopronouns hasn't shifted since then. I am still uncomfortable with using they/them pronouns for folks who use only neopronouns, and I am very sympathetic to the arguments put forward for why we should be doing more than mentioning them and actually using them in our articles. However, while there are instances of reliable sources, like Time, using neopronouns in their articles, and even with my preference for using them in mind, I'm not sure if enough general purpose styleguides recommend their usage yet. This is likely to change over time though, if and when their usage becomes more common. The AP Stylebook is due for renewal some time next year, and I would be interested to see if it has a shift in guidance. Sideswipe9th (talk) 17:48, 24 July 2023 (UTC)
- These are mostly style guides with no or virtually no influence on MoS anyway, and concluding that "styleguides are split" by including explicitly language-change-activistic ones is rather misleading (it's a lot like arguing that MOS:DOCTCAPS is wrong because it conflicts with Christian (or insert other religion here) style guides). GLAAD is rather overwhelmingly an advocacy organization (hell, at my old activism job, we hired GLAAD's former exec. dir. to take over an online activism role I was moving out of :-). It would be much more relevant to see whether Chicago Manual of Style and other academic style guides in their next editions suddenly start supporting neo-pronouns. Regardless, I think you're misinterpreting the TJA material as more activistic on this matter than it actually is; it is really advising what MoS is also already advising (without any recourse to TJA): to briefly mention their neopronouns. We've been doing that since the early 2010s at least (e.g. at Genesis P-Orridge). — SMcCandlish ☏ ¢ 😼 21:23, 24 July 2023 (UTC)
- I'm a little concerned that you seem to be judging styleguides that allow for or recommend the use of neopronouns as "activistic". That doesn't really seem helpful here.
- As for the academic styleguides, you're right, it slipped my mind to include them. For the big three: The Chicago Manual of Style is one I don't currently have access to, but they seem to slow at adopting singular they and generally recommend rewriting sentences to avoid pronoun use entirely so I doubt they have any guidance. If you or any other editor has access though, quoting from paragraphs 5.48 and 5.255 may be helpful here. The 9th edition of the MLA Handbook, for English language writing, states writers
writers should follow the personal pronoun of individuals they write about, if individuals' pronouns are known
, which seems inclusive though it doesn't explicitly mention neopronouns anywhere. I don't have access to the current edition of the APA Publication Manual, however a supplementary entry on their website endorses use of singular they becauseit is inclusive of all people and helps writers avoid making assumptions about gender.
- That being said, of these three styleguides I would note that some universities and university libararies, like University of Alberta, Indiana University Bloomington, and University of Sydney see all three guides as either being permissive or requiring the use of all personal pronouns, including neopronouns, where the person's pronouns are known. Sideswipe9th (talk) 00:24, 25 July 2023 (UTC)
- The CMoS material is too much to quote directly. Quite a large block of material. In summary....
- Extended content5.48 says singular they is common but informal and is "only lately showing signs of gaining acceptance in formal writing", but: "When referring specifically to a person who does not identify with a gender-specific pronoun, however, they and its forms are often preferred." Also "In general, a person's stated preference for a specific pronoun should be respected." The section mentions the existence of "gender-neutral" (specifically) neopronouns, without naming any of them, but does not advise for or against them. (That is rather odd, honestly, until one finds a condemnation in a later section, but then it gets weirder, with what reads like an "un-condemnation" a section later). Section 5.255 ("Techniques for achieving gender neutrality") is even longer that 5.48. In summary it advises (as mutual alternatives): omit the pronoun; repeat the noun; use a plural antecedent to eliminate the need for a singular pronoun; use an article instead of a pronoun; use one; use relative pronoun who[m]; use imperative mood ("A lifeguard must keep a close watch ..." – not applicable to WP per WP:NOT#ADVICE); use the phrase he or she "in moderation"; revise the sentence to avoid personal pronouns entirely. Oddly, it never mentions repeating the name (usually surname), a technique we use frequently. Section 5.256 is also fairly long; advises avoiding it, of course ("with very limited exceptions", acknowledging sotto voce that a very small number of TG/NB people prefer the term); says to avoid clumsy constructions like (s)he and (wo)man; says to avoid neopronouns: "Clumsy artifices like ... genderless pronouns have been tried—for many years—with no success. They won't succeed. And those who use them invite credibility problems." Also says anybody and someone often don't work; reiterates that they/their have become common in informal usage but are not fully accepted yet [2016] in formal writing, especially for cases where the gender is unknown (rewrite instead), but here actually advises its use for subjects who explicitly identify with they/them. This passage can also be read as directly contradicting 5.255 in advising again that "such preference should generally be respected", right after mentioning both declared singular-they yet also "or some other gender-neutral singular pronoun". It'll be interesting to see if they resolve this direct conflict of advice in the next edition (but I would not hold your breath; there are outright factual errors in CMoS that have persisted since at least the 12th edition!).If MLA doesn't address neopronouns, then it doesn't. There can hardly be any issue in English usage that is more fraught with debate than this question; to a large proportion of English-speakers, neopronouns don't actually constitute pronouns or English at all. So, if MLA was meant to include neopronouns, it rather obviously would have been explicit about it.The UAlberta thing is not a university style guide, it's a "Community" section blog post by one of their librarians, and is clearly activistic in intent, as is clear from its introduction. And it mischaracterizes the Chicago position, so I don't trust it on the MLA or APA material either without reading them in detail myself. It says "it is always appropriate to use any pronouns for an individual when it is known" [sic] and "This can include common pronouns, as well as newer pronouns (also known as neopronouns)." But we already know Chicago is self-contradictory on the matter and that MLA doesn't address neo-pronouns at all. Of ALA, this piece says that guide says to use they "when referring to someone whose gender is unknown", which is not an endorsement of neoprouns. So, this is clearly not a reliable source on usage, for several reasons; if this person were writing such material at Wikipedia, we would revert their changes as original research that badly distorts the source material.The UIndiana piece is another student-librarian opinion piece, not a university style guide. While it does not appear to directly mischaracterize the advice in major style guides, it leaps to examples of using neopronouns as if they had been recommended by the cited sources, which they were not (and just gives two of them, implying they in particular have wide acceptance, which is not true). It correctly [as far as I know – I don't own the current APA] summarized that Chicago, MLA, and APA admit of sigular-they when gender is unknown, and even gets right that MLA and Chicago both consider it "informal". Anyway, like the other library post, this one is clearly not even intended as a style guide but is a summary (reasonaly accurate in this case but not the other) of other style guides we already consult, so not evidentiary of anything.The USYD material is an actual style guide, not for an entire institution but for "library-created content". It's an in-house booklet. It is also activistic, in aligning with the notion that not using neopronouns is "misgendering", an idea that the community at Wikipedia has clearly not accepted, and which isn't reflected in widespread and growing use of singular-they as a neopronoun replacement across English-language writing. It relies heavily on a UNC-Greensboro piece of uncertain authority at that institution, which is advocacy material of specific (Spivak, etc). neopronouns among the student body. I don't think it's informative for this debate, as it doesn't reflect anything like a broad cultural consensus but is trying to engineer changed local behavior.
- — SMcCandlish ☏ ¢ 😼 01:48, 25 July 2023 (UTC)
- Wow, the CMOS stuff does sound like a right mess! I wonder if this was something that was added to piecemeal, with older parts not being updated as newer parts were added.
- One elided quote there did stand out to me though;
"Clumsy artifices like ... genderless pronouns have been tried—for many years—with no success. They won't succeed. And those who use them invite credibility problems."
I find it kinda shocking that such a strong genuinely activistic statement bordering on ridicule is in this styleguide. It's one thing to say something like "genderless pronouns are unfamiliar to most and should not be used in academic writing", but to say that any attempt at using them won't succeed is very gatekeepery, and to say that anywho use them invite credibility problems
is the sort of statement that would bring a style guide into disrepute. - It's a very different sort of statement entirely than saying "when writing about a person, use the pronouns the person uses". Sideswipe9th (talk) 22:05, 25 July 2023 (UTC)
- These are mostly style guides with no or virtually no influence on MoS anyway, and concluding that "styleguides are split" by including explicitly language-change-activistic ones is rather misleading (it's a lot like arguing that MOS:DOCTCAPS is wrong because it conflicts with Christian (or insert other religion here) style guides). GLAAD is rather overwhelmingly an advocacy organization (hell, at my old activism job, we hired GLAAD's former exec. dir. to take over an online activism role I was moving out of :-). It would be much more relevant to see whether Chicago Manual of Style and other academic style guides in their next editions suddenly start supporting neo-pronouns. Regardless, I think you're misinterpreting the TJA material as more activistic on this matter than it actually is; it is really advising what MoS is also already advising (without any recourse to TJA): to briefly mention their neopronouns. We've been doing that since the early 2010s at least (e.g. at Genesis P-Orridge). — SMcCandlish ☏ ¢ 😼 21:23, 24 July 2023 (UTC)
- Comment - For the very few biographies where person has neopronouns such as xe/xim, we can handle these on a case-by-case basis. Using they/them is appropriate given that neopronouns are, by definition, novel and not widely adapted. As an encyclopedia, we must make our content as accessible as possible. To avoid using they/them, use the person's surname or moniker. Inclusion of the neopronouns belongs in a prose section. EvergreenFir (talk) 17:49, 24 July 2023 (UTC)
- Maybe a header template that indicates neopronouns are used in the article and what they mean? I don't see a great deal of harm in this, as long as the neopronouns aren't words that would make writing prose ambiguous or just plain impossible ("the" or such I guess). —DIYeditor (talk) 17:56, 24 July 2023 (UTC)
- I don't see why would use esoteric and non-standard English when "they" works just fine. — Czello (music) 18:10, 24 July 2023 (UTC)
- I find "they" confusing in many cases but I may just be old (even though I have occasionally used "they" this way my whole life I guess). It's too bad we couldn't have made a neopronoun to cover all cases of singular pronouns with indefinite gender. —DIYeditor (talk) 18:15, 24 July 2023 (UTC)
- Our readers generally do not read hatnotes and other header templates, and they're going to be missing from most WP:REUSE of our content, along with other WP-specific templates. — SMcCandlish ☏ ¢ 😼 21:23, 24 July 2023 (UTC)
- Agreed. A hatnote would likely not solve anything. EvergreenFir (talk) 22:30, 24 July 2023 (UTC)
- I don't see why would use esoteric and non-standard English when "they" works just fine. — Czello (music) 18:10, 24 July 2023 (UTC)
- Maybe a header template that indicates neopronouns are used in the article and what they mean? I don't see a great deal of harm in this, as long as the neopronouns aren't words that would make writing prose ambiguous or just plain impossible ("the" or such I guess). —DIYeditor (talk) 17:56, 24 July 2023 (UTC)
- Neopronouns are not standard English, and we're writing for a global audience, where half our readers speak English as a second language. The singular "they" is fine. Using something like "xer" is going to be many times more confusing than using the singular they. GMGtalk 18:22, 24 July 2023 (UTC)
- Sorry if this has been asked somewhere above and I missed it, but do we have any instance where a Wikipedia article discusses someone who takes neopronouns and has said that they are uncomfortable with they/them? In such cases, it seems reasonable to just avoid pronouns entirely, as is occasionally done with historical figures of disputed gender identity. This is consistent with the current wording of MOS:NEOPRONOUN: This was discussed at the RfC, and AFAIK is the reason we have a "generally" in there. (That section was written mostly by me and RfC closer Red-tailed hawk; I forget which of us added that particular word, but I think we were in agreement there was no 100% requirement of using they/them rather than avoiding pronouns.) -- Tamzin[cetacean needed] (she|they|xe) 00:47, 25 July 2023 (UTC)
- I remember that there was at least one such case, but I can't for the life of me remember what it was. Sorry that's not very helpful. I even remember having (at least twice) done an editing pass on some article to do things like repeat the surname or other noun, and rewrite sentences otherwise to avoid need for a pronoun, but it was several years ago. — SMcCandlish ☏ ¢ 😼 01:52, 25 July 2023 (UTC)
- Well what it sounds like is that so far in this thread, no one is arguing that we must use they/them even when someone objects to it. Surname-only is an option, and the global consensus doesn't even entirely rule out using neopronouns in some special edge case. (I could see an argument for exceptions for synopses of fictional works like Provenance where such pronouns are standard in-universe, although I guess that's arguably not covered by MOS:BIO.) So I concur with others in this thread that using they/them in lieu of neopronouns does not inherently constitute misgendering—while acknowledging that in certain cases it might, and can be dealt with case-by-case while still complying with the current guidance. -- Tamzin[cetacean needed] (she|they|xe) 02:58, 25 July 2023 (UTC)
- Agreed (other than with "acknowledging that in certain cases it might"; it would probably be more accurate to say that in certain cases, when reliable sources demonstrate that particular subject has actually expressed opposition to they, to just avoid using it as unnecessary; that doesn't make those who don't agree with this position "misgenderers", an accusation that too many in this thread have been bandying about as if this wasn't a double-WP:CTOP thread). Anyway, see big block of paraphrasing from CMoS above; there are a whole bunch of strategies for writing around the need for pronouns. — SMcCandlish ☏ ¢ 😼 03:22, 25 July 2023 (UTC)
- Personally I've never liked surname-only as it generally just leads to bad/clunky writing. I'd probably default to they/them in those instances. — Czello (music) 09:38, 25 July 2023 (UTC)
- Well what it sounds like is that so far in this thread, no one is arguing that we must use they/them even when someone objects to it. Surname-only is an option, and the global consensus doesn't even entirely rule out using neopronouns in some special edge case. (I could see an argument for exceptions for synopses of fictional works like Provenance where such pronouns are standard in-universe, although I guess that's arguably not covered by MOS:BIO.) So I concur with others in this thread that using they/them in lieu of neopronouns does not inherently constitute misgendering—while acknowledging that in certain cases it might, and can be dealt with case-by-case while still complying with the current guidance. -- Tamzin[cetacean needed] (she|they|xe) 02:58, 25 July 2023 (UTC)
- I remember that there was at least one such case, but I can't for the life of me remember what it was. Sorry that's not very helpful. I even remember having (at least twice) done an editing pass on some article to do things like repeat the surname or other noun, and rewrite sentences otherwise to avoid need for a pronoun, but it was several years ago. — SMcCandlish ☏ ¢ 😼 01:52, 25 July 2023 (UTC)
- As weird as it's gonna be, I'll say this: it is simpler to use they/them. Not everyone who browses enwiki is gonna be 100% fluent in English, and seeing neopronouns might confuse people who don't have English as their first language. I do agree that it should be mentioned somewhere in the article, though. LilianaUwU (talk / contributions) 03:06, 25 July 2023 (UTC)
WP:TNT on GENDERID
Are you fatigued of talking about MOS:GENDERID? Here is a proposal to rewrite the section, which has languished into a poorly worded, somewhat illogical, and confusing mess. It needs to be clearly aligned with policies, reorganized for clarity, and address the various concerns about a social issue that is central to culture war in the west without pissing off everyone. This reorganization will honestly reduce the churning of numerous RFCs and endless debate. I know this because the ONLY reason I'm here is I glanced at it one day and was surprised at how far it deviated from standard policy, so decided to stick around and work on it. If it is reasonably worded and addresses the concerns of most trans-activists, I think it will stop attracting people to change it.
I appreciate BilledMammal's and Loki's attempts above, but I took the wording from BLP of multiple reliable third-party sources
because multiple high quality reliable and secondary sources containing non-trivial coverage of the person
uses "high quality", and it's not well defined on Wikipedia.
On the question of academics and changing names of older publications, I would guess that such a thorough attempt to expunge the former name would make it drop below the threshold of inclusion. And, well, WP:KISS.
Proposed MOS:GID section |
|---|
|
Refer to any person whose gender might be questioned with the name and gendered words (e.g. pronouns, waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources. Any information related to the prior gender of a person, including former names (deadname), should automatically be considered a matter of personal privacy and removed, with the exception of:
Unless the individual meets one of the exceptions, information that could reveal a gender transition should not be used in lists, redirects, disambiguation pages, category names, etc., even in quotations, even if a reliable source exists. When the individual meets one of the exceptions, information on their gender transition must not be given undue weight or overemphasis, and editors should always err on the side of excluding it. Former names are not automatically of encyclopedic value. The former name of a transgender or non-binary person may be placed in the infobox or background section of the article instead of the first sentence, to avoid giving it undue prominence. Articles or other works that were published under a pre-transition name should use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnote. In general, respectful extra mentions of the former name or transition should only be used to avoid confusion. When the individual does not meet one of the exceptions, there may be some difficulty in hiding the information on gender transition. Avoid confusing constructions (Jane Doe fathered a child) by rewriting (e.g., Jane Doe became a parent). If the former name appears in a quotation, the article may need to paraphrase, elide, or use square brackets to replace portions of quotations to avoid deadnaming or misgendering. Do not replace or supplement a person's former name with a current name if the two names have not been publicly connected and connecting them would out the person.
In rare cases where exact wording cannot be avoided (e.g. pun, rhyme, album cover), the quotation or work should not be used. |
Cuñado ☼ - Talk 18:32, 21 July 2023 (UTC)
Works for me. Folly Mox (talk) 18:52, 21 July 2023 (UTC)- Agree with this, though
The former name of a transgender or non-binary person may be placed in the infobox or background section of the article instead of the first sentence, to avoid giving it undue prominence.
should be clarified: if a name is mentioned in an infobox and/or in an article lead, it should also be mentioned in the body of the article. Additionally, pre-transition names are often included in the leads, to help with readers who may have only heard of a person pre-transition, to avoid confusion (e.g. at Chelsea Manning). This is a relatively minor concern, though, so I would still support this over the status quo. Elli (talk | contribs) 19:13, 21 July 2023 (UTC) - While I don't think this draft is too bad on a quick read, I don't see any need to rewrite the section. The existing wording, as you note, has been subject to tons of RFCs and discussions before and as a consequence is one of the most heavily workshopped sections in the MOS. The idea that it has some major issue despite all that seems patently silly to me.
- I also think this draft misunderstands the purpose of concealing a deadname. The point is not to conceal that someone has transitioned at all, the point is to conceal a piece of information that could be wielded by malicious actors. Wikipedia rarely publishes people's current addresses, and like here the privacy concern is not to conceal that they have moved but to prevent someone malicious from taking advantage of that private information. Loki (talk) 19:23, 21 July 2023 (UTC)
|
- I was just about to start brainstorming a GENDERID rewrite, and I see Cuñado's way ahead of me. Cool! So, first some general thoughts: The more I've worked in the trans/nonbinary biography space, the more displeased I've come with the current state of GENDERID. It was written, it feels, based on a very stereotyped understanding of trans-ness (viz., all trans people are binary and want their one true gender affirmed by having their pre-transition life discussed as little as possible) at a time when trans people were far less visible than they are now, and has since become a Frankenstein's monster of other considerations. Enforcement of it often becomes complicated by the fact that it's not entirely clear what it's supposed to promote: The privacy of living people? The dignity of all trans people? WP:DUE? Some combination of the three, but the current guideline blurs them in ways that have led to people citing privacy in cases where the real argument to make was a WP:DUE one, or otherwise muddling them. This proposal shifts us to a more common-sense-based approach that acknowledges the importance of subjects' dignity and not giving undue weight, while eliminating a bright-line rule for public figures' pre-transition names and leaving things up to local consensus to fill in the blanks (i.e., the way most of MoS works). So I broadly support something along the lines of Cuñado's proposal.
- Now, taking the proposal point by point:
- I support adding a public-figure exception. The lack of such an exception has led to too many debates over enforcing DEADNAME essentially for its own sake. I suggested something similar above. (I suggested outright replacing notability with public-figure status, but that's probably less likely to get consensus.) On articles like Rachel Levine, there would still be room to discuss whether including a deadname is DUE, and that could be sorted out by local consensus.
- I support broadening the consent exception from just pre-transition pronouns to all aspect of transition. Out current lack of such an exception is one of the best examples of that stereotyped understanding of trans-ness, and has gotten on my nerves e.g. at Sarah Ashton-Cirillo, where the subject readily discloses her deadname, but MoS currently says I should omit that.
- I would like to see a note to the effect of "Sometimes some information about a person's transition will be public, while other information will be private."
- In discussing DUE, I would suggest a note that, especially historically and to an extent still today, generally reliable sources have been known to include details' of people's transitions for reasons of sensationalism, when they were not actually relevant to the subject.
In general, respectful extra mentions of the former name or transition should only be used to avoid confusion.
— I think I get what you're going for, but this is hard to parse.- In the "Articles or other works" bit, there should still be an exception for those who prefer to be referred to by pre-transition names.
- When the individual does not meet one of the exceptions, there may be some difficulty in hiding the information on gender transition. — This should be removed entirely. It opens up a lot of questions about what "hiding" means and blurs the line between privacy-based and courtesy-based deadname avoidance, without clear benefit. The paragraph stands fine on its own without it.
- The last sentence of the penultimate paragraph should be made last overall; otherwise the Juno example doesn't make sense.
- -- Tamzin[cetacean needed] (she|they|xe) 21:30, 21 July 2023 (UTC)
- I appreciate and like much of this proposal. I share many of Tamzin's comments and concerns, but I want to address points 3 and 4 of the exceptions. The broader point of this whole section is that
"former names are not automatically of encyclopedic value.
- First, (many, if not all) people with pages on Wikipedia are or could be public figures. I wonder if the public figure exemption can become so large as to overwhelm the general principle. (I will note that the term public figure was added [] in 2005 and has never been specifically defined).
- Second, I don't quite understand exemption 4. On one hand, this may only apply in a small number of circumstances (the person was not notable under a former name, the person did not speak publicly about their transition, and is or was not a public figure). Still, my question is why should we retroactively (and what value does it provide to the community) to insert a former name on the page (which, in general does not have encyclopedic value)? This additional exemption does not seem to fit with the purpose of this section.
- Third, should we add guidance about people whose notablity is due to pre AND post transition? I am thinking specifically of authors or academics who might be notable because of coverage, reviews, or publications that occur before and after a transition?
- --Enos733 (talk) 23:05, 21 July 2023 (UTC)
- @Enos733: I think, taken with the subsequent paragraph about how falling under an exception still doesn't guarantee inclusion of transition-related information, exception 4 is reasonable. Your question thus sort of answers itself: If nothing would be added to an article by including the information, then it shouldn't be included, and the proposed rewrite wouldn't mandate inclusion. There would just not be a global rule as to whether to include in such cases (which is the status quo regardless for non-recently-deceased trans people's biographies).This ties into what might be my biggest problem with GENDERID as stands, which is that it's supposed to be part of a style guide. WP:BLP and WP:NPOV already provide the necessary policy bits (with respect to personal information and due weight, respectively). This guideline works best by giving an interpretation of how those policies apply and then giving general advice on what to do within the bounds of those policies. So really the four exceptions are the four exceptions because they're the four cases where BLPPRIVACY wouldn't apply—and it's only when BLPPRIVACY doesn't apply that MoS' opinion even matters. -- Tamzin[cetacean needed] (she|they|xe) 01:17, 22 July 2023 (UTC)
- I have mixed feelings on this. On the one hand, I completely sympathise with a desire to simplify and streamline the text of GENDERID. It's clear from a read of the discussions at MOS:GIDINFO that the guideline was progressively added to over time, and this is reflected in the current state of the text. I would also somewhat agree where Tamzin said
It was written, it feels, based on a very stereotyped understanding of trans-ness (viz., all trans people are binary and want their one true gender affirmed by having their pre-transition life discussed as little as possible) at a time when trans people were far less visible than they are now
. However, I have some pretty large reservations about what has been proposed here that lead me towards opposing this as currently written. Going through this a paragraph at a time:- First paragraph is fine.
- The second paragraph I find objectionable. What exactly does
Any information related to the prior gender of a person
mean? A plain reading of the sentence seems to imply that where a person was not notable prior to transitioning, but for whom being trans or non-binary is a large and relevant part of their personal identity, we would be unable to say that they are trans or non-binary in our articles about them. This seems to take the scope of the scope of the second, third, and fourth paragraphs of the current text of the guideline, and apply it to all aspects of a trans or non-binary person's gender identity, and not just their former name. I hope I'm reading this incorrectly, because otherwise this seems like it could be used for gender identity erasure of trans and non-binary individuals. - On the exemptions
- Exemption 1 is fine as this is the same as what we currently have.
- What does exemption 2 mean in practice? What would
clearly expressed their consent to share the information
even look like in a reliable source? Are there any articles you have in mind where this exemption that wouldn't currently be met by the current text of the guideline? Is there any evidence that you can point to that would suggest this is a more respectful way to handle - Exemption 3 is not a good idea and represents a rather large departure from the current text of the guideline. Because a public figure on enwiki is exceptionally broadly defined of late, this would mean that individuals who became notable after transitioning and/or changing their name would now have their former names mentioned in their respective articles almost as soon as WP:V is met. When looking at just the current examples in GENDERID, this means that we would now be allowed to include the former names of Rachel Levine and Laverne Cox. This would
- Exemption 4 is unworkable. This is at least the third time it has been proposed by Cuñado and it has been rejected every single time. It runs counter to the current consensus with regards to the former names of deceased trans and non-binary individuals. At the very least exemption 4 should mirror the text that was added two days ago as while that has issues per the discussion above, notwithstanding any changes that occur as a result of the discussion, as it is closer to the current consensus on this point.
- For paragraph 3 I have the same question for
information that could reveal a gender transition should not be used
as I do for the second paragraph. What exactly does this mean? A plain reading of this would mean that for any individual who does not meet one of the four exemptions, we cannot mention in their article that they are trans or non-binary. As before, I hope I'm reading this incorrectly, because it again seems like it could be used for gender identity erasure of trans and non-binary individuals. - On paragraph 4, I think
Articles or other works that were published under a pre-transition name should use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnote.
is a narrowing of the current guideline? It removes the current exemption where if a person prefers their former name to be used for past events, we can currently use it. I also agree with Tamzin that therespectful extra mentions
is hard to parse, and could do with a re-write. - For paragraph 5, I agree that
When the individual does not meet one of the exceptions, there may be some difficulty in hiding the information on gender transition.
should be removed. Tamzin has succinctly covered why it is unnecessary and unwise. The example for this paragraph is fine, as it's taken directly from the current text. - For paragraph 6, this should be condensed back in to paragraph 5. Formatting wise it could look weird for this section to end on a bullet point example, however this entire replacement text would be followed by MOS:NEOPRONOUN anyway so it's not a big deal.
- I realise this is a rather lengthy comment, but it's a rather lengthy proposal. My biggest issue here in general, is that this simplification pass is also including recommendations that depart significantly from both current practice and the current consensus. I would find this easier to support if this was just a simplification pass that otherwise included the current intent of the guideline, and with the departures from current practice presented separately. As a proposal, I think this is trying to do too much at one time, and that's caused at least some of the issues I've mentioned above. Sideswipe9th (talk) 22:53, 22 July 2023 (UTC)
- Disagreeing with the changes because they're a departure from the current guideline isn't really a strong position to take? I don't think the intent here was just to rewrite without changing the meaning. Like regarding
When looking at just the current examples in GENDERID, this means that we would now be allowed to include the former names of Rachel Levine and Laverne Cox.
, there is a good case to be made for including the former name of Rachel Levine. We don't need to shoot down any change just because it's a departure from the status quo or past consensus; that does not make any sense. - Also, anyone who is publicly trans or non-binary would pretty clearly fall under exemption two. The only reason we wouldn't include information on someone being trans or non-binary is if they transitioned pre-notability and don't make that public. For example, someone like Cavetown, before they publicly came out as trans. Elli (talk | contribs) 02:57, 23 July 2023 (UTC)
Disagreeing with the changes because they're a departure from the current guideline isn't really a strong position to take?
It is when the current guideline was formed through a series of strong consensus discussions based on exact wordings (typically RfCs, see MOS:GIDINFO). A proposal to streamline the existing guidance, without changing the scope of it is far more likely to get handwaved through a discussion like this. However a proposal that is fundamentally changing parts of the scope of the guidance, especially in a way that it would alter some rather long standing consensuses, is I'm afraid going to be a lot more contentious. To try and do both a streamline and change of scope at the same time seems foolhardy, given how slow the community as a whole likes to take when updating policies and guidelines in general.anyone who is publicly trans or non-binary would pretty clearly fall under exemption two
Would they? The exemption statesclearly expressed their consent to share the information
, which in my experience is actually quite rare in a reliable source. Often you'll see a sentence like "X is trans/non-binary/genderqueer", but not with any clear sign that X actually consented for that to be included in the source. Of course there are times when you'll have an interview where X states "I am...", which could be read as a clear sign of consent, but that is not always the case. Sideswipe9th (talk) 03:08, 23 July 2023 (UTC)To try and do both a streamline and change of scope at the same time seems foolhardy, given how slow the community as a whole likes to take when updating policies and guidelines in general.
If we're gonna change the scope, might as well do a full rewrite to clean things up. Despite all the discussions, it's clear many aren't happy with the status quo, and it has many issues.- Looking at the second point more... yeah, this would probably not be as much of an issue if point three dropped the "public figure" requirement (another very nebulously defined term around here). Elli (talk | contribs) 04:29, 23 July 2023 (UTC)
Despite all the discussions, it's clear many aren't happy with the status quo, and it has many issues
Ehhhh. While I could certainly identify a handful of editors in the two most recent RfCs who are dissatisfied with the scope of the current guideline, those seem to be in a minority. I would hesitate on drawing conclusions on the dissatisfaction of the guideline from the editors who are only contributing here, as it would be a form of selection bias. A talk page like being a natural place for those who are either seeking clarification on how to apply a policy or guideline, or those seeking to change a policy or guideline, to congregate."public figure" ... (another very nebulously defined term around here)
Yeah, the lack of clarity on how we define a public figure is causing issues in more areas than this. Sideswipe9th (talk) 04:37, 23 July 2023 (UTC)
Tamzin's rewrite + clarification in BLPPRIVACY
Trying to synthesize the overall general support for Cuñado's rewrite with the critiques I and others have given, my ideal approach would be this, which I feel better separates the policy considerations from the stylistic ones, allows for local consensus where the latter is concerned, and in relatively few words gives broad guidance for non-BLPPRIVACY-related deadname issues that will still prevent gratuitous usage:
- Add "and former names" to the relevant parts of WP:BLPPRIVACY, and after the line there about verifiability not guaranteeing inclusion, add the line "This includes the former names of living transgender and nonbinary persons, which should only be included in accordance with the principle of due weight". I think there's already a consensus that this is the case; this would just be emphasizing that detail.
- Change GENDERID to say:
Refer to any person whose gender might be questioned with the name and gendered words (e.g. pronouns, waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources.
Do not include any information about a living person that would violate WP:BLPPRIVACY. Information about a living person's gender transition (including the fact of the transition itself, any former names ["deadnames"], and medical information) is considered private if the person is a private figure or the information does not appear in high-quality reliable sources, unless the person has voluntarily disclosed this information.
Even when information about a living person is non-private, or when information concerns a deceased person, verifiability does not guarantee inclusion. Former names are not inherently of encyclopedic value, especially when the person was not notable prior to their transition. Articles must not give undue emphasis to these or other aspects of a transition, erring on the side of exclusion and, where information is included, avoiding unnecessary repetition. Sources that mention such information in passing, or purely for sensationalist reasons, should be given little weight.
When mentioning a transgender or nonbinary person in a context prior to their transition, use their current name, unless they have a preference otherwise; on articles other than their biography, their previous name can be given parenthetically or in a footnote if necessary to avoid confusion. Citations should generally not be modified, but the person's current name may be given in a note or via piped link. However, in no case should an article link a person to a pre-transition identity if that connection constitutes private information.
If the former name appears in a quotation, the article may need to paraphrase, elide, or use square brackets to replace portions of quotations to avoid deadnaming or misgendering.
- Critic X said "Juno needs a fine [actor] to play its pregnant teenage star, and [Elliot] Page has shown [himself] to be the perfect [man] for the job." involves many bracketed changes, so is better paraphrased: Critic X argued that portraying the pregnant teenage lead in the film Juno required a fine acting talent, and said that Page had proved perfect for the job.
Obviously this would require consensus at WT:BLP too, but first I'd like to get a sense for if this is something people here would support. -- Tamzin[cetacean needed] (she|they|xe) 18:56, 23 July 2023 (UTC)
- Should be made a bit more clear to indicate that including former names is almost always done when someone was notable pre-transition. Good with this otherwise, though. Elli (talk | contribs) 19:04, 23 July 2023 (UTC)
- Looks like we were drafting at the same time. I prefer the version with a list of exceptions. It really gets muddled when you try to cover all the different conditions in paragraph if/then form. Cuñado ☼ - Talk 23:58, 23 July 2023 (UTC)
- On the whole I think this is a better proposal, but I still have some issues:
- Would the addition to BLPPRIVACY not represent a weakening of the current formulation of GENDERID? Currently unless there's an exceptional case, we have a strong requirement not to include the former name, regardless of whether reliable sourcing exists, and that we should treat it as a privacy interest that is separate from and greater than the person's current name. By shifting this to just WP:WEIGHT I worry that this change would allow for the widespread inclusion of deadnames for living trans and non-binary individuals, because there are all manner of sources we consider reliable that nonetheless are trans and non-binary antagonistic and have a tendency to publish former names, often for no other reason than to say "Jane Doe was born John Doe" or vice versa. This is especially so in cases where the individual does not want that former name known. If we're going to move that section to BLPPRIVACY and/or BLPNAME, should we not incorporate what the current guidance states with respect to the privacy protections for former names? If we don't include the current guidance, from what I know of the sources, editors would now be allowed to include the deadnames of article subjects like Laverne Cox and Nicole Maines, who are open about their trans status and activism on LGBT+ issues, but for the most part do not disclose their former names or acknowledge their former names. I know above you've said you wish to address a part of the guidance that's preventing you from including Sarah Ashton-Cirillo's former name, and I sympathise with that, but Ashton-Cirillo's open disclosure of her former name is quite rare in my own experiences, both as a trans person, and as someone who edits many trans and non-binary biographies. If we're going to add an exemption for cases like her, then we need to make absolutely sure that it isn't so wide an exemption that it impacts on those trans and non-binary people who aren't open about their former names and do not ever wish to be linked to them.
- I'm still also hesitant over this new clause on public figures. The current discussions over at WT:BLP with respect to BLPCRIME and the scope of public figures for that policy's public figure exemption demonstrate how nebulously defined (thanks Elli) it is. The lines between whether a person is low or high profile after they meet WP:N, or a relevant SNG are incredibly blurry. Until we have a much stronger and less ambiguous definition of who is or is not a public figure, I'm not sure I could support a new exemption on this.
- For
However, in no case should an article link a person to a pre-transition identity if that connection constitutes private information.
I'd like if we could link or mention outing here, as that better explains the severity behind this requirement. - My last major concern is the lack of guidance for deceased individuals. While Cuñado's draft brought back a proposal that's been rejected a few times, this proposal doesn't contain any actual guidance for when you can include a former name. Yes it mentions that they are not of encyclopaedic interest per the recent RfC, and maybe we could wikilink that in the text, but it still leaves us in the situation prior to Billed Mammal's recent bold addition where we have no actual guidance for what that means. The placement of the former name aside, and assuming it doesn't change in the mean time, could we at least incorporate the requirement of it needing to have been documented in multiple HQRS and secondary/independent sources with non-trivial coverage of the person? Yes that means were still keeping some guidance on content inclusion criteria here, but I can't immediately think of anywhere else to put it. It doesn't really fit in with BLP, as this would apply longer than BDP.
- In summary, this is a better proposal than Cuñado's, but still some big issues that could cause us major privacy problems for living trans and non-binary individuals. Sideswipe9th (talk) 18:40, 24 July 2023 (UTC)
Revised proposal from feedback
Responding to several comments above:
pre-transition names are often included in the leads, to help with readers who may have only heard of a person pre-transition, to avoid confusion
- There was an oft-repeated concern in the last two RFCs that inclusion of a former name ends up with it in the first sentence with an elevated prominence. Not requiring it in the first sentence is an important part of the compromises going on. It's actual placement is up to editorial consensus, and this draft just says that it doesn't have to be in the first sentence.The point is not to conceal that someone has transitioned at all, the point is to conceal a piece of information that could be wielded by malicious actors.
- There is certainly a contingent of people who have transitioned and don't want it known that they are transgender. They want to pass as the new gender. For those cases, the fact of transition is a private matter that they don't want pointed out publicly, so we should maintain a higher bar for inclusion, just like the former differently-gendered name.I would like to see a note to the effect of "Sometimes some information about a person's transition will be public, while other information will be private."
- Added below.generally reliable sources have been known to include details' of people's transitions for reasons of sensationalism
- Added note below.respectful extra mentions...
- Deleted below.In the "Articles or other works" bit, there should still be an exception for those who prefer to be referred to by pre-transition names.
- I changed "under a pre-transition name should use" to "under a pre-transition name may use". I think that wording fits with this being the MOS and offering style ideas. The alternative was to make it more wordy and maybe overprescriptive.some difficulty in hiding the information
- Deleted below.The last sentence of the penultimate paragraph should be made last overall
- Moved below.public figure exemption
- I think the claim of 'public figure' being undefined is bogus. BLP has a section on WP:PUBLICFIGURE and there is the BLP-attached essay WP:Who is a low-profile individual that has a long list of examples and definitions of "high-profile" individuals. A public figure is someone who: has a multitude of reliable published sources, actively seeks out media attention, has given one or more scheduled interviews to a notable media company, is self-promotional... there are more descriptions on that page.I don't quite understand exemption 4
- This does two things: it says that the lingering privacy concerns described at WP:BDP should default to the maximum of two years in the case of GENDERID, and it raises the bar for inclusion to the same as living public figures (multiple reliable secondary sources). If a notable transgender person has a biography but doesn't meet any exceptions, their page doesn't mention their former name. Two years after they die, the bar for inclusion is higher than normal facts about their life. The last two RFCs failed to gain support partly because they lacked a coherent argument based on policy and failed to address why the information is excluded and how WP:BDP relates to the question.guidance about people whose notablity is due to pre AND post transition
- if that means people whose notability post-transition is not enough to pass GNG but pass with coverage pre- and post-? I think that would mean they were not notable prior to transition and is covered.The second paragraph I find objectionable... I hope I'm reading this incorrectly
- Clearly this is not an attempt at "gender identity erasure".I have some pretty large reservations about what has been proposed here that lead me towards opposing this as currently written.
- I also disagree with parts of the proposed re-write, but I compromised and drafted something that will satisfy the most amount of people. If there is not consensus for the draft, I'll take it to RFC, where I'm pretty confident it will pass.
Proposed MOS:GID section draft #2 |
|---|
|
Refer to any person whose gender might be questioned with the name and gendered words (e.g. pronouns, waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources. Any information related to the prior gender of a person, including former names (deadname), should automatically be considered a matter of personal privacy and removed, with the exception of:
Unless the individual meets one of the exceptions, information that could reveal a gender transition should not be used in lists, redirects, disambiguation pages, category names, etc., even in quotations, even if a reliable source exists.[a] When the individual meets one of the exceptions, information on their gender transition must not be given undue weight or overemphasis, and editors should always err on the side of excluding it. Former names are not automatically of encyclopedic value. The former name of a transgender or non-binary person may be placed later in the lead or elsewhere in the article instead of the first sentence, to avoid giving it undue prominence. Sometimes, some information about a person's transition will be public, while other information will be private. Articles or other works that were published under a pre-transition name may use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnote. When the individual does not meet one of the exceptions, avoid confusing constructions (Jane Doe fathered a child) by rewriting (e.g., Jane Doe became a parent). If the former name appears in a quotation, the article may need to paraphrase, elide, or use square brackets to replace portions of quotations to avoid deadnaming or misgendering. Do not replace or supplement a person's former name with a current name if the two names have not been publicly connected and connecting them would out the person. In rare cases where exact wording cannot be avoided (e.g. pun, rhyme, album cover), the quotation or work should not be used.
|
Cuñado ☼ - Talk 19:22, 23 July 2023 (UTC)
- "There is certainly a contingent of people who have transitioned and don't want it known that they are transgender." It's not WP's job to cover over basic facts that are reported in reliable sources. In short, you'll never get consensus for a "conceal that someone has transitioned at all" proposal. It's not WP's job to police the real world, and the fact that being trans or enby in some environments is challenging is simply a fact of life. Someone else higher up the page (in a different thread) objected to language like "person whose gender might be questioned", and I agree it's rather weird phrasing (though I'm not sure what to suggest in place of it; maybe "person whose gender might be unclear to the reader"?). "Third party" is not a phrase we normally use; the stock term is "independent", so use it and avoid confusion. "may be placed in the infobox or background section of the article instead of the first sentence" is wrong, because infoboxes are not for publishing information that is not found elsewhere in the article (see MOS:INFOBOX). I would revise this to "may be placed later in the lead or elsewhere in the article instead of the first sentence". (This will also fix the obvious loophole problem that people will mistake your original wording for "permission" to editwar to keep something out of the entire lead section. Never leave an exploitable, drama-bound loophole in any policy/guideline wording!)Much of the rest of the redrafting looks pretty good, but getting the community to accept a total overhaul is going to take another WP:VPPOL RfC, since WP:Writing policy is hard and every word in every sentence of it has the possibility of unintended negative consequences. Hell, just changing one sentence has involved three RfCs that have all failed to come to consensus. — SMcCandlish ☏ ¢ 😼 23:02, 23 July 2023 (UTC)
- Above I changed "third-party" to "independent" and used your wording of "may be placed later in the lead or elsewhere in the article instead of the first sentence".
- I'm curious about the "conceal that someone has transitioned at all" comment. I thought the point of this was guide was to address the sensitive issue of how Wikipedia includes details of gender transitions, and the former name is just one part of that. I thought "information related to the prior gender of a person" was pretty clear and broad enough to include a variety of potentially personal information, including medical details. Cuñado ☼ - Talk 23:56, 23 July 2023 (UTC)
- Well, see above; I just copy-pasted that wording from the rest of the discussion. Without staking out a strong position on every detail, I'll just reiterate that gaining site-wide consensus in this area is unusually and extremely difficult; right now there seems to be a rough consensus forming that deadnames should not be reported in our material at all, even of the semi-recently deceased, unless there is substantial coverage of them in multiple reliable sources. But that's as far as the consensus seems to be brewing. If you want to quite markedly expand this into a principle to completely hide the fact that someone went through a gender transition, you're going to find much, much more push-back against that idea, because it is so much broader a form of information-suppression and source-ignoring. In short, take baby steps. Gain clear consensus for what there is already a rough consensus for, then try moving a bit at a time toward other forms of TG/NB special-protectionism. (If at all. I'm not a big fan of this idea, personally, but I'm honestly telling you how you can go about changing policypages effectively; I've been at this since 2006-ish.) — SMcCandlish ☏ ¢ 😼 10:17, 24 July 2023 (UTC)
I think the claim of 'public figure' being undefined is bogus
The exact definition of public figure is taking up much editorial discussion over at WT:BLP right now, in relation to the scope of WP:BLPCRIME. A lot of editors are using a particularly expansive definition of it that doesn't entirely mesh with how reliable sources would define the term.The last two RFCs failed to gain support partly because they lacked a coherent argument based on policy and failed to address why the information is excluded and how WP:BDP relates to the question
That doesn't match with the discussions in the most recent RfC. Only four editors, including both you and I, even mentioned BDP. The primary opposition to the proposal, as noted in the closure, was that the barrier for inclusion was set too high. Even in the RfC before that, only 5 editors mentioned BDP, and only two did so in order to oppose a change from the then current lack of guidance. The other three editors who mentioned it supported removing the word "living" from the current text of GENDERID. SMcCandlish's suggestion above that we should be analysing in detail the most recent RfC to figure out roughly where the consensus lies, so that we're not repeating the same discussion and going off on a different tangent altogether, is a good one, and even a quick analysis of it would suggest that a BDP based exclusion criteria is a non-starter.If there is not consensus for the draft, I'll take it to RFC, where I'm pretty confident it will pass.
That would be inadvisable when we have another draft that is being worked on concurrently. It would also be inadvisable given SMcCandlish's advice on in depth analysis of the most recent RfC to try and figure out roughly where the consensus lies. I'm pretty confident that this proposal would not pass at this time, because the community's consensus is elsewhere. Sideswipe9th (talk) 19:28, 24 July 2023 (UTC)
- Sideswipe9th, who do you think these comments were directed at, at Village pump? and . Cuñado ☼ - Talk 22:58, 24 July 2023 (UTC)
- Though I fail to see the relevance to the feedback on your proposal, I would say that Anomie's suggestion is not congruent with WP:RFCBEFORE, which encourages discussion and workshopping prior to launching an RfC at a relevant venue. Their point on this being a local consensus formed by "a bunch of activists" ss also not representative of the history of discussions on this guideline point, with a lot of the RfCs on the scope and text of GENDERID occurring at the Village Pump or otherwise notified on WP:CENT. The current state of the guideline is very broadly supported by the community consensus.
- As for JohnFromPinckney's comment, they are right, there have been a lot of discussions on this recently. However almost all of the sections that John is referring to were stale, with most not having had a comment in about a month, until SMcCandlish added a single comment to each one yesterday. Until those single comments were added, only three (this section, the one directly above on WP:BOLD restrictions, and the discussion on neopronouns were actually active.
- Now, back to the feedback on your proposal please. Sideswipe9th (talk) 23:10, 24 July 2023 (UTC)
- Sideswipe9th, who do you think these comments were directed at, at Village pump? and . Cuñado ☼ - Talk 22:58, 24 July 2023 (UTC)
- My point was, you are making big claims about consensus of the community, and I think the last two RFCs, which you either initiated or helped initiate, had a biased activist-y setup that was opposed by people on this page (like me) beforehand, but you ignored my feedback, and rather than acknowledge the failure of each of them, you are continuing down the same path.
Public figure
I think you're really stretching for a criticism when this explains it and the phrasing is already used in BLP.That would be inadvisable when we have another draft that is being worked on concurrently.
that's not feedback on my proposal.SMcCandlish's advice
yes, they gave me good feedback that I'm trying to figure out how to incorporate. I thought the desire of maintaining the dignity of trans people would include allowing a living (or recently deceased) person the presumption of wanting details of their transition kept private unless they share it themselves. You interpreted my draft as "gender identity erasure", which was a surprise. If this is really about the deadname, then the exceptions could apply to deadname only. Cuñado ☼ - Talk 23:55, 24 July 2023 (UTC)- "the desire of maintaining the dignity of trans people" (which is very, very loaded phrasing) is not inherently a Wikipedia goal, and over-broadly interpreted is even inimical to actual Wikipedia goals, and it was not a consensus conclusion of the community. Rather, it was one of many arguments presented that in small part led to the limited amount of consensus that we've been able to hammer out at all. In short, you're kind of confusing an effect with a cause. — SMcCandlish ☏ ¢ 😼 00:13, 25 July 2023 (UTC)
- Oh stop SMcCandlish, you're making me like you too much. I feel the same, but I was trying to articulate a common sentiment that was expressed in the recent RFCs. Like I said, I disagree with several things about my draft but it needs to be acceptable to the most amount of people to pass. For example, Tamzin's response to my draft:
This proposal shifts us to a more common-sense-based approach that acknowledges the importance of subjects' dignity and not giving undue weight
. Cuñado ☼ - Talk 06:08, 25 July 2023 (UTC)- That's an interesting talk-quote, because I was going to say that the problems with the idea become immediately clear if you change "the desire of maintaining the dignity of trans people" to "the desire of maintaining the dignity of subjects" in general. Subjects' personally defined [search this page for "idolect" for related matters] "dignity" is not broadly an MoS or WP concern, aside from basic notions of human rights and WP:NPOV and (where applicable) WP:BLP policy. The kind of objective "basic human dignity" matters addressed by those policies have very little in common with the vernacular expansion of the "dignity" notion by a certain camp in the LGBTQIA+ sphere and perhaps far-left activism in general. (Search this page also for the phrase "means colloquially" for additional related matters of the hazards of using meaning-expansions that undermine the very concept a term was created for.)This has much to do with all the push-back at the last several RfC rounds, because the proposals were essentially trying to create a "special class" with protections – that exceed NPOV, BLP, NOT#INDISCRIMINATE, and other policies – that would apply to no one else (and to do it by trying to misuse a style guideline to supersede core policy, which is not procedurally really possible in the first place). The real trick to getting consensus on an improved MOS:GENDERID is going to be staying within the bounds of existing core policy. There's a really fine line between addressing a concern (e.g. deadnaming) that largely or entirely only pertains to a particular class, and carving out a special level of "extra protection" (which equates to extra censorship and extra ignoring of reliable sources, etc.) pertaining to that class.Going too far the other (broadly generalizing) direction won't work either. I'll even go so far as to say that editors trying to "borrow" the deadnaming idea from TG/NB/GQ subjects and apply it to anyone, ever, who has changed their name and would rather never hear/see the old one again, like the entertainer Teller (see this VPPOL thread) is basically subcultural appropriation of a certain type of wrong that affects the real subcultural class very differently and much more potently, and applying it in an aggradizing way to something else, trivializing the concept in the process. (The "means colloquially" post mentioned above also raises related matters again.) Reminds me of bogus arguments that have been made about "Celtic" indentured servants in early America being "the same as" enslaved Africans, or mockery of satiric pseudo-religions (Chuch of the SubGenius, etc.) being "the same as" attacking someone for being Jewish or Amish or whatever, and several other false-analogy arguments that people make involving a real sociological class with a shared social experience, and something else entirely that is only similar in a superficial way. — SMcCandlish ☏ ¢ 😼 07:09, 25 July 2023 (UTC)
- Oh stop SMcCandlish, you're making me like you too much. I feel the same, but I was trying to articulate a common sentiment that was expressed in the recent RFCs. Like I said, I disagree with several things about my draft but it needs to be acceptable to the most amount of people to pass. For example, Tamzin's response to my draft:
- "the desire of maintaining the dignity of trans people" (which is very, very loaded phrasing) is not inherently a Wikipedia goal, and over-broadly interpreted is even inimical to actual Wikipedia goals, and it was not a consensus conclusion of the community. Rather, it was one of many arguments presented that in small part led to the limited amount of consensus that we've been able to hammer out at all. In short, you're kind of confusing an effect with a cause. — SMcCandlish ☏ ¢ 😼 00:13, 25 July 2023 (UTC)
TNT on GENDERID draft #3
Made a few changes based on conversation above, including:
- "whose gender might be questioned" to "whose gender might be unclear"
- "Any information related to the prior gender of a person, including former names (deadname)" to "A transgender or non-binary person's former name (deadname)"
- "information that could reveal a gender transition" to "the former name"
- "where exact wording cannot be avoided (e.g. pun, rhyme, album cover), the quotation or work should not be used" to "may be included"
- added footnote in first paragraph
Mainly it was shortened, and reduced in scope to focus on the former name and not other details of gender transition. Feedback is most welcome.
Proposed MOS:GID section draft #3 |
|---|
|
Refer to any person whose gender might be unclear with the name and gendered words (e.g. pronouns, waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources. A transgender or non-binary person's former name (deadname) should be considered a matter of personal privacy and removed,[a] with the exception of:
Unless the individual meets one of the exceptions, the former name should not be used in lists, redirects, disambiguation pages, category names, etc., even in quotations, even if a reliable source exists.[b] When the individual meets one of the exceptions, the former name must not be given undue weight or overemphasis, and editors should err on the side of excluding it. Former names are not automatically of encyclopedic value. The former name of a transgender or non-binary person may be placed later in the lead or elsewhere in the article instead of the first sentence, to avoid giving it undue prominence. Articles or other works that were published under a pre-transition name may use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnote. When the individual does not meet one of the exceptions, avoid confusing constructions (Jane Doe fathered a child) by rewriting (e.g., Jane Doe became a parent). If the former name appears in a quotation, the article may need to paraphrase, elide, or use square brackets to replace portions of quotations to avoid deadnaming or misgendering. Do not replace or supplement a person's former name with a current name if the two names have not been publicly connected and connecting them would out the person. In rare cases where exact wording cannot be avoided (e.g. pun, rhyme, album cover), the quotation or work may be included.
|
Cuñado ☼ - Talk 05:24, 26 July 2023 (UTC)
- Some feedback:
- You could probably simplify
Refer to any person whose gender might be unclear with the name and gendered words...
toRefer to any person with the name and gendered words...
without much of an issue here. A person doesn't need to be trans or non-binary to need or want to say "Hi my name is X and my pronouns are Y/Z". - I think
A transgender or non-binary person's former name (deadname)...
would read better asThe former name (deadname) of a transgender or non-binary person...
. I don't like the weakening though of making it just a privacy interest, as the current version of the guideline states that it's a privacy interest separate from and greater than their current name. Is there a reason for this change? - As a new clause that isn't in the current version of GENDERID, the public figure exemption needs to be stronger. At minimum that should be something like
multiple high quality reliable sources
and some extra wording that takes into sensationalism (it's late and I can't wordsmith that right now). There's all manner of marginally reliable sources that include sentences like "Jane Doe was born John Doe", and the sheer volume of those sources alone shouldn't be an inclusion criteria when high quality sources do not do this. I know there's a footnote B somewhat along those lines, but in context it looks like footnote B only applies to individuals who don't meet the 4 exemptions you're proposing. - Still has the BDP issue. See my earlier comments for why this is unworkable, and SMcCandlish's earlier comments about reviewing the most recent two RfCs in detail to assess for some wording that would better fit where the community consensus lies.
- Are you sure your fourth bullet point is accurate? That change doesn't seem to be reflected in the text.
- You could probably simplify
- May have more to say later. It's late and my brain has mostly gone to sleep. Sideswipe9th (talk) 05:50, 26 July 2023 (UTC)
- Thanks for taking the time to look it over, I incorporated your 2nd and 5th bullets into the draft above. A few comments on the others:
Refer to any person with the name and gendered words...
I have to disagree on this one. I only proposed changing "questioned" (current) to "unclear" because of a comment about the current wording sounding strange. Most people (like 99%) do not state their preferred names and pronouns and there is no ambiguity on their gender, so it makes more sense to start the section saying, in the least offensive way possible, that this is for those whose gender is unclear or out of the ordinary.a privacy interest separate from and greater than their current name
- I don't know what this means. There is no privacy concern about a person's current name.the public figure exemption needs to be stronger
- I thought about this for awhile and reviewed several policies. The same wording could be used for this and the deceased example. There is no policy or guide defining "high-quality" sources. The closest you get is WP:RS referencing "high-quality mainstream publications", but I don't think that would work here because it is contrasting those to scholarly sources. Keep in mind my draft phrasing of "multiple reliable sources" is directly from BLP, and the MOS should not be making policy. The best I could come up with from policy is to say "multiple reliable, neutral sources". Neutral is well described in policy and allows the exclusion of low-quality, opinionated, or questionable sources. I think that gets to the spirit of excluding sensational reliable sources.the BDP issue
- this is a change that I think needs to go to RFC. We won't agree on this talk page.
- Cuñado ☼ - Talk 17:51, 30 July 2023 (UTC)
Most people (like 99%) do not state their preferred names and pronouns and there is no ambiguity on their gender
Hard disagree. One of the first things that is said when you are introduced to someone you have never met (either by yourself or a third party) is your name. In modern contexts, this often also includes your pronouns, if they're not inferrable from words said during the introduction, for exampleHave you met Jane Doe yet? They're/She's new here and working on X project
. And lets not even touch on how many people include their pronouns in their email footers and social media bios.There is no privacy concern about a person's current name.
Yes there is. WP:BLPNAME covers the most common privacy concerns over names. As for the rest, consider it as two complementary clauses;a privacy interest separate from their current name
anda privacy interest greater than their current name
. The first clause is easy, you simply evaluate the privacy concerns separately from their current name. The second clause likewise is pretty straightforward, when evaluating the privacy concerns, you need to do so at a level beyond that at which we would normally include a person's name.The same wording could be used for this and the deceased example.
Maybe, if written correctly.There is no policy or guide defining "high-quality" sources.
Huh, I could have sworn WP:HQRS redirected to a specific section of WP:RS that defined it. That aside, from looking elsewhere I'm not sure if the lack of definition is a problem. The text at WP:EXCEPTIONAL states thatany exceptional claim requires multiple high-quality sources
, though footnote 4 sadly only gives some philosophical reasons for why we require strong evidence. WP:BLP contains multiple mentions throughout to both "high-quality sources" and "high-quality reliable sources", linking to WP:SOURCES. WP:MEDRS likewise contains mentions throughout "high-quality sources" and "high-quality reliable sources" without definition. The closest we seem to get right now is the WP:BESTSOURCES section of WP:NPOV, but even then it mentions "high-quality sources" without defining it. I question then if this lack of definition for the term is a problem that we need to concern ourselves with. Yes it would be exceptionally helpful if it was defined somewhere, but given that core content policies use the term without defining it suggests that such a definition may not be necessary.The best I could come up with from policy is to say "multiple reliable, neutral sources". Neutral is well described in policy and allows the exclusion of low-quality, opinionated, or questionable sources.
It is, but it's also the subject of considerable and frequent debate at an article level. "Is this source baised against/towards [article subject]?" is the sort of question you'll see variations of frequently, especially in contentious topic areas like gender and sexuality,this is a change that I think needs to go to RFC
Why do we need an RfC to datamine the results of the two most recent RfCs? Why can't we put a pause on the BDP point for now, and just start a separate discussion (either as a subsection or new discussion here, or on a dedicated page) where we can compare notes on those RfCs to find out what people have already said, and from that see if we can distil something that might stand a very strong chance of being accepted? Yes it will take us a little time and effort now, but it will save us a lot of time and effort later, and afford us a fair degree of community good will. Maybe at the end of that process a BDP based clause will be the right option, or maybe it'll be something else that no-one here has yet put forward. Sideswipe9th (talk) 18:22, 31 July 2023 (UTC)In modern contexts, this often also includes your pronouns
- no, it almost never does. A person's gender is almost always extremely clear from their chosen appearance and that is expected and understood to be sufficient in nearly all social contexts. A standard that would require people to explicitly say "my gender is male and my pronouns are he/him" would send the vast majority of people (and even more historical individuals) into a genderless they/them category, which is far more offensive and misgendering than anything else.- Pronouns in social media bio are also by no means universal and seem to have reached saturation in uptake. Crossroads -talk- 19:16, 31 July 2023 (UTC)
- Respectfully I think you've misread this chain. Nowhere did I say that a person typically introduces their gender in introductions, only their name and pronouns. I also struggle to see how rephrasing to
Refer to any person with the name and gendered words ... that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources.
would result in sendingthe vast majority of people...into a genderless they/them category
. Perhaps you could expand on why you think this might happen? - The scope of this change is to make sure we're always using the correct name and pronoun, for any biographical subject, regardless of any other circumstance. This is something that we should be already doing for the vast majority of articles. A gender being clear does not negate the necessity to ensure that we're using the correct names and gendered terminology for our article subjects. Sideswipe9th (talk) 19:31, 31 July 2023 (UTC)
- I've already commented on pronouns in introductions so I won't repeat myself on that. We shouldn't open ourselves up to wikilawyering or technicalities. Most people never specify their pronouns. They consciously choose to appear a certain way, are referred to by others with the words that fit with that, and that's it. We don't want an opening for someone to say 'well the person never said she/her is correct, how can we really know?' And if someone thinks pronouns in introductions are necessary, then the corollary of that is most people's pronouns are unknown because they've never specified them. We don't want to go that route, that's not how RS or society works. Crossroads -talk- 19:47, 31 July 2023 (UTC)
- I'm gonna agree with Crossroads here on the pronouns issue. I dunno if it's 99% of the time but it's definitely far more common for someone to trust others to infer their gender from their appearance (which, to be clear, is usually pretty accurate, which is why people keep doing it) then to explicitly mention their pronouns.
- Which is to say, I think the original wording is more-or-less fine. Someone not mentioning their gender does not mean it is unclear, and requiring people to state their gender before we can mention it, even implicitly, causes way more problems than it solves. If someone does say their gender explicitly we should go with what they say, but having a robust default if they don't is not optional. Loki (talk) 20:08, 31 July 2023 (UTC)
- While I clearly disagree, I can see that the consensus is not with me on this point, so I shall drop it. Sideswipe9th (talk) 00:16, 1 August 2023 (UTC)
- Respectfully I think you've misread this chain. Nowhere did I say that a person typically introduces their gender in introductions, only their name and pronouns. I also struggle to see how rephrasing to
- Responding to Sideswipe9th:
Refer to any person whose gender might be unclear...
- I have to agree with others that the scope of this MOS should be clear in the intro. We're talking about a special case and I think the question here is whether "unclear" is better than "questioned".There is no privacy concern about a person's current name.
- I see what you mean now. The examples are of names who are not the subject of articles. As in, suspects in crimes who don't need to be named, names of family members of a notable person, loosely or uninvolved low-profile persons, etc. I think the current wording ("separate from and greater than a current name") just sounds confusing and doesn't really add anything useful. This is MOS/biography, of course the current name will be mentioned.There is no policy or guide defining "high-quality" sources.
- This was one of the sticking points at the last RFC. I agree with your assessment that it is used enough in policies that it can probably be used here safely, but it will have the same problem that you describe defining what is "neutral". I could support either wording but I lean toward "multiple reliable, neutral sources".Why do we need an RfC?
- There is a high level of fatigue on this subject and the reasons seem to be that a local consensus on this page, where gender-activists are overrepresented, will probably not create something that will win consensus at Village Pump. The last two RFCs had a fairly biased setup and seemed to disregard the magnitude of creating an exception to WP:NOTCENSORED in the MOS, without a tie-in to BLP. I would be thrilled to work out a local consensus for a re-write, but I have been described as "the opposition" and even the most basic good-faith contributions have been blocked at every step. Prove me wrong.Why can't we put a pause on the BDP point for now?
- Think of it another way. The last two RFCs tried to extend the censoring of former names to deceased people indefinitely. There was no consensus, BilledMammal's attempt to work something in got reverted, and the MOS went back to excluding the former names of living trans people, leaving the rest to BLP. BLP allows censorship of reliably-sourced information about living people, but the policy does not apply to people confirmed dead, with the only exception for recently deceased, and allows that protection to gradually fade after death, the policy can extend based on editorial consensus for an indeterminate period beyond the date of death—six months, one year, two years at the outside. So given the concern, why would you not support the MOS saying that on this subject, automatically extend to the maximum of two years? Would you rather some cases be six months? Your moonshot to extend it indefinitely failed twice, and anyway, the MOS is not the place to make such a policy.- Cuñado ☼ - Talk 22:22, 31 July 2023 (UTC)
The last two RFCs tried to extend the censoring of former names to deceased people indefinitely.
This sentence is a perfect example of why we need to review the last two RfCs in detail. While it is true that one of the options in the first RfC would have extended the protections (please stop calling this censoring, it's not censoring) afforded to living trans and non-binary individuals indefinitely (specifically, topic 2 option 3), that was not the case for the second RfC. The second RfC laid out a set of inclusion criteria for deceased individuals that was complementary to the existing guidance on living individuals, and in doing so allowed for the former names to be included when either they met the specific test for deceased individuals, or for individuals whose former names we could include when they were alive.- When I drafted the proposal that lead to the second RfC, I did so after thoroughly reading both the close and the comments made in the first RfC, alongside a side discussion by another editor who was going to close the first RfC. In doing so, I came up with a proposal that the closer of the first RfC thought was
a reasonable summation of how [they] read the consensus
. With the benefit of hindsight, I clearly made an error somewhere in that assessment, and that the community's consensus set a barrier for inclusion that wasn't quite as high as what I proposed. However making that error does not negate that making such an analysis is a good and necessary thing. - Right now we know three high level things:
- From the first and second RfCs that there is a community consensus for a change to GENDERID to provide guidance for deceased individuals
- From the first RfC that the consensus for the inclusion criteria of the former name of a deceased individual should be set to a high level
- From the second RfC, based on the comments by the closer, that the specific proposal in the second RfC set too high a barrier
- What we need to do before we can present any further options on guidance for deceased individuals to a future RfC, is to assess both of the recent RfCs in detail, and from those data points see if we can distil a proposal that would fit with what the community has said in both recent discussions. Both of those recent RfCs were held at WP:VPP, and were exceedingly well attended, so any concerns about
a local consensus on this page
would immediately be invalid as any proposal we come up with should first and foremost be based on what was said during the broad consensus discussions. Sideswipe9th (talk) 00:09, 1 August 2023 (UTC) The examples are of names who are not the subject of articles.
Not quite. See WP:BLP1E and WP:BIO1E, both of which advise us to avoid creating a biography on an individual who is only notable in the context of a single event. It's also inaccurate to say that this is only for criminal suspects. It also covers individuals whose notability is connected to any other controversial or non-controversial event.- The reason why there's two separate wikilinks here is that BLP1E applies only to individuals who are alive (or recently deceased), whereas BIO1E applies to those who are also deceased past the point of BDP. In either scenario, living or deceased past the point of BDP, if a person's notability stems from a single event, we have PAG reasons not to create an article about them. Sideswipe9th (talk) 00:29, 1 August 2023 (UTC)
- Thanks for taking the time to look it over, I incorporated your 2nd and 5th bullets into the draft above. A few comments on the others:
- This is looking better. I agree with all of Sideswipe9th's suggestions above, other than that I'll note that going with "high quality reliable sources" may increase resistance to the overhaul, as this phrase and the elevated standard it seems to refer to (but which is not actually defined anywhere) was a sticking point for various people in the last RfC (and probably the one before it, though I don't recall for sure). For my own part, I find "Individuals who have clearly expressed their consent to share the name" to be weird wording that will probably not meet with consensus (both "consent" and "share" are problematic for various reasons); but right this moment my head hurts, and I'm not thinking of a suitable replacement. I would also remove "or mockery" from the second footnote; that appears to be editorializing without any basis sourced so far in these discussions, and any publisher that engaged in outright mockery of TG/NB/GQ subjects would not be one WP considered "generally reliable". — SMcCandlish ☏ ¢ 😼 06:01, 26 July 2023 (UTC); rev'd. 06:28, 26 July 2023 (UTC)
- RE: changing
Individuals who have clearly expressed their consent to share the name
- how about "Individuals who have shared the name publicly" or something along those lines? Cuñado ☼ - Talk 17:56, 30 July 2023 (UTC)- Something like that is closer, but I think it's still missing that fact that this is usually a matter of public record and doesn't have anything to do with the subject disclosing something. It may be more a matter of what if anything the subject has said, in published material, about the name and their present relationship to it. But wordsmithing something like this is difficult, and as others have said elsewhere in here, trying to change more than one GENDERID factor at a time is probably a bad idea, because it gives anyone who would oppose one aspect of the proposal a reason to oppose the entire thing. — SMcCandlish ☏ ¢ 😼 23:17, 30 July 2023 (UTC)
- I do think that the bar should be that they've consented for people to reference the name. Janet Mock includes her birthname in her autobiography, but I don't think we should ever include it the article about her on that basis. Tekrmn (talk) 05:25, 31 July 2023 (UTC)
- At no point will an article be written based upon what the subject consents for us to write about them. That's just a non-starter out of the gate. WP:DUE and ensuring we use quality WP:RS will be sufficient. —Locke Cole • t • c 05:49, 31 July 2023 (UTC)
- thanks for sharing your opinion. do you have any policy or guidelines to support that? BLP:PRIVACY clearly indicates that consent is an important consideration for including personal information, such as a persons name, and the current MOS states that the birth names of living trans and nonbinary people's birthnames are treated as a privacy interest separate from and greater than a current name. we're obviously not talking about living people here, but to me the fact that this concern is "greater than" a privacy interest indicates, among other things, that the need to omit a person's birthname should still apply after their death. Tekrmn (talk) 17:13, 31 July 2023 (UTC)
At no point will an article be written based upon what the subject consents for us to write about them.
Actually the BLP policy already provides several clauses where an article subject can request the removal of information, which would include non-consensual publishing by reliable sources.- Date of births are covered by WP:BLPPRIVACY
If a subject complains about our inclusion of their date of birth, or the person is borderline notable, err on the side of caution and simply list the year, provided that there is a reliable source for it.
WP:BLPNAME urges caution for article subjects who are discussed primarily in connection with a single event, along with a strong presumption in favour of privacy for the family members of article subjects. WP:BIOSELF states that if an article subject finds that an article contains personal information or potentially libellous statements, they should contact the oversight team so that it can be evaluated and suppressed as appropriate. And yes, per the Foundation's website content that is reliably sourced can still be libellous, especially when it is subject to link rot, and we can be compelled to remove it. And WP:BLPREQUESTDELETE provides for non-public figure article subjects to request deletion of articles about them. Sideswipe9th (talk) 17:41, 31 July 2023 (UTC)- I see a lot of that being redundant to NPOV/RS, so I have no comment on that. Thank you for cataloging all the ways BLP runs against NPOV for me. I stand by my original statement. —Locke Cole • t • c 17:54, 31 July 2023 (UTC)
- If you believe that BLP runs counter to NPOV and given how strong your opinion on this is seems to be, might I suggest that you use this brief list to open a discussion at WP:BLPN and/or WP:NPOVN on this issue? It seems that you might want or need to fix this disconnect between BLP and NPOV first, as this will no doubt be affecting far more guidelines within the MOS and elsewhere than just GENDERID. Sideswipe9th (talk) 17:59, 31 July 2023 (UTC)
- I see a lot of that being redundant to NPOV/RS, so I have no comment on that. Thank you for cataloging all the ways BLP runs against NPOV for me. I stand by my original statement. —Locke Cole • t • c 17:54, 31 July 2023 (UTC)
- It is tricky to come up with wording. Maybe,
Individuals who have made the name public and not expressed a desire to conceal it.
orIndividuals who have made the name public post-transition
. Cuñado ☼ - Talk 22:47, 31 July 2023 (UTC)- The later is more plausible than the former. Unless the person is living in a country that has an equivalent to a super-injunction, where there is some sort of protection in law that prevents even the discussion of the protection, expressing a desire to conceal their name would likely have a Streisand effect outcome. In other words, it would likely be the same as shouting "don't think about the pink elephant" in a crowd, and expecting the crowd not to think about a pink elephant.
- I'm not sure about the later option though. It's certainly better than what's in the draft above, but I'm not sure it's robust enough to clearly differentiate between someone whose former name is known because they're open about it being their former name, and someone whose former name is known because a source has outed them. But I'm still not quite sure how you could reflect that in guideline text. Sideswipe9th (talk) 01:15, 1 August 2023 (UTC)
- At no point will an article be written based upon what the subject consents for us to write about them. That's just a non-starter out of the gate. WP:DUE and ensuring we use quality WP:RS will be sufficient. —Locke Cole • t • c 05:49, 31 July 2023 (UTC)
- RE: changing
- Personally, I think (as other editors commented earlier) that trying to make multiple substantive changes and also rewrite/reorder some things at the same time is inadvisable, since anyone who opposes any part of that (or just can't track all the changes) seems to be left having to oppose the whole thing—hence past RFCs have been closed with the advice to ask specific questions! In particular, since the just-closed RFC hinged in part on people feeling the proposed wording was insufficiently well defined, it seems unwise to introduce a term we already know is poorly defined ("Public figures", the subject of a huge discussion on BLP at this very moment), especially when one of the widely-held interpretations of it is "everyone mentioned in enough sources that we at Wikipedia are mentioning them in an article", meaning a sizeable portion of editors will read the new text as saying to deadname basically everyone who's discussed in enough sources that we're mentioning them in the first place. (For example, Laverne Cox is a public figure; the new text would seem to allow deadnaming her; I wasn't aware there was appetite for that from anyone but the few folks who want Wikipedia to deadname all trans people in all cases.) Both the allowance of deadnaming "Public figures" and the "BDP" part seem to come out of the blue, since I'm not recalling any widespread clamour to use those as metrics in the many previous discussions of this which have happened (indeed, in the pre-RfC discussion for one of the last RfCs, I got the impression more people felt "deadname people after—but only after—two years" was a poor approach, than liked it). -sche (talk) 07:59, 26 July 2023 (UTC)
- I think this is a great start. I agree with everything sideswipe said, I definitely agree that we should scrape the previous rfcs to find the exact exceptions people are concerned about, and I also agree that proposing this whole thing as-is or in some other iteration would be unwise- we should ask specific questions. I also think that there will be pushback on not requiring the deadname to be in the first paragraph, so personally I feel we might just want to remove that part for now since, in my opinion, inclusion is a bigger issues than overemphasis. Tekrmn (talk) 01:28, 27 July 2023 (UTC)
- Just noticed that there is a resolution by the Wikimedia Foundation accompanying the formation of BLP that says
human dignity and respect for personal privacy
are both reasons for the policy. Cuñado ☼ - Talk 18:05, 27 July 2023 (UTC)- Problem is, our editors can (and do) disagree on what constitutes “human dignity”.
- Is merely mentioning someone’s verifiable deadname in a respectful tone a violation of that person’s “human dignity”? Some will say “yes”, others will say “no”, and yet others will say “it depends”. We could argue that question for years with no consensus. Blueboar (talk) 19:31, 27 July 2023 (UTC)
- Admittedly, it's not a bad draft, this, but I have concerns about the last two bullet points.
- On the "public figure" exception – for example, in the UK, IPSO guidance often isn't worth the paper it's written on, and doubly so when it comes to trans issues. The IPSO Code of Conduct says that deadnaming even may constitute an unethical practice, but once a RS like the Telegraph prints someone's deadname, even if it's later ruled a breach of the IPSO CoC, the odds of getting an amendment to the source article in the current climate is slim. I also have concerns with how undefined the term "public figure" is.
- On deceased people: I agree that the legal considerations of BLP don't apply upon death, but this is a moral consideration; if Laverne Cox dropped dead now, I think it would be perverse to have people circling like vultures in 2025 to add the name once the two-year limit is up. I think just letting BDP hold here, as vague as it is is a better idea.
- Additionally, I think these two points is essentially re-arguing for positions that have been recently rejected at RfC and I would like to see more consensus before these are added. Also, I think the operative word on inclusion of deadnames should be, well, should; I think the exemptions in these areas should be implied and require justification if needed (as part of the BRD cycle or whatever else). Sceptre (talk) 00:42, 28 July 2023 (UTC)
TNT on GENDERID draft #4
- Incorporated some word improvements from SideSwipe9th and SMcCandlish
- Changed
Individuals who have clearly expressed their consent to share the name
toIndividuals who have made the name public post-transition
. The wording here could still be improved, but shouldn't be over-prescriptive. - Changed
where multiple reliable independent sources have documented the name
towhere multiple reliable and neutral sources have documented the name
in #3 and #4. I could be convinced that "high-quality" could go here instead of "neutral", but I think this will get the most agreement from the wider community. "Neutral" focuses on excluding low-quality sources and is better defined. - Expanded second footnote to include Wikimedia Foundation's resolution.
If local consensus is in agreement, I think this change is ready to go on the MOS.
Proposed MOS:GID section draft #4 |
|---|
|
Refer to any person whose gender might be unclear with the name and gendered words (e.g. pronouns, waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources. A transgender or non-binary person's former name (deadname) should be considered a matter of personal privacy and removed,[a] with the exception of:
Unless the individual meets one of the exceptions, the former name should not be used in lists, redirects, disambiguation pages, category names, etc., even in quotations, even if a reliable source exists.[b] When the individual meets one of the exceptions, the former name must not be given undue weight or overemphasis, and editors should err on the side of excluding it. Former names are not automatically of encyclopedic value. The former name of a transgender or non-binary person may be placed later in the lead or elsewhere in the article instead of the first sentence, to avoid giving it undue prominence. Articles or other works that were published under a pre-transition name may use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnote. When the individual does not meet one of the exceptions, avoid confusing constructions (Jane Doe fathered a child) by rewriting (e.g., Jane Doe became a parent). If the former name appears in a quotation, the article may need to paraphrase, elide, or use square brackets to replace portions of quotations to avoid deadnaming or misgendering. Do not replace or supplement a person's former name with a current name if the two names have not been publicly connected and connecting them would out the person. In rare cases where exact wording cannot be avoided (e.g. pun, rhyme, album cover), the quotation or work may be included.
|
Cuñado ☼ - Talk 17:02, 1 August 2023 (UTC)
- I'm going to once again echo sideswipe and say that proposing another assortment of changes to the MOS is, without a doubt, not going to result in a consensus. we need to go through the previous rfcs to find the sticking points and address them. other editors have agreed with this as well. Tekrmn (talk) 17:55, 1 August 2023 (UTC)
- I'd like to see some examples of how this would be applied as opposed to the present language. One example might be, let us say the person who perpetrated the 2023 Nashville school shooting. Unless I'm missing something, the shooter did not make the name public post-transition, was not a public figure, was not notable prior to the shooting (which the article states was post-transition), and has not been dead two years. Would then that name be excluded, and face the need to gain consensus for addition after two years? If so, is this a different outcome than under the present state of the MOS? Wehwalt (talk) 18:01, 1 August 2023 (UTC)
- In my assessment, that person's former name would not be mentioned in the article until two years after death, when BDP no longer applies, then its inclusion would be based on the "multiple reliable and neutral sources", which is a higher bar than normal content inclusion. Cuñado ☼ - Talk 18:32, 1 August 2023 (UTC)
- At present, it is mentioned. Is that in accordance with the MoS as it presently stands? Wehwalt (talk) 18:45, 1 August 2023 (UTC)
- Assuming you mean before BilledMammal's recent attempt, then yes it is. WP:BDP leaves it up to editorial consensus. Cuñado ☼ - Talk 21:35, 1 August 2023 (UTC)
- I disagree with point #4. IMO, it should say
Deceased individuals, where multiple reliable and neutral sources have documented the name
. Editors shouldn't have to wait at least two years to include a notable former name of a recently deceased individual. That just seems like delaying the inclusion of encyclopedic information for the sake of delaying. Some1 (talk) 23:13, 1 August 2023 (UTC)- Some1, the two years is a reference to WP:BDP:
the policy can extend based on editorial consensus for an indeterminate period beyond the date of death—six months, one year, two years at the outside
. If we say "Deceased individuals, where..." then it would become a range of time case-by-case based on consensus. The suggetion here is to default to the maximum privacy range of two years in the special case of former transgender names, so it isn't re-hashed on every page. With that background, do you still think it should change? Cuñado ☼ - Talk 23:55, 1 August 2023 (UTC)- Based on the answer to Wehwalt's question above, leaving things up to editorial consensus is better than
default[ing] to the maximum privacy range of two years
. Personally, I don't think a re-write is needed; MOS:GENDERID as it presently stands is fine as is. Adding a sentence about living transgender and non-binary people who are open about their former names/who have made the name public post-transition would be a nice addition to the MOS though. Some1 (talk) 00:40, 2 August 2023 (UTC)
- Based on the answer to Wehwalt's question above, leaving things up to editorial consensus is better than
- Some1, the two years is a reference to WP:BDP:
- I disagree with point #4. IMO, it should say
- Assuming you mean before BilledMammal's recent attempt, then yes it is. WP:BDP leaves it up to editorial consensus. Cuñado ☼ - Talk 21:35, 1 August 2023 (UTC)
- At present, it is mentioned. Is that in accordance with the MoS as it presently stands? Wehwalt (talk) 18:45, 1 August 2023 (UTC)
- In my assessment, that person's former name would not be mentioned in the article until two years after death, when BDP no longer applies, then its inclusion would be based on the "multiple reliable and neutral sources", which is a higher bar than normal content inclusion. Cuñado ☼ - Talk 18:32, 1 August 2023 (UTC)
- I suggest changing the introductory sentence to
Refer to any person who is transgender or non-binary, or whose gender might be unclear...
Otherwise, the implication is that all trans/nb individuals have an unclear gender, which I don't think is the intention. - The
became a parent
has always annoyed me, as it feels very awkward. I suggesthad a child
as the more natural recommended text.--Trystan (talk) 19:02, 1 August 2023 (UTC)- "Had a child" could be misleading. That expression (in the singular) generally refers to a biological female giving birth, rarely someone fathering a child. In the example "Jane Doe had a child" strongly suggests that Jane gave birth to a child, which presumably is wrong, in the context of the example. Mitch Ames (talk) 23:46, 1 August 2023 (UTC)
- I'm open to alternative formulations, or removing the example entirely. My dislike of the wording is that it recommends replacing weird drafting with weird drafting. It implies that writing about trans people will be more problematic than it is, because it places an undue emphasis on biology in a way we don't for cis people. I don't think an article would be likely to say
Sean Connery fathered a child
orSean Connery became a parent
, but it could well saySean Connery had one son
, without any implication of him giving birth.--Trystan (talk) 16:45, 2 August 2023 (UTC)
- I'm open to alternative formulations, or removing the example entirely. My dislike of the wording is that it recommends replacing weird drafting with weird drafting. It implies that writing about trans people will be more problematic than it is, because it places an undue emphasis on biology in a way we don't for cis people. I don't think an article would be likely to say
- "Had a child" could be misleading. That expression (in the singular) generally refers to a biological female giving birth, rarely someone fathering a child. In the example "Jane Doe had a child" strongly suggests that Jane gave birth to a child, which presumably is wrong, in the context of the example. Mitch Ames (talk) 23:46, 1 August 2023 (UTC)
- I still think there are problems with how the exemptions are written. The way it naturally reads is that all four exemptions are equivalent, while in reality they are not. I don't think there is any concerns with the first two (notable prior to transition or self-declared). However, the others are not as clear cut. As I mentioned before, we do not have a good definition of a public figure (as who is or is not a "public figure" is based on a specific moment of time, while we are an encyclopedia), and second, I believe there remains a tension in the fourth exemption between names are not "automatically of encyclopedic value" and well, after two years, our tolerance for "contentious or questionable material" eases so editors who may be eager to expose the deadname can find a source or sources to connect the individual to a non-notable past. So, my preference is closer to a two tiered approach to the exemption - a blanket exemption for the first two categories and a strong "May be exempted" (or similar language) for the other categories. --Enos733 (talk) 21:19, 1 August 2023 (UTC)
Edit - I changed the fourth exception in the proposal to Deceased individuals, where...
. I think it was actually in the interests of people trying to exclude former names, but it was perceived as the opposite. Now the privacy provided to living individuals extending after death would range from 2 months to 2 years depending on the case and consensus. Cuñado ☼ - Talk 15:25, 2 August 2023 (UTC)
- I agree that it was in the interests of exclusion on paper, but IMO including an explicit time limit like that invites attempts to game the system. One particular one I could easily see is the mentions of "individuals" being implicitly read as living individuals only, which would put deceased individuals as having no protections until two years after their death. (I don't think this argument would win a discussion but I definitely anticipate it being tried.) Loki (talk) 19:47, 2 August 2023 (UTC)
Loki's proposed draft
Some of the discussion on the previous drafts appears to be going in circles. Repeated objections to the third and fourth points have not been reflected in previous drafts. So, I've written my own draft with some of the changes that have been repeatedly proposed, as well as fixing some other weaknesses I noticed in previous drafts:
Proposed MOS:GID section draft #5 |
|---|
|
Refer to any person whose gender might be unclear with the name and gendered words (e.g. pronouns, waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources. A transgender or non-binary person's former name (deadname) should be considered a matter of personal privacy and removed,[a] with the exception of:
When the individual was notable prior to transition, the former name of a transgender or non-binary person should be included somewhere in the lead of their article to avoid confusion from readers who are unaware of the individual's transition. Usually it should be included in the first sentence, but in some cases where the risk of confusion is low, it may be placed later in the lead or elsewhere in the article, to avoid giving it undue prominence. After this one time, it should not be mentioned again. When the individual has consented to have their prior name disseminated, or a deceased individual's name has been included in multiple reliable sources, it can be mentioned in the same situations that any other name could be. However, be aware that former names are not automatically of encyclopedic value, and therefore the name still should only be included if there is a compelling reason to do so. Do not give the former name undue weight or overemphasis. If the appropriate weight is ambiguous, lean on the side of mentioning it as infrequently as possible, up to and including not mentioning it at all. In either case where an exception applies, articles or other works that were published under a pre-transition name may use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnotes. When the individual does not meet one of the exceptions, the former name should not be used in lists, redirects, disambiguation pages, category names, etc., even in quotations, even if a reliable source exists.[c] Avoid confusing constructions (Jane Doe fathered a child) by rewriting (e.g., Jane Doe became a parent). If the former name appears in a quotation, the article may need to paraphrase, elide, or use square brackets to replace portions of quotations to avoid deadnaming or misgendering. Do not replace or supplement a person's former name with a current name if the two names have not been publicly connected and connecting them would out the person. In rare cases where exact wording cannot be avoided (e.g. pun, rhyme, album cover), the quotation or work may be included.
|
Specifically, I've:
- Rephrased the second bullet: "making the name public" is IMO not a good description of what we mean here.
- Deleted the previous third bullet about public figures. IMO it's redundant with the first one, so the only practical effect would be to incorporate the significant issues around defining a "public figure".
- Deleted the two-year requirement on what had been the fourth bullet about deceased individuals, as the consensus arrived at for deceased individuals in the previous RFC did not refer to any such time limit, and there were significantly more objections to such a time limit than support.
- Significantly rephrased the sourcing requirement on the bullet about deceased individuals to pull in an editorial judgement requirement, and added a footnote explaining further.
- Added some extra explanatory text in the previously second footnote.
- Broke the paragraph about what to do if an exception applies into separate paragraphs about the notability exception and the other exceptions. These exceptions are not really parallel, as they're motivated by entirely different concerns: the notability exception is a real exception to a strong privacy concern motivated by a specific strong encyclopedic need, while the other two exceptions instead establish any privacy concern that still exists is not very strong. The previous paragraph as worded would have, oddly, made the notability exception a lot stricter than it had been, as it encouraged exclusion of the name entirely.
- Moved the paragraphs about if the exception does not apply nearer to each other, just for flow reasons.
Loki (talk) 05:33, 2 August 2023 (UTC)
- I think the issue of public figures is misunderstood here. I applied BLPPRIVACY to this guide, and there is a privacy exemption for public figures. This is not the place to debate whether BLPPRIVACY is correct, and it's not the place to make policy. The brief discussion at BLP was misrepresented on this talk to suggest that it's a questionable phrase. Cuñado ☼ - Talk 15:31, 2 August 2023 (UTC)
- Respectfully, I think you misunderstand the problem with the public figure question as it applies to BLPPRIVACY. For our project, an individual is either meets our notability guidelines and may have a page written about them (or not). We look at individuals over the context of their entire life (and, potentially, their legacy after their death). A public figure, by contrast, is a momentary thing. Someone may or may not be a public figure at particular moments of time (as recognized in the last paragraph of the essay on Who is a low-profile individual). So, even if we could agree on whether an individual is (or who is not) a public figure (which could be subject to walls of text), we should not explicitly state that once a public figure all verifiable aspects of one's life are now encyclopedic (as Loki mentions in the footnotes to the draft). So, all I see with the public figure exemption is a loophole to drive a truck through since it could be argued that many, if not most, individuals we consider notable could be public figures (See most elected and appointed officials, entertainers, athletes, journalists, business owners, influencers...). - Enos733 (talk) 16:00, 2 August 2023 (UTC)
- Respectfully, I think you're missing the point as well. Someone who seeks public attention has a different level of personal privacy protection under BLP.
In the case of public figures... BLPs should simply document what these sources say
,there are additional protections for subjects who are not public figures
, andnames of family members who are not also notable public figures must be removed from an article if they are not properly sourced
. Without BLP, we would always include former names if properly sourced. Because of BLP, we require a higher bar for inclusion. The justification for removing the former name is for personal privacy, and we can't use the MOS to create a more restrictive policy. An elected official is a public figure, and if they have a former name that is documented in numerous reliable and neutral sources, it should be on Wikipedia. Cuñado ☼ - Talk 16:45, 2 August 2023 (UTC)- I agree that people who are high-profile individuals have a different level of personal privacy. That said, people may be high-profile individuals at certain parts of their lives. An athlete may be a high-profile figure during their peak playing years and a low-profile individual at other times. Recognizing that once notable = always notable under our policies and guidelines, it is not equally logical to say that once a public figure = always a public figure. But creating an explicit exemption means that once a public figure = always a public figure in terns of what material may be included. - Enos733 (talk) 18:36, 2 August 2023 (UTC)
- Do you have an example? I can't think of how this could be a problem. Cuñado ☼ - Talk 18:50, 2 August 2023 (UTC)
- Imagine a CEO of a large Fortune 500 company who transitioned before becoming notable. Ostensibly a public figure, with lots of influence, the individual does not want their deadname (or even their transition) to become public. Under your draft, the name can be shared when "multiple reliable and neutral sources have documented the name." As Loki mentions in the footnotes, an editor who knows and wants the deadname to become widely known can search for the deadname and find a couple local stories, perhaps as a child the CEO won a spelling bee and was in the local paper, and because there were a couple reliable sources, the name is now able to be added to the CEO's page. - Enos733 (talk) 21:58, 2 August 2023 (UTC)
Do you have an example?
Consider pretty much any actor who retires. During their career, when they are appearing in film or television frequently, or press junkets promoting their latest production, they are unquestionably public figures. But after they retire, unless they stay otherwise active in public life by transitioning to another role, they stop being public figures. Sure you might hear from them once every so often, typically when one of their well loved productions has an anniversary, sequel, or reboot, but are they still a public figure when they're living quietly at home?- For an actual example, consider Peter Ostrum. In 1971 he starred as Charlie Bucket in Willy Wonka & the Chocolate Factory. After that, he retired, and as our article states in the lead "became reluctant to speak about his one starring role". Was Ostrum a public figure in 1971, when the film was released? Absolutely. Was he a pubic figure after that when he became a veterinarian however, or got married? No. Aside from some interviews over the years, and giving an annual speech at a non-notable school in New York state, he largely seems to stay out of public life. Or consider John Deacon. Between 1971 and 1991 Deacon was a member of Queen, writing many songs for the band, and appearing at countless concerts and music venues. After the death of Freddie Mercury however, Deacon started to withdraw from public life, before retiring from the music industry in 1997. Since then, aside from giving a couple of interviews, Deacon has avoided publicity. Was he a public figure during his decades with Queen? Yes. But since retiring? No, very clearly no.
- Being a public figure is not a once-and-done thing. The WP:LOWPROFILE essay, as limited as it is on an actual clear definition, states clearly in the last section that the high/low profile status of an individual changes over time. BLPPRIVACY and BLPPUBLIC likewise adapt over time, with respect to a person's status. A person who becomes a public figure has the same reasonable expectation of privacy up until the point at which they become one as any other low profile individual. Likewise a person who was one and ceases to be one, has the same expectation of privacy after the point at which they retire from public life. However, even when one is a public figure, there are still aspects of their personal life that they have (or should have, tabloids notwithstanding) a reasonable expectation of privacy over. Sideswipe9th (talk) 23:58, 2 August 2023 (UTC)
- Do you have an example? I can't think of how this could be a problem. Cuñado ☼ - Talk 18:50, 2 August 2023 (UTC)
- I agree that people who are high-profile individuals have a different level of personal privacy. That said, people may be high-profile individuals at certain parts of their lives. An athlete may be a high-profile figure during their peak playing years and a low-profile individual at other times. Recognizing that once notable = always notable under our policies and guidelines, it is not equally logical to say that once a public figure = always a public figure. But creating an explicit exemption means that once a public figure = always a public figure in terns of what material may be included. - Enos733 (talk) 18:36, 2 August 2023 (UTC)
- Respectfully, I think you're missing the point as well. Someone who seeks public attention has a different level of personal privacy protection under BLP.
- I don't see anything in WP:BLPPRIVACY or WP:PUBLICFIGURE that would mean a former name of a public figure is automatically not a privacy concern (even if we can source it). Would we publish the address of a public figure, even if sourceable, simply because they're a public figure? Obviously not (and in fact WP:BLPPRIVACY specifically instructs otherwise).
- The exception, as I read it, is for current full names that
have been widely published by reliable sources
, not former names (and this guidance isn't specific to public figures either). There's no instruction about former names other than the instruction for miscellaneous personal info (which is to say, it should be removed). Loki (talk) 19:36, 2 August 2023 (UTC)
- Respectfully, I think you misunderstand the problem with the public figure question as it applies to BLPPRIVACY. For our project, an individual is either meets our notability guidelines and may have a page written about them (or not). We look at individuals over the context of their entire life (and, potentially, their legacy after their death). A public figure, by contrast, is a momentary thing. Someone may or may not be a public figure at particular moments of time (as recognized in the last paragraph of the essay on Who is a low-profile individual). So, even if we could agree on whether an individual is (or who is not) a public figure (which could be subject to walls of text), we should not explicitly state that once a public figure all verifiable aspects of one's life are now encyclopedic (as Loki mentions in the footnotes to the draft). So, all I see with the public figure exemption is a loophole to drive a truck through since it could be argued that many, if not most, individuals we consider notable could be public figures (See most elected and appointed officials, entertainers, athletes, journalists, business owners, influencers...). - Enos733 (talk) 16:00, 2 August 2023 (UTC)
- So, on the whole I think this is definitely more solid than the other drafts we've seen so far. There's a few bits though where I think some clarification and tweaks would be helpful.
- On exemption 3, what does
exercised some editorial judgement, however slight
actually mean in practice? How do you define a source that has exercised editorial judgement? Is this something as general as the source publication having an editorial policy and team, or is it something else entirely? Do you have any examples of this in practice so we could see what it looks like? - In paragraph 3 the proposal states
When the individual has consented to have their prior name disseminated
. I'm concerned that this doesn't properly differentiate between someone who acknowledged their former name once or twice when first coming out, and someone who later distanced themselves or otherwise refused to acknowledge their former name. Would this not lead to the inclusion of deadnames that we currently exclude because they were not notable under that name, like for example Nicole Maines (see this November 2020 RfC for why we currently exclude the name)? Or are we seriously considering consent for dissemination a one-and-done thing that cannot be revoked at a later date? - In paragraph 4, the proposal states
articles or other works that were published under a pre-transition name may use their current name as the primary name...
. Is that not softer than the current guideline? The current guideline text is a lot more definitive, use their current name unless they prefer to be credited under their former name for past events. The implication that I get from the text in the proposal is that using their current name is optional in all cases, whereas the current text is optional if the person prefers it. To better fit with the current text, I think this would be better phrased as something likearticles or other works that were published under a pre-transition name should use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnotes, unless they prefer their former name be used for past events
(changes in italics). Sideswipe9th (talk) 20:55, 2 August 2023 (UTC)- For exemption 3, I mean basically the same thing as WP:BLPPRIMARY means. Honestly, I probably should replace it; I just wasn't aware of it at the time of writing the draft. (My one remaining qualm is that it's a BLP policy and this is explicitly about dead people.)
- For paragraph 3, I'm not sure of the distinction you're trying to get at. Reading the RFC, it seems the supporters are trying to argue that Maines' former name should be used because she has said it publicly, which is the exact distinction between "made public" and "consented to have disseminated" that I'm trying to get at with the wording change.
- For paragraph 4, I was just copying over Cuñado's wording. I'm fine with that amendment. Loki (talk) 23:34, 2 August 2023 (UTC)
- On exemption 3, you could maybe replace it with some sort of reference to WP:NOR#Primary for deceased individuals. A court transcript, or some sort of public governmental record is no more or less a primary source whether the person is alive or dead. I'll reserve judgement until I can see your replacement, but I would urge some sort of consideration towards source quality here, as well as source quantity when you're redrafting. The first of the two recent RfCs mentions concerns about both source volume and source quality in its closure.
- On paragraph 3, the distinction is I'm trying for is, is the consent for dissemination something that's done once and is otherwise irrevocable? Or is it something that can be withdrawn in the future? If a person gave an interview shortly after coming out saying something like "my former name is X", but at some point after that interview being published they withdrew that consent and otherwise never acknowledged the former name, would we still include it? If they contacted the original source publisher, and the publisher agreed to remove it because they no longer consented to it being disseminated, would we not include it?
- I guess I'm deeply uncomfortable with this new inclusion criteria, because it would result in the inclusion of the deadnames of many trans people that we currently exclude for privacy concerns, as they changed their names prior to becoming notable. With the exception of rare cases, like Sarah Ashton-Cirillo or Caitlyn Jenner, who are pretty open about their former names, most trans and non-binary people are not. Deadnaming, as the article lays out, is generally regarded as harmful, and most trans or non-binary people do not ever wish their former names to be known or mentioned. I would honestly see a change along these lines as a step backwards, as it would allow for the routine inclusion of names that, for the most part, our article subjects do not wish known. I'm reminded of what Laverne Cox said in 2019 when she remarked on IMDB including her deadname prior to changing their policies; "the ultimate insult", yet any of the changes presented so far by Tamzin, Cuñado, or yourself, would allow for us to start including her former name. That is something that, until this set of TNT proposals, I'm not sure the community has even discussed anywhere, let alone recently. Sideswipe9th (talk) 00:29, 3 August 2023 (UTC)
- After this one time, it should not be mentioned again. There is no consensus on how often a former name can or should be mentioned, so that sentence should be removed. And if the person was notable prior to transition, the former name should be in the lead sentence and bolded, as the MOS currently advises, not floating around somewhere in the lead unbolded.
- The third paragraph wiki-links to WP:WEIGHT twice... I would simplify that paragraph to say
When the individual has consented to have their prior name disseminated, or a deceased individual's name has been included in multiple reliable sources, it can be mentioned in the same situations that any other name could be. However, former names are not automatically of encyclopedic value, and should not be given undue weight or overemphasis. If the appropriate weight is ambiguous, lean on the side of mentioning the name as infrequently as possible.
- I would change "have said post-transition" to "expressed post-transition". I would get rid of the first sentence from footnote B as I don't think it's necessary to single out books and newspapers; 'reliable sources' is already mentioned. I would also remove the first sentence from footnote C since that seems more like an opinion rather than a fact. Some1 (talk) 23:56, 2 August 2023 (UTC)
- Also strongly disagree with
After this one time, it should not be mentioned again
as it's in clear violation of how leads are supposed to work. There should not be content in the lead that is not also contained in the article body, and this goes for names as well. Elli (talk | contribs) 01:23, 3 August 2023 (UTC)- Yes. And there's weird wording in some places, like "avoid confusion from readers" (try "avoid confusing readers"), etc. — SMcCandlish ☏ ¢ 😼 02:02, 3 August 2023 (UTC)
should not be mentioned again
is very clearly how the guideline works now, so no, I'm not removing that. You'd need a strong consensus of editors to overturn that. Mentioning the former name only in the lead is how every article about a trans person notable before transition on Wikipedia is currently worded. See for instance Chelsea Manning, whose deadname we mention once in the lead and thereafter only in quotes, or The Wachowskis, whose deadnames are mentioned in the lead and thereafter only in quotes.- It's also required by the current text, which starts out by insisting that we refer to any person by their most recently expressed name and pronouns, before adding an exception in the case of trans people who were notable before transition which only applies to the first sentence of the lead of the article about them. The general rule applies after we're done with the mention required by the exception, so after that point we can only use the name and pronouns they prefer. Loki (talk) 04:23, 3 August 2023 (UTC)
is very clearly how the guideline works now
The current MOS doesn't require that a former name be mentioned once, only in the lead. For example, Caitlyn Jenner and Elliot Page's former names are included in the lead, but also in the Early life section of their respective articles. At least for deceased trans or nonbinary people, there's no consensus for including language about how often a former name can/should be used, see the RfC from two months ago. https://en.wikipedia.org/w/index.php?oldid=1158982243#Topic_3:_How_often_to_mention_deadnames?_(MOS:GENDERID_3rd_paragraph*) Some1 (talk) 11:33, 3 August 2023 (UTC)
- Also strongly disagree with
Use of "Rabbi"
Should "Rabbi" be used in running text (here, for example)? Or just the individual's surname, as is the norm? I strongly assume it's the latter and that the recommended action is to remove "Rabbi", just wanted to confirm and check to see if there's been any discussion regarding this already. Mooonswimmer 17:05, 15 July 2023 (UTC)
- MOS:REVEREND says no to "Rabbi". "In general, honorific prefixes ... should not be included... In particular, this applies to: ... styles and honorifics related to ... clergy ..." Mitch Ames (talk) 03:59, 16 July 2023 (UTC)
- Yep. — SMcCandlish ☏ ¢ 😼 22:46, 23 July 2023 (UTC)
- I'm not convinced that MOS is intended to cover the case of "Rabbi". "Rabbi" is not like "Her Majesty" or "The Reverend" or similar two word titles; it's a lot more like "Doctor". Furthermore that section links to a part of the MOS specifically about Christian clergy.
- That being said, I agree that the overall rule not to use honorifics in running text applies here. I just disagree that that specific section, which says honorifics for clergy should not be used at all, applies to rabbis. Loki (talk) 02:17, 5 August 2023 (UTC)
- So MOS:DOCTOR or MOS:SURNAME, instead of MOS:REVEREND. Mitch Ames (talk) 03:31, 5 August 2023 (UTC)
- Why do you think that rabbis are exempt from a guideline that applies to clergy? It's like "Father", "Pastor", and "Reverend" without the "the". And we don't use "Doctor" either. What the word is unfortunately linked to doesn't override what the guidelines says and isn't an indication that Wikipedia has special rules that applied to Christian clergy only. Why would it? Largoplazo (talk) 10:53, 5 August 2023 (UTC)
- Yeah, MoS would definitely not intend something to apply to clergy of a particular religion only. If the material needs to be adjusted to include titles like rabbi and imam then let's do it and put this to rest. — SMcCandlish ☏ ¢ 😼 13:33, 5 August 2023 (UTC)
- I think it is exactly like any of those honorifics considering it is capitalized. Uncapitalized though, I get a little vague. "According to rabbi [first] [last]" seems a bit like "according to engineer [first] [last]" or "according to philosopher [first] [last]". —DIYeditor (talk) 13:54, 5 August 2023 (UTC)
- Sure; there are times also that mentioning someone is a doctor or professor or pastor is also contextually relevant. — SMcCandlish ☏ ¢ 😼 14:06, 5 August 2023 (UTC)
- Yep. — SMcCandlish ☏ ¢ 😼 22:46, 23 July 2023 (UTC)
WP:BOLD restrictions on the use of deceased transgender or non-binary persons birth name or former name
I've WP:BOLDly added the following to MOS:DEADNAME:
For deceased transgender or non-binary persons, their birth name or former name (professional name, stage name, or pseudonym) should be included in the lead sentence of their main biographical article only if the name is documented in multiple high quality reliable and secondary sources containing significant coverage of the person.
I understand that some editors will want stricter restrictions than this, and I understand that some editors will want looser restrictions than this. However, I believe the former group will consider this an improvement over the status quo, and I believe the latter group will recognize that if this went to RfC it would get consensus.
Hopefully, this is an acceptable compromise that will allow us to avoid yet another RfC, at least for now. BilledMammal (talk) 05:03, 20 July 2023 (UTC)
- Is there precedence including the wording " "high quality" reliable sources"? I mean, reliable sources are reliable or not. I don't know since when not including the birth name of a notable person who is an article is considered a good encyclopedic practice. Maybe it is actually a thing and I simply don't know about it. But why only give this exception to transgender or non-binary? I think if anything such guidance should be for everyone if it is good guidance. Regards, Thinker78 (talk) 05:16, 20 July 2023 (UTC)
- There is absolutely a quality level difference in reliable sources, despite them being reliable in general. On the side of news, the Daily Dot is nowhere near the level of the New York Times. Significant coverage of a topic in the latter is worth far more than the former. SilverserenC 05:20, 20 July 2023 (UTC)
- There is no consensus in the reliability of the Daily Dot, actually. Although there are some sources considered high-quality, a source in general is considered reliable or not. It can be high-quality in some contexts but not considered reliable in others, as in WP:MEDRS. Regards, Thinker78 (talk) 05:30, 20 July 2023 (UTC)
- We definitely don't want to include this merely because someone finds the name recorded in a library catalog entry or something like that. It should be central to the notability of the subject, not merely incidental. In that sense, I support the spirit of BilledMammal's attempt. But I strongly oppose pushing GNG-based definitions of SIGCOV into non-GNG parts of our guidelines. We should use that only where it is appropriate in some (not all!) notability guidelines. More general wording like "central to the notability of the subject" would be a better way to go here. —David Eppstein (talk) 05:21, 20 July 2023 (UTC)
central to the notability of the subject
The issue with that is I'm not certain what it means; at least WP:SIGCOV is somewhat well understood. BilledMammal (talk) 05:24, 20 July 2023 (UTC)- I disagree. SIGCOV means whatever the people arguing at AfDs want it to mean. Often it means "I want to include this subject so I will count this churnalism consisting of a press release with the serial numbers filed off as SIGCOV" or "I don't want to include children's fantasy novels so I will rewrite SIGCOV to disallow the sorts of content that are typically included in reviews of those novels so that I can argue that they do not have SIGCOV". It is too politicized and too frequently gamed in ways that have nothing to do with what we want here. —David Eppstein (talk) 05:33, 20 July 2023 (UTC)
- I know there have been very extensive discussions about this gender topic but I still fail to understand how come in an encyclopedia the transitioning of a person is not a major piece of information to be included, and that includes their former names. I am not very versed in trans philosophy but I am guessing it is an issue of privacy. Usually that's the realm of living people though. What's the rationale about providing extra limitations for alternative names of trans and non-binary deceased people exclusively? Regards, Thinker78 (talk) 05:43, 20 July 2023 (UTC)
- I would interpret "high quality reliable sources" as being limited to WP:GREL sources; "reliable sources" would include WP:MREL sources.
I think if anything such guidance should be for everyone if it is good guidance.
Personally, I would have no objection to expanding this to all bios; if reliable sources don't consider a name relevant, why should we? BilledMammal (talk) 05:24, 20 July 2023 (UTC)- You are moving the goalposts. "Reliable sources" and "SIGCOV" are not the same thing. A source can be reliable despite being non-independent of the subject, or despite only sourcing one small factoid above the subject. (I would argue that, in cases where the factoid can only be sourced in this way, it is not particularly central to the notability of the subject. But for non-controversial information (not deadnames) these non-central claims can still be helpful in building out an article to a more complete length. —David Eppstein (talk) 05:36, 20 July 2023 (UTC)
- This response was to Thinker78's comment where they said
Is there precedence including the wording " "high quality" reliable sources"? I mean, reliable sources are reliable or not.
My understanding of their comment was that it was focused on a different aspect of the paragraph than what your comment was focused on; if I misunderstood their comment I apologize, but I am certainly not moving any goalposts. BilledMammal (talk) 05:39, 20 July 2023 (UTC)
- This response was to Thinker78's comment where they said
- Sounds reasonable. Regards, Thinker78 (talk) 05:56, 20 July 2023 (UTC)
- You are moving the goalposts. "Reliable sources" and "SIGCOV" are not the same thing. A source can be reliable despite being non-independent of the subject, or despite only sourcing one small factoid above the subject. (I would argue that, in cases where the factoid can only be sourced in this way, it is not particularly central to the notability of the subject. But for non-controversial information (not deadnames) these non-central claims can still be helpful in building out an article to a more complete length. —David Eppstein (talk) 05:36, 20 July 2023 (UTC)
- There is absolutely a quality level difference in reliable sources, despite them being reliable in general. On the side of news, the Daily Dot is nowhere near the level of the New York Times. Significant coverage of a topic in the latter is worth far more than the former. SilverserenC 05:20, 20 July 2023 (UTC)
Second version
David Eppstein has now reverted, saying Some restriction like this may be appropriate but pushing your SIGCOV-fetish into MOS goes too far
.
To try to address this, I've changed the wording to:
For deceased transgender or non-binary persons, their birth name or former name (professional name, stage name, or pseudonym) should be included in the lead sentence of their main biographical article only if the name is documented in multiple high quality reliable and secondary sources containing non-trivial coverage of the person.
This still requires that the source contains more than a passing mention, but it omits the reference to SIGCOV that David found so objectionable. BilledMammal (talk) 05:26, 20 July 2023 (UTC)
- As said above, I agree with the spirit of your proposal: we should only include deadnames if we have some evidence that they are a significant part of the biography, not just something incidental that we happen to find barely-adequate sourcing for. What I am opposed to is not that, but the way you worded it in terms of something that properly belongs only in our notability guidelines. This is better, but I'm still concerned: we have some classes of people (for instance academics) for whom notability does not rely on the existence of high-quality reliable secondary sources containing non-trivial coverage of those people. If such a person happens to be transgender (I know of multiple notable examples, not all of whom say anything about that in the article) are we to be entirely forbidden from mentioning it? Even if, for instance, much of their academic publication record happens to be under their deadname? In that case it would, I think, be central to their notability, but in a way different from the sort of sourcing you are imagining to exist, which might not exist at all. —David Eppstein (talk) 05:31, 20 July 2023 (UTC)
- WP:NACADEMIC is not a guideline that I have a good understanding of; JoelleJay, I understand you do have a very strong understanding of it. Perhaps you could comment on how this would interact with that guideline and, if you agree it would interact as David describes, recommend changes to address that? BilledMammal (talk) 05:44, 20 July 2023 (UTC)
- I think David's point about academics not receiving the type of biographical significant coverage that would provide sourcing on a trans person's birth name is accurate (and perhaps he should have participated in the aforementioned RfCs and in the ones that decided deadnames can never be mentioned in living transpeople's articles if they weren't notable pre-transition). However, I would argue that in cases where
much of their academic publication record happens to be under their deadname
, our guidance already licenses mentioning the deadname because the individual's notability is unlikely to be derived wholly from post-transition publication. In most NPROF evaluations, notability is far more a cumulative measure than what we use in any other guideline; in my opinion, if someone could not have established an NPROF pass without pre-transition publications, the deadname is DUE even if they wouldn't have met notability criteria before adopting their new name. But if their publication record was strong enough to pass NPROF post-transition and it was too weak to pass pre-transition, then exclusion of the name may be warranted according to the RfC close. JoelleJay (talk) 06:05, 20 July 2023 (UTC)- As an example, I don't think we mention Lynn Conway's deadname (although she certainly passes GNG as well as PROF), because her most significant publications were post-transition. Another class of subjects who do have significant coverage, but about their works and less commonly about their personal lives, is book authors. If we think someone is notable per WP:AUTHOR, because they have in-depth published reviews of their books, we should still probably not use a review that happens to mention a deadname as an excuse to include that deadname. On the other hand if many of their reviewed books were published under the deadname, then we probably should mention the deadname even if we don't have in-depth biographical coverage beyond the reviews. Again, what's important is that it's central to the notability of the subject, not what kind of sources we have. —David Eppstein (talk) 06:14, 20 July 2023 (UTC)
- Thank you both. Perhaps if we reworded the paragraph to:
For deceased transgender or non-binary persons, their birth name or former name (professional name, stage name, or pseudonym) should be included in the lead sentence of their main biographical article only if the name is documented in multiple high quality reliable and secondary sources containing non-trivial coverage of the person, or if the person published multiple reviewed works under the name.
- I'm not sure
multiple reviewed works
is the correct line to draw, but we can work on that; would anyone object to the general principle? BilledMammal (talk) 06:47, 20 July 2023 (UTC)
- As an example, I don't think we mention Lynn Conway's deadname (although she certainly passes GNG as well as PROF), because her most significant publications were post-transition. Another class of subjects who do have significant coverage, but about their works and less commonly about their personal lives, is book authors. If we think someone is notable per WP:AUTHOR, because they have in-depth published reviews of their books, we should still probably not use a review that happens to mention a deadname as an excuse to include that deadname. On the other hand if many of their reviewed books were published under the deadname, then we probably should mention the deadname even if we don't have in-depth biographical coverage beyond the reviews. Again, what's important is that it's central to the notability of the subject, not what kind of sources we have. —David Eppstein (talk) 06:14, 20 July 2023 (UTC)
- I think David's point about academics not receiving the type of biographical significant coverage that would provide sourcing on a trans person's birth name is accurate (and perhaps he should have participated in the aforementioned RfCs and in the ones that decided deadnames can never be mentioned in living transpeople's articles if they weren't notable pre-transition). However, I would argue that in cases where
much of their academic publication record happens to be under their deadname
So this is an interesting point. Many academic journals, such as everything published by Springer Nature, SAGE, Elsevier, Wiley, PLOS.one, now allow for names to be changed on previously published works without any corrections note being added to the paper. This is in line with the current COPE ethics guidance on name changes, which states that correction notices for name changesare not appropriate in all circumstances however, particularly in the case of transgender, non-binary, and/or gender diverse (hereafter shortened to “trans”) authors because of the potential trauma caused by the continued circulation of their previous names and the risks to which disclosure of their gender identity subjects them.
- Accordingly it is far more likely going forward that any academic who meets NACADEMIC for works published prior to their name change, that those works will only ever contain their current name. For the question of
If such a person happens to be transgender (I know of multiple notable examples, not all of whom say anything about that in the article) are we to be entirely forbidden from mentioning it?
I would ask back, how are we going to verify the name change through an academic's publication record if their publication record for the duration of their career only contains papers published in their current name, even for works published years or decades prior to changing it? Sideswipe9th (talk) 15:29, 20 July 2023 (UTC)- Let me give a hypothetical to better illustrate this. Lets say we have an academic who is currently called Jessie Smith after changing it some time in 2022/2023. Jessie has been publishing for the last ten or twenty years, primarily or exclusively in one or more of the journals I mentioned above. We have an article on Jessie because they meet NACADEMIC#1, and that article is in their former name. And we have no
high-quality reliable secondary sources containing non-trivial coverage
of Jessie . - At some point in 2023 after Jessie changed their name, they request that their previously published papers are updated with their new name. The journal(s) comply with the request per their name change policies and leave no record of Jessie's former name. As such every paper written by Jessie in the last ten or twenty years contains only Jessie's current name. How do we proceed? Jessie's former name is now unverifiable to the current version of the sources we previously used to verify their name (ie their publication record). If it's considered to be encyclopaedic interest that we include that person's former name, how do we do so in a way that does not breach WP:V given that all of the sources we could have used only contain Jessie's current name? Sideswipe9th (talk) 16:05, 20 July 2023 (UTC)
- You are missing something. We do not base academic notability on having publications. We base it, most commonly, on the impact of those publications, as measured for instance by citations. Those citations are in other works that are not going to retroactively cite the same publication under a different author name; they will use the name under which they found the publication. So new citations will go to the new name but old citations will remain under the old name. —David Eppstein (talk) 18:15, 20 July 2023 (UTC)
Those citations are in other works that are not going to retroactively cite the same publication under a different author name
That's not entirely true. If you check the policies I linked all of them cascade changes through DOI metadata to update citations in the works of other authors. Now if you're looking only at a print or PDF copy of the journal or paper, that was printed or generated at the time the paper was originally published or at any point prior to the name change, then that copy will obviously contain a citation to the person's former name. However if you're looking at the same journal or paper, either through the journal's website, or a PDF copy that is generated after the name change, then the citation in the paper will contain the new name only. Sideswipe9th (talk) 19:17, 20 July 2023 (UTC)
- You are missing something. We do not base academic notability on having publications. We base it, most commonly, on the impact of those publications, as measured for instance by citations. Those citations are in other works that are not going to retroactively cite the same publication under a different author name; they will use the name under which they found the publication. So new citations will go to the new name but old citations will remain under the old name. —David Eppstein (talk) 18:15, 20 July 2023 (UTC)
- Let me give a hypothetical to better illustrate this. Lets say we have an academic who is currently called Jessie Smith after changing it some time in 2022/2023. Jessie has been publishing for the last ten or twenty years, primarily or exclusively in one or more of the journals I mentioned above. We have an article on Jessie because they meet NACADEMIC#1, and that article is in their former name. And we have no
- WP:NACADEMIC is not a guideline that I have a good understanding of; JoelleJay, I understand you do have a very strong understanding of it. Perhaps you could comment on how this would interact with that guideline and, if you agree it would interact as David describes, recommend changes to address that? BilledMammal (talk) 05:44, 20 July 2023 (UTC)
- FWIW I prefer to WP:SIGCOV version to this version, but like both, with one caveat.
- I don't think we need to specifically address the situation of academics, and relatedly I feel like trying to carve out specific exceptions for every special notability guideline is a clear case of rules creep. Rather than either of these we should just incorporate the notability guideline we already use for living people, so:
For deceased transgender or non-binary persons, their birth name or former name (professional name, stage name, or pseudonym) should be included in the lead sentence of their main biographical article only if they were notable under their former name or if their former name is documented in multiple high quality reliable and secondary sources containing non-trivial coverage of the person.
- Almost all academics who published significantly under their deadname are going to be notable pre-transition. There may be a few exceptions who published only very insignificant works pre-transition, and in those cases I don't see why we'd need to mention the deadname. Loki (talk) 14:24, 20 July 2023 (UTC)
- So I have a different concern than what David has stated. I think saying
their birth or former name should be included in the lead sentence
(emphasis mine to highlight objectionable point) is too strong, in that it mandates inclusion if the criteria is met. The May/June RfC closed with a consensus thatthere is a consensus against using the former names of transgender or non-binary people, living or dead, except when of encyclopedic interest or when necessary to avoid confusion. Also, there is clear consensus that a former name is not automatically of encyclopedic interest.
andthe community believes that, for the most part, the prior name should not be used
. - Taking those points in mind, I would prefer if we tweak this to
may be included
, as this would still provide guidance for what the inclusion criteria is without mandating inclusion if that criteria is met. I realise this is different than what I suggested for the just closed June/July RfC, however for that version I felt as though the inclusion criteria was high enough on their own that they would cover this. Sideswipe9th (talk) 14:52, 20 July 2023 (UTC)- It's not
should be included
, it'sshould be included ... only if
. Or to rephrase,should only be included if
. - Also, honestly, the MOS should provide some positive guidance for when a former name should be included.
May be included
feels very much too weak to me. By the rejection of the "never" option in the previous RFC, we've already agreed that there are some cases where we should include a previous name. And if we're going to have those cases, I want to know what they are rather than having to argue about it every time. WP:IAR is still a thing for really extraordinary cases but I don't want to have significant ambiguity about the typical case. Loki (talk) 15:57, 20 July 2023 (UTC)- The current version is
should be included...only if [the conditions are met]
. In other words, we are mandating inclusion when condition is true. In programming language that isif (A == true || B == true) { /* include name /*} else { /* exclude name */ }. Even if we move the only earlier in the sentence, we are still mandating inclusion by sayingshould only be included if [conditions are met]
, because the emphasis is on the should and the conditions. It does not allow for a local consensus to form for exclusion of the name, if the conditions are otherwise met, short of invoking WP:IAR. - Conversely by saying
may be included...only if [the conditions are met]
we're not mandating inclusion. We're still providing the same set of positive inclusion criteria for when a previous name could be included, while also leaving it open within the letter of the guideline for local consensus to form around exclusion of the name should that be felt necessary based on the circumstances specific to each article. The only significant change is that we stop just short of mandating inclusion. In my mind, that isn't weaker, because the same criteria for inclusion must be met before a name can be included. It just allows for a little more editorial judgement on whether or not inclusion of the former name would or would not improve the article. Sideswipe9th (talk) 16:18, 20 July 2023 (UTC)- But I don't want more editorial judgement. What you're calling "editorial judgement" I call "content disputes". The clearer the guideline is about this, the less likely we will have a content dispute on the talk page every time this situation comes up.
- I'm not against arguing on the talk page; that's how Wikipedia works. But I am against arguing on the talk page for cases that should be trivial. Loki (talk) 16:42, 20 July 2023 (UTC)
- The current version is
- It's not
should be included in the lead sentence
IMO, notable deadnames of deceased trans people should be included in the lead, but non-notable deadnames of deceased trans people should be in the Early life section (if they have one). Some1 (talk) 18:55, 20 July 2023 (UTC)
- Yeah, on reflection I more or less agree with this. Maybe just delete the bit about where exactly to put it. Loki (talk) 21:06, 20 July 2023 (UTC)
- Now that I think about it more, BilledMammal's addition to the MOS as currently worded is actually pretty decent. Basically,
if the name is documented in multiple high-quality reliable and secondary sources containing non-trivial coverage of the person
then itshould be included in the lead sentence
. Any former names of deceased transgender or non-binary persons' that don't meet that criteria can still be included in the article, just not in the lead. That's my interpretation of that one sentence anyway. Some1 (talk) 22:49, 1 August 2023 (UTC)- FWIW, that's not how I interpret it nor the consensus that generated it. The way the equivalent guideline for living trans people has been interpreted is that you either include the name in the lead or you don't include it anywhere.
- Maybe the section does need a little rewrite, because I admit that's not super clear from just the text. Loki (talk) 04:05, 2 August 2023 (UTC)
- Now that I think about it more, BilledMammal's addition to the MOS as currently worded is actually pretty decent. Basically,
Second revert
SnowRise has now reverted this, saying I'm sorry BM, but 1) this is substantially the same language advanced at the recent WP:VPR discussion, with massive community input, that failed to gain consensus. And 2) GENDERID is about the last MoS section where WP:BOLD is well-advised, especially in these circumstances. Please wait a while and attempt another go at consensus if you wish, but this feels like an effort to back-door in non-consensus language, and feels borderline TE, IIAH.
- I'm not certain if I can address these by adjusting the proposal, but I hope I can convince you that they are inaccurate.
- For #1, I believe the language diverges significantly from the language used at the recent VPR proposal; the VPR proposal required extensive coverage of the name, an impossible standard, while this requires that the name be included in sources that focus on the subject.
- For #2, I am hoping that I can come up with a compromise that will let us proceed without needing further drama. Regarding the comment about
borderline TE
, I note that I strongly opposed the VPR proposal, on many grounds. I don't believe any of those grounds apply to this proposal. BilledMammal (talk) 02:42, 31 July 2023 (UTC)- Fix ping: User:Snow Rise. BilledMammal (talk) 02:43, 31 July 2023 (UTC)
- I've WP:BOLDly reverted the removal. Far as I'm concerned, we have a clear consensus for some wording to this effect from the previous and highly attended RFC. While that RFC didn't agree on specific wording it did agree we should add some wording to this effect, so any change that removes all language that addresses the case of deceased trans people is against consensus.
- (FWIW I also view this wording as basically the minimum viable wording.) Loki (talk) 03:16, 31 July 2023 (UTC)
- I think that's a highly problematic choice Loki, and you might be buying yourself some trouble with that bold reading of the consensus, which I think did not reflect the closer's interpretation. I'll also note that a number of people, admins included, thanked me for that edit, which I made on procedural rather than partisan grounds. You might be chewing off some trouble with what could be considered an edit warring edit on a policy page; that change has already been reverted twice before your own re-insertion, and BRD applies as much to policy pages as anywhere, especially where the related RfC involved nearly a hundred community members and the majority opposed. That said, it's your skin and best of luck. SnowRise let's rap 03:30, 31 July 2023 (UTC)
- With all due respect here, we already went through the WP:BRD cycle and seemed to be pretty clear on keeping the new language before you popped in and reverted the change without discussion. So I think your revert is on considerably shakier ground than mine, if it comes to that. Loki (talk) 18:22, 31 July 2023 (UTC)
- I don't you really appreciate how BRD works. 10 days is not enough time to establish a "status quo" version. Nor was I the first person to revert the edit. BilledMammal inserted an edit that dubiously defensible as a WP:BOLD edit to a policy (I mean style page technically, but think with the heaviness people ascribe to this issue, we can safely call it a policy determination), in light of the recent "no consensus" result at the RfC, which rejected substantially the same language. Now I believe BM was acting in good faith in doing so, but it was a questionable call, and beyond a shadow of a doubt, when that edit was reverted, they should have come here to discuss. Instead they chose to edit war an (again, substantially similar) version into the policy/style guidance. That is out of process, so I reverted it.
- At that point, BM did what they should have done from the start: came here to discuss. Now you've again introduced the language, rather than allowing that process to take place, which is absolutely edit warring. You say that the previous RfC greenlights this, because it suggested there may be consensus for "something like this", but the more recent (and larger) RfC was held to address just that question, and to determine whether to add similar language to that which you are edit warring to introduce here. That discussion resulted in no consensus, with a substantial majority strongly opposing it. So clearly you do not have consensus here; "we went through the BRD cycle already" means nothing in terms of validating your preferred approach if there was no consensus at the end of that process. So if you really think you are on "solid ground" here, I think you may want to review some policies: WP:EW, WP:CONSENSUS, WP:BRD, and WP:TE, because to my eye you are in various levels of violation of each of them.
- And I'm genuinely telling you this out of a friendly motive to spare you trouble. I don't care enough about this issue to fight you on this and don't have the time if I did. I have no intention of reverting and getting caught up in an edit war. But I am concerned that you and BM are on the edge of getting yourselves an unflattering variety of community attention. Whether you see it or not, you are way out on a limb here, and somebody could easily have taken you to ANI just based on your conduct so far, let alone what you may do next if someone else reverts you (which seems likely to me).
- You should be discussing--or for crying out loud, just letting the issue lay dormant for a while. A week even, so the community can digest the previous discussion and contemplative consideration of the next proposal can take in feedback from the last RfC and draft something that more of the community can get behind. If you haven't noticed it from the numerous comments in the last RfC, the community's patience is ebbing around the ceaseless runs at this page, with every rebuked proposal spawning two more, like the heads of a hydra, and almost all of it coming from the same small circle of editors. Patience is almost out, I believe and now you are taking the most aggressive possible posture by edit warring the content in right after the RfC rejected very similar language. You're sitting on a powder keg smoking, and whether you believe me or not, it's your and BM's rear ends that would most benefit from hearing what I am trying to tell you. SnowRise let's rap 21:47, 31 July 2023 (UTC)
Now I believe BM was acting in good faith in doing so, but it was a questionable call, and beyond a shadow of a doubt, when that edit was reverted, they should have come here to discuss. Instead they chose to edit war an (again, substantially similar) version into the policy/style guidance. That is out of process, so I reverted it.
- Just a quick correction; the second version I added was modified to address the other editors concerns (replacing "significant coverage" with "non-trivial coverage"), and I opened a discussion about that version above at #Second version. I don't think it is accurate to characterize that as edit warring. BilledMammal (talk) 00:22, 1 August 2023 (UTC)
- I understand that. And honestly, BM, I wish I wasn't in a position to have to characterize it at all; I don't think you are looking to frustrate process, so I would have been happiest to say nothing more here, except to respond to your inquiry when I could. You already know I think you should have discussed the addition before making it to begin with, given all the context, and once it was reverted you were definitely required to discuss. The "I adapted it according to the feedback I got in the reverting edit, so it should be alright to repeat the disputed edit with those changes, right?" reasoning for not taking the issue to the talk page per BRD is a grey area in the absolute best of instances; in circumstances where you certainly know the edit is on a controversial topic, the 'D' in BRD is hard stopping point, where discuss before you edit--not something to be handled in your edit summaries after you go ahead and add the disputed content again. BRD and WP:EW are very clear about that.
- But all that said, after the second revert, you did the proper thing and tried to open a line of dialogue here. I wish Loki had seen that step for the necessary and helpful one that it is, rather than stepping in to proxy/tag-team the edit back in for a third time. In doing so, they definitely took the whole thing unambigously into edit war territory, and I hope you don't get dragged along into any disruption or oversight that results. I wish you both good luck in disentangling the matter, really, but I'm gonna also be blunt that the overall approach here so far has been suboptimal and I think likely to be viewed as TE if this ends up at ANI or ANEW. So if somebody reverts Loki, I urge you both not to continue to try to force the language back in. SnowRise let's rap 03:11, 1 August 2023 (UTC)
- I really don't like all these WP:ASPERSIONS, and I think if your only argument is that we're reverting you and you don't like it, that means you have no actual argument for excluding that content. I was nowhere near 3RR (I haven't edited this page at all in over 24 hours) and I reverted you to restore text that was status quo and had consensus.
- The basic fact of the situation is that we have an RFC with a very strong consensus for language like this. We don't currently have an RFC with consensus on specific wording, but there's no reason to think we'd need that: consensus on the talk page should be all that's necessary. And this wording had that. So reverting it was inappropriate: if you object to it, you need to come in and discuss. Loki (talk) 03:46, 1 August 2023 (UTC)
"I really don't like all these WP:ASPERSIONS, and I think if your only argument is that we're reverting you and you don't like it, that means you have no actual argument for excluding that content."
- First off, no one is casting WP:ASPERSIONS at you: that policy is not in any way about someone describing easily verifiable actions you actually undertook.
- Second, there is no "we" here; I was reverted precisely once--by you. The chain of events was this: BM made a WP:BOLD edit, and another editor reverted them. BM made minor corrections to the edit and then re-introduced it again. I felt this change required discussion, so I reverted again. BM then brought the matter here as they almost certainly should have done before the first edit, given the context of the multiple RfCs and ongoing dispute over the language and which they beyond question were required to do before introducing the edit a second time. And then you blew in and, instead of lending your support to BM in discussion here, as you should have, you instead re-introduced the edit again. That's edit warring. I'm sorry, it just is.
- So please don't try to bootstrap your position with this "we are reverting you" comment that completely misrepresents the chain of events and how relevant policy applies here, dragging BilledMammal into your conduct. Your edit is more unfair to them than anyone else here: they were discussing at the point you decided to continue the edit war: now if you get your butt dragged to AE, ANI, or ANEW, they are likely to be brought along for the ride. That's not really fair to them, so again, I strongly encourage you not to revert again if the language is removed by another party (and I assure you, it won't be me). Lastly, my argument is not that WP:IDONTLIKEIT. My argument is that you are violating WP:BRD, WP:EW, and WP:TE. And you are.
"I was nowhere near 3RR (I haven't edited this page at all in over 24 hours..."
- If you need someone to explain to you the difference between WP:Edit warring and WP:3RR, and that the former does not require (and in fact rarely involves) the latter, then you really, really do need to read the relevant policies before making any future reverts. Edit warring is not about specific metrics in terms of numbers of edits over a period of time: 3RR is just a rule of thumb to warn people when they probably are edit warring. It is sufficient to establish EW, but not required. The point is that you were out of process, and there was ongoing discussion on the talk page. You aren't meant to be reverting under those circumstances. Please, really, read the policy: I'm not making any of this up, I promise you.
"...and I reverted you to restore text that was status quo and had consensus."
- If you think that "status quo version of the page" can be constituted by a change to policy that 1) was forced into the page the same day a second RfC closed with "no consensus" (where the two discussions involved well over a hundred community members), 2) was reverted almost instantly, and 3) was introduced into a major area of controversy and significance, merely because nobody reverted it for ten measly days, you really need to stay out of controversial policy areas until you undertand what "status quo version" means on this project. Because this is not it, my friend.
"The basic fact of the situation is that we have an RFC with a very strong consensus for language like this."
- Yeah, and then you had a more recent and even larger RfC which found no consensus for language even more precisely similar to the language you are edit warring to include here. And in fact, a significant majority opposed it in that discussion. You have not met your burden for attaining consensus to include this language. And I'm not the only one telling you this: literally every other person engaging with BM here in this thread other than you has said as much. Even one of the primary advocates for the need to make GENDERID protections more robust has said as much. You should be discussing until you get that consensus. Why does this seem so controversial to you? This is standard process.
"We don't currently have an RFC with consensus on specific wording, but there's no reason to think we'd need that: consensus on the talk page should be all that's necessary."
- Except you don't have that, or anything remotely like it. BM introduced the edit and only then came to the talk page to discuss. And that's this thread here and there unambigously not consensus here to include the language. If you see that consensus...well, I honestly don't know what to tell you, I don't think think I can reach you on this if that's the case.
"So reverting it was inappropriate: if you object to it, you need to come in and discuss.
- The policy is BRD, not BRRD. You and BM are advocating a WP:BOLD addition to an important piece of policy language. When you get challenged on that, you seek consensus before forcing the language in, not the other way around. And no, again you are not "defending the status quo version". If you think you get to override all the voluminous community discussion and enforce your preferred version of a hotly debated piece of policy language merely because you happened to clear a week and a half without someone reverting that version (especially considering it was actually reverted by a third party almost immediately after it was first added, and was EW'd back in)...well, then good luck with that.
- And with that, I'm done here. I can't be any more clear about the relevant policies and despite your belief that I am particularly attached to one version over the other here, I'm actually not: I reverted BM's WP:BOLD edit for procedural reasons. And whether you believe it or not, my initial comments here to you were meant primarily to warn you of potential fallout from your actions and for no other purpose: that's why they were phrased as they were. Now you seem unable to hear that and just dig yourself deeper and deeper into convincing yourself you have policy and consensus on your side here. But bluntly: if you believe that, you have some serious deficits in your understanding of both, and you're on a collusion course with ANI if you edit war further. I won't be the one to take you there, or to argue with you about any of this further, but I'm also done being the one trying to spare you that outcome. Good luck. SnowRise let's rap 05:25, 1 August 2023 (UTC)
Yeah, and then you had a more recent and even larger RfC which found no consensus for language even more precisely similar to the language you are edit warring to include here.
The proposed wording here changes the requirement from a deadname itself receiving multiple pieces of SIGCOV to the deadname being mentioned in multiple pieces of SIGCOV. Most opposes were specifically opposing the former wording rather than opposing the whole idea of restrictions on deadnaming dead transpeople (which had already received consensus in the earlier RfC where deadnames in this context were deemed to be "not inherently encyclopedic" and "must be avoided to some undetermined extent"). JoelleJay (talk) 06:02, 1 August 2023 (UTC)- Which you and I may very well agree is a significant change. It certainly addresses a major concern for me. But neither you, nor I, not any small clique of editors gets to just assume that all those opposers would change their !votes and support the version here, based on our own idiosyncratic reading of their reasoning. All manner of confirmation bias could get imputed by such an approach, which is one of numerous reasons why consensus generation on this project does not operate in that fashion.
- I'm not saying we necessarily need another RfC, but some sort of much more robust, broad community discussion here was due before adding in this language. And once it was challenged, it definitely needed to stay out until a significant consensus was reached to include it. None of that happened here, and it's a problem. It's actually going to cost support for this possibly feasible compromise version, if the lack of respect for process keeps up, mark my words. Loki has presumed that I and everyone cautioning them to back off from forcing the changes in is diametrically opposed to the addition, but that's not what's going on here. SnowRise let's rap 06:41, 1 August 2023 (UTC)
- With all due respect here, we already went through the WP:BRD cycle and seemed to be pretty clear on keeping the new language before you popped in and reverted the change without discussion. So I think your revert is on considerably shakier ground than mine, if it comes to that. Loki (talk) 18:22, 31 July 2023 (UTC)
- I think that's a highly problematic choice Loki, and you might be buying yourself some trouble with that bold reading of the consensus, which I think did not reflect the closer's interpretation. I'll also note that a number of people, admins included, thanked me for that edit, which I made on procedural rather than partisan grounds. You might be chewing off some trouble with what could be considered an edit warring edit on a policy page; that change has already been reverted twice before your own re-insertion, and BRD applies as much to policy pages as anywhere, especially where the related RfC involved nearly a hundred community members and the majority opposed. That said, it's your skin and best of luck. SnowRise let's rap 03:30, 31 July 2023 (UTC)
- Hi again, BM. There may very well be some merit to the argument that there are significant operative implications to the distinctions you are making between the wording of the recently closed no consensus proposal and your own wording, but I'm going to strongly stick by my assessment at least as far as saying that it is similar enough to what the community just failed to authorize that a WP:BOLD edit to introduce it into the policy was not the way to go here.
- As to whether I can be personally won over by your argument, I think those issues are complex and nuanced, and I want to give it some thought before engaging. I just burnt out much of the little remaining capacity for such thought (mired in sleep deprivation as I am at the moment) with my last few edits here; I'm well late for an obligation; when I get back, I have to somehow rally and get my mind focused enough for several hours of intensive work (actual work) tonight; and I'm into an intimidating couple of days immediately after! And when I do login next I am engaged with a couple of other fast moving community matters. All of which is my way of asking for patience with regard to my reply: without, I hope, feeling that I am dismissing your views or not prepared to engage with them! I'll be back to this as soon as I can be. Let me at least say for now that I do recognize that your proposed edit was goodfaith: I hope the TE did not imply otherwise. SnowRise let's rap 03:24, 31 July 2023 (UTC)
- Concur with SnowRise. We just had another RfC come to a failure of consensus on language like this. While it made some steps closer to consensus than the RfC before it, what it means is that we need to workshop another proposal and get consensus on that; much of the discussion on this page is workshopping such a proposal. Let's not short-circuit that more productive endeavor by editwarring to inject something that doesn't have a consensus for it. — SMcCandlish ☏ ¢ 😼 01:13, 1 August 2023 (UTC)
- Yeah I agree with both here. As I've said in another discussion below, we really should be analysing in detail (beyond just the remarks of the closing) both of the recent RfCs to try and distil where the community consensus actually lies. It'll take time, as both recent RfCs were lengthy, but it'll have a better result overall. Sideswipe9th (talk) 01:18, 1 August 2023 (UTC)
- If people insist I'll run an RfC on this wording, but it seems to be a waste of time - I struggle to see anyway that this proposal won't receive consensus, given that in the previous RfC many who opposed the wording there expressed support wording like what I have inserted. BilledMammal (talk) 01:28, 1 August 2023 (UTC)
- We're not asking you to run an RfC on this wording. Both SMcCandlish and I are saying that we should analyse the two most recent RfCs before making any proposal on this point. After undertaking that analysis, it may be that your wording is a fair and reasonable interpretation of where the community consensus lies, and it may not be. Right now, without having done that analysis, we simply do not know.
- If we do that work now, then any proposal we take further will have a much higher chance of being accepted, in no small part because we can refer to that analysis when presenting the new proposal. Sideswipe9th (talk) 01:32, 1 August 2023 (UTC)
- If editors require formal consensus for an proposal, then they are asking the editors supporting that edit to either drop the proposal or to run an RfC. I believe that consensus is behind this edit, based on my analysis of the previous RfC and the support expressed for this option among those who opposed that proposal, so I will chose the second path if formal consensus is deemed to be required here. BilledMammal (talk) 01:38, 1 August 2023 (UTC)
based on my analysis of the previous RfC and the support expressed for this option among those who opposed that proposal
This is the first time you've alluded to having done an analysis of the previous RfC. As such, could you elaborate on this please? How did you reach the text of this proposal? Where there any other alternative formulations were considered and ruled out during the analysis, and if so what were they and why were they ruled out? Beyond the specific questions that were asked in each RfC, are there any proposals that your analysis would consider doomed from the outset? Sideswipe9th (talk) 01:45, 1 August 2023 (UTC)- I've previously alluded to such an analysis when I said
given that in the previous RfC many who opposed the wording there expressed support wording like what I have inserted
, and I believe I've alluded to it elsewhere as well. I reached the text of this proposal by considering the discussions during that RfC, and found that JoelleJay's suggestion was particularly convincing to editors involved in that discussion and so heavily based my proposal on it. Beyond the specific questions that were asked in each RfC, are there any proposals that your analysis would consider doomed from the outset?
I could think of dozens, but I don't think it is very useful to discuss doomed proposals unless someone actually proposes them.- In the end, my position is that this is a proposal that is all but certain to receive consensus if brought to a formal discussion (
I understand that some editors will want stricter restrictions than this, and I understand that some editors will want looser restrictions than this. However, I believe the former group will consider this an improvement over the status quo, and I believe the latter group will recognize that if this went to RfC it would get consensus.
), and I proposed it on that basis in the hope that we could avoid yet another formal discussion - but as I said, if editors insist on it needing to receive formal consensus then I will open an RfC on it. BilledMammal (talk) 01:58, 1 August 2023 (UTC)In the end, my position is that this is a proposal that is all but certain to receive consensus if brought to a formal discussion
I would like to agree with this, however I need evidence to do so. I ask because there's at least one other competing view on how to interpret what was discussed at the RfCs. While I'm opposing that one currently, I have to ask why is that one a less accurate reading of the community consensus than yours? Sideswipe9th (talk) 02:05, 1 August 2023 (UTC)- Also, why JoelleJay's suggestion, and not Trystan's? If you considered Trystan's suggestion in the evaluation, what lead to your discounting of it over JoelleJay's? I know we discussed it at the time, but the closer did seem to imply a reference to it, even if they did not specifically name it. Sideswipe9th (talk) 02:10, 1 August 2023 (UTC)
- Before addressing that "competing view", I think it would be helpful to better explain my view. When reading that discussion I found that most editors, including those who opposed the proposal, didn't believe that deadnames should always be included. Reading the specific arguments I found that the most common objections were focused on including it when reliable sources had not done so, among both editors who supported and opposed the proposal. I also found that when such an alternative was raised it received relatively broad support.
- I don't think that Cuñado's view competes with this; their view is broader and deeper, but it doesn't conflict with what I have said here, and indeed their proposal includes a section that is almost identical to what I propose (
Individuals who have been deceased for at least two years, where multiple reliable independent sources have documented the name
). - Regarding Trystan's proposal (
is established through discussion of the name in high quality sources
), the primary reason I didn't base it on that was that there was no chance it could be implemented as a WP:BOLD edit; it is almost identical to the proposal rejected in the previous RfC, it shares the issues that proposal had, and it was opposed by too many editors in that discussion including myself. For those reasons I also don't believe it would receive consensus even if a formal RfC was opened on the topic, and I suspect that even opening an RfC on that topic would be controversial and invite accusations of tendentious editing. Further, if we are going to open another RfC on this topic it shouldn't be for yet another highly controversial proposal; it should be one that most of the community can get behind and produce a clear consensus for. (Regarding the closer's reference, I read that as referring to all the alternatives, including JoelleJay's, but reasonable minds may disagree.) BilledMammal (talk) 02:28, 1 August 2023 (UTC)
- I've previously alluded to such an analysis when I said
- If editors require formal consensus for an proposal, then they are asking the editors supporting that edit to either drop the proposal or to run an RfC. I believe that consensus is behind this edit, based on my analysis of the previous RfC and the support expressed for this option among those who opposed that proposal, so I will chose the second path if formal consensus is deemed to be required here. BilledMammal (talk) 01:38, 1 August 2023 (UTC)
- FWIW, I also oppose another RFC, at least so soon. Every time we do one, it takes a month to resolve a binary question about a specific wording, when the issue is that we need to craft a wording that people will agree to. As such, if we keep jumping the gun on these we're just going to annoy people with RFC after RFC on not-quite-perfect wordings of this guideline.
- We saw this at the previous RFC where it was clear that many people objected to a single specific phrasing, but it was impossible to change that phrasing by the nature of the format. If we'd just pinged people to a discussion here, we could easily have fixed the objection on the first day instead of having to wait thirty before proposing anything else. Loki (talk) 03:53, 1 August 2023 (UTC)
- If people insist I'll run an RfC on this wording, but it seems to be a waste of time - I struggle to see anyway that this proposal won't receive consensus, given that in the previous RfC many who opposed the wording there expressed support wording like what I have inserted. BilledMammal (talk) 01:28, 1 August 2023 (UTC)
- Yeah I agree with both here. As I've said in another discussion below, we really should be analysing in detail (beyond just the remarks of the closing) both of the recent RfCs to try and distil where the community consensus actually lies. It'll take time, as both recent RfCs were lengthy, but it'll have a better result overall. Sideswipe9th (talk) 01:18, 1 August 2023 (UTC)
- Concur with SnowRise. We just had another RfC come to a failure of consensus on language like this. While it made some steps closer to consensus than the RfC before it, what it means is that we need to workshop another proposal and get consensus on that; much of the discussion on this page is workshopping such a proposal. Let's not short-circuit that more productive endeavor by editwarring to inject something that doesn't have a consensus for it. — SMcCandlish ☏ ¢ 😼 01:13, 1 August 2023 (UTC)
- Fix ping: User:Snow Rise. BilledMammal (talk) 02:43, 31 July 2023 (UTC)
The closure of the previous discussion was clear
The closer specifically stated: "Several comments argued that a variance on the proposed change would be far more preferable (and obviously could be the subject of a subsequent RFC), but consensus doesn't clearly support that version (yet)." and "Of course, further discussion/consensus can (and probably will) help address these points and/or alter wording.", but going in and trying to push through these changes via a discussion that preceded that one is out of process, and this is getting to be a tiresome way of seeing BilledMammal and other editors joining him conduct business on here. Those controversial changes should never have been made without discussion, and I am reverting them back to the status quo. Just because they didn't get noticed for 7 days is no excuse. Huggums537 (talk) 06:22, 2 August 2023 (UTC)
- Question - The proposed change states that the former name “…should be included in the lead sentence of their main biographical article only…” etc. Am I correct in thinking that this change applies ONLY to the lead sentence and is intentionally NOT addressing the question of whether a deadname should be included at some later point in the article (such as in an “early life” section)? Blueboar (talk) 11:55, 2 August 2023 (UTC)
- Yeah, that wouldn't make any sense per MOS:LEADNOTUNIQUE. Our articles actually need to make sense without the lead being present at all (since we have no control over WP:REUSE of our content). — SMcCandlish ☏ ¢ 😼 02:09, 3 August 2023 (UTC)
- I agree with Smc, if there is consensus for inclusion, it should be consistent for the whole article, and not just the lead. I've often felt that implementing special rules for the lead were just back door gateways to getting them introduced as a concept for the whole article anyway... Huggums537 (talk) 00:25, 4 August 2023 (UTC)
- That was not the intent; see below for an updated draft. BilledMammal (talk) 01:51, 4 August 2023 (UTC)
- Yeah, that wouldn't make any sense per MOS:LEADNOTUNIQUE. Our articles actually need to make sense without the lead being present at all (since we have no control over WP:REUSE of our content). — SMcCandlish ☏ ¢ 😼 02:09, 3 August 2023 (UTC)
- "Didn't get noticed"? I opened a discussion publicizing the changes at the same time as making them. BilledMammal (talk) 01:51, 4 August 2023 (UTC)
- Okay, I stand corrected about that. My apologies. SnowRise has pointed out in another comment that David Eppstein reverted the post less than 20 minutes later so I guess it did get noticed, and my facts were not accurate, but that would also indicate that neither was the claim Loki made it went unchallenged for 7 days so... Huggums537 (talk) 02:29, 7 August 2023 (UTC)
- It went unchallenged for 7 days. BM made the requested changes and re-added it within 10 minutes, and David Eppstein thereafter dropped his objection. David Eppstein's objection was a narrow one about incorporating WP:SIGCOV into other guidelines.
- This whole discussion is literally just above. You can read the whole thing very easily. Loki (talk) 18:47, 7 August 2023 (UTC)
- Okay, I stand corrected about that. My apologies. SnowRise has pointed out in another comment that David Eppstein reverted the post less than 20 minutes later so I guess it did get noticed, and my facts were not accurate, but that would also indicate that neither was the claim Loki made it went unchallenged for 7 days so... Huggums537 (talk) 02:29, 7 August 2023 (UTC)
Updated draft
For deceased transgender or non-binary persons, their birth name or former name (professional name, stage name, or pseudonym) should be included in their main biographical article only if the name is documented in multiple reliable and secondary sources containing non-trivial coverage of the person.
I've updated this version to address comments made above. If there are no further issues with it, I am hoping we can get an informal consensus to include it rather than wasting more community time with an RfC; do any editors both oppose this change and believe there is a chance it wouldn't be approved in an RfC? BilledMammal (talk) 01:54, 4 August 2023 (UTC)
- I like this change, FWIW. Loki (talk) 04:25, 4 August 2023 (UTC)
- Yeah, that seems to work. — SMcCandlish ☏ ¢ 😼 14:07, 5 August 2023 (UTC)
- @Snow Rise and Huggums537: Any opposition to this? BilledMammal (talk) 15:59, 7 August 2023 (UTC)
- This seems perfectly reasonable to me and has my personal support; I don't think I would have included the parenthetical as I think it might muddy the waters a bit, but even so it is viable language. That said, I think you're still taking an imprudent tack and imperiling the longterm stability of the addition if you introduce this back in with even the unanimous agreement of just the six users in this thread, given the larger context here. So my strong advice to you is to be scrupulously pro forma and package the language together with the general GENDERID overhaul being contemplated below and discuss it as a part of that proposal. Since that proposal is meant to be an overhaul of the entire MoS and BLP wording regarding individual gender identity, I think that makes sense, and I doubt Cuñado, Tamzin, Sideswipe9th, SMcCandlish, and the others would object to that. I don't know if they plan to present their TNT/reboot proposal in RfC format (I think it would be advisable, but I don't know), but even if you just got the additional support of those participating in that thread, it would be better than the level of support we have right now. Let me reiterate that I do not think I am being needlessly BURO about this: I think this is the smart thing to do to enshrine your hard work into policy with clear community support. Best of luck, however you approach it, and please consider this a formal request to ping me to future discussions / !votes on the matter. SnowRise let's rap 16:34, 7 August 2023 (UTC)
- Leaving aside my concern about this being too low a bar, there's one small change from this proposal below that might be worth implementing. Swap
...multiple reliable and secondary sources...
to...multiple reliable and neutral sources...
. This will implicitly avoid the issue of biased and sensationalistic sources, while also maintaining some degree of source quality per the rest of the text. Sideswipe9th (talk) 16:52, 7 August 2023 (UTC)- While Sideswipe9th warmed me up to the idea of using the phrase "high-quality sources", I think "multiple reliable and neutral sources" is the best overall, emphasizing the avoidance of low-quality rather than promoting high-quality sources. I don't think the source being "secondary" is the main concern.
- The main issue I see is that this phrasing is introducing a major policy change in the MOS. You can't take lightly that we are talking about violating WP:NOTCENSORED with an MOS guideline and without clear justification. This wording might not even fly at BLP because that policy is about living people (or RDP) only. Cuñado ☼ - Talk 18:07, 7 August 2023 (UTC)
- I'm way more worried about primary sources than sensationalistic sources personally. Sensationalistic sources are usually not reliable. In the cases where we allow them, if the Telegraph and the Times of London publish someone's deadname, then I think there's at least some argument for including it, especially if you were to take as a given that those sources are reliable for trans issues (which I think is the actual issue here).
- But I really want to avoid the situation where someone digs up someone's birth certificate or college admission records and says that therefore that means their deadname must be included. That's a real concern for a large majority of deceased trans people: their deadname is often documented somewhere and establishing a strong line between "sourceable in theory" and "this is what the news actually calls this person" is IMO a bigger concern for me. Loki (talk) 18:57, 7 August 2023 (UTC)
- How about something like
..multiple reliable, neutral, and secondary sources...
, which combines all three and that way we avoid both the primary source and sensationalistic source issues entirely? Sideswipe9th (talk) 22:22, 7 August 2023 (UTC)- Sideswipe: I would strongly argue for not including "neutral", per my comment below. It drastically conflicts with what we mean when we typical speak about "neutrality" in terms of sourcing on this project. It would almost certainly invite endless entrenched debates about whether this or that source is truly "neutral" in its treatment of an article subject, and because there would be no objective editorial test for resolving that question, every dispute of the application of wording would become a quagmire of original research.Furthermore, I feel like it would almost certainly tank the proposal if and when it went before the broader community. I don't think it's useful and only muddies the water. Again, per the below, the major change that the proposed wording brings is actually at the back of the sentence. That's the part that should be protected if you want this proposal to heighten the burden, even a little. A highly subjective and value-laden term like "neutral" (that already has another very different and more pragmatic meaning on this project, with regard to sourcing) should be avoided if it is going to imperil the much more useful bit. Just my twopence worth. SnowRise let's rap 22:40, 7 August 2023 (UTC)
- I dunno. When we talk about neutral sources, generally we're speaking about the second paragraph of WP:BIASEDSOURCES and NPOV#Bias in sources. Yes RS uses a different definition of neutral versus NPOV, but it's something that we already discuss and somewhat define in both WP:RS and NPOV. To answer the point about there being "no objective editorial test", accounting for source bias is something that we already have to do, especially in contentious topics like this, when assessing whether or not some piece of content represents the NPOV on a given subject. Yes discussions on it can be contentious at times, but no more so than any other discussion. Sideswipe9th (talk) 23:05, 7 August 2023 (UTC)
- Well, look, I realize that this subject has already seen it's fair share of contention, and I'm not looking to further inflame discussion, but in my opinion what you are suggesting flies directly, diametrically in the face of WP:NPOV; we are not meant to be judging or evaluating the conclusions of sources in any way (whether that pertains to bias or factual accuracy or any other element of their claims) in individual cases; we faithfully and accurately report them (through summary or attribution) with WP:DUE respect for the WP:WEIGHT given claims have, and without stamping our own perspectives on top of them. The closest this project ever gets to utilizing editor perspective in judging the worth or bias of a given source's perspective is when we deprecate a source: usually for blatant lack of proper internal editorial controls and/or a long and exhaustive history of objectively misrepresenting the facts. And even that is invariably a contentious affair and requires a large community consensus. What we do not do is insert ourselves into the judgment and evaluation business of the content to be found in sources, whether for supposed "bias" or any other purpose. That is expressly, precisely, unambiguously, the thing WP:NPOV tells us we are not meant to do. So long as a source has WP:RS status and has not been deprecated for a specific purpose, it is acceptable to WP:verify facts and, in the case of nuanced issues, provide it's share of WP:WEIGHT. And putting aside the fact that what you are proposing is nothing short of the precise inversion of the normal NPOV process, and the exact opposite of the normal emphasis we give to word "neutral" when discussing sources, I just think you could not be more wrong about the level of WP:disruption introducing such an adjective into a description of sources in a policy/style page (any policy, let alone this particularly contentious bit centered at the epicenter of the American culture war in particular) would have. It would enable endless subjective, POV-oriented fighting. "Neutral" according to whom? Based on what idiosyncratic standard? The entire point of NPOV is that it takes our perspectives as editors out of the analysis, and moves the test to the objective standard of how many sources say a certain thing (and in what particular ways and with how much consistency). This language would do the exact opposite and actively encourage editors to argue from the basis of their own value judgments. It would open the floodgates of subjective analysis and functionally un-resolveable bickering. It's not at all like our normal processes. As contentious as the discussions that flow from WP:V and WP:NPOV/WP:WEIGHT can be, they do at the end of the day come down to a test that is external to our own perspectives--though some people just rationalize their own perspectives through selective reading of the sources even then. What you are suggesting would be an entirely different animal; an incentive to allow POV pushing through the back door of arguing the virtues and perspective of the sources themselves.Lastly, I don't think this language has a WP:SNOWBALL's chance of passing community scrutiny. It adds very little of functional use to the statement and would almost certainly make the proposal dead on arrival. And the proposal's useful language is elsewhere in the sentence:
"...containing non-trivial coverage of the person."
. I strongly urge that we don't endanger the potential benefit of that wording (and our best chance yet to fashion together a community consensus at last here) for a highly irregular use of a term that already has a distinct and more or less polar-opposite meaning in policy. I very much respect your effort to bring the disparate sides of this issue together here, but adding this word is a terrible, terrible idea. I'm certain of it. Much better to stick with "secondary" which has a precise, actionable, applicable meaning under existing policy that directly aligns with what we want it to say here.SnowRise let's rap 23:51, 7 August 2023 (UTC)we are not meant to be judging or evaluating the conclusions of sources in any way (whether that pertains to bias or factual accuracy or any other element of their claims) in individual cases
Yes we are. Part of our role as editors is in figuring out what the neutral point of view on any given topic is, and NPOV straight up tells us thatA neutral point of view should be achieved by balancing the bias in sources based on the weight of the opinion in reliable sources
(emphasis added). There is no way to determine whether an article is or is not NPOV compliant without assessing the sourcing used against all of the reliable sources on the topic and accounting for their biases in doing so.Lastly, I don't think this language has a WP:SNOWBALL's chance of passing community scrutiny.
That's fair, and I'm not going to belabour this any more than I already have. I've made a suggested tweak that I think would improve the draft and whether or not that tweak finds consensus prior to bringing this forward (if necessary) is not something I'm going to lose sleep over either way. But please, don't say that NPOV tells us not to do something that it explicitly tells us to do. Sideswipe9th (talk) 00:30, 8 August 2023 (UTC)- Except the section you are selectively quoting doesn't tell us to do what you are suggesting we urge in this policy language: it tells us to do exactly the opposite. Here's that same section but with the several contextualizing sentences you omitted before the sentence you quoted:
"A common argument in a dispute about reliable sources is that one source is biased, meaning another source should be given preference. Some editors argue that biased sources should not be used because they introduce improper POV to an article. However, biased sources are not inherently disallowed based on bias alone, although other aspects of the source may make it invalid. A neutral point of view should be achieved by balancing the bias in sources based on the weight of the opinion in reliable sources and not by excluding sources that do not conform to the editor's point of view."
(emphasis added)
- What you are suggesting in this context is to omit sources from consideration of what is essentially a WP:weight determination. That is not what the quoted section of the policy is telling us. Again, it's the exact, polar opposite: what NPOV tells us to do is to do is to cover all major views, and you evaluate the bias only for purposes of WEIGHT and for presenting all the major prevailing views. You don't judge the bias for purposes of throwing out sources you personally do not find "neutral", which is what you are suggesting we should suggest here: disregarding entirely, in a given context, based on a given editor's (or group of editors') personal feelings about their bias. I don't want to give offense, but I think you are clearly reading what the policy urges utterly and completely backwards if you think it supports the suggestion we should be ommitting sources we personally judge as "biased". And it's meaningful here. Look, Cuñado is absolutely, 100% completely correct above when they say that the major reason getting community consensus for this proposed wording is going to be tricky is because it violates WP:NOTCENSORED. It manifestly does. If any small group of editors is to actually get past that enormous burden, they have to face that reality head-on. Trying to finagle it past the community won't work: instead, one hell of a WP:IAR argument has to be made here. It has to be argued that the dignity of these encyclopedic subjects warrants this obviation of a usually very ironclad rule. It's the only feasible strategy. And it's gonna take a lot of really convincing rhetoric. Every word of the proposal and the support argument has to be tight, and I can't think of anything that would sink the effort faster than trying to use the word "neutral" in a way that is such a massive reversal of how it is meant to apply to such situations. It will instantly turn virtually every veteran editor who would otherwise be on the fence about this proposal against it, because it will feel either terribly disingenuous or like the proposing editors just don't understand the very basics of a pillar policy. SnowRise let's rap 01:43, 8 August 2023 (UTC)
- Except the section you are selectively quoting doesn't tell us to do what you are suggesting we urge in this policy language: it tells us to do exactly the opposite. Here's that same section but with the several contextualizing sentences you omitted before the sentence you quoted:
- Well, look, I realize that this subject has already seen it's fair share of contention, and I'm not looking to further inflame discussion, but in my opinion what you are suggesting flies directly, diametrically in the face of WP:NPOV; we are not meant to be judging or evaluating the conclusions of sources in any way (whether that pertains to bias or factual accuracy or any other element of their claims) in individual cases; we faithfully and accurately report them (through summary or attribution) with WP:DUE respect for the WP:WEIGHT given claims have, and without stamping our own perspectives on top of them. The closest this project ever gets to utilizing editor perspective in judging the worth or bias of a given source's perspective is when we deprecate a source: usually for blatant lack of proper internal editorial controls and/or a long and exhaustive history of objectively misrepresenting the facts. And even that is invariably a contentious affair and requires a large community consensus. What we do not do is insert ourselves into the judgment and evaluation business of the content to be found in sources, whether for supposed "bias" or any other purpose. That is expressly, precisely, unambiguously, the thing WP:NPOV tells us we are not meant to do. So long as a source has WP:RS status and has not been deprecated for a specific purpose, it is acceptable to WP:verify facts and, in the case of nuanced issues, provide it's share of WP:WEIGHT. And putting aside the fact that what you are proposing is nothing short of the precise inversion of the normal NPOV process, and the exact opposite of the normal emphasis we give to word "neutral" when discussing sources, I just think you could not be more wrong about the level of WP:disruption introducing such an adjective into a description of sources in a policy/style page (any policy, let alone this particularly contentious bit centered at the epicenter of the American culture war in particular) would have. It would enable endless subjective, POV-oriented fighting. "Neutral" according to whom? Based on what idiosyncratic standard? The entire point of NPOV is that it takes our perspectives as editors out of the analysis, and moves the test to the objective standard of how many sources say a certain thing (and in what particular ways and with how much consistency). This language would do the exact opposite and actively encourage editors to argue from the basis of their own value judgments. It would open the floodgates of subjective analysis and functionally un-resolveable bickering. It's not at all like our normal processes. As contentious as the discussions that flow from WP:V and WP:NPOV/WP:WEIGHT can be, they do at the end of the day come down to a test that is external to our own perspectives--though some people just rationalize their own perspectives through selective reading of the sources even then. What you are suggesting would be an entirely different animal; an incentive to allow POV pushing through the back door of arguing the virtues and perspective of the sources themselves.Lastly, I don't think this language has a WP:SNOWBALL's chance of passing community scrutiny. It adds very little of functional use to the statement and would almost certainly make the proposal dead on arrival. And the proposal's useful language is elsewhere in the sentence:
- I dunno. When we talk about neutral sources, generally we're speaking about the second paragraph of WP:BIASEDSOURCES and NPOV#Bias in sources. Yes RS uses a different definition of neutral versus NPOV, but it's something that we already discuss and somewhat define in both WP:RS and NPOV. To answer the point about there being "no objective editorial test", accounting for source bias is something that we already have to do, especially in contentious topics like this, when assessing whether or not some piece of content represents the NPOV on a given subject. Yes discussions on it can be contentious at times, but no more so than any other discussion. Sideswipe9th (talk) 23:05, 7 August 2023 (UTC)
- Sideswipe: I would strongly argue for not including "neutral", per my comment below. It drastically conflicts with what we mean when we typical speak about "neutrality" in terms of sourcing on this project. It would almost certainly invite endless entrenched debates about whether this or that source is truly "neutral" in its treatment of an article subject, and because there would be no objective editorial test for resolving that question, every dispute of the application of wording would become a quagmire of original research.Furthermore, I feel like it would almost certainly tank the proposal if and when it went before the broader community. I don't think it's useful and only muddies the water. Again, per the below, the major change that the proposed wording brings is actually at the back of the sentence. That's the part that should be protected if you want this proposal to heighten the burden, even a little. A highly subjective and value-laden term like "neutral" (that already has another very different and more pragmatic meaning on this project, with regard to sourcing) should be avoided if it is going to imperil the much more useful bit. Just my twopence worth. SnowRise let's rap 22:40, 7 August 2023 (UTC)
- (edit conflict)I tend to agree that the former version is preferable. "Neutral" in this context is far too subjective, and is only going to invite ambiguity and conflict, I think we can almost certainly predict. That said, in my opinion, this is actually by far the lesser impactful phrase in the sentence. Technically any fact cited in article should be supported by reliable sourcing, and we already have policies cautioning to use primary sources with extreme caution. The addition in this proposal that is really doing the heavy lifting is
"...containing non-trivial coverage of the person."
That's also the language that most substantial increases the burden here, and it's also likely to keep out the kinds of primary sources that you are concerned with, as I read it, because these sources contain no real substantive "coverage" but rather just routine clerical data. But I don't necessarily think we need to drop the "secondary" either; I'd argue it is much more useful, clear, and functionally dispositive than "neutral". SnowRise let's rap 22:34, 7 August 2023 (UTC) - I largely agree with SnowRise and Loki on this; we need the secondary aspect to exclude primary sources - while most won't be WP:SIGCOV some, like a school report card, would be - and the "neutral" aspect is likely to introduce conflict. Even without such a requirement, I vaguely recall someone arguing that the BBC was not neutral on this topic. BilledMammal (talk) 22:41, 7 August 2023 (UTC)
- If the sensationalist media thing really is a concern, my proposed change would be to sub out
multiple ... sources
fora majority of ... sources
or at leasta plurality of ... sources
. As written, the standard is just two reliable secondary sources, and while in cases where there isn't a lot of coverage I think that's fine, in the case where a subject has received a lot of coverage and most sources don't use the former name, just two sources may not really be a convincing argument to use it in practice. - The argument for that clause is "we should follow the sources", and if we're going to do that then we should follow the sources the same way we normally do, namely giving the greatest weight to the greatest number of sources. Loki (talk) 04:15, 8 August 2023 (UTC)
- (Oh, that all being said, I also believe the BBC is not neutral on this topic, because the entire British media is not neutral on this topic. The BBC is not the worst among them, but it's also not the best: they've put out at least one blatantly bad article about trans issues, and more relevant to our reliability policy were very reluctant to issue corrections even to obvious factual mistakes in said article.) Loki (talk) 04:22, 8 August 2023 (UTC)
- You had already mentioned two of the worst sources we otherwise consider generally reliable earlier in this discussion; The Times and The Telegraph. The Times in particular recently hit a new low when they included the former name of a recently killed trans teen earlier this year. But the British media's transphobia issues are a discussion for another talk page. Sideswipe9th (talk) 04:27, 8 August 2023 (UTC)
- You're not exactly covering yourself in glory with the sources-I-disagree-with-are-not-neutral discussion.
- I think Snow Rise convinced me that the "reliable and neutral" is probably not the best wording, but now I'm pondering whether multiple reliable sources containing non-trivial coverage might be a winner (without "secondary"). WP:RS already has significant guidance, including "Prefer secondary sources", "Context matters", "News organizations", or "Biased or opinionated sources". It catches most issues by using that with "multiple" and "non-trivial coverage". Cuñado ☼ - Talk 05:44, 8 August 2023 (UTC)
- I would disagree with that, because I don’t see any circumstances where we would want to use primary sources for this. BilledMammal (talk) 05:52, 8 August 2023 (UTC)
the entire British media is not neutral on this topic
If the entire media of a major nation with freedom of the press is not neutral on this topic then I would suggest no media is neutral on it, which does demonstrate the issue with adding a “neutrality” clause.- I don’t think majority or plurality will work; plurality because there are only two options, to include or not to include the name, and thus no option will ever have a plurality, majority because determining a majority is difficult and can result in flip flopping if the count is close, and because using “majority” in related proposals has been opposed for reasons that are likely to apply here. I think it’s better to keep it simple and get at least something in; if we find that something is too weak we can look at tightening it then. BilledMammal (talk) 05:52, 8 August 2023 (UTC)
- The case I had in mind was when a person has released it themself and doesn't mind sharing it, thus removing the privacy concern. That sharing would mostly be primary sources, like a blog. Cuñado ☼ - Talk 18:11, 8 August 2023 (UTC)
- The issue is that national media of other major nations (such as the NYT or WaPo) as well as international media such as the AP and Reuters are all neutral on this issue. There's a very large and noticeable difference in the UK media position on this issue because of how it fits into UK politics that has been commented on by other reliable sources. So for instance, CNN's commented on the issue, as have the CBC, Insider, and Al Jazeera. The US version of the Guardian even condemned the UK version's stance on trans issues. Loki (talk) 06:33, 8 August 2023 (UTC)
- You had already mentioned two of the worst sources we otherwise consider generally reliable earlier in this discussion; The Times and The Telegraph. The Times in particular recently hit a new low when they included the former name of a recently killed trans teen earlier this year. But the British media's transphobia issues are a discussion for another talk page. Sideswipe9th (talk) 04:27, 8 August 2023 (UTC)
- If the sensationalist media thing really is a concern, my proposed change would be to sub out
- How about something like
- Reading through much of the above leads me to suggest "multiple, secondary, reliable sources containing non-trivial coverage of the person". — SMcCandlish ☏ ¢ 😼 18:50, 8 August 2023 (UTC); clarified: 05:01, 9 August 2023 (UTC)
- "...non-trivial coverage of the person", let us hasten to specify, in accordance with BM's proposal. Let's stay out of the headlights of the major source of opposition in the last RfC as much as possible. I doubt even swapping out "significant coverage" for "non-trivial coverage" will provide enough change to keep those same users from !voting the same way if it comes to it, if the standards is still tied to how much prominence the name is given. Better to focus on a standard that allows the incidental use of the name in sources, but at least underlines a need for that usage to appear in multiple, secondary reliable sources that are actually focused on the subject. SnowRise let's rap 00:34, 9 August 2023 (UTC)
- Right-oh. — SMcCandlish ☏ ¢ 😼 05:01, 9 August 2023 (UTC)
- "...non-trivial coverage of the person", let us hasten to specify, in accordance with BM's proposal. Let's stay out of the headlights of the major source of opposition in the last RfC as much as possible. I doubt even swapping out "significant coverage" for "non-trivial coverage" will provide enough change to keep those same users from !voting the same way if it comes to it, if the standards is still tied to how much prominence the name is given. Better to focus on a standard that allows the incidental use of the name in sources, but at least underlines a need for that usage to appear in multiple, secondary reliable sources that are actually focused on the subject. SnowRise let's rap 00:34, 9 August 2023 (UTC)
Addition to filter
Hi, I've noticed there's a filter or something called "possible MOS:ETHNICITY violation" in Wikipedia's code. How does it work? Does it for example avoid edits consisting in the removal of demonyms from an article? If so I'd like to propose an addition. But firstly I'd like to know what does it do. Super Dromaeosaurus (talk) 21:45, 8 August 2023 (UTC)
- Those tags are applied by edit filters, and the best place to discuss them in general is at the Wikipedia:Edit filter noticeboard, to request a new/expanded filter post at Wikipedia:Edit filter/Requested. Note that while the workings of most of them are public there are some that of necessity that need to remain private for WP:BEANS reasons (this is unlikely to apply to one that tags MOS violations though). Thryduulf (talk) 00:05, 9 August 2023 (UTC)
- Thank you, I'll start a thread there. Super Dromaeosaurus (talk) 09:25, 9 August 2023 (UTC)
Proposal to split MOS:GENDERID from Wikipedia:Manual_of_Style/Biography
Split Wikipedia:Manual_of_Style/Biography#Gender_identity to Wikipedia:Manual of Style/Gender identity. Currently the topic is a WP:FORK between the two. Being a subtopic in MOS:Biography perpetuates forked discussions, forked manual-of-style-guidance, prevents LGBT+ communities and other stakeholders from using the "watch" feature and accessing this policy discussion, and floods disinterested wiki policymakers with a high-barrier-to-entry inaccessible discussion. We already have about 100 conversation threads identified for this and it is unsustainable to center them here at Wikipedia_talk:Manual_of_Style/Biography. I fail to recognize negative consequences of this proposal; if anyone sees any then please state them.
- Proposal -
- Replace {{Further}} {{Further|Wikipedia:Manual of Style/Gender identity}} with {{Main}} {{|Main|Wikipedia:Manual of Style/Gender identity}}
- Summarize this topic at Wikipedia:Manual_of_Style/Biography#Gender_identity in 3-5 sentences - no great detail here
- Future development and discussion go to Wikipedia:Manual of Style/Gender identity
- Shortcuts now go to Wikipedia:Manual of Style/Gender identity including
- MOS:GENDERID
- MOS:GID
- MOS:DEADNAME
- MOS:NB
- WP:GENDERBLP
- Similarly, merge Wikipedia:Manual_of_Style#Identity into Wikipedia:Manual of Style/Gender identity, because it is another WP:FORK of the same topic
- Support as proposer. Bluerasberry (talk) 15:12, 2 August 2023 (UTC)
- I would take it a step further… and remove it from MOS space entirely. That happened because originally it simply discussed pronouns (which was a style issue)… but it has grown well beyond that. The issues we have been wrestling with for the last few months are far more than style issues… there are mostly content issues: focused on relevance, Verifiability and reliability, Neutrality, and a host of other things. I would suggest a separate WP:GENDER guideline. Blueboar (talk) 16:20, 2 August 2023 (UTC)
- Support: the large majority of discussion on this talk page is about this one guideline and that strongly suggests to me that it deserves its own page. In addition, I agree with Blueboar that MOS:GENDERID is really not a style guideline, it's a content guideline with style implications. It bears more relation to WP:BLP than to the rest of the MOS. So I wouldn't oppose breaking out the parts about excluding names for privacy reasons to WP:BLP or a subpage, and leaving the MOS parts for how to properly word things given those content restrictions. Loki (talk) 19:22, 2 August 2023 (UTC)
- Support I can see good reasons for a simple split. The amount of discussion on this guideline, not just the current discussions on amendments and rewrites, but also discussions on how to interpret and apply it to relevant content are pretty lengthy and frequent. Separating this out would allow for those discussions to occur without impacting on other discussions here relating to MOSBIO. I also find myself agreeing with Loki and Blueboar, GENDERID has grown beyond a simple style guide into something that touches upon inclusion criteria, neutrality, privacy of biographical subjects. There is a strong argument here for making this or elements of this either a standalone guideline or policy in its own right, or integrated into the policy or guideline they are founded upon. If this finds consensus, I would still be minded to leave behind transclusion of the style related aspects (ie, use the most recent name and gendered terms for the person), as those are truly style related issues, and can be considered separate from content inclusion issues. I'd prefer a transclusion though than a summary, only because that means we only need to update it in a single place should the style text be amended in any major way. Sideswipe9th (talk) 19:52, 2 August 2023 (UTC)
- To restate succinctly why I think we've reached the point where this needs to be split off into its own stand-alone guideline. When GENDERID was first added to MOSBIO in something resembling its current form it was a style guideline with content implications; use the name and pronouns the subject uses; if they weren't notable prior to changing their name, don't include the former name. As time progressed, the guideline was amended to and added, and in its current form I think it's more accurately described as a content guideline with style implications; use the name and pronouns the subject uses; if they weren't notable prior to changing their name, don't include it; don't detail name and gender presentation changes in other articles unless pertinent; paraphrase, elide, or use square brackets to avoid deadnaming and misgendering in quotes.
- MOSBIO on the whole a style guideline, with some minor content implications, which typically amount to "don't give undue weight" (see the sections on bad nicknames and sexuality). However because GENDERID is now a content guideline with style implications, and is typically enforced as such at dispute resolution and behavioural noticeboards (AN, ANI, AE, BLPN) it's clear that it has outgrown this guideline. That alone is sufficient reason to me to split it off into its own guideline.
- Finally, on the arguments that this split would result in local consensus or ownership problems, frankly in my opinion that isn't a reason to not split, nor is it one I can find that's supported by policy or guideline. If there is a policy or guideline that supports not splitting, could it please be linked? Editors who are fearful of such a situation would be able to watchlist it just as easily as the stakeholder groups that Blueraspberry has mentioned. Likewise there are well established mechanisms to prevent and challenge local consensuses, like RfCs and notifications to relevant noticeboards or WikiProjects, and WP:CENT, which are designed to stop such a thing from occurring. The option to use a contextually relevant mechanism will remain open regardless of whether future discussions on the guideline occur here, on a stand-alone guideline page, or some other venue like VPP (the forum for the two most recent RfCs). Sideswipe9th (talk) 17:52, 4 August 2023 (UTC)
- I'm inclined to support, particularly the idea that this should be split out and separated from the MOS. That said, I worry that a move to this guidance mainly residing at Wikipedia:Manual of Style/Gender identity (or wherever that page moves to) might incidentally downgrade most of the guidance from guideline status to explanatory essay status. If the resulting page is a guideline page, I'm all for it. Firefangledfeathers (talk / contribs) 01:06, 3 August 2023 (UTC)
- Oppose in part because the material is short and isn't really suited to being an entire guideline page, in part because orders of magnitude fewer people would be watchlisting it, leaving much more room for mischief, and in part because a separate page on this would be highly likely to develop WP:LOCALCONSENSUS problems, including the probable formation of a WP:OWN-attempting WP:FACTION. This material is much safer in a major guideline page with over 700 watchers, over 100 of whom are actively engaged in keeping this page sensible. — SMcCandlish ☏ ¢ 😼 02:06, 3 August 2023 (UTC)
- Oppose Similar grounds to SMcCandlish.--Wehwalt (talk) 04:42, 3 August 2023 (UTC)
- Oppose per SMcCandlish. The proposal is explicitly made because the status quo
prevents LGBT+ communities and other stakeholders from using the "watch" feature
. I am not sure whether there are other stakeholder communities this could be referring to, and if not, then the question remains that once this change is made, would there will be appropriate balance in resultant discussions, instead of a local consensus? starship.paint (exalt) 04:59, 3 August 2023 (UTC) - Oppose per SMcCandlish. This is a topic of discussion that needs as much sunlight on it as possible. Stifle (talk) 08:25, 3 August 2023 (UTC)
- Oppose Nothing is preventing certain communities and "other stakeholders" from watchlist-ing this page or participating in discussions here. SMcCandlish raises good points, particularly that a separate page would develop
WP:LOCALCONSENSUS problems, including the probable formation of a WP:OWN-attempting WP:FACTION.
Some1 (talk) 11:57, 3 August 2023 (UTC) - Oppose Anything other than making it policy and making it clear that WP:NPOV does not mean that we have to deadname people just because reliable sources do is a complete waste of time. As long as people use WP:NPOV as an argument for deadnaming any MOS on the matter is completely meaningless. -- Random person no 362478479 (talk) 12:22, 3 August 2023 (UTC)
- FWIW it's already the case that WP:NPOV does not mean we have to deadname people. That's always been a losing argument whenever I've seen it, which is very rarely. I much more often see arguments based off WP:NOTCENSORED among people who want to ignore this guideline. Loki (talk) 00:48, 4 August 2023 (UTC)
FWIW it's already the case that WP:NPOV does not mean we have to deadname people.
If it's WP:DUE, then it does. If there arelosing argument[s]
, then it's because you're witnessing editors willingly choose to violate the non-negotiable status WP:NPOV enjoys and it's a shame because our ability to cover topics neutrally is a deeper concern than helping someone trying to stop a streisand effect (or put a genie back in a bottle, etc, etc) over something that not all of society agrees with (as evidenced by reliable sources). Of late, the arguments for change are boldly running straight through WP:RGW and are disruptive with the non-stop proposals/threads/debates and it grows tiring. If someone had told me 3-4 years ago I'd be on Wikipedia arguing about transgender topics, I'd never have believed them. And yet here I am, because apparently we're trying to change Wikipedia from being a follower of sources to being an encyclopedia that picks and chooses which reliable sources to ignore or acknowledge. And that's the most dangerous thing to come out of this to me in my decades of being here. —Locke Cole • t • c 16:09, 4 August 2023 (UTC)- Could you explain please, why you think a person's name (or in this case former name) is a point of view on a topic? And how a name could a dispute? Sideswipe9th (talk) 16:13, 4 August 2023 (UTC)
- From WP:DUE:
Undue weight can be given in several ways, including but not limited to the depth of detail, the quantity of text, prominence of placement, the juxtaposition of statements, and the use of imagery.
And I don't think it's a point of view (and it doesn't really matter what I think here), our sources do. —Locke Cole • t • c 16:23, 4 August 2023 (UTC)- That doesn't really answer the question, and opens a few more. Our sources don't have a concept of what we define to be a neutral point of view. They have their own criteria and reasons for including or excluding content, just as we do. Despite this, you're asserting that including or not including the deadname of a trans or non-binary person is a point of view on that person, so I return to my original question, how is a person's name a point of view?
- Just because our sources include a piece of information doesn't mean we have to include it (see WP:VNOT, WP:NOTEVERYTHING, WP:NOTNEWS, WP:INDISCRIMINATE). A piece of information must have encyclopaedic value before it can be included in any article. Now if you want to make an argument that the former name of a trans or non-binary person (living or dead) has encyclopaedic value, then by all means make that argument. Sideswipe9th (talk) 16:31, 4 August 2023 (UTC)
- You asked
Why [do] you think a person's name (or in this case former name) is a point of view on a topic?
, I cited the exact wording from WP:NPOV that addressed your question. As to the rest, I'll leave you with WP:RGW which addresses what's happened here far better than I'm capable of. —Locke Cole • t • c 14:57, 5 August 2023 (UTC)- You've stated what you think, but I was asking why you think it. I want to understand why you think a trans or non-binary person's deadname is a point of view, as NPOV defines it. Or perhaps, based on this reply, why you think our sources believe the former name is a point of view, and not a factoid (as in the CNN definition of it being minor trivia) about the person. If our sources believe, as you assert, that a person's name is a point of view, could you perhaps cite a relevant style guide or editorial policy that elaborates on this? Sideswipe9th (talk) 15:19, 5 August 2023 (UTC)
- Oh, you misunderstand. I don't think this, WP:NPOV says it. And you apparently can't understand that. If you think something as integral as how we identify someone in an encyclopedia article is simply a
factoid
, you'll need to let the folks who came up with WP:AT and the various Wikipedia naming conventions that their work was all for nothing. But this is all basic writing: who someone is (their name) is as important as what they've done, where they did it, and the why of what happened. This is all very academic. I won't be re-quoting NPOV since apparently the words don't mean anything to you, but it's all right there. —Locke Cole • t • c 15:54, 5 August 2023 (UTC)- AT, and the various naming conventions deal with an article subject's name, and with a few exceptions will typically follow WP:COMMONNAME. Name changes of article subjects are one of the major exceptions to the article naming conventions for why we might break with the historical common name for a subject. And that policy point, alongside GENDERID is why our articles about trans and non-binary individuals always use the current name of the article subject, and not their former name. However, we're not discussing article titles and naming conventions, we're discussing content inclusion or exclusion.
- The NPOV policy covers points of view on a topic. The purpose behind it is that we describe disputes, and not engage in them. As DUE states, neutrality requires that our articles
fairly represent all significant viewpoints that have been published by reliable sources, in proportion to the prominence of each viewpoint in those sources
. Ordinarily when we discuss DUE, we are asking and answering questions like "does [insert label] apply to this article/?" or "what does current academic research state about this topic?" or "is this theory disputed and by whom?" This is so that whenever we're answering those questions, we're always following whatever the mainstream view on a topic is. - The logical leap that I can't understand is why you're asserting that the former name of a person is a point of view, as that is in no way clear from the text of the policy. The only places in NPOV that actually use the word name are WP:POVNAMING and the paraphrasing of Jimbo Wales' 2003 mailing list post about naming the prominent adherents to a significant minority viewpoint. The questions that I've been asking have been to try to understand this logical leap you're making, because it is not an obvious one from the text of the policy. In other words, there is some base assumption that you are making here when reading the policy text that I am not, and it is one that I would like to understand. Based on your most recent reply, the only way I can think of that your interpretation makes sense is if you believe, or you're asserting that our sources believe, that a person cannot ever change their name, and that the act of changing names is a dispute that we cannot engage in. Is that the case? If that is not the case, would you please elaborate on what non-obvious base assumption you are making, because again, it's not obvious from what you've been saying or quoting? Sideswipe9th (talk) 16:41, 5 August 2023 (UTC)
- WP:DUE:
Undue weight can be given in several ways, including but not limited to
(emphasis added, the "several ways" provided are just a sampling and not an exhaustive list)the depth of detail
(a name is a "detail" that sources may go into depth on, omitting such a detail when reliable sources report it runs afoul of DUE)[...] the juxtaposition of statements
(our sources may list a "deadname" near a subjects current name, deviating significantly from that would again run into NPOV concerns). —Locke Cole • t • c 05:25, 6 August 2023 (UTC)- Ok, so why is that encyclopaedically relevant? To pick another characteristic for a moment, if the majority of our sources said something like "X had curly red hair" or "Y spoke with a Scottish accent", is that something that NPOV would compel us to include in our articles? How do you balance that against other policy points like WP:INDISCRIMINATE and WP:5P1? Sideswipe9th (talk) 16:15, 6 August 2023 (UTC)
- If lots and lots of sources highlight the fact that someone has/had curly red hair, that fact is obviously considered a significant trait for that person. It would be UNDUE for Wikipedia to omit it. The same is true for former names. We can quibble over how many sources are needed, and about the quality of those sources… but… eventually it comes down to: if enough sources all highlight a fact about a person, that fact should be considered encyclopedic and worth including in our article about that person. Blueboar (talk) 16:31, 6 August 2023 (UTC)
- Ok, so why is that encyclopaedically relevant? To pick another characteristic for a moment, if the majority of our sources said something like "X had curly red hair" or "Y spoke with a Scottish accent", is that something that NPOV would compel us to include in our articles? How do you balance that against other policy points like WP:INDISCRIMINATE and WP:5P1? Sideswipe9th (talk) 16:15, 6 August 2023 (UTC)
- WP:DUE:
- NPOV isn't just about points of view; it's also about aspects. See WP:BALASP and WP:DUE. BilledMammal (talk) 16:33, 5 August 2023 (UTC)
- This is true but IMO irrelevant. If lots of sources said what a BLP subject's current address was, we still couldn't include that information. That's not a WP:NPOV matter, because neither WP:NPOV nor WP:V require us to include information no matter how well it's sourced.
- Rather, if we do include information we need to include all significant points of view about it in proportion to their prominence in reliable sources, but we always have the option of just not including it at all, and there are many polices (WP:NOT for instance) that instruct us to not include some information sometimes. Loki (talk) 19:22, 5 August 2023 (UTC)
- We can include a BLP subject's current address, and often do so. The article on Donald Trump, for example, states that he resides at Mar-a-lago. WP:BLPPRIMARY only forbids the sole use of primary documents for the purpose of identifying a subject's address. Hawkeye7 (discuss) 20:25, 5 August 2023 (UTC)
- WP:BLPPRIVACY says
articles should not include postal addresses, e-mail addresses, telephone numbers, or other contact information for living persons
. Loki (talk) 03:07, 6 August 2023 (UTC)- There are a few rare cases where WP:NPOV overrides that aspect of WP:BLP. For example, Donald Trump and Jeremy Hunt. BilledMammal (talk) 03:12, 6 August 2023 (UTC)
- WP:BLPPRIVACY says
- We can include a BLP subject's current address, and often do so. The article on Donald Trump, for example, states that he resides at Mar-a-lago. WP:BLPPRIMARY only forbids the sole use of primary documents for the purpose of identifying a subject's address. Hawkeye7 (discuss) 20:25, 5 August 2023 (UTC)
- Oh, you misunderstand. I don't think this, WP:NPOV says it. And you apparently can't understand that. If you think something as integral as how we identify someone in an encyclopedia article is simply a
- You've stated what you think, but I was asking why you think it. I want to understand why you think a trans or non-binary person's deadname is a point of view, as NPOV defines it. Or perhaps, based on this reply, why you think our sources believe the former name is a point of view, and not a factoid (as in the CNN definition of it being minor trivia) about the person. If our sources believe, as you assert, that a person's name is a point of view, could you perhaps cite a relevant style guide or editorial policy that elaborates on this? Sideswipe9th (talk) 15:19, 5 August 2023 (UTC)
- You asked
- From WP:DUE:
- Could you explain please, why you think a person's name (or in this case former name) is a point of view on a topic? And how a name could a dispute? Sideswipe9th (talk) 16:13, 4 August 2023 (UTC)
- I am not saying that WP:NPOV does mean that we have to deadname people. Personally I think that is a bizarre interpretation of what a point of view is (and conflicts with a whole host of rules and guidelines, including, but not limited to the ones listed by Sideswipe9th). But WP:NPOV is used to argue for deadnaming. Of course most people just go with "reliable sources do it so we have to do it" without giving any policy rationale. And unfortunately I don't share you optimism that it is a losing argument. -- Random person no 362478479 (talk) 20:15, 4 August 2023 (UTC)
- FWIW it's already the case that WP:NPOV does not mean we have to deadname people. That's always been a losing argument whenever I've seen it, which is very rarely. I much more often see arguments based off WP:NOTCENSORED among people who want to ignore this guideline. Loki (talk) 00:48, 4 August 2023 (UTC)
- Move out of MOS. I also agree with Blueboar and LokiTheLiar that much of MOS:GENDERID is about content not style and should be part of WP:BLP, not MOS. And yes, I do think that it should be restricted to living or recently dead people. The same rules should apply equally to all people, regardless of gender or gender identity. But even if we have different rules for trans etc people, it should still be a content guideline, not a style guideline. Mitch Ames (talk) 12:59, 3 August 2023 (UTC)
- It actually is a bit of BOTH content and style… but that just highlights the need for it to be on a page of its own. Blueboar (talk) 16:21, 3 August 2023 (UTC)
- Lots of bits of MoS have elements of content guideline to them; that's not a good rationale for such a split. — SMcCandlish ☏ ¢ 😼 14:22, 5 August 2023 (UTC)
- It actually is a bit of BOTH content and style… but that just highlights the need for it to be on a page of its own. Blueboar (talk) 16:21, 3 August 2023 (UTC)
- Oppose per SMc. I support it in principle, but it's not a simple split as we'd be effectively elevating it from a MOS guideline to either a guideline or a policy. And that makes the NPOV/DUE conflict even more important to resolve. —Locke Cole • t • c 16:27, 3 August 2023 (UTC)
- Comment I posted this invitation to comment to Wikipedia:Manual of Style, WP:Feminism, WP:LGBT, WP:Women, WP:Men, and WP:Gender studies. These were stakeholder communities that I imagined might have opinions. If anyone else knows of others, then invite more participation. Bluerasberry (talk) 19:17, 3 August 2023 (UTC)
- Oppose as proposed, but really agree with Mitch Ames and others that the best solution would be a short section in BLP (perhaps based on proposal #4 above) to decide on content exclusion, and leave the MOS for style tips. Cuñado ☼ - Talk 20:08, 3 August 2023 (UTC)
- Oppose; this will reduce the number of eyes on this section and I do not believe that is a positive change. There are also WP:CONLEVEL issues with this proposal; it will either upgrade Wikipedia:Manual of Style/Gender identity to a style guideline, or it will downgrade Wikipedia:Manual of Style/Biography#Gender identity to an essay. Which one will occur isn't specified, but either way a split discussion lacks the CONLEVEL to do so. BilledMammal (talk) 01:50, 4 August 2023 (UTC)
this will reduce the number of eyes on this section
— I don't think the number of watchers should affect where a guideline goes. It's either about content or style (or both, as Blueboar pointed out), and its location in the guideline/policies structure should be dictated by its scope, not by how many people chose to watch it. Anyone can watch or subscribe to anything - we don't hide our policies and guidelines. If anything, it should be easier to find and watch if it is in a sensible place, matching the scope of the guideline/policy. Mitch Ames (talk) 02:15, 4 August 2023 (UTC)
- Support as second preference to moving out of MOS per Blueboar. This needs it's own page that deals with both the content and style issues, the former can and should be summarised at WP:BLP, the latter can and should be summarised here, with both pointing to the specific page for more detail and precision. Thryduulf (talk) 13:52, 4 August 2023 (UTC)
- That is something I could support. -- Random person no 362478479 (talk) 20:09, 4 August 2023 (UTC)
- Oppose per SMcCandlish; it's not necessary and it shunts it off somewhere with less scrutiny. Crossroads -talk- 00:01, 5 August 2023 (UTC)
- Extremely strong support for alternative proposal to move this out of Manual of Style altogether. I've seen discussions as to whether revision deletion or oversight is acceptable for violations of this guideline, and while I can understand that sort of thing on BLP grounds, I cannot accept it on MoS grounds. The Manual of Style – Style! – is a guideline, not a policy, that discusses how to write, not what to write, and the idea that MoS violations should be deleted/oversighted is extremely WP:TROUT-worthy. As for other places where the MoS dictates what content is allowed, those should also be pruned down; I'm not so sure why, for example, relevant portions of Wikipedia:Manual of Style/Video games should be treated differently from Wikipedia:WikiProject Military history/Content guide. See also Wikipedia:Manual of Style/Words to watch, which notes that
[t]here are no forbidden words or expressions on Wikipedia
and focuses on avoiding the loss of information (MOS:SAID is a good example of this). -BRAINULATOR9 (TALK) 23:48, 6 August 2023 (UTC)
GENDERID in BLP
Based on the consensus that seems to be forming around the split, here is a proposed wording for a paragraph in BLP, so that the MOS is for style and not making content policy.
Proposed paragraph for WP:BLPNAME |
|---|
|
For the special case of the former name of a transgender or non-binary individual, it is reasonable to assume they would not want the name disseminated, and it should be removed unless the person was notable under the name, they made the name public post-transition, or they are a public figure. Any inclusion must be supported by multiple reliable and neutral sources.[a]
|
Proposed MOS:GID |
|---|
|
Refer to any person whose gender might be unclear with the name and gendered words (e.g. pronouns, waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources. The former name of a transgender or non-binary person should only be included if the person was notable under the name, they made the name public post-transition, or they are a public figure (See WP:BLPNAME). The former name must not be given undue weight or overemphasis. It may be placed later in the lead or elsewhere in the article instead of the first sentence, to avoid giving it undue prominence. Articles or other works that were published under a pre-transition name may use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnote. When the former name or gender is not included in the article, avoid confusing constructions (Jane Doe fathered a child) by rewriting (e.g., Jane Doe became a parent). If the former name appears in a quotation, the article may need to paraphrase, elide, or use square brackets to replace portions of quotations to avoid deadnaming or misgendering. Do not replace or supplement a person's former name with a current name if the two names have not been publicly connected and connecting them would out the person. In rare cases where exact wording cannot be avoided (e.g. pun, rhyme, album cover), the quotation or work may be included.
|
Cuñado ☼ - Talk 21:16, 5 August 2023 (UTC)
- I would suggest that we NOT change any existing language at this point… but merely MOVE the existing guidance to a new WP:GENDER page. Once people get used to it being consolidated at a new location we can discuss changes. Go one step at a time. Blueboar (talk) 21:52, 5 August 2023 (UTC)
- Perhaps I'm missing something but I don't see where there's consensus to take anything out of the MoS.--Wehwalt (talk) 21:55, 5 August 2023 (UTC)
- Yeah,
consensus that seems to be forming
, whaaaat? No jumping the gun, please. Crossroads -talk- 00:24, 6 August 2023 (UTC) - The "consensus that seems to be forming" is opposition to splitting this material out of MoS. And as Blueboar says, trying to change the material in the process of proposing a different split is just asking for opposition. We already know from all the discussion prior that there is considerable opposition to phrasing like "they made the name public post-transition" (which is a rephrasing of the same idea behind "clearly expressed their consent to share the information"), because these are matters of public record that are not dependent on what the subject themselves did/said. — SMcCandlish ☏ ¢ 😼 03:14, 6 August 2023 (UTC)
- Yeah,
- Perhaps I'm missing something but I don't see where there's consensus to take anything out of the MoS.--Wehwalt (talk) 21:55, 5 August 2023 (UTC)
- While there certainly are a few comments supporting moving parts of GENDERID into BLP, I don't see anything close to a consensus or even an emerging consensus. I also don't see anyone in the above discussion having mentioned the public figure changes that are part of this proposal. Once again I agree with the points that Blueboar and SMcCandlish have made, either move the guidance or change the guidance. Don't do both at the same time. Sideswipe9th (talk) 16:22, 6 August 2023 (UTC)
- But policy opponents will likely assume that a proposed move is motivated by a desire to make changes under more friendly circumstances, so there's sort of a linkage. Wehwalt (talk) 18:03, 6 August 2023 (UTC)
- What is amusing is that I have the exact same concern about leaving it here (“hidden away” as a section within a “Style” guideline). By promoting it to its own guideline, I would expect that any proposed changes would be spotted sooner, and can be discussed by a wider selection of the community. Blueboar (talk) 18:42, 6 August 2023 (UTC)
- This page has 773 watchers at present. A new page would, by default, start with 0. There's also the matter of what status it should have if it's moved out of the MOS. I would support an essay, but I would oppose any attempt to enshrine this as guideline or policy while the NPOV conflict remains. —Locke Cole • t • c 18:04, 7 August 2023 (UTC)
There's also the matter of what status it should have if it's moved out of the MOS.
That's easy. GENDERID is already a guideline, and is regularly enforced as such at both content and behavioural noticeboards. As such any move to a stand alone location would, at minimum, also be a guideline to keep parity.while the NPOV conflict remains
While this has been going on, I've re-read every formative discussion on the text of the guideline (ie those that were on the text of the guideline or lead to changes of it, and not application of it). In doing so I discovered that NPOV concerns have been raised by a handful of editors in total, across the hundreds contributing to the various discussions. The views that you're expressing do not seem to be representative of the broader community consensus on this. Sideswipe9th (talk) 18:46, 7 August 2023 (UTC)GENDERID is already a guideline
It's a style guideline and part of the manual of style. It is not a traditional content guideline.As such any move to a stand alone location would, at minimum, also be a guideline to keep parity.
This would not be parity, but a promotion by fiat unless it was accompanied by a community conversation that showed support for such a promotion.The views that you're expressing do not seem to be representative of the broader community consensus on this.
NPOV is non-negotiable, whether a community of editors supports something is irrelevant. If you want to split it off and promote it, you'll need to address these issues or face the reality that it will likely fail. —Locke Cole • t • c 20:29, 7 August 2023 (UTC)- WP:NPOV is non-negotiable; however your particular interpretation of NPOV is very much negotiable. It seems to be a very small minority, in fact.
- Like it or not, all interpretation of policy on Wikipedia is determined by consensus. If you really want to settle the issue, we can take it to an RFC. But if not, nobody has any obligation to WP:SATISFY you or your decidedly minority interpretation of WP:NPOV. Loki (talk) 01:24, 8 August 2023 (UTC)
This policy is non-negotiable, and the principles upon which it is based cannot be superseded by other policies or guidelines, nor by editor consensus.
I'll note that WP:SATISFY is an essay. We'll go with the policy here. But we won't be sacrificing our neutrality on the altar of WP:RGW just because a vocal minority (the small group here) wishes it so. The community decided the principles of NPOV are above consensus decision making, and likely rightly so if the conversations here are any indicator of how quickly some groups are willing to set aside our neutrality in the name of "feeling good" or some misguided desire to "respect" people in a way that society (and more importantly, our sources) have not. There is genuine real-world progress to be made on these issues, but Wikipedia cannot be the "leader" of change that some here seem to be pushing. —Locke Cole • t • c 16:19, 8 August 2023 (UTC)- NPOV is indeed policy, but what NPOV means in any given scenario can only be determined by consensus. You seem to be (nearly?) the only person here who thinks a person's name is a point of view, and thus the (nearly?) the only person who thinks including or not including a person's former name is something that is of any relevance to NPOV. This is exactly the same way that reasonable editors may disagree about whether an actor should be primarily referred to by their stage name or their real name, but that disagreement is not an NPOV matter. Thryduulf (talk) 21:43, 8 August 2023 (UTC)
- This page has 773 watchers at present. A new page would, by default, start with 0. There's also the matter of what status it should have if it's moved out of the MOS. I would support an essay, but I would oppose any attempt to enshrine this as guideline or policy while the NPOV conflict remains. —Locke Cole • t • c 18:04, 7 August 2023 (UTC)
- What is amusing is that I have the exact same concern about leaving it here (“hidden away” as a section within a “Style” guideline). By promoting it to its own guideline, I would expect that any proposed changes would be spotted sooner, and can be discussed by a wider selection of the community. Blueboar (talk) 18:42, 6 August 2023 (UTC)
- But policy opponents will likely assume that a proposed move is motivated by a desire to make changes under more friendly circumstances, so there's sort of a linkage. Wehwalt (talk) 18:03, 6 August 2023 (UTC)
- Comment - While the majority opposes the specific proposal by Bluerasberry, there are five comments that suggest moving the content guideline to BLP would be an improvement. Considering the hurdle of getting agreement for a new exception at BLP, I think my proposal is about the best you can get. Cuñado ☼ - Talk 18:24, 6 August 2023 (UTC)
- There is a difference though between simply moving part of the existing guideline to BLP, which some editors do seem to support above (though not yet a consensus), and moving part of the existing guideline while adding to it, which no-one other than yourself seems to support.
- We could very easily make a proposal here that just replicates the existing inclusion guidance into the relevant portions of BLP, and that otherwise does not contain the new public figure and "made the name public post-transition" exemptions. Simply moving the existing guidance without any significant change to scope is a far easier thing to "sell" to the community than moving it and changing it at the same time. Sideswipe9th (talk) 16:58, 7 August 2023 (UTC)
- If you propose that we move to BLP to exclude all former names unless they were notable under the previous name, it would fail. I think even my proposal might fail for the opposite reason you're saying, due to being overly censoring. Cuñado ☼ - Talk 17:34, 7 August 2023 (UTC)
If you propose that we move to BLP to exclude all former names unless they were notable under the previous name, it would fail.
Outside of IAR, we already exclude all former names unless the person was notable under the former name. Moving the relevant parts to BLP for something we already have a long standing consensus for and have been doing routinely for years is much easier to do than adding wholly new exemptions or moving and adding new exemptions.- The problem with this proposal is that it's trying to do two things at once. Move part of the guidance to BLP, that is already enforced as though it were part of BLP, and add a new exemption. As multiple editors have said now, those need to be done separately. Sideswipe9th (talk) 18:52, 7 August 2023 (UTC)
- If you propose that we move to BLP to exclude all former names unless they were notable under the previous name, it would fail. I think even my proposal might fail for the opposite reason you're saying, due to being overly censoring. Cuñado ☼ - Talk 17:34, 7 August 2023 (UTC)
Draft RFC
I'd like to get feedback on this proposal before taking it to VPP. Assume a preamble and option to oppose all.
Option 1 - Expand MOS:GENDERID to deceased |
|---|
|
Add this paragraph to MOS:GENDERID: For deceased transgender or non-binary persons, their birth name or former name (professional name, stage name, or pseudonym) should be included in their main biographical article only if the name is documented in multiple secondary, reliable sources containing non-trivial coverage of the person. |
Option 2 - Move content restriction to WP:BLPNAME with normal privacy exceptions, and revise down MOS:GENDERID |
|---|
|
Add this paragraph to the end of WP:BLPNAME: It is reasonable to assume that a transgender or non-binary individual would not want a former name disseminated, and it should be removed unless the person was notable under the name, it has been widely published by reliable sources, or it may be reasonably inferred that the individual does not object to the name being made public.[a]
Revise MOS:GENDERID to remove content restrictions and other cleanup: Refer to any person whose gender might be unclear with the name and gendered words (e.g. pronouns, waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources. The former name of a transgender or non-binary person must not be given undue weight or overemphasis. It may be placed later in the lead or elsewhere in the article instead of the first sentence, to avoid giving it undue prominence. Articles or other works that were published under a pre-transition name may use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnote. Added back in:Outside the main biographical article, generally do not discuss in detail changes of a person's name or gender presentation unless pertinent. When the former name or gender is not included in the article, avoid confusing constructions (Jane Doe fathered a child) by rewriting (e.g., Jane Doe became a parent). If the former name appears in a quotation, the article may need to paraphrase, elide, or use square brackets to replace portions of quotations to avoid deadnaming or misgendering. Do not replace or supplement a person's former name with a current name if the two names have not been publicly connected and connecting them would out the person. In rare cases where exact wording cannot be avoided (e.g. pun, rhyme, album cover), the quotation or work may be included.
|
Option 3 - Move content restriction to WP:BLPNAME with only exception for notability, and revise down MOS:GENDERID |
|---|
|
Add this paragraph to the end of WP:BLPNAME: It is reasonable to assume that a transgender or non-binary individual would not want a former name disseminated, and it should be removed unless the person was notable under the name.[a]
Revise MOS:GENDERID to remove content restrictions and other cleanup (same wording as Option 2): Refer to any person whose gender might be unclear with the name and gendered words (e.g. pronouns, waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources. The former name of a transgender or non-binary person must not be given undue weight or overemphasis. It may be placed later in the lead or elsewhere in the article instead of the first sentence, to avoid giving it undue prominence. Articles or other works that were published under a pre-transition name may use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnote. Added back in:Outside the main biographical article, generally do not discuss in detail changes of a person's name or gender presentation unless pertinent. When the former name or gender is not included in the article, avoid confusing constructions (Jane Doe fathered a child) by rewriting (e.g., Jane Doe became a parent). If the former name appears in a quotation, the article may need to paraphrase, elide, or use square brackets to replace portions of quotations to avoid deadnaming or misgendering. Do not replace or supplement a person's former name with a current name if the two names have not been publicly connected and connecting them would out the person. In rare cases where exact wording cannot be avoided (e.g. pun, rhyme, album cover), the quotation or work may be included.
|
Cuñado ☼ - Talk 19:18, 9 August 2023 (UTC)
- I've some thoughts on the phrasing of options 2 and 3, but have an immediate question on the format. While option 2 and 3 are clearly mutually exclusive, due to the conflicting nature of what they'll respectively add to BLPNAME, is option 1 supposed to be mutually exclusive to 2 and 3? Or will this be the sort of RfC where you could !vote "option 1 and 2" or "option 1 and 3"? Sideswipe9th (talk) 19:22, 9 August 2023 (UTC)
- The question of deceased individuals can't go in BLP because it is about living or recently-deceased persons. I (personally) think it also can't go in the MOS, but considering that the last two RFCs came close to doing exactly that, then option 1 is there. I think to expand the exclusion of deadnames to deceased individuals you need to figure out a policy/guide that makes sense and run a policy RFC to do exactly that, or create a new one. Would it help to include in the preamble that option 1 can be combined with other options to enshrine an MOS-based policy about past-RDP deadnames? Cuñado ☼ - Talk 19:35, 9 August 2023 (UTC)
Would it help to include in the preamble that option 1 can be combined with other options
Perhaps, though that particular clause might just be better handled as a separate RfC, or as a separate question within one overall RfC. I'm not entirely sure that the drafting of that text has reached a conclusion yet and I wouldn't want to pre-empt it by placing a non-final version of it in here. The alternative would be to wait until that process and this process has finished and we have finalised text for all of the options/options. Sideswipe9th (talk) 19:43, 9 August 2023 (UTC)
- The question of deceased individuals can't go in BLP because it is about living or recently-deceased persons. I (personally) think it also can't go in the MOS, but considering that the last two RFCs came close to doing exactly that, then option 1 is there. I think to expand the exclusion of deadnames to deceased individuals you need to figure out a policy/guide that makes sense and run a policy RFC to do exactly that, or create a new one. Would it help to include in the preamble that option 1 can be combined with other options to enshrine an MOS-based policy about past-RDP deadnames? Cuñado ☼ - Talk 19:35, 9 August 2023 (UTC)
- If I'm reading this right, wouldn't options 2 and 3 remove large chunks of the GENDERID guidance without moving them to any other page? Firefangledfeathers (talk / contribs) 19:28, 9 August 2023 (UTC)
- Thoughts on the phrasing of options 2 and 3. Beyond the text that's moving to BLP, and the excising of the examples, there's also some key elements of the existing version of GENDERID that have been removed entirely. I'm using del and ins tags below to (hopefully) highlight the differences a little more clearly.
- Refer to any person whose gender might be
questionedunclear with the name and gendered words (e.g. pronouns,man/woman/person,waiter/waitress/server) that reflect the person's most recent expressed self-identification as reported in the most recent reliable sources, even if it does not match what is most common in sources. This holds for any phase of the person's life, unless they have indicated a preference otherwise. Outside the main biographical article, generally do not discuss in detail changes of a person's name or gender presentation unless pertinent. Where a person's gender may come as a surprise, explain it on first occurrence, without overemphasis. Avoid confusing constructions (Jane Doe fathered a child) by rewriting (e.g., Jane Doe became a parent).The former name of a transgender or non-binary person must not be given undue weight or overemphasis. It may be placed later in the lead or elsewhere in the article instead of the first sentence, to avoid giving it undue prominence.In articles on works or other activity by a living trans or non-binary person before transition, use their current name as the primary name (in prose, tables, lists, infoboxes, etc.), unless they prefer their former name be used for past events. If they were notable under the name by which they were credited for the work or other activity, provide it in a parenthetical or footnote on first reference; add more parentheticals or footnotes only if needed to avoid confusion.Articles or other works that were published under a pre-transition name may use their current name as the primary name while describing the work, while crediting the prior name in parentheticals or footnote.- When the former name or gender is not included in the article, avoid confusing constructions (Jane Doe fathered a child) by rewriting (e.g., Jane Doe became a parent). If the former name appears in a quotation, the article may need to Paraphrase, elide, or use square brackets to replace portions of quotations to avoid deadnaming or misgendering
, except. Do not replace or supplement a person's former name with a current name if the two names have not been publicly connected and connecting them would out the person. in rare cases where exact wording cannot be avoided, as where there is a pun on the notable former name, etc.(e.g. pun, rhyme, album cover) the quotation or work may be included- Critic X said "Juno needs a fine [actor] to play its pregnant teenage star, and [Elliot] Page has shown [himself] to be the perfect [man] for the job." involves many bracketed changes, so is better paraphrased: Critic X argued that portraying the pregnant teenage lead in the film Juno required a fine acting talent, and said that Page had proved perfect for the job.
In source citations, do not remove names of authors, or references to former names in titles of works. If the author is notable, the current name may be given, for example as "X (writing as Y)". Do not replace or supplement a person's former name with a current name if the two names have not been publicly connected and connecting them would out the person.
- Refer to any person whose gender might be
- Some of the insertions and deletions are where sentences have been moved about, or subject to some minor word changes that don't significantly change the meaning. However there are several sentences that I'll now highlight separately that have been removed entirely
- even if it does not match what is most common in sources. This holds for any phase of the person's life, unless they have indicated a preference otherwise
- Outside the main biographical article, generally do not discuss in detail changes of a person's name or gender presentation unless pertinent.
- In articles on works or other activity by a living trans or non-binary person before transition, use their current name as the primary name (in prose, tables, lists, infoboxes, etc.), unless they prefer their former name be used for past events.
- Note while some of this text has been moved, there is a significant change between
use their current name as the primary name
andmay use their current name as the primary name
- Note while some of this text has been moved, there is a significant change between
- In source citations, do not remove names of authors, or references to former names in titles of works. If the author is notable, the current name may be given, for example as "X (writing as Y)".
- I'm very concerned that once again we're looking at a proposal that radically alters the scope of the current version of GENDERID while also moving or rewording portions. It's one thing to move portions of the guideline to BLP and make small textual changes to accommodate the move, while keeping parity with the current scope of the guidance. It's another thing entirely to reduce the scope of the guidance, while moving portions of it to BLP. Until the text of the guidance that will remain as part of GENDERID in options 2 and 3 maintains parity with the current scope of the guidance, this option cannot be brought forward to an RfC. Sideswipe9th (talk) 20:21, 9 August 2023 (UTC)
- I have made a good-faith draft to clean up the section and accommodate moving content restrictions to the policy page. The specific examples you brought up either do not "radically alter" the scope or are wordings already discussed on this page. For example, Tamzin previously commented,
In the "Articles or other works" bit, there should still be an exception for those who prefer to be referred to by pre-transition names.
Which resulted in the change to "may use their current name" addressing works published under pre-transition names. In another example,even if it does not match what is most common in sources
is redundant and unnecessary. You have the right to oppose all of my efforts, but you can't insist that itcannot be brought forward to an RFC
with specious complaints. Due to this topic having a history of WP:GAME and WP:ADVOCACY by WP:ACTIVISTs (as noted in numerous RFC comments) I don't expect 100% agreement on this page but I welcome any feedback to make it a better proposal. Cuñado ☼ - Talk 21:23, 9 August 2023 (UTC)- The feedback I'm giving is the same feedback that SMcCandlish, -sche, Loki, Tekrmn, Blueboar, and I have given you already at multiple stages throughout these discussions. Stop trying to do two things, move/rewrite GENDERID, and change the scope of GENDERID at the same time. Either propose a split that otherwise keeps parity with the existing guideline with some minor textual changes to accommodate the split, or propose an amendment that alters the scope of the existing guideline. Sideswipe9th (talk) 22:26, 9 August 2023 (UTC)
- I agree with Sideswipe9th et al. Trying to make multiple changes at the same time is all-but guaranteed to result in no consensus for any of them and possibly even consensus against all of them. You stand a much higher chance of getting consensus for both if they're discussed one at a time, so pick which you think is the highest priority and discuss only that. When discussion of that has concluded and consensus reached on a change, then return to the other matter. Thryduulf (talk) 23:03, 9 August 2023 (UTC)
- You're suggesting running two RFCs? How many people have been commenting like this or this, ready to put a lid on all the GENDERID discussion? And these complaints about my revision are an example of why it's helpful to incorporate a cleanup into a single RFC. My cleanup has already received generally positive comments from less-active editors. The only scope altering is to move inclusion criteria to BLP. I'll respond to each of Sideswipe9th's points here to show what I mean:
- Removed:
even if it does not match what is most common in sources. This holds for any phase of the person's life, unless they have indicated a preference otherwise
- this is redundant to the "Refer to any person" in the previous sentence, and the "unless they have indicated a preference" is just obvious. It could be included, but it's a question of style and quality of writing, not scope of guideline. Even though it's not my preference, I can put it back in to build unity. - Removed:
Outside the main biographical article, generally do not discuss in detail changes of a person's name or gender presentation unless pertinent.
- 1) this is MOS/BIOGRAPHY and it's talking about outside of biographies, 2) it's in scope for removing in the spirit of moving content criteria out of the MOS, 3) also obvious given many relevant content policies. - Changed
use their current name as the primary name
tomay use their current name as the primary name
for pre-transition publications. This was not my idea but I was incorporating a recommendation from Tamzin:In the "Articles or other works" bit, there should still be an exception for those who prefer to be referred to by pre-transition names.
Nobody opposed this until now. As I've been reading hundreds of RFC comments over the last 3 months, proposing drafts and soliciting feedback, I'm trying to get the best version forward. Similarly, the change in the first sentence from "questioned" to "unclear" was a result of feedback from Jerome Frank Disciple and SMcCandlish on this page. - Removed:
In source citations, do not remove names of authors, or references to former names in titles of works. If the author is notable, the current name may be given, for example as "X (writing as Y)".
This is poorly worded and the section has become a bit bloated. See WP:KISS. If you think it's important, please propose a better wording. This is a style example and has absolutely nothing to do with scope. Cuñado ☼ - Talk 00:16, 10 August 2023 (UTC)It could be included, but it's a question of style and quality of writing
The content that refers to is part of the Manual of Style. It makes sense for style guidance to be a part of that text.this is MOS/BIOGRAPHY and it's talking about outside of biographies
Per the first paragraph of WP:MOSBIOThis page sets out guidelines for achieving visual and textual consistency in biographical articles and in biographical information in other articles
. All biographical content, regardless of whether it's in a biography or any other article is subject to MOSBIO.Nobody opposed this until now.
I cautiously opposed it on 24 July. However that is separate to the reason I'm opposing it now. The reason I'm opposing it now is because it represents a significant departure from the current scope of the guideline, by adding a new exclusion criteria to GENDERID. We should not be launching an RfC that alters both the scope and location of the guideline at the same time. Do one of those two actions, and do that one action well. Now if it was only that change of scope that was being discussed, I would be somewhat more inclined to support it, but I still think it has issues that require further wordsmithing.This is poorly worded and the section has become a bit bloated.
Possibly, and given the widespread shift in academic journals with regards to allowing for silent retrospective name changes for trans and non-binary authors this might even be (partially) outdated. That said, removing it again represents a significant change in scope of the guideline, in this case by removing guidance on how to handle source author name changes in citations. However saying this is a style example is again irrelevant, because this is referring to content that in options 2 and 3 will be remaining in MOSBIO. And as I've said above, MOSBIO refers to all biographical content and not just biographical articles. Sideswipe9th (talk) 00:59, 10 August 2023 (UTC)
- I agree with Sideswipe9th et al. Trying to make multiple changes at the same time is all-but guaranteed to result in no consensus for any of them and possibly even consensus against all of them. You stand a much higher chance of getting consensus for both if they're discussed one at a time, so pick which you think is the highest priority and discuss only that. When discussion of that has concluded and consensus reached on a change, then return to the other matter. Thryduulf (talk) 23:03, 9 August 2023 (UTC)
- The feedback I'm giving is the same feedback that SMcCandlish, -sche, Loki, Tekrmn, Blueboar, and I have given you already at multiple stages throughout these discussions. Stop trying to do two things, move/rewrite GENDERID, and change the scope of GENDERID at the same time. Either propose a split that otherwise keeps parity with the existing guideline with some minor textual changes to accommodate the split, or propose an amendment that alters the scope of the existing guideline. Sideswipe9th (talk) 22:26, 9 August 2023 (UTC)
even if it does not match what is most common in sources. This holds for any phase of the person's life, unless they have indicated a preference otherwise
- If I hear wider support that this is important I'll include it. Again, not a scope change.the first paragraph of WP:MOSBIO
- you win! I'll add it back in to the MOS text.may use their current name as the primary name
- nobody opposed this particular change until now, and the change was in drafts #2,3,4, and 5 above. The link you gave of you opposing it is just some general opposition to Tamzin's draft (#5). Perhaps some wording along the lines of "...unless they have a preference otherwise" would be in order, but I don't think it is very consequential whether we use "should" or "may". The proposal is clear that we assume privacy concerns unless the individual says otherwise, so that would override the "should". If I hear wider support that this is important I'll change to "should".In source citations, do not remove names of authors, or references to former names in titles of works. If the author is notable, the current name may be given, for example as "X (writing as Y)".
- Please propose a better wording. Both sentences look like they were formed by committee. To me at least, it's not clear what situation it's trying to address, or whether the "author is notable" refers to the new or former name. Try writing like you're explaining it out loud.- I realize that I should not have used the phrase "style" in my last comments because this is the manual of STYLE. I was talking more about style of writing the guideline, not style guidance. As in, each person has their own style of writing. I'll try to be more clear. Cuñado ☼ - Talk 17:03, 10 August 2023 (UTC)
- I have made a good-faith draft to clean up the section and accommodate moving content restrictions to the policy page. The specific examples you brought up either do not "radically alter" the scope or are wordings already discussed on this page. For example, Tamzin previously commented,
- Agreed with Thryduulf and Sideswipe. This RFC is trying to do too much in one question. "What should be the wording added to the guideline for deceased individuals?", "Where should the guideline be?" and "Should we have extra exceptions other than notability?" are three different questions that should all be asked separately. It'd IMO be fine to ask those three different questions at the same time but they are three different questions and should be asked separately. So for instance:
Question 1 - Wording for deceased individuals |
|---|
|
Which of the following paragraphs should be added to the guideline on referring to trans people?
|
Question 2 - Location of the guideline |
|---|
|
Where should the main guideline on referring to trans people be located?
|
Questions 3 and 4 - Exceptions |
|---|
|
Which of the following reasons should require mention of a trans person's former name in the lead of their article? (You may select more than one.)
Which of the following reasons should allow mention of a trans person's former name in their article? (You may select more than one.)
|
- Loki (talk) 04:18, 10 August 2023 (UTC)
- Given how many contentious MOS:DEADNAME debates we have had recently, I would strongly encourage any RfC we have to be simple, and to propose something that is all but certain to receive consensus.
- I don't believe Questions 2, 3, or 4 meet this definition; Question 2 in particular, as a proposal to change the level of this guideline, should be a standalone debate.
- When we do hold Question 4, I would also suggest
The person's former name has been widely published by reliable and secondary sources
, based on WP:BLPPRIVACY - For question 1, I would suggest we have a single wording to propose, as a support/oppose option. Trying to give multiple options will make the debate more contentious and less likely to find any consensus; I would suggest
For deceased transgender or non-binary persons, their birth name or former name (professional name, stage name, or pseudonym) should be included in their main biographical article only if the name is documented in multiple secondary, reliable sources containing non-trivial coverage of the person.
However, I am still hoping we can avoid an RfC on that question. BilledMammal (talk) 04:43, 10 August 2023 (UTC) - I think Loki's proposal is actually doing more things than mine was. My proposal really only has one main fork: should we add a deceased exception to MOS, or move content criteria to BLP? Due to the inability to agree on this talk page, there is a second fork of whether the BLP move should be limited to notability only. Loki's question 2 would be a disaster by asking a question of where policy should go without specific wording, resulting in more (likely failed) RFCs in the future. Keep it simple. Cuñado ☼ - Talk 17:12, 10 August 2023 (UTC)
- What Loki's proposal is doing is more clearly delineating the change aspects of your proposal. Your proposal's option 2 is implicitly asking questions 3 and 4, because it contains text that incorporates those questions (ie the new public figure exemption). If Loki's proposal seems to be doing too much to you, this might perhaps give you insight into why I've been opposing your proposals, because by my reading yours and Loki's proposal have the same overall amount of change to the guideline. The differences are in the presentation. Sideswipe9th (talk) 17:26, 10 August 2023 (UTC)
- For question 1, the lesson we should learn from the first of the two recent RfCs is that too many options makes determining consensus difficult. Ideally we should have one reasonably robust option that we're asking a yay/nay on, as that will result in the clearest consensus either way.
- For question 2, we do seem to have at least three mutually exclusive options here; split part to BLP while keeping the rest in MOSBIO, elevate all to a standalone guideline, or no change. I'm not sure we can pare that down any further than that. RfC formatting wise, that could be asked akin to the three question format of the first of the two recent RfCs, where we have one RfC tag and asking multiple independent questions. But I do fear that in total we might be asking too much at once. While I do agree with Cunado that question 2 would benefit from more concrete wording in principle, the way that I'm reading Loki's proposal here is that it's more of a draft formatting/structural proposal on how to present and ask the generalised questions, than one that has the specific phrasing for any given question or option in place.
- For questions 3 and 4, those maybe need to be standalone RfCs. They're wholly new exemptions, and both the phrasing and location of the finalised text would be highly dependent on the outcome of question 2. I'd worry that asking this, alongside the question on splitting/moving GENDERID, would come across as too much simultaneous change by the broader community. Sideswipe9th (talk) 17:21, 10 August 2023 (UTC)
- FWIW I am also okay with simply skipping Questions 3 and 4. I don't think there's really much cause to ask those right now. I included them because I was making my version of Cuñado's proposal, and Cuñado's proposal included those questions. Loki (talk) 18:38, 10 August 2023 (UTC)
- Personally, I think the questions are distinct enough that I would trust the community at VPP to be able to parse them without much impact on the outcome of any one proposal, but, at the same time, I don't see any harm in staggering them either. However, I would suggest a different order of operations:
- Question 1: It's the simplest inquiry, has fairly streamlined language at this point, and I believe it is something the community can get behind at this point. Let's try to get the benefit of inertia from the start.
- Questions 3&4: I actually think it maybe makes sense to run these concurrent with Question 1, as they really should be considered in tandem insofar as each contains language that will impact the others. I also think that this approach runs the least chance of fatiguing the community's remaining reserves of patience for proposals in this area. But we can always try them back-to-back; it's possible that one of Question 1's proposed wordings have hit enough of a sweet spot that the support will be overwhelming and that the mood surrounding this cluster of disputes will turn much more positive in light of finally having a consensus.
- Question 2: I agreed with Cuñado that a serious discussion about where this wording ultimately goes is important (and honestly, there's strong arguments for all the variations, imo), but I really do think it can and should wait until we iron out the actual language. Besides, the discussion about the language itself will heavily inform the pragmatics of determining what will go where.
- So, either Q1, Q3 and Q4 ---> Q2. Or Q1 ---> Q3 and Q4 ---> Q2. But I do think the community can handle all four at once if it came down to it. What has held up the previous proposals has been less procedural hitches and more a lack of preparation at the front end, I suspect (no offense intended to anyone who worked on those proposals, but we've just had a very healthy amount of discussion dialing the current proposals in, further informed by the previous discussions. SnowRise let's rap 02:26, 11 August 2023 (UTC)
- Personally, I think the questions are distinct enough that I would trust the community at VPP to be able to parse them without much impact on the outcome of any one proposal, but, at the same time, I don't see any harm in staggering them either. However, I would suggest a different order of operations:
- FWIW I am also okay with simply skipping Questions 3 and 4. I don't think there's really much cause to ask those right now. I included them because I was making my version of Cuñado's proposal, and Cuñado's proposal included those questions. Loki (talk) 18:38, 10 August 2023 (UTC)
- I don't think we should combine "moving the guideline" and "modifying the guideline"; those are two completely separate things and should be totally separate unrelated RFCs. The bare minimum requirement for any move RFC should be that the overall guidelines will not change as a result of any options in it, and such an RFC should clearly state at the top that no change to the substance of the guideline can result from it regardless of outcome; if it's impossible to do that for one reason or another then the guideline shouldn't be moved. "We should cut it it fits in slot XYZ" isn't a good reason to change a guideline that has received as much input, discussion, and consensus-building as this. If people want to tweak, trim, or otherwise alter the guideline that should be a totally unrelated RFC that does not discuss moving it at all - trying to combine everything into a single do-everything RFC for something with as much history and complexity as this is doomed to failure. And if people want to cover the same material elsewhere or incorporate this elsewhere, that can be done without substantitive changes here. --Aquillion (talk) 21:33, 11 August 2023 (UTC)
- I confess to some confusion. What are questions 3 and 4 "exceptions" to? Are the lists of four items meant to be exhaustive? What is a "public figure"? How does "public figure" differ from 'notable' in the Wikipedia sense? EddieHugh (talk) 17:08, 12 August 2023 (UTC)
- This is specifically supposed to be a rephrasing of Cuñado's RFC wording. So I don't have a great answer for you on the public figure question. Questions 3 and 4 are supposed to be exceptions to the general rule not to use/mention a trans person's deadname. None of these lists are necessarily exhaustive, feel free to suggest things. Loki (talk) 18:43, 12 August 2023 (UTC)
RfC at VPP
RfC has started at Wikipedia:Village pump (policy)#RfC on GENDERID in BLP. Cuñado ☼ - Talk 18:53, 11 August 2023 (UTC)
But this is a good time for a page break anyway: is a proposal nearing ready?
I'd like to suggest that Loki's presentation of the issues, divided among three potential proposals, looks to have a the requisite levels of simplicity and clarity to my eyes, and has taken the feedback of the above discussions into account, regarding what we can predict from the last two RfCs and how ambitious the new proposed wording can be while still standing a decent chance of capturing community consensus. The advocates for increasing the privacy protections of trans individuals as biographical subjects have adjusted their approach, and I am hopeful that those with strong NOTCENSORED conerns among the respondents of the next RfC at VPP will also give some ground in light of / as a result of the extra level of preparation and tailoring that went into this language.
As such, I'd like to read the room and see if we are good to go on this in the coming week or so, pending some additional tweaks to the precise language? (For example, do we want to leave the inquiries of Q3/Q4 open-ended as they stand now or propose precise language?) If there is support to propose this soon, I think the following timeline is most advisable:
- We ask Q1 at some point in the next week. The OP should foreground the fact that this will be a series of RfCs but that they will be held in series in order to not confuse respondents, overwhelm this page with feedback from what is already likely to be a large and involved discussion, or tax the community's patience on these matters unnecesarily. We let this first RfC run its course at VPP for 30 days and hopefully get a timely close with a clear consensus.
- Repeat the process with the complimentary (and I think clverly presented) wording of Q3 and Q4. The results of this discussion should, by a combination of the responses to each question, create a sense of the range of acceptable commentary about deadnames in relevant articles. Wording can then be drafted for the policy with close fidelity to the outcome. The only concern I have here is that with a two-part inquiry, each of which allows for four options, we may not end up with a clear consensus. However, it's possible we will and even if we don't the feedback may be of substantial help moving forward. Given the complexity of the issues involved, and the foregoing disputes, I think this is a reasonable way to present the inquiry for this cluster of issues and get useful community input. Again this should run for the full 30 days, needless to say.
- Once the language is dialed in, if we have remainign appetite for it and a strong consensus here that the matter should be pursued further, we can discuss a third RfC for purposes of re-distributing the resulting language of GENDERID between BLP and MoS sections.
I appreciate this puts us potentially more than three months out before all of this gets resolved, but there seems to clear consensus above not to run all of these inquiries concurrently, and that may well be for the best (and ultimately save a lot of time and effort) in the long run. Incidentally, my thanks to everyone for pulling together and trying to meet in the middle after a tumultuous start to this series of discussions. Thoughts? SnowRise let's rap 01:59, 12 August 2023 (UTC)
- I agree with Loki's suggested structure and with your suggested sequencing and timing with two caveats
- I'd consider waiting a week or so between each part (maybe more if discussion was intensive up to or beyond the 30 days) to further mitigate against fatigue and reduce conflating of issues.
- I would avoid starting it until at least a full day or so after the ANI discussion about Cuñardo has concluded.
- Regarding the actual options, I'm not completely sure I am happy with the language of all the options yet (I need to do more thinking), but I don't think we're far off. If others agree with the structure and sequencing then we should focus energy on the wording of Q1 for now, especially as feedback from that may inform later options. Thryduulf (talk) 02:17, 12 August 2023 (UTC)
- All good points, I think. SnowRise let's rap 07:05, 12 August 2023 (UTC)
- Yep to all of that. — SMcCandlish ☏ ¢ 😼 11:40, 12 August 2023 (UTC)
- Yeah, I like this schedule with Thryduulf's suggestions, and Loki's structure. Assuming we're all not exhausted, we'll have the time while Q1 is running to get the wording sorted for questions 3 and 4.
- On the wording of the amendment for question 1, I'm still concerned that the barrier for inclusion is too low with respect to the consensus established by the first RfC. It's not enough of a concern to say "we can't launch the RfC yet", but it is enough that I think there might be a slightly better text we could use. There's one editor who I'd like to hear from on this, who has contributed to earlier parts of this discussion but not on this specific issue, but I'd like to check with you all if it's OK to notify them. Is there any objections to asking that person for an opinion here? Sideswipe9th (talk) 23:16, 12 August 2023 (UTC)
- I'm curious who you mean but it doesn't matter for me, I'm fine with asking them. Loki (talk) 02:33, 13 August 2023 (UTC)
- If they contributed to the broader series of discussions already, at any point, I see no reasonable grounds for objection to notifying them, if being pro forma about canvassing / soliciting input is your concern. And in a more general sense, the more perspectives, the better is my general rule of thumb. SnowRise let's rap 06:01, 13 August 2023 (UTC)
- Yeah it's mostly a canvassing concern. I didn't want people to ask "why are you pinging that one editor", and didn't want to cause any fuss if anyone had any objections. Sideswipe9th (talk) 22:45, 13 August 2023 (UTC)
- Which editor are you referring to? I'll probably be fine with notifying them; in general though I don't want to make the proposal any stricter - I want something that will receive consensus, and if in practice we find issues with it we can use those issues as evidence towards strengthening it through a future discussion. BilledMammal (talk) 06:06, 13 August 2023 (UTC)
- In terms of strictness, the RFC we're following up came to the consensus that the rule should be more permissive than "never" but more restrictive than "Principle of least astonishment / majority of sources" and so I cannot agree to presenting options outside that range. My preference would be include somewhere between 2 and 4 options that represent different points within the range, which gives the best chance at community consensus. Regarding pings, I have no objection to pinging someone involved previously in this discussion as long as they have not since been topic banned. Thryduulf (talk) 10:40, 13 August 2023 (UTC)
My preference would be include somewhere between 2 and 4 options that represent different points within the range, which gives the best chance at community consensus.
I would strongly oppose that. We have tried multiple ambitious RfC's, and they have done nothing but exhaust community patience. We need to run with a single conservative proposed wording, that is guaranteed to get community consensus. My wording has broad acceptance, even if some editors think it is too strong, and others thing it is too weak. Let us use that, and if down the line we find it is not strict enough we can look at a modifications to address specific issues that are raised. BilledMammal (talk) 12:44, 13 August 2023 (UTC)- I'm with Thryduulf on this. If we present a single option – already knowing that some object to it as too much and others as not enough – then that is simply a recipe for everyone who doesn't agree with it to the precise letter to !vote against it, for reasons that are actually antithetical to each other. Present the range of options, and consensus is much more likely to settle on one of them (statistically speaking, most like in the middle of the range, which might very well be the version you want to run solo anyway). — SMcCandlish ☏ ¢ 😼 12:51, 13 August 2023 (UTC)
- In addition to what SMcCandlish says, those of us discussing things here are not necessarily representative of the community as a whole so what we like may or may not mesh with what the broader consensus us. Also presenting a single option will almost certainly be perceived by some as an attempted fait accompli (even though that is not the intent) and will get opposition on that basis alone (even if the same people would pick that option from a list). Thryduulf (talk) 13:04, 13 August 2023 (UTC)
Also presenting a single option will almost certainly be perceived by some as an attempted fait accompli (even though that is not the intent) and will get opposition on that basis alone (even if the same people would pick that option from a list).
Honestly, I doubt that - most policy proposals have a single option with editors !voting either "support" or "oppose", and I've never seen anyone oppose a proposal on that basis.- If we must include multiple options - and again, I strongly argue against doing so, as multiple option RfC's are far more likely to result in "no consensus" than single option RfC's - I would suggest the following, keeping in mind that any proposal has to be less restrictive than the one most recently rejected by the community:
- For deceased transgender or non-binary persons, their birth name or former name should be included in their main biographical article only if the name is documented in multiple secondary, reliable sources containing non-trivial coverage of the person.
- For deceased transgender or non-binary persons, their birth name or former name should be included in their main biographical article only if the name is widely documented in secondary and reliable sources containing non-trivial coverage of the person.
- For deceased transgender or non-binary persons, their birth name or former name should be included in their main biographical article only if the name is documented in at least one secondary and reliable source.
- For deceased transgender or non-binary persons, their birth name or former name should be included in their main biographical article only if the name is documented in multiple secondary, reliable sources.
- BilledMammal (talk) 13:34, 13 August 2023 (UTC)
- Why "is documented" rather than "has been documented"? If a news source gives the information and then the news source is changed to exclude it, doesn't that set things up for arguments, especially if there are archived copies of the source giving the information? Wehwalt (talk) 14:03, 13 August 2023 (UTC)
- I don't recall why I worded it that way; I didn't have an intention of having it speak on modified news articles. I don't have a strong preference either way. BilledMammal (talk) 14:07, 13 August 2023 (UTC)
- Best to avoid side issues, I'd say. Or, if there's a feeling we should be governed by sources changing, address it directly. Wehwalt (talk) 14:11, 13 August 2023 (UTC)
- I'll see if others have a preference, but if they don't, or if they also prefer "has been documented", I'll switch over to that. BilledMammal (talk) 14:44, 13 August 2023 (UTC)
- I didn't really read the wording that way either, but also I prefer "is documented". The reasoning for adding this language in the first place is that we're trying to suss out whether sources think that it's OK to use this person's former name. So if they change their mind, that's relevant. We're not just looking for proof as to what the name actually is. Loki (talk) 16:30, 13 August 2023 (UTC)
- I agree with Loki. There are multiple reasons a source might remove a name, and all the ones I can think of are relevant to whether we include the name or not (although we wont always follow suit, we should be considering it). Whether a source has ever used the name is relevant to verifiability, which is obviously an absolute prerequisite for even discussing inclusion, but whether it currently does matters more for whether we should. Especially as one of the reasons for a source no longer using a name is because it was incorrect (this is very unlikely for someone who was notable under a previous name but plausible for someone like Brianna Ghey). Thryduulf (talk) 16:46, 13 August 2023 (UTC)
- I didn't really read the wording that way either, but also I prefer "is documented". The reasoning for adding this language in the first place is that we're trying to suss out whether sources think that it's OK to use this person's former name. So if they change their mind, that's relevant. We're not just looking for proof as to what the name actually is. Loki (talk) 16:30, 13 August 2023 (UTC)
- I'll see if others have a preference, but if they don't, or if they also prefer "has been documented", I'll switch over to that. BilledMammal (talk) 14:44, 13 August 2023 (UTC)
- Best to avoid side issues, I'd say. Or, if there's a feeling we should be governed by sources changing, address it directly. Wehwalt (talk) 14:11, 13 August 2023 (UTC)
- I don't recall why I worded it that way; I didn't have an intention of having it speak on modified news articles. I don't have a strong preference either way. BilledMammal (talk) 14:07, 13 August 2023 (UTC)
- Why "is documented" rather than "has been documented"? If a news source gives the information and then the news source is changed to exclude it, doesn't that set things up for arguments, especially if there are archived copies of the source giving the information? Wehwalt (talk) 14:03, 13 August 2023 (UTC)
- Agreed with Thryduulf here. We got a consensus on the first RFC, which had multiple options, and didn't on the second with one option even though it seemed to have consensus while being drafted, so I don't think multiple options is the barrier to consensus BM thinks it is.
- If you think the guideline should be changed but favor permissive wording, then you'll tend to !vote for that if there's an option for that, but against restrictive wording if that's the only option. And vice versa. Loki (talk) 13:57, 13 August 2023 (UTC)
- I find myself agreeing with BilledMammal here. The problem with presenting more than two options is that you can very easily get into a situation where one of the options has the plurality of support, but not the majority of support. This happened most recently with second question of the first RfC, where "never" had the plurality of support (or in the words of someone else who was closing it there was a
near, but not quite reached, consensus for option 3
), but not enough overall to gain consensus. This is why in the second RfC the barrier for inclusion was set very high, as it was to try and respect that consensus, but clearly that failed because it was too high. - If we're set on presenting multiple options, then we should present as few variations as possible to try and minimise the chances of that situation of plurality but still non-consensus from happening again. Sideswipe9th (talk) 23:04, 13 August 2023 (UTC)
- That being said, what if we're looking at this the wrong way around. Instead of presenting several finalised (or mostly finalised) options to the community and asking them to pick one, we instead take a leaf out of a fill-in-the-blank questionnaire. We start with the common base text, eg from the 4 options listed above
For deceased transgender or non-binary persons, their birth name or former name should be included in their main biographical article only if...
and then present a series of options that complete the sentence, egmultiple, reliable sources
,multiple, secondary, reliable sources
,multiple high-quality reliable sources
. Editors then contributing to the RfC can then chose which combination of options how restrictive or non-restrictive they feel this part of the guideline should be. - Or do we think that would that get too messy for a closer to determine consensus on? Sideswipe9th (talk) 23:14, 13 August 2023 (UTC)
- I actually considered that option, but I'm pretty sure that it would reduce the chance of a consensus being produced to around zero as we - and the closer - can't assume that just because someone supports an option is a specific context that they support that option in all contexts. For example, they might support "multiple high-quality reliable sources" when those sources aren't required to include "non-trivial coverage of the person", but that doesn't mean they will support "multiple high-quality reliable sources" when those sources are required to include that coverage.
- As such, the effect of it will be to produce dozens or hundreds of different options, and the likelihood that any of those options will find majority support is minimal. BilledMammal (talk) 23:30, 13 August 2023 (UTC)
- Yeah that's true. Even if you keep the number of options to fill in the blanks small, you can still get a large number of permutations. And as you say, cross checking becomes troublesome unless people are explicitly saying "I support options A/B/C or B/C/E or ...". Sideswipe9th (talk) 23:52, 13 August 2023 (UTC)
- Honestly, this is one of those cases where each side has a hold of the Stick of Truth with a good argument. There are statistical advantages and risks for deadlocks in both approaches:
- Too many options absolutely can dilute support to the point where even a closer making reasonable adjustments for context will not be able to find a single conclusion they can judge as definitely endorsed by consensus. Technically nothing stops the supporters from endorsing more than one option (usually), other than their own reasoning about which options are definitely ill-advisable. But with even the remaining proposals they may view as permissible, they may incline towards a Goldilocks principle and !vote (or at least endorse most strongly) only a subset, or one. At the same time, remember that you're going to have, in a discussion like this, a certain number of people who will be opposed to all options on principle.
- On the other hand, a straight up or down, binary vote has it's own set of pragmatics that also pull up and down. Yes, it's much easier in these cases for two sides to get entrenched. And you're definitely going to lose some people in terms of support for the specific chosen proposal who might have been on board for one of the alternatives. But at the same time the support you do have is generally rowing a little more uniformly in the same direction with their arguments and the weight of their support.
- The thing is, one of the advantages of our methodologies on this project is that there is enough flexibility built into our communal discussions that if someone someone sees the alternatives anyway (and some definitely will in a discussion of the scope of involvement this one will probably be), they can always adjust their feedback accordingly, and you can actually end up with a closer reasonably making consensus conclusions that weren't even included in the original proposal. So in the final analysis, all the 'vote' running statistical pragmatics, process constraints, psychoscial factors, and game theory that might be applied to the different options might play a smaller role than one might think.
- Nevertheless, we have to decide on something, and I think I'm inclined to say keep it on the lower end here. Or at least, let me say this: I know I can support the first wording we have for Q1 right now. I'm not sure what advantage we get from offering the second variant, honestly. Because here's the thing: it's the lesser-strict option (i.e. the one with the larger burden for the person wanting to use a deadname). But interestingly, because of the the way the last discussion shook out, I think it's actually going to appeal more to the on-the-fence community members who previously had concerns about right threshold/burden of proof here.
- Honestly, this is one of those cases where each side has a hold of the Stick of Truth with a good argument. There are statistical advantages and risks for deadlocks in both approaches:
- Yeah that's true. Even if you keep the number of options to fill in the blanks small, you can still get a large number of permutations. And as you say, cross checking becomes troublesome unless people are explicitly saying "I support options A/B/C or B/C/E or ...". Sideswipe9th (talk) 23:52, 13 August 2023 (UTC)
- That being said, what if we're looking at this the wrong way around. Instead of presenting several finalised (or mostly finalised) options to the community and asking them to pick one, we instead take a leaf out of a fill-in-the-blank questionnaire. We start with the common base text, eg from the 4 options listed above
- In terms of strictness, the RFC we're following up came to the consensus that the rule should be more permissive than "never" but more restrictive than "Principle of least astonishment / majority of sources" and so I cannot agree to presenting options outside that range. My preference would be include somewhere between 2 and 4 options that represent different points within the range, which gives the best chance at community consensus. Regarding pings, I have no objection to pinging someone involved previously in this discussion as long as they have not since been topic banned. Thryduulf (talk) 10:40, 13 August 2023 (UTC)
- Because the significant majority roundly rejected "significant coverage of the deadname itself" as a standard. And "non-trivial coverage of the person" sounds a lot more tame than that by comparison. And most of the respondents there will not have been privy to this intervening series of drafting discussions. Their frame of reference will be either as as someone with the last proposal most fixed in their memory, or entirely new to the discussion. So with regard to many of the respondents, I would suspect this wording is going to demonstrate just how much the needle has moved towards the middle for this proposal. Meanwhile, the second option / alternative wording of Q1 is paradoxically less useful to those who want stricter requirements for using the deadname, and yet at the same time less likely to appeal to the editors who are skeptical of the need/advisability of tightening those provisions. So including it seems unlikely to change the result (people will either !vote for Q1-1, or reject a change outright.
- That's not to say that there's not some alternative wording worth offering up here. Per the start of this post. It may be worth splitting the difference between the two arguments here and offering a proposal with two options (well, three really:Add language A, add language B, or no change). But until we see a decent offering (and it was hard enough to arrive at this one, let's remember), I can't see the wisdom of supporting that approach blindly. SnowRise let's rap 17:31, 14 August 2023 (UTC)
- As I'm not seeing any objection, Trystan I was hoping you could give your opinion on the barriers for inclusion listed in in this reply, and the quoted text in this reply. With respect to the two most recent RfCs, are any of these options either too high or too low of a restriction? Sideswipe9th (talk) 22:53, 13 August 2023 (UTC)
- Thanks for the ping. I haven't had the opportunity to stay on top of the recent discussions on this issue, so I don't think I have anything useful to contribute at this stage.--Trystan (talk) 18:37, 15 August 2023 (UTC)
- Trystan that might actually be a benefit here, as it would be useful to hear what someone who hasn't been following this discussion closely has to say about the current selection of choices that will be brought forward to an RfC shortly. Sideswipe9th (talk) 20:22, 15 August 2023 (UTC)
- Thanks for the ping. I haven't had the opportunity to stay on top of the recent discussions on this issue, so I don't think I have anything useful to contribute at this stage.--Trystan (talk) 18:37, 15 August 2023 (UTC)
- The big problem here is that the last RFC closure asked us to find a compromise between “never” and “sometimes”. But that is an impossible task … because anything more permissive than “never” IS “sometimes” (and anything more restrictive than “sometimes” IS “never”). So we keep going in circles. Blueboar (talk) 14:11, 13 August 2023 (UTC)
- If you're looking at it as a ternary of always/sometimes/never, then yes you're right. But if you're looking at it as a spectrum, there are degrees that are more restrictive than sometimes and less restrictive than never (eg "almost never"). Sideswipe9th (talk) 22:46, 13 August 2023 (UTC)
RfC on complex gender identities
How should complementary or complex preferences with regard to gender expression and identity be handled? This applies to article subjects such as Conchita Wurst or Trixie Mattel, where the article contains information both on the person and their stage persona(s), as well as to articles like Eddie Izzard, where the subject's expressed identity does not clearly indicate how they should be referred to under MOS:GID.[a] In such cases, should the article text:
A. Refer to the subject with only one set of pronouns throughout the article
OR
B. Refer to them variably?
Note relevant discussion in the GID inclarity section above. Actualcpscm (talk) 10:34, 13 July 2023 (UTC)
- There is no single “right” answer to this question. A LOT depends on the expressed desires of the subject of the article… which means we often have to figure it out on a case-by-case basis. Blueboar (talk) 12:06, 13 July 2023 (UTC)
- I also feel this is something needing to be thrashed out on individual talk pages. There has been a lot of discussion that can help with guidance on this page and elsewhere.--Wehwalt (talk) 12:10, 13 July 2023 (UTC)
- Hard cases make bad law GMGtalk 12:14, 13 July 2023 (UTC)
- Agree with Blueboar. This isn't the sort of situation where a one-size-fits-all rule can be crafted without creating more problems than are solved. —Carter (Tcr25) (talk) 12:55, 13 July 2023 (UTC)
- I agree with the above people that this is something that needs to be dealt with on a case by case basis, not with a wholesale policy change. (Summoned by bot) I dream of horses (Contribs) (Talk) 13:15, 13 July 2023 (UTC)
- (Summoned by bot)
There is no single “right” answer to this question. A LOT depends on the expressed desires of the subject of the article… which means we often have to figure it out on a case-by-case basis
, per Blueboar but in general, refering to someone variably within an article is a recipe for confusion IMO. The drag artists (Conchita Wurst and Trixie Mattel) have some justification since the articles are ostensibly in the name of the character, rather than the artist, but even so, the articles seem needlessly confusing, both whether the article itself is actually about a performer, or the drag persona they created and in the use of pronouns (the character or creator could be referred to by name throughout). Pincrete (talk) 13:32, 13 July 2023 (UTC) - Case-by-case, follow the reliable sources, lather, rinse, repeat. Do we really need this RfC? Where and with whom did you decide how to frame the RfC question? — JohnFromPinckney (talk / edits) 10:13, 14 July 2023 (UTC)
- I'm sure this is asked with the best of intentions, but... Please please please, not another GENDERID RfC. This is not urgent. The wiki is not burning down. The trans/nonbinary biography space does a pretty good job self-regulating and does not need RfC after RfC on style rules. Give people some time to breathe. -- Tamzin[cetacean needed] (she|they|xe) 02:43, 15 July 2023 (UTC)
Agree I don't keep my pronouns in my sig like Tamzin, but anyone who met me in my thirties or forties would attest that "complex / complementary gender expression" would apply to any bio of me were I somehow most unwelcomely to pass WP:N. So, I claim an "inside view" of this topic, and with that perspective I ask please take a break. I cannot remember a time there were not at least two concurrent pronoun and/or deadname RfCs running in fairly public venues.I see nowhere established an inability of talkpage conversations to handle this corner case. Further, and kindly, I claim that unambiguously [gender]-identifying first name
is a fallacious construct. To step outside this culture for a moment, whenever one of the teachers I worked alongside in China would hear from another teacher the name of a student they didn't know, the first question was always "boy or girl?" Leaving aside the obvious gender-binary cultural blinders, even the idea of an unambiguously gender-identifying first name is unknown is some settings.And for a counterexample from Western culture, one of the easy ways people in our department at grad school used to suss out whether some student was actually familiar with the secondary literature or had just read a few articles here or there would be to bring up Michael Nylan, now the most prominent active Han dynasty historian in the Western world, and see if the student misgendered her based on assumptions about her first name.I'm sorry this got rambly and ranty, and I appreciate that the people initiating these RfCs are doing so in good faith to protect and respect notable people who are similar to me in a vulnerable way that makes us visible minorities wherever we go. But what I'm feeling instead is that the image being presented to the wider Wikipedia community is that trans people are delicate to the point we need a constant flow of RfCs to head off any possible affront no matter how minor or unintentional. When people address you with the wrong pronouns, you remind, forgive, and have patience. It takes a while to learn, but people are learning. The ceaseless pushing on these topics is a road to resentment, not consensus.Apologies for the feelings. It's been a wholeass week over here. Double apologies to everyone who has their pronouns tattooed on their knuckles and gets tilted about pronouns on the daily (although I doubt the person I'm thinking of reads anything in the Wikipedia_talk: namespace). Folly Mox (talk) 04:36, 15 July 2023 (UTC)- "I see nowhere established an inability of talkpage conversations to handle this corner case." Yep. We already have a WP:MOSBLOAT problem, and MoS should not get new rules added that are not frequent sources of reader confusion or editorial in-fighting. — SMcCandlish ☏ ¢ 😼 22:34, 23 July 2023 (UTC)
- Reiterating what's already been said, we should handle these on a case-by-case basis. I beg that we do not have another RfC. Like Tamzin and Folly Mox, this has a personal connection for me. I'd not claim to have
complex / complementary gender expression
, rather I have a "don't give a fuck" approach which means I don't mind any personal pronouns. But even in that, the same issue arises as described by Actualcpscm. I don't think we have enough BLPs that would require us to create a uniform policy and AFAIK we've been able to self-regulate well enough. EvergreenFir (talk) 06:30, 15 July 2023 (UTC)
- Izzard has expressed a preference for being called Suzie, but "remains Eddie in public".
Determining Nationality: Is duress a factor?
MOS:ETHNICITY covers several useful situations for how to refer to the nationality or ethnicity of a biography subject in the lead section. However, there is no guidance on whether duress can be a factor in determining a person's nationality. At Talk:Sergei Bortkiewicz, there is currently a riveting discussion regarding how to refer to Sergei Bortkiewicz' nationality and/or ethnicity in the lead section. Even if these questions are mooted by other factors, the question of duress may still relevant to many biography subjects who have lived in the middle of geopolitical conflicts, especially if they lived in occupied territories. @Mzajac raises an interesting concern regarding Bortkiewicz: "His own comments have to be interpreted in his cultural and historical context: in the Russian empire one could get in serious trouble for publicly acknowledging Ukrainian as a separate national identity so it wasn’t done, and the name Ukrainian wasn’t universally used as an ethnonym until after the revolution (in Austro-Hungarian Ukraine, Ukrainians had referred to themselves as Rusyns, Rusnaks, or Ruthenians). This coloured the way people from there referred to themselves and others, and the way the rest of the world referred to them."
To what extent can duress be a factor in determining a person's identity? 169.156.16.220 (talk) 23:35, 9 August 2023 (UTC)
To what extent can duress be a factor in determining a person's identity?
No extent, because that requires WP:OR. Instead, we should just follow the sources; if the sources describe Bortkiewicz as Russian, we describe him as Russian. If the sources describe him as Ukrainian, we describe him as Ukrainian. If the sources are conflicted, we reflect that conflict. BilledMammal (talk) 23:49, 9 August 2023 (UTC)- Duress doesn't really apply to Bortkiewicz since he was living in Germany for most of his life. But as @BilledMammal said: we should trust sources that they are able to acknowledge every factor while determining subjects nationality, we shouldn't do that ourselves. Marcelus (talk) 06:05, 10 August 2023 (UTC)
- I concur with BilledMammal and Marcelus. — SMcCandlish ☏ ¢ 😼 10:37, 10 August 2023 (UTC)
- The issue isn’t duress, it’s colonialism. Bortkiewicz grew up in imperial Russia where everything Ukrainian was either denigrated as low peasant culture, or appropriated as Russian. He was from a landlord family of foreign ancestry. Why would he ever associate himself with Ukrainianness?
- And of course, these prejudices were exported to Western academia by Russian émigrés, and are still only partially addressed, so his connection to Ukrainian culture is only now beginning to be examined, as evidenced by sources that I quoted from in Talk:Sergei Bortkiewicz#Edit war regarding Countries of Bortkiewicz’ Heritage. —Michael Z. 15:10, 10 August 2023 (UTC)
- It is entirely possible that the academic RS consensus on Bortkiewicz's identity is about to change, but until it does it's not up to us as Wikipedia editors to jump the gun. At most it may be reasonable to omit content relating to Russian identity if it is connected to outdated scholarship, but purporting new content about connections to Ukraine in the absence of sourcing is OR.signed, Rosguill talk 15:14, 10 August 2023 (UTC)
- And (not looking specifically at the sources in this case) if only Ukrainian sources describe him as Ukrainian and other sources describe him differently, like it currently happens a lot, this situation should be mentioned in the article (rather than saying 50% sources so, other 50% sources so). Ymblanter (talk) 16:13, 10 August 2023 (UTC)
- I don't think we can automatically treat sources as WP:BIASED solely because of their nationality. That would lead to problems for eg. Arab–Israeli conflict. Or, for another example, would we require that every source about the Vietnam War published in the United States or written by an American attribute that fact? The fact that sources from region X tend to say Y is something we could attribute to a secondary source observing that fact, but putting a bunch of sources together and using attribution to say it seems like it could lead to problems. --Aquillion (talk) 17:09, 10 August 2023 (UTC)
- We have a lot of situations when Ukrainian sources say something and all (or almost all) other sources say smth else. And the proponents of Ukrainian POV bring these sources en masse and demand changing the text of the article. We need to learn how to deal with such situations. Ymblanter (talk) 18:25, 10 August 2023 (UTC)
- [citation needed][citation needed][citation needed][original research]
- Now lecture us about Russian sources. —Michael Z. 02:40, 11 August 2023 (UTC)
- The sources I cited in the discussion linked above are published by:
- The New Criterion, New York NY
- Roman & Littlefield, Lanham MD
- Orpheus Publications, Harrow, Middlesex, UK
- Doubleday, New York NY
- Alfred Publishing, Van Nuys CA
- R. Glier Kyiv Institute of Music, Tchaikovsky National Music Academy of Ukraine, Kyiv
- Notes Muzyczny, Academy of Music in Łódź
- University of Nebraska – Lincoln.
- So what is it we need to learn how to deal with? —Michael Z. 02:58, 11 August 2023 (UTC)
- Yeah, I'm strongly inclined to agree with the general sentiment Michael is expressing here and the points raised by Aquillion. I'm not going to challenge Ymblanter's subjective read of this particular corpus of sources in this particular context, because that is an exceedingly difficult or outright impossible thing to do in most circumstances, and even if you accomplish it, you may not convince the other party. But I will say that our policies are very obviously, directly, and deliberately design to have us avoid introducing meta-analysis of the sources unless an WP:RS compliant source can be found supporting it: ideally with attribution.That said, attribution can be used to operate in the other direction as well: if you have a concern about the balance of sources along some criteria, attribution is the one way you can flag that. You just can't get too extrapolative/OR/SYNTH about how you describe things in doing so. SnowRise let's rap 04:42, 11 August 2023 (UTC)
- That said and returning to the OP's original question, I'm in agreement with BilledMammal, Marcelus, Rosguill and SmMCandlish above: just map to the sources. Implications of duress or cultural suppression or appropriation are WP:extraordinary claims (that can really only come in the midst of controversial issues) that must meet a high burden of sourcing. Mind you WP:BIASED does tell us to present all significant viewpoints, but you still need at least one or two high quality sources for such observations of purported systemic bias. But you can reasonably, briefly, and neutrally point out any very obvious (and easily verifiable) connections between the sources and let the reader draw their own conclusions. Again, just don't get excitable with the wording. SnowRise let's rap 04:42, 11 August 2023 (UTC)
- As I mentioned above, I am making a general point. I did not even look at a specific corpus of sources in this case, and it might very well be that the Ukrainian point of view is prevalent in the sources for this specific issue. Ymblanter (talk) 12:07, 11 August 2023 (UTC)
- It’s not a “Ukrainian point of view” that Bortkiewicz was from Ukraine (except in that the musician from Ukraine literally wrote this fact about himself). On the contrary, there is a POV pushed in the original discussion, the baseless or distorted assertion that Ukraine “wasn't even existing at that time.” —Michael Z. 13:56, 11 August 2023 (UTC)
- Yeah, I'm strongly inclined to agree with the general sentiment Michael is expressing here and the points raised by Aquillion. I'm not going to challenge Ymblanter's subjective read of this particular corpus of sources in this particular context, because that is an exceedingly difficult or outright impossible thing to do in most circumstances, and even if you accomplish it, you may not convince the other party. But I will say that our policies are very obviously, directly, and deliberately design to have us avoid introducing meta-analysis of the sources unless an WP:RS compliant source can be found supporting it: ideally with attribution.That said, attribution can be used to operate in the other direction as well: if you have a concern about the balance of sources along some criteria, attribution is the one way you can flag that. You just can't get too extrapolative/OR/SYNTH about how you describe things in doing so. SnowRise let's rap 04:42, 11 August 2023 (UTC)
- We have a lot of situations when Ukrainian sources say something and all (or almost all) other sources say smth else. And the proponents of Ukrainian POV bring these sources en masse and demand changing the text of the article. We need to learn how to deal with such situations. Ymblanter (talk) 18:25, 10 August 2023 (UTC)
- I don't think we can automatically treat sources as WP:BIASED solely because of their nationality. That would lead to problems for eg. Arab–Israeli conflict. Or, for another example, would we require that every source about the Vietnam War published in the United States or written by an American attribute that fact? The fact that sources from region X tend to say Y is something we could attribute to a secondary source observing that fact, but putting a bunch of sources together and using attribution to say it seems like it could lead to problems. --Aquillion (talk) 17:09, 10 August 2023 (UTC)
- And (not looking specifically at the sources in this case) if only Ukrainian sources describe him as Ukrainian and other sources describe him differently, like it currently happens a lot, this situation should be mentioned in the article (rather than saying 50% sources so, other 50% sources so). Ymblanter (talk) 16:13, 10 August 2023 (UTC)
- It is entirely possible that the academic RS consensus on Bortkiewicz's identity is about to change, but until it does it's not up to us as Wikipedia editors to jump the gun. At most it may be reasonable to omit content relating to Russian identity if it is connected to outdated scholarship, but purporting new content about connections to Ukraine in the absence of sourcing is OR.signed, Rosguill talk 15:14, 10 August 2023 (UTC)
- Although I originally opened the topic to discuss the limited topic of duress, this section has clearly blossomed into a healthy discussion about the proper application of MOS:ETHNICITY to the broader question of Bortkiewicz' nationality/ethnicity. Several users have weighed in here supporting the general concept that the lead section should guided by WP:RS, to prevent WP:NOR or WP:SYNTH. At Talk:Sergei Bortkiewicz, multiple WP:RS each were raised identifying Bortkiewicz as Polish, Ukrainian, Russian, and Austrian.
- I cannot take seriously Marcelus' argument that multiple sources describing Bortkiewicz as "Ukrainian-born" or listing "Ukraine" next to his name do not consider him Ukrainian.
- Similarly, in response to Michael's arguments for rejecting the sources that facially identify Bortkiewicz as Russian, I'm concerned this would risk committing WP:SYNTH or WP:OR. Even if Michael's claim that anyone who was born and grew up in Ukraine was Ukrainian were valid, this would not answer the question of whether Bortkiewicz was also Russian, which the WP:RS clearly answer in the affirmative.
- Previously, I suggested the compromise solution of omitting both Russian and Ukrainian references in the first sentence, based on the potential conflict between sources and the Copernicus example in MOS:ETHNICITY, but that didn't seem to gain support. I am also convinced by BilledMammal's point that the sources should reflect conflict, if any. Thus, I have edited Sergei Bortkiewicz to note in the first sentence that he was Ukrainian as well as what was previously listed, with multiple WP:RS each to indicate his Ukrainian, Russian, Austrian, and Polish identities. The citations allow the readers to make their own informed decisions about Bortkiewicz' identities.
- (Also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 14:14, 12 August 2023 (UTC)
- I did not reject sources that identify Bortkiewicz as Russian. I did say (somewhere) that it is better say exactly what that means, that he was a subject of the Russian empire. This is what some recent sources say is better (I’ll provide a reference if I can find it). —Michael Z. 15:15, 12 August 2023 (UTC)
- I think the body should definitely be improved to describe the identities in more detail, including his statements about his identity, and the ethnological interpretation of his music. The lead would not be the right place, to avoid MOS:LEADCLUTTER. However, the content should be specific to Bortkiewicz. If we have two sources that identify Bortkiewicz as Russian, and a third source that says that "Russian" at that time meant subject of the Russian Empire (generally and without specificity to Bortkiewicz), then WP:SYNTH might incorrectly follow the form, "Bortkiewicz was Russian[source 1,2], which means that he was a subject of the Russian Empire[source 3]."
- (Also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 15:39, 12 August 2023 (UTC)
- This discussion is already going on: Talk:Sergei_Bortkiewicz#Edit_war_regarding_Countries_of_Bortkiewicz'_Heritage, there is zero reason to start another one here. Everybody who has interest in the topic is free to join the discussion there. Marcelus (talk) 19:29, 12 August 2023 (UTC)
- This page frequently hosts WP:RFC regarding disputes about the application of MOS:BIO. You yourself have raised some important points on Talk:Sergei Bortkiewicz regarding the proper application of Wikipedia policies. It is important that these pressing points be discussed by the broader Wikipedia community, instead of just a Talk page. (Also used 50.169.82.253, 169.156.16.220, and 167.102.146.19) 134.192.8.17 (talk) 21:19, 12 August 2023 (UTC)
- I did not reject sources that identify Bortkiewicz as Russian. I did say (somewhere) that it is better say exactly what that means, that he was a subject of the Russian empire. This is what some recent sources say is better (I’ll provide a reference if I can find it). —Michael Z. 15:15, 12 August 2023 (UTC)
- I'd like to put in a plug here for just omitting nationality from the first sentence when it's complicated and not very relevant to the person's notability. In fact I'd even be good with omitting it (from the first sentence) just whenever it's not very relevant to the person's notability, complicated or not. Whether that's the case for Bortkiewicz I haven't bothered to form an informed opinion on, but I'd like to challenge the apparently popular assumption that we should always or almost always lead with nationality. There's plenty of time to discuss it in the body of the article. --Trovatore (talk) 18:56, 12 August 2023 (UTC)
- I'd like to hear more perspectives on this. I'm not closed to the idea of removing both "Ukrainian" and "Russian" from the first sentence, although I believe that only including "Russian" and not "Ukrainian" is neither supported by consensus nor by references. At the moment, I'm quite convinced by the argument of BilledMammal, that the article should reflect any conflict between sources. I don't see much of a conflict: only one source says Bortkiewicz was not Ukrainian, and none say he was not Russian. This does not seem inconsistent with a claim that he was both Ukrainian and Russian, and this claim seems well supported by references. While Copernicus is precedent for how MOS:ETHNICITY need not be included for someone whose ethnicity/nationality is disputed, I don't see any similar standard for not including a complicated nationality. If someone has four different ethnicities/nationalities and all four are well supported by sources, and all four are WP:NOTABLE, I think all should be included. But I'd like to hear from others on this point.
- I think the Johnson dissertation and the Levkulych paper, and the Polish language source provide the best arguments for the notability of each of these ethnicites/nationalities: they were notable because they heavily informed Bortkiewicz's music, which itself was notable. (Also used 50.169.82.253, 169.156.16.220, and 167.102.146.19) 134.192.8.17 (talk) 23:01, 12 August 2023 (UTC)
- I only learned of this discussion now; it would have been very helpful, not to mention a welcome sign of goodwill, had IP user mentioned they were going to take the Bortkiewicz discussion elsewhere after failing to achieve their aims at the article talk page.
- Some points:
- "Duress" isn't a credible excuse for why Bortkiewicz self-identified as Russian and not Ukrainian. As has been mentioned before, his stated being Russian after leaving Russia, when he was no longer in danger of official reprisal. Even had he remained in Russia/the USSR, the notion of official reprisal for asserting one's nationality isn't as clear-cut as others make it here. During the Soviet period, expressions of nationalism were encouraged by authorities, so long as they did not threaten the integrity of the Soviet state. Levko Revutsky, Boris Lyatoshinsky, Viktor Kosenko, among many others, not only were allowed to assert their Ukrainian identity, but were allowed to thrive because of it. In the case of Revutsky, his being Ukrainian even ended up being a professional advantage during the nominations for the 1940 Stalin Prize. The committee ultimately booted Sergei Prokofiev's Alexander Nevsky from the short list in favor of Revutsky's Symphony No. 2 because they needed more non-Russian nominees. All of these composers were highly regarded and were honored by the state.
- His nationality, whatever it was, ultimately played no part in his notability. These certainly did not secure him lasting fame in his lifetime, nor did it prevent him from being practically forgotten by the musical mainstream in Russia, Austria, and Ukraine until the late 20th century. Bortkiewicz also did not appreciably influence or participate in the musical history and development of infrastructure anywhere, much less in Ukraine, unlike the aforementioned composers who are crucial figures in the ongoing history of Ukrainian music.
- That he used Ukrainian music in his own work does not make him Ukrainian. If that were the case, then Colin McPhee would be "Indonesian", not Canadian; Béla Bartók "Romanian" and/or "Turkish" instead of or in addition to being Hungarian.
- The best compromise would be to omit all mentions of nationality in the lead. —CurryTime7-24 (talk) 01:56, 13 August 2023 (UTC)
- A formula I've used occasionally for subjects whose current nationality is non-obvious is to omit the nationality from the first sentence, but then later in the lead to list the relevant nations for major life phases like "Born in Argentina and educated in France and Switzerland, she works in Germany as..." —David Eppstein (talk) 02:10, 13 August 2023 (UTC)
- Yes, that is a very good technique and should be used more. (I've seen a few places where both at once are being done, though, which is clumsy. E.g., Alex Pagulayan "is a Filipino-born Canadian professional pool player. Pagulayan was born in Cabagan, Isabela, Philippines and was raised in Toronto, Ontario, Canada. In 2012, Pagulayan became a citizen of Canada and now resides in Toronto." — SMcCandlish ☏ ¢ 😼 02:21, 13 August 2023 (UTC)
- That would be a sensible choice elsewhere, but I don't think it would work here as editors with a nationalist agenda would likely try to game this one way or another.
- The main problem is that Ukraine, in the sense of an independent polity, didn't exist at the time of Bortkiewicz's birth. Adding to the confusion—and frustration to nationalists on both sides—is that notions of what it meant to be Ukrainian and Russian were a lot more ambiguous and fluid back in Bortkiewicz's time than today. —CurryTime7-24 (talk) 03:01, 13 August 2023 (UTC)
- Wow. Why not just name the bad-faith editors instead of casting aspersions widely to show you have no trust in the discussion and poison it?
- I don’t know why that would be a particular main problem. Plenty of independent polities didn’t exist throughout much of history. Somehow we manage to label Bach and Beethoven German before 1866 and Vivaldi Italian before 1861, and Ghandi’s not even “British.”
- The question is about “notions” in current sources, not in Bortkiewicz’s time. —Michael Z. 03:33, 13 August 2023 (UTC)
- Why do you keep derailing discussion by accusing others of attacking you and Ukraine? I even forgot about you until now. Furthermore, nobody here or at the other discussion was maligning Ukraine. The only person who kept bringing up outdated terms for it that are now considered derogatory was you. So please take my word: I neither hate you, nor am I trying to attack you or Ukraine, whether directly or by implication.
- Getting back on-topic, Vivaldi, for example, was ethnically Italian, spoke Italian, contributed to the development of Italian music, and was referred to as Italian by sources in his time and since. Sources are clear that Bortkiewicz was born in what was then Russia and that his ethnicity was Polish, but arguments for his Ukrainian nationality, on the other hand, did not appear until well after his death. As I mentioned above, "duress" cannot be the reason he self-identified as Russian even after leaving Russia; even had he remained, the cases of Revutsky, et al, prove that assertions of Ukrainian identity were celebrated and encouraged in the USSR. (Since Bortkiewicz never returned there, however, this is besides the point.)
- Bortkiewicz himself neither ever identified as Ukrainian, nor had any ethnic connection to Ukraine. So the grounds for him being Ukrainian, aside from being born in a territory that 114 years later became Ukraine, are a lot more debatable. If anything, the situation here is more like trying to refer to E. T. A. Hoffmann as Russian or Béla Bartók as Romanian simply because their respective birthplaces eventually became Russia and Romania. —CurryTime7-24 (talk) 04:02, 13 August 2023 (UTC)
- Now you’re making up false accusations. Please take them back.
- And you’re indulging in a straw man argument, or maybe several. I’ll repeat what I said before: the article should say Bortkiewicz was from Ukraine. Since that meets the definition of a Ukrainian, it could use that term to say it, but it would be better to be specific. —Michael Z. 04:09, 13 August 2023 (UTC)
- And Immanuel Kant was from Russia because even though he never identified as such, spoke the language, or was in any way directly involved with its culture or history, his birthplace is located in what is today Kaliningrad. Doesn't that meet the definition of a Russian? —CurryTime7-24 (talk) 04:17, 13 August 2023 (UTC)
- MOS:ETHNICITY does not support the claim that just because someone is from a region, that person should be referred to by the demonym of that region. Review the guidance on the usage of British vs Scottish/Welsh/English/Irish, and Spanish vs regional demonym. The course of action in that case is to consult reliable sources that refer to the person using those particular demonyms. (also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 04:34, 13 August 2023 (UTC)
- The only two sources raised that claim Bortkiewicz was Russian were Grove (2001), and Johnson (2016), both long after Bortkiewicz died. If you found fault in the recency of the sources claiming his Ukrainian nationality, the sources claiming his Russian nationality would be weak for the same reason. Claiming Bortkiewicz was Russian because he was born in Russia would be impermissible WP:OR, which is the same thing I said to @Mzajac about the claim that Bortkewicz was Ukrainian because he was born in Ukraine. (also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 04:16, 13 August 2023 (UTC)
- For one thing, The New Grove is "only" the largest reference work on music in any language. For another, whether anyone likes it or not, Bortkiewicz's birthplace was internationally recognized as being an integral part of Russia at the time he was born. —CurryTime7-24 (talk) 04:23, 13 August 2023 (UTC)
- You’re not citing your sources, but I suggest newer ones than 1877. —Michael Z. 04:36, 13 August 2023 (UTC)
- Grove has many editions from many years. The citation in question was from 2001.
- Schwarz, Boris (20 January 2001). "Bortkiewicz [Bortkievich], Sergei [Sergey] Eduardovich". Grove Music Online. doi:10.1093/gmo/9781561592630.article.03637. Retrieved 12 January 2023.
{{cite web}}: CS1 maint: url-status (link) - (also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 04:40, 13 August 2023 (UTC)
- Yes. A lot of articles are preserved in new editions if they are believed by their editorial board to still be authoritative and accurate. The article about Igor Stravinsky by Stephen Walsh, for example, is still in use. Your gripe isn't with me, but Oxford University Press. —CurryTime7-24 (talk) 04:54, 13 August 2023 (UTC)
- Where am I not citing sources? I was the first and, for awhile, the only user at the Bortkiewicz article to cite an actual source. Until I started editing the page in January, the article lacked citations entirely. That I didn't add more was simply because The New Grove is one of the most respected sources on music in any language and that I'm not personally invested in Bortkiewicz enough to exhaustively expand and improve the article as I do for subjects that actually interest me. And The New Grove article is from 2001. Not new enough? —CurryTime7-24 (talk) 04:51, 13 August 2023 (UTC)
- Grove, or at least the edition provided was published long after Bortkiewicz's death, which means that it falls to your own criticism of recency. MOS:ETHNICITY does not support the claim that just because someone is from a region, that person should be referred to by the demonym of that region. Review the guidance on the usage of British vs Scottish/Welsh/English/Irish, and Spanish vs regional demonym. The course of action in that case is to consult reliable sources that refer to the person using those particular demonyms. 50.169.82.253 (talk) 04:37, 13 August 2023 (UTC)
- Well, you're just in luck then because I have a number of articles clipped from Newspapers.com and ProQuest from Bortkiewicz's lifetime wherein he is referred to as Russian. —CurryTime7-24 (talk) 04:56, 13 August 2023 (UTC)
- You’re not citing your sources, but I suggest newer ones than 1877. —Michael Z. 04:36, 13 August 2023 (UTC)
- For one thing, The New Grove is "only" the largest reference work on music in any language. For another, whether anyone likes it or not, Bortkiewicz's birthplace was internationally recognized as being an integral part of Russia at the time he was born. —CurryTime7-24 (talk) 04:23, 13 August 2023 (UTC)
- Yes, that is a very good technique and should be used more. (I've seen a few places where both at once are being done, though, which is clumsy. E.g., Alex Pagulayan "is a Filipino-born Canadian professional pool player. Pagulayan was born in Cabagan, Isabela, Philippines and was raised in Toronto, Ontario, Canada. In 2012, Pagulayan became a citizen of Canada and now resides in Toronto." — SMcCandlish ☏ ¢ 😼 02:21, 13 August 2023 (UTC)
- One minute before I opened the new topic here, I wrote in Talk:Sergei Bortkiewicz: "I am consulting Wikipedia Talk:Manual of Style/Biography for an opinion on whether duress can be a factor in determining the nationality of a biography subject." (also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 02:49, 13 August 2023 (UTC)
- Your wording implied that you merely were referring to the MOS for guidance, not opening a new RfC which is what you did here. Regardless of what you meant, you should've notified editors in the other talk page that you were opening this; that you didn't is a bad look. The fact that you also attempted to WP:WL @Marcelus (by "weaponizing policies, guidelines, noticeboards ... with the goal of deprecating an editor rather than of resolving a problem") also does not reflect well on your intentions. —CurryTime7-24 (talk) 03:16, 13 August 2023 (UTC)
- I'm not sure why I would merely read a talk page. People consult talk pages by opening new sections and participating in discussions.
- If you're concerned that my report violated Wikipedia policy, please contact the administrators. It didn't, and there's nothing else I can say. (also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 03:49, 13 August 2023 (UTC)
- Again, whatever wording you chose, it would have been a welcome gesture of goodwill had you informed involved editors that you intended to open a new RfC. You chose not to, which is as I said a bad look, especially after you gained no consensus that favored your edits at the Bortkiewicz talk page.
- Unless a user is unambiguousItalicly vandalizing mainspace, I'm not interested in reporting anyone. —CurryTime7-24 (talk) 04:11, 13 August 2023 (UTC)
- The consensus for my edit came from you. I mentioned that here and you did not respond. I'm further confused because you again confirmed your position that you don't want either Russian or Ukrainian nationality or ethnicity to be mentioned in the lead. So why do you continue to contest that my edit, which resulted in neither Russian nor Ukrainian identity being mentioned in the lead, was without consensus? (also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 04:26, 13 August 2023 (UTC)
- As flattering to my ego as it would be, my say so alone does not make consensus. Clearly there was at least one other editor who wanted to include "Ukrainian" in the lead and another who wanted "Russian". Moreover, there should have been a formal RfC process initiated with unbiased proposals and explanations explaining them. This was not done.
- And as the edit history shows, I did not revert you. I trimmed your citation overkill, removed one of your sources because it was a children's book, and added better source needed tags because at least one other user pointed out problems with them, but I did not remove your edit that stated Bortkiewicz was Ukrainian. Although I did not revert you, the fact that another editor did indicates that consensus had yet to be achieved. —CurryTime7-24 (talk) 04:43, 13 August 2023 (UTC)
- Your description of WP:CONSENSUS is not accurate. Consensus can be assumed in the WP:SILENCE of disagreement. Before I removed "Russian", no one expressed disagreement with this change. Even though WP:CCC, consensus existed at the time of my edit. My edit did not affect any occurrences of "Ukrainian". It's quite counterintuitive for you to now be upset that I made a change that you wanted, and that you evidently still want. If this process of gaining consensus is so paramount, I find it quite puzzling how four times (diff, diff, diff, diff), you removed "Ukrainian" and placed "Russian" into the article without ever seeking consensus for this change. (also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 05:03, 13 August 2023 (UTC)
- You cited an explanatory essay that explicitly states: "This page is not one of Wikipedia's policies or guidelines"... —CurryTime7-24 (talk) 05:05, 13 August 2023 (UTC)
- The point, "Consensus can be assumed if no editors object to a change.", is in WP:CONSENSUS. I recall that you accused me of WP:WL. That's an essay. 50.169.82.253 (talk) 05:22, 13 August 2023 (UTC)
- I certainly did. Which is one of the reasons I did not take you up on your offer to report you, because I don't confuse explanatory essays with policy. —CurryTime7-24 (talk) 05:40, 13 August 2023 (UTC)
- The point, "Consensus can be assumed if no editors object to a change.", is in WP:CONSENSUS. I recall that you accused me of WP:WL. That's an essay. 50.169.82.253 (talk) 05:22, 13 August 2023 (UTC)
- You cited an explanatory essay that explicitly states: "This page is not one of Wikipedia's policies or guidelines"... —CurryTime7-24 (talk) 05:05, 13 August 2023 (UTC)
- Your description of WP:CONSENSUS is not accurate. Consensus can be assumed in the WP:SILENCE of disagreement. Before I removed "Russian", no one expressed disagreement with this change. Even though WP:CCC, consensus existed at the time of my edit. My edit did not affect any occurrences of "Ukrainian". It's quite counterintuitive for you to now be upset that I made a change that you wanted, and that you evidently still want. If this process of gaining consensus is so paramount, I find it quite puzzling how four times (diff, diff, diff, diff), you removed "Ukrainian" and placed "Russian" into the article without ever seeking consensus for this change. (also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 05:03, 13 August 2023 (UTC)
- The consensus for my edit came from you. I mentioned that here and you did not respond. I'm further confused because you again confirmed your position that you don't want either Russian or Ukrainian nationality or ethnicity to be mentioned in the lead. So why do you continue to contest that my edit, which resulted in neither Russian nor Ukrainian identity being mentioned in the lead, was without consensus? (also used 134.192.8.17, 169.156.16.220, and 167.102.146.19) 50.169.82.253 (talk) 04:26, 13 August 2023 (UTC)
- Your wording implied that you merely were referring to the MOS for guidance, not opening a new RfC which is what you did here. Regardless of what you meant, you should've notified editors in the other talk page that you were opening this; that you didn't is a bad look. The fact that you also attempted to WP:WL @Marcelus (by "weaponizing policies, guidelines, noticeboards ... with the goal of deprecating an editor rather than of resolving a problem") also does not reflect well on your intentions. —CurryTime7-24 (talk) 03:16, 13 August 2023 (UTC)
- A formula I've used occasionally for subjects whose current nationality is non-obvious is to omit the nationality from the first sentence, but then later in the lead to list the relevant nations for major life phases like "Born in Argentina and educated in France and Switzerland, she works in Germany as..." —David Eppstein (talk) 02:10, 13 August 2023 (UTC)
- I agree, what's more it's a WP:DISCUSSFORK by the IP user. Marcelus (talk) 07:51, 14 August 2023 (UTC)
I got sucked into this rabbithole topic by User:Mzajac/Michael's comment, because Bach and Beethoven and Vivaldi get rather less controversial anachronistic ethno-nationalities in the lead paragraphs, while Mozart and Haydn get into historical/pseudohistorical and politicized Godwin-converging Talk battles. There's even a Nationality of Wolfgang Amadeus Mozart article (entirely SYNTH imo). If you browse the archives of any such bio's Talk page they raise the same basic points: nationality, ethnicity(s), language, citizenship, residence, and self-identification are all different concepts that may vary in different contexts at different times in the subject's life. An appropriate RS may indeed cover such a topic in some detail. But if it's only mentioned as a throwaway line in a bio -- "Bach was born in X. The precocious young German did Y." -- is that really a suitable source that a historian has staked out a position on the subject's ethnicity, especially if the historian provides no footnote for that singular nominalization? I hear way too often the entirely false mantra that "an RS is an RS". Tldr: maybe editors here who say it suffices to adhere to reliable sources are correct, but I have yet to see editors consistently understand what reliable sources are, especially when tribal lines are being drawn. If something like duress is even remotely an issue, then I'd be shocked if editors ever agree to put any positive ethnicity or nationality anywhere. SamuelRiv (talk) 04:38, 18 August 2023 (UTC)
bolding of "sir"
Per MOS:BOLD, "The most common use of boldface is to highlight the first occurrence of the article's title word or phrase in the lead section." However, the guidance at MOS:SIR is, "The title is placed in bold in the first use of the name." In cases when the title of the article does not include the honorific, this is contradictory; not knowing that MOS:SIR even existed, I've been conforming articles to MOS:BOLD.
I'm not clear why "sir" should be different than any other honorific in terms of the use of boldface; shouldn't it only be in bold when it's part of the article title? If in fact it's the consensus that "sir" is an exception, shouldn't MOS:BOLD be updated to reflect that? ~TPW 15:04, 31 August 2023 (UTC)
- It should not be treated any differently from other titles and honorifics, whether pre- or post-nominal. This is a WP:POLICYFORK that needs to be fixed. — SMcCandlish ☏ ¢ 😼 15:26, 31 August 2023 (UTC)
- You're forgetting that the person's full name is always bolded even when their full name doesn't feature in the article title. Nicknames and other common names by which a person is known are also bolded in the first paragraph. So are former names. So this does not stand up to scrutiny. -- Necrothesp (talk) 15:28, 31 August 2023 (UTC)
- I appreciate the good-faith assumption that I am forgetful, but that's not it at all. Most titles are not placed in bold, except when they are part of the article title. In other words, they are not considered "part of the full name" unless the consensus is that the article title include it. I'm just trying to understand why the guidance and MOS:SIR appears to contradict that. Do you know of other specific guidelines or policies that would shed light on this seeming contradiction? ~TPW 16:16, 31 August 2023 (UTC)
- Bolding the Sir seems to be a continuation of bolding the MOS:FULLNAME? For example, for the article title Winston Churchill we have bold text
Sir Winston Leonard Spencer Churchill
. Equivalently, in the article Ruth Westheimer includesKarola Ruth Westheimer
and laterDr. Ruth
. An alternative route to the same result is that Sir Winston Leonard Spencer Churchill and Dr. Ruth are both redirect pages. - In either case, I think it would help for MOS:BOLD to include this, but I think it should encompass the bolding of all full name variations, not just the title Sir. Mgp28 (talk) 15:28, 31 August 2023 (UTC)
- I don't see anything at MOS:FULLNAME that refers to titles; that would suggest that titles are not placed in bold as a matter of course. For Churchill I'd not put the "sir" in bold for that reason. Dr. Ruth, however, is in bold as an alternative name redirected to the main article pursuant to MOS:BOLD. Paul McCartney does not have a redirect from Sir Paul McCartney, on the other hand, and I'm trying to understand why bold of that title is appropriate regardless. ~TPW 16:22, 31 August 2023 (UTC)
- Sorry I was unclear. I didn't mean that the guidance at MOS:FULLNAME mentions titles. I meant that if we're bolding full names then it seems reasonable that some titles will end up included in that. Andrew Lloyd Webber's
Andrew Lloyd Webber, Baron Lloyd-Webber
would look strange if we unbolded the "Baron". Other examples of titles that are bolded include Mother Teresa's (among others)Saint Teresa of Calcutta
. - As an aside, Sir Paul McCartney is a redirect. Despite having brought up redirects in my first reply, I now think it's unwise to focus too strongly on that justification because misspellings are also redirects and we would never use that as a reason for bolding. Mgp28 (talk) 16:34, 31 August 2023 (UTC)
- Oh, I somehow missed that. Still getting used to the way search terms pop up in the newest interface, I guess. ~TPW 16:50, 31 August 2023 (UTC)
- As for what seems reasonable for inclusion, maybe it would be appropriate to request comments on that, but I don't think I could come up with a concise enough request quite yet. ~TPW 16:52, 31 August 2023 (UTC)
- Perhaps something along the lines of "In what circumstances should a title be considered as part of a person's full name?"
- I don't know if there can be a strict rule. It would probably need to be some combination of the title's permanency (e.g. not jobs / elected offices) and WP:COMMONNAME.
There's also issues of article titles. For example, popes' articles tend to have "Pope" in the title, so that'll be bold regardless of whether we say Pope is part of their name. Redirects opens up even more, e.g. should Princess Grace be bold? I know there have been extensive discussions about article titles for UK monarchs and their consorts. Bolding in those articles seems mostly to be just the article title. I don't know how broad those discussions have been. Perhaps evidence of a broad consensus already exists in those discussions and we don't need to re-open it?Mgp28 (talk) 17:20, 31 August 2023 (UTC)
- I found a better example: the lead of August Thayer Jaccaci refers to "Captain August Thayer Jaccaci, Sr." The "captain" is not in bold. Should it be? Why, or why not? If not, how is it qualitatively different than "sir," in articles that do not include the title in the article name? ~TPW 20:14, 31 August 2023 (UTC)
- Captain Tom Moore has "Captain" in the article title, then starts
Captain Sir Thomas Moore
. I have no idea... Mgp28 (talk) 20:53, 31 August 2023 (UTC) - Because captain is a rank, not a title. They are entirely different things. When someone is knighted they are referred to as "Sir Whatever" for the rest of their lives. Effectively, it does become part of the name (and can, incidentally, appear on passports and other official documents as part of the name). Taking this opposition to bolding titles to its logical conclusion, it would also lead to the ridiculous situation where Sir John Smith, 1st Baronet was referred to as Sir John Smith, 1st Baronet in the first line, whereas Edmund Affleck was referred to as Sir Edmund Affleck, 1st Baronet. Both are baronets, but only the first needs to be disambiguated by his title. Presumably under this thinking, Winston Churchill would appear as Sir Winston Leonard Spencer Churchill. And if not, why not? -- Necrothesp (talk) 12:32, 1 September 2023 (UTC)
- I tend to follow the same line of thinking as Necrothesp. "Sir" is not the same thing as "Captain" is, it effectively used as part of the name. --Jayron32 13:11, 1 September 2023 (UTC)
- All I ask is a demonstration that this practice is consensus, to allow me to read through that discussion, or, in the alternative, reliable sources supporting the asserting that "sir" is part of a name, which would certainly be helpful in achieving consensus now. ~TPW 13:17, 1 September 2023 (UTC)
- This has been discussed endlessly in the past. Periodically someone comes along and asks why we do it. It's explained to them. A few people (usually those who don't like titles) object. It goes round and round for a bit. Debate peters out. Then some other person reignites it... -- Necrothesp (talk) 15:55, 1 September 2023 (UTC)
- I fear there was more context in my head than in what I wrote. For whatever it may be worth, the bold in the first line of the Captain Tom Moore article matches my preference. In a series of unhelpful comments, I made a suggestion to TPW, deleted it on the basis that article titles are always bold, then found counter-examples. Given that I'm perfectly happy with the status quo it's probably time for me to step away but I do think it would be reasonable for MOS:BOLD to include (or point to) guidance about bolding of people's names. Mgp28 (talk) 16:42, 1 September 2023 (UTC)
- Perhaps it wasn't clear from my last comment that I am not interested in reigniting a past debate if consensus was reached at that time. I ask again if someone could provide me a link to that discussion. ~TPW 18:28, 1 September 2023 (UTC)
- Previous discussion: Wikipedia talk:Manual of Style/Biography/2023 archive § Remove bold for honorific titles in lead sentence, Mitch Ames (talk) 00:25, 2 September 2023 (UTC)
- After reviewing the last thread on this (thanks for that, @Mitch Ames), I have a clearer understanding of why no one has pointed to consensus; none has been achieved. In that thread, at least, some editors expressed distaste for the idea. The arguments were largely based on vaguely-defined distinctions among "titles," "honorofics," and "pretitles." It appears that some of the editors participating at that time weren't clear on what any of those mean; I am similarly in the dark. There were also suggestions that anyone questioning this practice must be opposed to titles, although no evidence of that assertion was presented. ~TPW 14:52, 5 September 2023 (UTC)
- In all of these sorts of discussions I'm aware of, there has repeatedly been an assertion along the lines that "Sir/Dame becomes part of the name", which is a very confused argument. It fails to distinguish between the actual name (which pre-existed the honour, and may survive it – I saw in the news only a few days ago that King Charles stripped someone of a knighthood), versus something later added in front of the name that is conventionally (not invariably) used along with it. This odd "titles and names are distinguishable" argument appears to be the primary if not sole backing of the "we should boldface Sir/Dame in the lead" stance. Observing how logically weak this position is, is not in any way an "IDONTLIKEIT" take, as True Pagan Warrior repetitively suggests. We have guidelines that call for extremely minimal use of boldface, and abiding by them is also not IDONTLIKEIT nonsense. If anyone is triggering I[DONT]LIKEIT concerns, it's the other side of the coin, arguing for Sir/Dame in bold simply because they "like" it one sense or another (e.g. it appeals to their traditionalist sense of propriety and deference). The very notion is also against the spirit of MOS:SIGCAPS (which is rooted in WP:NPOV policy): Wikipedia does not do special typography to try to force a sense of importance-signification into the brain of the reader. Doing it with excessive boldfacing (or unwarranted italicisation, or smallcaps, or use of colour fonts, or any other typographical trickery) isn't any better than doing it with everyday over-capitalization of things that are not normally capitalized. — SMcCandlish ☏ ¢ 😼 01:39, 6 September 2023 (UTC)
- This has been discussed endlessly in the past. Periodically someone comes along and asks why we do it. It's explained to them. A few people (usually those who don't like titles) object. It goes round and round for a bit. Debate peters out. Then some other person reignites it... -- Necrothesp (talk) 15:55, 1 September 2023 (UTC)
- Captain Tom Moore has "Captain" in the article title, then starts
- Sorry I was unclear. I didn't mean that the guidance at MOS:FULLNAME mentions titles. I meant that if we're bolding full names then it seems reasonable that some titles will end up included in that. Andrew Lloyd Webber's
- I don't see anything at MOS:FULLNAME that refers to titles; that would suggest that titles are not placed in bold as a matter of course. For Churchill I'd not put the "sir" in bold for that reason. Dr. Ruth, however, is in bold as an alternative name redirected to the main article pursuant to MOS:BOLD. Paul McCartney does not have a redirect from Sir Paul McCartney, on the other hand, and I'm trying to understand why bold of that title is appropriate regardless. ~TPW 16:22, 31 August 2023 (UTC)
First name mononym
We're having a discussion at Sia (edit | talk | history | protect | delete | links | watch | logs | views) about if/how to introduce per MOS:LEGALNAME why we refer to her as Sia throughout the article. She has not changed her legal name to her mononym. This is similar to the examples in Wikipedia:Manual_of_Style/Biography#Subsequent_use: Aaliyah, Selena, and Usher; where only Selena has an introduction, "known mononymously as Selena" in the first sentence.
Is there a general consensus to prefer an introduction over none? - Hipal (talk) 20:58, 7 September 2023 (UTC)
- See also Madonna. Like Usher, this is a Good Article. -- Ssilvers (talk) 21:11, 7 September 2023 (UTC)
- Prefer the introduction, since it makes things clearer for readers (not everyone is an avid follower of Western pop culture), and is better for WP:REUSE of our content. — SMcCandlish ☏ ¢ 😼 21:27, 7 September 2023 (UTC)
Discussion about the redirect category {{R from deadname}}
There’s currently a discussion going on at RfD regarding the redirect {{R from deadname}}. One of the potential outcomes is the creation of a new rcat.
During the discussion so far, an editor has raised potential BLP concerns, so it would therefore be good to hear the opinions of editors experienced in this area. I’ve linked the discussion below — any editor who wishes to take part may do so.
Courtesy link: Wikipedia:Redirects for discussion/Log/2023 September 7 § Template:R from deadname
All the best, user:A smart kittenmeow 09:29, 11 September 2023 (UTC)
Fictional characters known by initials - what qualifies as the "preferred style for their own name" ?
- The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
- — SMcCandlish ☏ ¢ 😼 14:03, 30 October 2023 (UTC)
WP:Requested moves has consistently interpreted the "Initials" section as also applying to names of fictional characters.
An initial is capitalized and is followed by a full point (period) and a space (e.g. J. R. R. Tolkien), unless:
- the person demonstrably has a different, consistently preferred style for their own name; and
- an overwhelming majority of reliable sources use that variant style for that person.
In such a case, treat it as a self-published name change. Examples include k.d. lang, CC Sabathia, and CCH Pounder.
- Owner: E.T. for E.T. the Extra-Terrestrial, style followed in secondary source
- Owner: C.C. for C.C. (Code Geass), style followed in secondary source
- Owner: MJ for MJ (Marvel Cinematic Universe), style followed in secondary source
- Owner: JD McDonagh for JD McDonagh, style followed in secondary source
- Owner: O.B. for Ouroboros "O.B.", style followed in secondary source
- Owner: K.K. Slider for K.K. Slider, style followed in secondary source
- Owner: B.A. for Knights of the Dinner Table#Boris Alphonzo "B.A." Felton, style followed in secondary source
starship.paint (RUN) 13:37, 30 October 2023 (UTC)
- I would support the above in adherence to key content policies, when we adhere to the owner's name of the character, we satisfy WP:V and avoid WP:OR, and we are less likely to run afoul of WP:NPOV because sources tend to follow the official name as the WP:COMMONNAME. However, if the official name differs from the most widely used name in reliable sources, then the official name would not qualify for the exception. starship.paint (RUN) 13:40, 30 October 2023 (UTC)
- There is absolutely nothing like a "key content policy [to] adhere to the owner's name" of anything. Quite the opposite. See WP:OFFICIALNAME and MOS:TM. And WP:V and WP:OR and WP:NPOV are satisified by doing what a large majority of independent reliable sources are doing, not what is found in a primary source. Making up your mind based on a movie poster or a title card that the trademark holder must be upset about spacing or dot placement in a name just because they style it one way and we and various other publishers style it another way is OR by definition. Bending over backwards to satisfy trademark holders' stylization demands is entirely a POV exercise. And V is dependent on independent secondary sourcing. — SMcCandlish ☏ ¢ 😼 13:58, 30 October 2023 (UTC)
- WP cares most what independent sources are doing, not (per MOS:TM) what the trademark holder prefers, when it comes to any style questions. Fictional characters do not have feelings that can be hurt and preferences that can be offended, so the "self-published name change" idea (or anything else derived from WP:ABOUTSELF) cannot apply to them. This initials stylization stuff is pretty much arbitrary, so there's no particular reason not to just follow MOS:INITIALS's default of "J. D. McDonagh", except in a case where a style like "JD McDonagh" is pretty close to universal in independent reliable sources. However, some of the above are not initials, but two-letter acronyms/initialisms, including E.T. and C.C., so the question about them would really be whether to remove the dots. E.T. the Extra-Terrestrial is a work title, so we'd generally be inclined to leave it alone (unless "ET the Extra-Terrestrial" was well represented in sources, too), and thus to write the character as "E.T." to agree with the work title. As for C[.]C[.], I dunno. If the indepdendent sources near-univerally write it as "C.C.", then we would, too. But if they sometimes use "C.C." and sometimes use "CC", we would probably use the MOS:ACRO default of "CC". PS: Googling around, I see some highly speculative claims the C[.]C[.] character actually has an original human name in her backstory, that also has initials of "C. C." (though they can't decide what that name actually is), so that case might be futher complicated/debatable. But only weakly because of lack of any definitive and reliable sourcing at all. Expecially since the human name is not the source of the acronymic CC code name, but just an [alleged] fictional coincidence. — SMcCandlish ☏ ¢ 😼 13:58, 30 October 2023 (UTC)
- BTW, this really is a matter for WT:MOSWAF; it has nothing to do with MOS:BIO. — SMcCandlish ☏ ¢ 😼 13:58, 30 October 2023 (UTC)
- I moved the entire discussion over there, with all comments, since it's just completely off-topic here. — SMcCandlish ☏ ¢ 😼 14:03, 30 October 2023 (UTC)
Ethnicity
It seems that the ethnicity section needs more elaboration. There are missing gaps in the policy; how do we reference people that lived in empires? How do we reference people that lived in abstract geographic regions in past times when no political entity existed? It wouldn't make sense to remove any ethnic/geographic reference from the lede.
Checking a number of Wikipedia biographies reveals this inconsistency: Niccolò Machiavelli, Leonardo da Vinci and Galileo Galilei would be Florentines instead of Italians; Thomas Aquinas would be Sicilian instead of Italian; Jesus would be Roman instead of Jewish; Aristotle would be Chalcidian/Macedonian instead of Greek; Johann Wolfgang von Goethe, Johannes Kepler and Gottfried Wilhelm Leibniz would be "Roman Holy Empirer" instead of German; Maimonides would be Almoravid instead of Sephardic Jewish; Saladin would be Abbasid instead of Kurdish; Muhammad would be identified as having been born in the Hejaz instead of being Arab.
A new paragraph should be added along the lines of: "Persons who lived under empires and persons who lived in abstract geographic regions in pre-modern times, can be referenced by their ethnicity or by mentioning the geographic region if this supported by a majority of sources as a notable identification." Makeandtoss (talk) 14:34, 3 October 2023 (UTC)
- Maybe. Or maybe we should say not to apply ethnic labels to them, since that's primarily a modern concept. — SMcCandlish ☏ ¢ 😼 15:13, 3 October 2023 (UTC)
- It’s neither a modern concept nor is it our job to apply any labels; we take what reliable sources have described them to be. Makeandtoss (talk) 17:24, 3 October 2023 (UTC)
- The word dates to 1765–75, which is well within the Modern English span. But yes, of course, follow the preponderance of usage in the source material. — SMcCandlish ☏ ¢ 😼 17:39, 3 October 2023 (UTC)
- Modern word doesn’t mean modern concept. Makeandtoss (talk) 19:22, 3 October 2023 (UTC)
- The word dates to 1765–75, which is well within the Modern English span. But yes, of course, follow the preponderance of usage in the source material. — SMcCandlish ☏ ¢ 😼 17:39, 3 October 2023 (UTC)
- It’s neither a modern concept nor is it our job to apply any labels; we take what reliable sources have described them to be. Makeandtoss (talk) 17:24, 3 October 2023 (UTC)
- You claim, It wouldn't make sense to remove any ethnic/geographic reference from the lede. Uh, why not exactly? For my money there's entirely too much emphasis on this nonsense. Editing on bios of fascinating figures is dominated by arguments over their nationality or other sorts of identity. Give it a rest. It just doesn't matter that much, and it's fine to leave it out when it isn't clear. --Trovatore (talk) 17:56, 3 October 2023 (UTC)
- Agreed. When it's known, it's usually helpful to say where someone lived (e.g. was this an Ancient Greek philopher or a Roman one? Or Egyptian?), but material (often speculative and based on iffy primary sourcing) that delves into alleged ethnic origin is very often better covered in the article body, with sufficient WP:DUE balance. — SMcCandlish ☏ ¢ 😼 19:16, 3 October 2023 (UTC)
- Sure, when it’s controversial its better to be elaborated in the body. But when it’s not controversial, I see no problems in specifying this in the opening paragraph if supported by a majority of reliable sources; as is currently the case in majority of biographies as demonstrated above. Makeandtoss (talk) 19:31, 3 October 2023 (UTC)
- It's one of the first pieces of context one would be curious about. Readers are used to biographies starting with that. As long as it corresponds with reliables sources, this should be included. If reliable sources only say where the person was born, or lived, or became famous, then we can stick to just that. If it gets into WP:NATIONALIST bickering then yeah it is a waste of our time. —DIYeditor (talk) 19:23, 3 October 2023 (UTC)
- Agreed, the identification by reliable sources should be used in the opening paragraph. If controversial it could be discussed later in lede. My point is these things should be elaborated so that the policy is applied consistently across Wikipedia. Makeandtoss (talk) 19:34, 3 October 2023 (UTC)
- When nationality, residency and citizenship information aren’t available, which is often the case in pre-modern times, something needs to be used to contextualize the subject at hand; and this is the case as seen by a large number of Wikipedia biographies I cited above. A greater conflict will occur if these ethnic references are removed. What I am proposing is to elaborate how this identification could be handled by relying on reliable sources. It definitely matters what context this historical figure lived through; especially if reliable sources have given them due weight. Makeandtoss (talk) 19:27, 3 October 2023 (UTC)
- It matters a little bit. It doesn't matter nearly as much as some editors seem to think. --Trovatore (talk) 19:32, 3 October 2023 (UTC)
- It very much matters to me to know for example that Jesus was a Jew living under the pagan Roman Empire; it provides important context. Makeandtoss (talk) 19:36, 3 October 2023 (UTC)
- There is a significant contingent of editors who think nationality (and similar characteristics) matter more than they do. They do not matter that much. --Trovatore (talk) 19:48, 3 October 2023 (UTC)
- They matter a little enough to deserve a one word mention in the opening paragraph, I don’t think that’s giving these labels that much importance. Makeandtoss (talk) 21:29, 3 October 2023 (UTC)
- There is a significant contingent of editors who think nationality (and similar characteristics) matter more than they do. They do not matter that much. --Trovatore (talk) 19:48, 3 October 2023 (UTC)
- It very much matters to me to know for example that Jesus was a Jew living under the pagan Roman Empire; it provides important context. Makeandtoss (talk) 19:36, 3 October 2023 (UTC)
- It matters a little bit. It doesn't matter nearly as much as some editors seem to think. --Trovatore (talk) 19:32, 3 October 2023 (UTC)
- Agreed. When it's known, it's usually helpful to say where someone lived (e.g. was this an Ancient Greek philopher or a Roman one? Or Egyptian?), but material (often speculative and based on iffy primary sourcing) that delves into alleged ethnic origin is very often better covered in the article body, with sufficient WP:DUE balance. — SMcCandlish ☏ ¢ 😼 19:16, 3 October 2023 (UTC)
- Aristotle would be included in a list of "Greek philosophers" in any reference or scholarly material, would he not? Just stick to the sources. —DIYeditor (talk) 19:25, 3 October 2023 (UTC)
- Exactly, he would be. However the policy doesn’t specify this. It says we should use citizenship, nationality or residency and says that we need to remove ethnic references. What I am proposing is allowing ethnic references if supported by reliable sources. Makeandtoss (talk) 19:28, 3 October 2023 (UTC)
- If the question is “should we mention this person’s ethnicity somewhere in the article?” I would say, “yes… assuming we have sources to support it, we should”.
- However, if the question is “should we highlight this person’s ethnicity by mentioning it in the lead paragraph?” I am much more dubious. The lead paragraph should focus on what makes the person notable, and often (but not always) ethnicity plays no part in that. Blueboar (talk) 20:16, 3 October 2023 (UTC)
- Yes, exactly. We can talk about lots of stuff in the body of the article, as long as there are good sources. The first paragraph, and especially the first sentence, needs to be more focused. --Trovatore (talk) 20:20, 3 October 2023 (UTC)
- And how would you reconcile that with the reality on the ground, that the majority of articles and editors have given the opening paragraph in the lede, at least a brief mention of their ethnicity? Makeandtoss (talk) 21:27, 3 October 2023 (UTC)
- Some of it is just inertia and should stop. Some of it is from nationalists, identitarians, or identity-politics advocates, whom I'm going to oppose. And some of it is reasonable — politicians, generals, etc are likely to be persons for whom these things speak directly to why we want to read about them. --Trovatore (talk) 22:07, 3 October 2023 (UTC)
- You imply the people who disagree with you are doing some kind of WP:ADVOCACY but isn't the same true of your position? Why do you want to change the "inertia" on Wikipedia and elsewhere which is to describe a person's nationality in the beginning of their biography? Britannica generally does so especially of more recent people. De-focusing on national or ethnic identity is an agenda. How does it serve Wikipedia, its pillars, its goals, or its readers other than to promote your worldview? —DIYeditor (talk) 22:47, 3 October 2023 (UTC)
- No. Opposing misuse of WP for advocacy purposes is not magically an "equal but opposite" form of advocacy, it's following our policies, even when we might actually agree, off-site, with what is being advocated. — SMcCandlish ☏ ¢ 😼 23:10, 3 October 2023 (UTC)
- The position that biographies, particularly of people who were alive when modern countries existed, should not start with identifying the nationality, is quite a bold position, and seems to be ADVOCACY. Again, Britannica describes Alan Turing as a "British mathematician". Of course, Catherine of Aragon is not given an ethnicity or nationality which would be harder to justify. For the average person, the first thing they categorize people by after gender is probably nationality. That's the first question they are going to have about the context for a biography article about anyone who has been alive in recent history. Whether Aristotle is "one of the most important ancient Greek philosophers" or "one of the most important philosophers of ancient Greece" is not a difference worth arguing over, what is important is that it is established up front.
- I think you are right, it is not an equal but opposite situation. The advocacy is this novel idea that a biography shouldn't start with nationality if it is possible and appropriate to the person in question. I think if we just stick to the sources, we are going to find most people described with a nationality if possible. For people who predate modern countries indeed a more nuanced treatment may be appropriate, but it should still be in the lead. —DIYeditor (talk) 23:42, 3 October 2023 (UTC)
- For example, from a stub I have been working on, is this an improvement? Is it important? —DIYeditor (talk) 23:53, 3 October 2023 (UTC)
- Yes, removing the "Italian" claim is an improvement, because "Italy" as a nation-state and "Italian" as a concept (other than a vague geographical one that didn't correspond to any political or cultural boundaries), did not exist until much later, with the 19th-century Unification of Italy. Calling Ferrara "Italian" is a terrible anachronism. She was Mantuan, which is not an ethnicity but a geographical specifier and a politico-cultural one to some extent (one temporally limited, like being Pictish). The "from Mantua in modern-day Italy" is perfectly adequate and reasonable, without breaking actual history to pander to racialists/identarians. What we call "Italy" now was back then a patchwork of kingdoms and principalities and whatnot, with a bunch of different languages spoken (some of which still survive as minority languages). For similar reasons, Bridei son of Beli should not be referred to as "Scottish". — SMcCandlish ☏ ¢ 😼 00:04, 4 October 2023 (UTC)
- Ok I think we agree there. It is a worthwhile distinction. I'd support something like this being in the MOS. —DIYeditor (talk) 00:06, 4 October 2023 (UTC)
- How to craft the wording is open to some question, though. — SMcCandlish ☏ ¢ 😼 00:08, 4 October 2023 (UTC)
- Switching for example from Italian to Florentine and Sicilian at Niccolò Machiavelli, Leonardo da Vinci and Galileo Galilei will set off a huge conflict between editors, especially when no reliable source can be attributed for this label (or if minority do). Although I agree that modern identities should not be imposed on the past, however, this is my opinion, and in no way does that mean reliable sources agree (i.e. original research). I would say we stick to what the majority of reliable sources use. Makeandtoss (talk) 12:22, 4 October 2023 (UTC)
- Ok I think we agree there. It is a worthwhile distinction. I'd support something like this being in the MOS. —DIYeditor (talk) 00:06, 4 October 2023 (UTC)
- Yes, removing the "Italian" claim is an improvement, because "Italy" as a nation-state and "Italian" as a concept (other than a vague geographical one that didn't correspond to any political or cultural boundaries), did not exist until much later, with the 19th-century Unification of Italy. Calling Ferrara "Italian" is a terrible anachronism. She was Mantuan, which is not an ethnicity but a geographical specifier and a politico-cultural one to some extent (one temporally limited, like being Pictish). The "from Mantua in modern-day Italy" is perfectly adequate and reasonable, without breaking actual history to pander to racialists/identarians. What we call "Italy" now was back then a patchwork of kingdoms and principalities and whatnot, with a bunch of different languages spoken (some of which still survive as minority languages). For similar reasons, Bridei son of Beli should not be referred to as "Scottish". — SMcCandlish ☏ ¢ 😼 00:04, 4 October 2023 (UTC)
- No. Opposing misuse of WP for advocacy purposes is not magically an "equal but opposite" form of advocacy, it's following our policies, even when we might actually agree, off-site, with what is being advocated. — SMcCandlish ☏ ¢ 😼 23:10, 3 October 2023 (UTC)
- You imply the people who disagree with you are doing some kind of WP:ADVOCACY but isn't the same true of your position? Why do you want to change the "inertia" on Wikipedia and elsewhere which is to describe a person's nationality in the beginning of their biography? Britannica generally does so especially of more recent people. De-focusing on national or ethnic identity is an agenda. How does it serve Wikipedia, its pillars, its goals, or its readers other than to promote your worldview? —DIYeditor (talk) 22:47, 3 October 2023 (UTC)
- Some of it is just inertia and should stop. Some of it is from nationalists, identitarians, or identity-politics advocates, whom I'm going to oppose. And some of it is reasonable — politicians, generals, etc are likely to be persons for whom these things speak directly to why we want to read about them. --Trovatore (talk) 22:07, 3 October 2023 (UTC)
- Then according to MOS: ETHNICITY, Adolf Hitler should be listed only as German and not Austrian-born German (even though that is exactly what he is) as he is listed. Also, he renounced his Austrian citizenship in 1925. Zapho653 (talk) 22:59, 21 October 2023 (UTC)
- There's a different relevant guideline MOS:BIRTHPLACE:
—Bagumba (talk) 00:11, 22 October 2023 (UTC)Birth and death places, if known, should be mentioned in the body of the article, and can appear in the lead if relevant to notability...
- Then it should go for everyone who was not born in the same country they were raised. For instance, the Young brothers (especially George, Malcolm and Angus) are all cited only as Australians instead of Scottish-born Australians (as they were all born in Glasgow), or the Van Halen brothers, who were Dutch-born Americans (who were born in Amsterdam and raised in Nijmegen), but are only listed as Americans. Or is that irrelevant in their case? Zapho653 (talk) 13:27, 22 October 2023 (UTC)
- You would need to establish consensus to change that, as it currently says to mention it
if relevant to notability
—Bagumba (talk) 13:32, 22 October 2023 (UTC)- Understood. But just to be sure, in Hitler's case, is there any consensus saying that his birthplace is relevant for his notability for him to be listed as Austrian-born German? That is all I want to know. Zapho653 (talk) 13:36, 22 October 2023 (UTC)
- That's a question to ask at Talk:Adolf Hitler. WT:MOSBIO isn't really for arguing out the details of every individual bio article, or there would be thousands of threads on this page. — SMcCandlish ☏ ¢ 😼 22:13, 22 October 2023 (UTC)
- Understood. But just to be sure, in Hitler's case, is there any consensus saying that his birthplace is relevant for his notability for him to be listed as Austrian-born German? That is all I want to know. Zapho653 (talk) 13:36, 22 October 2023 (UTC)
- You would need to establish consensus to change that, as it currently says to mention it
- Then it should go for everyone who was not born in the same country they were raised. For instance, the Young brothers (especially George, Malcolm and Angus) are all cited only as Australians instead of Scottish-born Australians (as they were all born in Glasgow), or the Van Halen brothers, who were Dutch-born Americans (who were born in Amsterdam and raised in Nijmegen), but are only listed as Americans. Or is that irrelevant in their case? Zapho653 (talk) 13:27, 22 October 2023 (UTC)
- There's a different relevant guideline MOS:BIRTHPLACE:
"in modern-day [x]"
I found this discussion via "Margherita Gonzaga, Marquise of Ferrara", which I'd arrived at from a search for the term "in modern day Italy". It seems to me that using "modern-day" (or "modern day", or simply "modern") in this way often leads to absurdities. Earlier today I learnt that "Capsian [neolithic] culture was concentrated mainly in modern Tunisia"; previously, that "Etruscan was the language of the Etruscan civilization in modern day Italy", and that the Third Punic War "was fought entirely within Carthaginian territory, in modern northern Tunisia". Elsewhere, I learn that the Gothic language was "preserved and transmitted by northern Ostrogoths in modern-day Italy".
I'm old-fashioned, and quite British, but is it really acceptable to use "modern" or "modern-day" like that? There are no Ostrogoths in modern-day Italy, the Third Punic War was not fought in modern Tunisia, and the Etruscan civilisation died out long before modern Italy was thought of. Margherita Gonzaga was born in Mantua, and Mantua is now in Italy, but she wasn't born in modern Italy, or in modern-day Italy. Doesn't the Manual of Style have anything to say about this? Jean-de-Nivelle (talk) 23:37, 14 October 2023 (UTC)
- It's a common locution meaning "a place that today is (in) X". Largoplazo (talk) 01:01, 15 October 2023 (UTC)
- I understand how it's being used. I just wonder why it's being used in that way, and whether it should be. Jean-de-Nivelle (talk) 08:51, 15 October 2023 (UTC)
- I don't see any reason why it shouldn't be. It's being used that way because language evolves, words get compressed, and long phrases are collapsed: "taxi" instead of "taxicab" or, before that, "taximeter cabriolet", for example. Similarly, if someone uses the word "nice", we don't worry about the fact that the word used to mean, not "pleasant", but "stupid" or why its meaning evolved. We just use it with the generally understood meaning it has today. Largoplazo (talk) 11:59, 15 October 2023 (UTC)
- I do understand that language evolves. I suppose my question (and thank you for helping me refine it) is this: has this usage evolved to a point that it can now be considered encyclopaedic? My own instinct is that it hasn't. Britannica, for example, is much more careful in its use of the construction. But I'm old-fashioned. Jean-de-Nivelle (talk) 13:13, 15 October 2023 (UTC)
- I don't see any reason why it shouldn't be. It's being used that way because language evolves, words get compressed, and long phrases are collapsed: "taxi" instead of "taxicab" or, before that, "taximeter cabriolet", for example. Similarly, if someone uses the word "nice", we don't worry about the fact that the word used to mean, not "pleasant", but "stupid" or why its meaning evolved. We just use it with the generally understood meaning it has today. Largoplazo (talk) 11:59, 15 October 2023 (UTC)
- I understand how it's being used. I just wonder why it's being used in that way, and whether it should be. Jean-de-Nivelle (talk) 08:51, 15 October 2023 (UTC)
- It's a common locution meaning "a place that today is (in) X". Largoplazo (talk) 01:01, 15 October 2023 (UTC)
- In any case where something confusing has resulted from poor writing, like "Capsian Neolithic culture was concentrated mainly in modern[-day] Tunisia", just rewrite it to make sense. This is not rocket science. "Capsian Neolithic culture was concentrated mainly in what today is Tunisia". Likewise, this kind of rewording would fix every single bad example given above. There is not cause for some "new rule" here. Just WP:BEBOLD and fix it. — SMcCandlish ☏ ¢ 😼 03:11, 15 October 2023 (UTC)
- I'm not arguing for a "new rule", and note that I've "fixed" most of the examples I gave above. But I don't want to waste my time "fixing" problems that aren't generally regarded as problems, which is why I asked the question. I've been looking for a more appropriate place to ask, but this will do. "In what is now Italy" or "in what is today Italy" seem more appropriate (to me) in nearly every case, but this use of "modern" is common enough that I wonder if it's acceptable to other readers. What's intended by it is generally fairly clear. In the case of Italy, we could also argue that "Italy" has a geographical sense as well as a political one, and that Mantua was in Italy, if not in Italy, when Margherita Gonzaga was born there. But that's not the case for every country. Jean-de-Nivelle (talk) 08:51, 15 October 2023 (UTC)
- Sure, I'm just saying excercise your own judgment when there's not a rule about it. I've seen plenty of "modern [Foo]" cases that were not confusing, but the ones highlighted above clearly had potential to be. It's more likely to be confusing when some action/event is the subject, and seems to be implied to have taken place in modern times. But there's no issue with writing "medieval Ossory (modern Kilkenny and western Laois)". — SMcCandlish ☏ ¢ 😼 08:58, 15 October 2023 (UTC)
- If you are going to distinguish between Italy (geographical region) and Italy that is going to need to be clearly linked with no sneaker links from "Italy" to something else. Maybe it would be better to say "on the Italian peninsula" in that article? I made the edit to Margherita Gonzaga, Marquise of Ferrara for illustrative purposes in this discussion, there are two other similar articles I've made of her female relatives (Paola Malatesta and Margherita Malatesta) which are now in two variations (bringing the total to three variations) of how to describe it. I don't think it's that important of an issue as long as you don't equivocate on the meaning of "Italy" or use it in a confusing or potentially inaccurate manner. —DIYeditor (talk) 22:33, 15 October 2023 (UTC)
- "Italian Peninsula" also has an article. My own inclination would be simply to describe Mantua as being "in what is now Italy". Or perhaps we could use "Italian city-state": Margherita Gonzaga ... was a noblewoman of the House of Gonzaga from the Italian city-state of Mantua. Jean-de-Nivelle (talk) 10:44, 16 October 2023 (UTC)
- Mantua was always in Italy. Just because there was at the time no sovereign state called Italy (or, indeed, Germany) doesn't mean the terms weren't used for the areas now occupied by those countries. There is absolutely nothing wrong with saying Mantua was in Italy, even if referring to a time before the sovereign state existed. And linking Italy is unnecessary per WP:OVERLINKING. -- Necrothesp (talk) 13:32, 16 October 2023 (UTC)
- (ec) ExactlyThere are tens of thousands of articles on Italian subjects predating the Unification of Italy, and there is absolutely no reason not to do what the vast majority do, which is just to link to "Italy". Italy was was a well-understood cultural area from Roman republican times, let alone during the Renaissance, with pretty trivial differences as to the area the term embraced. RS use the term constantly without feeling the need to explain anything. There's no point linking to geographical articles like Italy (geographical region) or Italian Peninsula. Really there's no reason for a link at all, as Italy is well enough known. Tunisia and Germany, even France, are rather less simple cases. Johnbod (talk) 13:41, 16 October 2023 (UTC)
- How about this for Caterina de' Medici, Governor of Siena. Or should she just be "Italian" since she had a Mantuan title by marriage? Actually I think "Tuscan" is the most correct in this case? My reason for suggesting it was because Catherine de' Medici is described as Florentine (linked thus). —DIYeditor (talk) 23:54, 19 October 2023 (UTC)
- "Tuscan" would make more sense than "Italian". — SMcCandlish ☏ ¢ 😼 18:41, 26 October 2023 (UTC)
- How about this for Caterina de' Medici, Governor of Siena. Or should she just be "Italian" since she had a Mantuan title by marriage? Actually I think "Tuscan" is the most correct in this case? My reason for suggesting it was because Catherine de' Medici is described as Florentine (linked thus). —DIYeditor (talk) 23:54, 19 October 2023 (UTC)
- "Italian Peninsula" also has an article. My own inclination would be simply to describe Mantua as being "in what is now Italy". Or perhaps we could use "Italian city-state": Margherita Gonzaga ... was a noblewoman of the House of Gonzaga from the Italian city-state of Mantua. Jean-de-Nivelle (talk) 10:44, 16 October 2023 (UTC)
- I'm not arguing for a "new rule", and note that I've "fixed" most of the examples I gave above. But I don't want to waste my time "fixing" problems that aren't generally regarded as problems, which is why I asked the question. I've been looking for a more appropriate place to ask, but this will do. "In what is now Italy" or "in what is today Italy" seem more appropriate (to me) in nearly every case, but this use of "modern" is common enough that I wonder if it's acceptable to other readers. What's intended by it is generally fairly clear. In the case of Italy, we could also argue that "Italy" has a geographical sense as well as a political one, and that Mantua was in Italy, if not in Italy, when Margherita Gonzaga was born there. But that's not the case for every country. Jean-de-Nivelle (talk) 08:51, 15 October 2023 (UTC)
Two Examples, and Comments
First, I agree with User:Makeandtoss that the ethnicity section needs clarification. That is evidenced, among other things, by two disputes that I am mediating, and I don't usually mediate two disputes about the same class of issue at the same time.
One of them, Marco Polo, really does involve whether you can refer to medieval Italians as Italians, and the specific questions are:
- 1. Can persons born on the Italian peninsula between 476 AD and 1860 AD be referred to as Italian?
- 2. Can persons born in the Republic of Venice between 697 AD and 1797 AD be referred to as Venetian?
- 3. Can a person be both Venetian and Italian?
I think that the answer to all three questions is yes. In particular, Italy was a geographic region, and a part of the Roman Empire, long before the Kingdom of Italy was proclaimed. I think that we need a statement to that effect somewhere, because the issue keeps coming up.
The second dispute is more controversial, and has to do with Sergei Bortkiewicz, a composer who was born in what is now Ukraine, which was part of the Russian Empire at the time. Since blood is being spilled as I write this, we clearly need to be ready to deal with disputes about persons born in what is now Ukraine. Robert McClenon (talk) 17:43, 26 October 2023 (UTC)
- The historically accurate name should be used. GiantSnowman 17:59, 26 October 2023 (UTC)
- User:GiantSnowman your statement to use the historically accurate name is useful but inadequate. Both Italian and Venetian are accurate for Marco Polo, since Italy was a defined geographic region even when it was not a nation. In the case of Sergei Bortkiewicz, how do you define historical accuracy? Robert McClenon (talk) 23:59, 26 October 2023 (UTC)
- Except Italian is not "accurate" in this case because it has multiple meanings, and the most common one in readers' minds is the present nation-state of Italy. "Italian" in such a case is confusing and ambiguous at best, and even directly misleading. "Italy was a defined geographic region" in Marco Polo's time is even debatable. We certainly can't have an across-the-board expectation that every reader agrees with this, much less an assumption that each understands that our article means "Italy as a geographic region not a nation-state". There was not even an Italian language in that era, but a continuum of related Italic languages (some of which still separately survive). The idea that what we now call Italy had a consistent culture throughout it and that people living in it thought of themselves as Italians is highly questionable and not something anyone has proven with reliable sources. So applying such a label to Marco Polo is not appropriate. It makes much more sense to say that he was from the Republic of Venice in what today is Italy. — SMcCandlish ☏ ¢ 😼 01:43, 28 October 2023 (UTC)
- User:GiantSnowman your statement to use the historically accurate name is useful but inadequate. Both Italian and Venetian are accurate for Marco Polo, since Italy was a defined geographic region even when it was not a nation. In the case of Sergei Bortkiewicz, how do you define historical accuracy? Robert McClenon (talk) 23:59, 26 October 2023 (UTC)
- @Robert McClenon: I am only surprised how a discussion about this hasn't been opened here before. They should be able to be referred to as Italian if its supported by majority of reliable sources; while Sergei should be referred to as whatever most RS claim (without contradicting he was Russian Empire citizen). My line of thinking is as follows:
- So to identify the problem: it is the presence of conflicting ethnic identifications and the raging disputes around them.
- The possible solutions to this: we leave it for editors to decide amongst themselves (an original research disaster as currently seen by the raging disputes and the obvious bigger problem of inconsistency across Wikipedia as evidenced by my examples above); or simply using what the majority of reliable sources have said. The latter option is simple, straightforward and to the point.
- The sentence to be added as part of the only solution: "Persons who lived under empires and persons who lived in abstract geographic regions in pre-modern times, can be mainly referenced by their ethnicity or the geographic region only when this supported by a majority of sources as a notable identification." Makeandtoss (talk) 18:03, 26 October 2023 (UTC)
- Something like that could work. It defaults to the "use the historically accurate term" position that GiantSnowman just posted and which I also argued in the thread above (and which I regularly observe to be our general practice; we don't call Julius Caesar an Italian, but a Roman), while leaving room for this default to be overridden by sourcing. More specifically, that should only happen when a preponderance of modern, independent, reliable sources use not the historical term we would default to but agree on another alternative term. If they don't largely agree on a particular alternative, then our default should still apply, even if it is not found in the majority of sources (if chaos reigns, then it will be our chaos, not one of competing external chaoses). Needs a little other wordsmithing, like "is" missing between "this" and "supported", and "notable identification" not really meaning anything concrete. That's not how we use the word "notable". But the germ of the right idea is in here. PS: On Marco Polo, I would think it would be "Venetian" not "Italian", which is in at least some senses anachronistic as well as unhelpfully (for that time period) vague. — SMcCandlish ☏ ¢ 😼 18:40, 26 October 2023 (UTC)
- We don't call Julius Caesar an Italian because the majority of RS call him a Roman. Similarly for Marco Polo, a quick Google search reveals that he is more referred to as Venetian rather than Italian. I stress again that we must follow RS, like we do for anything else on Wikipedia, rather than leave this to original research and thus apply it inconsistently across Wikipedia as it is the case currently. And to stress, we are currently talking about ethnic identification in the opening paragraph, which doesn't negate the fact that conflicting identities could be elaborated elsewhere in the body. Ex: Marco Polo was a Venetian merchant... And in the body: Marco Polo was a Venetian merchant, but a number of sources have also referred to him as being Italian. Makeandtoss (talk) 19:47, 26 October 2023 (UTC)
- Something like that could work. It defaults to the "use the historically accurate term" position that GiantSnowman just posted and which I also argued in the thread above (and which I regularly observe to be our general practice; we don't call Julius Caesar an Italian, but a Roman), while leaving room for this default to be overridden by sourcing. More specifically, that should only happen when a preponderance of modern, independent, reliable sources use not the historical term we would default to but agree on another alternative term. If they don't largely agree on a particular alternative, then our default should still apply, even if it is not found in the majority of sources (if chaos reigns, then it will be our chaos, not one of competing external chaoses). Needs a little other wordsmithing, like "is" missing between "this" and "supported", and "notable identification" not really meaning anything concrete. That's not how we use the word "notable". But the germ of the right idea is in here. PS: On Marco Polo, I would think it would be "Venetian" not "Italian", which is in at least some senses anachronistic as well as unhelpfully (for that time period) vague. — SMcCandlish ☏ ¢ 😼 18:40, 26 October 2023 (UTC)
- I entirely agree that the answer to all three questions is yes. However, we don't need to say "Venetian and Italian" (any more than we need to say "English and British"). "Venetian" is fine. Stick to RS, per usual. -- Necrothesp (talk) 08:16, 27 October 2023 (UTC)
- @Necrothesp: That's precisely the problem, sticking to RS isn't highlighted in the guideline, which states instead that any ethnic identification must not be included in lede, and thus leaving us with countless of raging disputes. Makeandtoss (talk) 10:18, 27 October 2023 (UTC)
- Some of these people might only be included in a book on e.g. Italian subjects and never described in a particular RS as being from the sovereign state they were born in. —DIYeditor (talk) 10:22, 27 October 2023 (UTC)
- @DIYeditor: Again, also the problem lies here. If we identify people using the sovereign state they were born in, then Jesus would be a Roman and not a Jew. He was indeed a Roman citizen, but the notable identification is that he was a Jew ethnically, and that is only because this is what most RS have used. However, this rationale is not specified here in the guideline, and leaves raging disputes. Makeandtoss (talk) 10:47, 27 October 2023 (UTC)
- Going by consensus across RSs seems like a good rule of thumb. I think there can be a false consensus due to what I described with some sources being more general and only making a passing or brief mention of the person whose information is being cited, even if when mentioned as the primary subject they might be called something else. —DIYeditor (talk) 11:19, 27 October 2023 (UTC)
- "Going by consensus across RSs seems like a good rule of thumb." Again, this is the current situation, and has failed to stymie disagreements. The policy needs amendment. Makeandtoss (talk) 11:22, 27 October 2023 (UTC)
- Jesus was not a Roman citizen. In the provinces of the Roman Empire, Roman citizenship was the exception rather than the rule. Roman citizens who were put to death were not crucified. That is why St. Paul was beheaded while St. Peter was crucified. What this illustrates is that the modern concept of citizenship may cause confusion when we try to apply it to earlier times. That is, of course, why we are here, and why this discussion is complex. Robert McClenon (talk) 17:32, 30 October 2023 (UTC)
- Fair enough but St. Paul is not called a Roman citizen either, rather a Christian apostle. Again, my argument remains the same: usage of what majority of RS are reporting. Makeandtoss (talk) 09:34, 31 October 2023 (UTC)
- Going by consensus across RSs seems like a good rule of thumb. I think there can be a false consensus due to what I described with some sources being more general and only making a passing or brief mention of the person whose information is being cited, even if when mentioned as the primary subject they might be called something else. —DIYeditor (talk) 11:19, 27 October 2023 (UTC)
- @DIYeditor: Again, also the problem lies here. If we identify people using the sovereign state they were born in, then Jesus would be a Roman and not a Jew. He was indeed a Roman citizen, but the notable identification is that he was a Jew ethnically, and that is only because this is what most RS have used. However, this rationale is not specified here in the guideline, and leaves raging disputes. Makeandtoss (talk) 10:47, 27 October 2023 (UTC)
- Some of these people might only be included in a book on e.g. Italian subjects and never described in a particular RS as being from the sovereign state they were born in. —DIYeditor (talk) 10:22, 27 October 2023 (UTC)
- @Necrothesp: That's precisely the problem, sticking to RS isn't highlighted in the guideline, which states instead that any ethnic identification must not be included in lede, and thus leaving us with countless of raging disputes. Makeandtoss (talk) 10:18, 27 October 2023 (UTC)
Proposal for the adoption of a new rule regarding anachronism
I started a Village pump (proposals) discussion regarding the problem of anachronism in the articles, considering that the articles are uneven in this regard. If there are sources that speak differently about a historical person, I don't think we can use that argument alone ie only RS argument. Because with the will of most editors and some sources if there are any, we can have anachronistic information in the article. Thus, for a certain Roman emperor, we could put information in the article that he was the Italian emperor. The key problem is that we do not have any guidelines regarding anachronism in the articles. If you want to discuss this problem, feel free to join. Wikipedia:Village_pump_(proposals)#Rule_that_will_cover_anachronistic_informations_in_the_articles
Mikola22 (talk) 07:21, 31 October 2023 (UTC)
- The discussion at Village pump (proposals) has largely fizzled out. In my opinion, it was in the wrong forum. Mikola22 did not specify what they wanted to do about "anachronisms", so that their idea was a partially baked idea rather than a proposal, and should have been at the Idea Lab if anywhere. I think that if there are any remaining issues that need to be addressed (and I think that they are), they can be addressed here. Robert McClenon (talk) 04:22, 7 November 2023 (UTC)
- I proposed to adopt a new rule concerning anachronism in articles. The only place for that procedure is Village pump (proposals). And in that sense I presented the proposal there. Mikola22 (talk) 05:53, 7 November 2023 (UTC)
- You presented a proposal to present a proposal, and the community was not interested. Robert McClenon (talk) 16:42, 7 November 2023 (UTC)
- I proposed to adopt a new rule concerning anachronism in articles. The only place for that procedure is Village pump (proposals). And in that sense I presented the proposal there. Mikola22 (talk) 05:53, 7 November 2023 (UTC)
- The discussion at Village pump (proposals) has largely fizzled out. In my opinion, it was in the wrong forum. Mikola22 did not specify what they wanted to do about "anachronisms", so that their idea was a partially baked idea rather than a proposal, and should have been at the Idea Lab if anywhere. I think that if there are any remaining issues that need to be addressed (and I think that they are), they can be addressed here. Robert McClenon (talk) 04:22, 7 November 2023 (UTC)
Do we want to discuss further? Do we have consensus? Has this discussion fizzled out?
Is there agreement that the MOS can be left alone? Do we need to formalize anything, such as that we should state what the majority of reliable sources say? Robert McClenon (talk) 04:52, 7 November 2023 (UTC)
- Majority of reliable sources can say that someone is Italian even though he lived in the Roman Empire and the Roman era. So most of the sources in this case mean nothing as an argument. As far as I know, the information in the article must be presented in a time context, at least as far as the biography of famous people is concerned. Mikola22 (talk) 06:02, 7 November 2023 (UTC)
The specific case of medieval Italy
A specific question that recurs from time to time has to do with people born in the region of Italy between 476 AD and 1860 AD, who are often referred to as Italian, but also often the subject of arguments because there was not an Italian state. Should we specifically discuss either a rule that this characterization should be avoided, or that this characterization is permitted? Robert McClenon (talk) 04:52, 7 November 2023 (UTC)
- I don't think it's just a problem of medieval Italy. This is problem of all European countries, historical peoples, etc. What I know from experience is that information in articles must be presented in a time context. This would mean if Italy as a country existed only from 1860 AD then from that year we can talk that someone is Italian. Mikola22 (talk) 06:19, 7 November 2023 (UTC)
- The issue here is that there is often overlap between the names of modern political states, and the names of geographical area in which they exist. It is not anachronistic to talk of “Germany”, “Italy”, “Ireland” (etc) in a geographical context - even for periods prior to the formation of the modern nation states of the same name. Similarly, “German”, “Italian”, “Irish” (etc) can refer to ethno-geographic peoples as well as citizens of modern political units.
- Context is important. When you say “Florence was one of the most influential cities in Italy during the Renaissance” it is understood that you are using “Italy” in its geographic context and not its modern political context.
- There are limits, however. While it is not anachronistic to say that Normandy was an important region of medieval France, it would be anachronistic to say that Julius Caesar invaded France and defeated the French. This is because “France” and “French” are not used in an ethno-geographic sense in relation to Caesars’s time frame. Blueboar (talk) 17:53, 7 November 2023 (UTC)
Minor consolidation merge
Please see Wikipedia talk:Manual of Style/Trademarks#Minor consolidation merge - Idea to merge a line-item (about stylization of stage/pen names) out of MOS:INITIALS (where the one of the examples is only semi-pertinent anyway) and into MOS:TM, leaving behind a cross-reference to MOS:TM from MOS:NAMES. — SMcCandlish ☏ ¢ 😼 14:22, 8 November 2023 (UTC)
Death cause parameter in infobox
Quite a while I posted on the person infobox template talk page to ask about this. I checked back again just now and saw my attempt at a discussion disappeared but an identical one is there now from another editor. Someone suggested to try here. The template doc says to only include this parameter when "the cause of death has significance for the subject's notability." However, it appears this is inconsistently enforced and honestly it seems extremely objective and in some cases difficult to prove. The prime example is Michael Jackson. Can we honestly and truly say one of the best selling and most popular artists of all-time's cause of death had significance to his notability? The death itself, absolutely. But the actual cause? Not necessarily. He's the only one I can come up with that's a good example but I'm sure there's others. People like Tupac Shakur, John Lennon, that were murdered and had their legacies live on partially due to how they died makes sense. Elvis had his for the longest but it was recently removed (I've since added it back). I'm looking to either change this silly having "significance for the subject's notability" rule or make it a little more clear as to what exactly this means. There's a single editor I will not mention by name that has been on a tear over the last couple of years of removing death cause parameter, sometimes for articles that have had it up for years (like Elvis).--Rockchalk717 05:52, 15 November 2023 (UTC)
Initials derived from names with "Jr."
MOS:INITIALS reads:Would this also apply for people with "Jr." in their name, for example, D. J. Hayden, whose full name is Derek Sherrard Hayden Jr.? —Bagumba (talk) 08:10, 12 November 2023 (UTC)With initials, it is not necessary to spell out why the article title and lead paragraph give a different name. For example, H. P. Lovecraft has that title, H. P. Lovecraft appears in his infobox, and his lead sentence just gives Howard Phillips Lovecraft ... was an American writer ..., without "explaining" to the reader what "H. P." stands for.
- I don’t think MOS:INITIALS is relevant since he is known as “D.J.” and not “D.S.” … This example seems to be more a case of an initialized nickname than a true use of initials (at least I assume that “D.J.” stands for “Derek Jr.”) (Blueboar (talk) 12:21, 12 November 2023 (UTC)
- My main question is whether "D. J." should be presented in the lead sentence or not. And whatever is decided, does it warrant some mention in the MOS? —Bagumba (talk) 12:49, 12 November 2023 (UTC)
- Should likely be in the lead sentence, since it's what he's best known as but is not instantly apparent from what his full name is (especially since "DJ" or "D. J." is also used occupationally/avocationally, from "disc jockey"). Edge cases like this nearly never need new MoS line items (WP:MOSBLOAT!) since they don't come up often, aren't a subject of recurrent "stylewarring", and are easy enough to figure out from the existing rules after a short discussion). — SMcCandlish ☏ ¢ 😼 18:57, 12 November 2023 (UTC)
- MOSBLOAT: For the record, it did come up here with edit summary
Don't need to add DJ here if it's obvious where it comes from
. —Bagumba (talk) 00:29, 13 November 2023 (UTC)- Well, it's not obvious where it comes from. Even my 95% sure assumption that it's from "Derek Junior" could be flat-out wrong, and he could have picked up the nickname from DJing at parties. — SMcCandlish ☏ ¢ 😼 05:04, 13 November 2023 (UTC)
- "<first-name initial>. J." is common for people named "Jr.". However, I only came to know this later in life, and I'm guessing a lot of readers might not even be aware of it. —Bagumba (talk) 05:36, 13 November 2023 (UTC)
- And it might be largely an Americanism; I've learned the British "Juniors" typically drop the Junior after the death of the father rather than treating it as lifelong and indelible part of their name. — SMcCandlish ☏ ¢ 😼 05:48, 13 November 2023 (UTC)
- "<first-name initial>. J." is common for people named "Jr.". However, I only came to know this later in life, and I'm guessing a lot of readers might not even be aware of it. —Bagumba (talk) 05:36, 13 November 2023 (UTC)
- Well, it's not obvious where it comes from. Even my 95% sure assumption that it's from "Derek Junior" could be flat-out wrong, and he could have picked up the nickname from DJing at parties. — SMcCandlish ☏ ¢ 😼 05:04, 13 November 2023 (UTC)
- MOSBLOAT: For the record, it did come up here with edit summary
- Should likely be in the lead sentence, since it's what he's best known as but is not instantly apparent from what his full name is (especially since "DJ" or "D. J." is also used occupationally/avocationally, from "disc jockey"). Edge cases like this nearly never need new MoS line items (WP:MOSBLOAT!) since they don't come up often, aren't a subject of recurrent "stylewarring", and are easy enough to figure out from the existing rules after a short discussion). — SMcCandlish ☏ ¢ 😼 18:57, 12 November 2023 (UTC)
- My main question is whether "D. J." should be presented in the lead sentence or not. And whatever is decided, does it warrant some mention in the MOS? —Bagumba (talk) 12:49, 12 November 2023 (UTC)
- Go with MOS:QUOTENAME: Derek Sherrard "D. J." Hayden Jr.? Largoplazo (talk) 13:01, 12 November 2023 (UTC)
- Cleaner markup: Derek Sherrard "D. J." Hayden Jr. .... But it would probably be more appropriate to go with: Derek Sherrard Hayden Jr., best known as D. J. Hayden, ..... What we have here is an unsual case where someone is habitually called D. J. as short for "Derek Junior", so it's really a form of hypocorism (as WP broadly uses that term, to include shortenings), not a nickname like "Spanky" or "Killer", so it really doesn't belong in quotation marks as a nickname. — SMcCandlish ☏ ¢ 😼 18:53, 12 November 2023 (UTC)
...case where someone is habitually called D. J. as short for "Derek Junior", so it's really a form of hypocorism (as WP broadly uses that term, to include shortenings), not a nickname like "Spanky"...
: I think many might stumble on the nuance between a nickname and hypocorism to determine whether to quote or not, or simply mix this up with MOS:INITIALS. —Bagumba (talk) 00:51, 13 November 2023 (UTC)- Doesn't much matter, because someone else will clean it up later if they care, and it's not hard to remember anyway: if it's not something kind of silly like "Thunderman" or "Cheeks", or a weird half-descriptive half-praising phrase like "Wonder from Wolverhampton" – i.e. if it's not an actual nickname in the usual sense, as opposed to a simple name-shortening like "C. C." or "Beth" – then don't put it in scare-quotes. — SMcCandlish ☏ ¢ 😼 05:48, 13 November 2023 (UTC)
- Cleaner markup: Derek Sherrard "D. J." Hayden Jr. .... But it would probably be more appropriate to go with: Derek Sherrard Hayden Jr., best known as D. J. Hayden, ..... What we have here is an unsual case where someone is habitually called D. J. as short for "Derek Junior", so it's really a form of hypocorism (as WP broadly uses that term, to include shortenings), not a nickname like "Spanky" or "Killer", so it really doesn't belong in quotation marks as a nickname. — SMcCandlish ☏ ¢ 😼 18:53, 12 November 2023 (UTC)
- Just throwing out there that Robert Downey Jr. is often nicknamed "RDJ". BD2412 T 18:30, 14 November 2023 (UTC)
- That's in the same class "JLo" and "WinRy" and "JenLaw" - shortenings made up by fans and sometimes the intertainment press but which aren't generally used by the subjects themselves. Sometimes called "nicknames" anyway, but really a different class of things, and probably not encyclopedic except in some cases to mention but not to use in Wikipedia's own voice. — SMcCandlish ☏ ¢ 😼 22:27, 15 November 2023 (UTC)
"MOS: SURNAME" listed at Redirects for discussion
The redirect MOS: SURNAME has been listed at redirects for discussion to determine whether its use and function meets the redirect guidelines. Readers of this page are welcome to comment on this redirect at Wikipedia:Redirects for discussion/Log/2023 December 5 § MOS: SURNAME until a consensus is reached. Utopes (talk / cont) 04:04, 5 December 2023 (UTC)
Minor overhauling
I've done one of my periodic "guideline overhaul" jobs , that should not result in any substantive changes (no new style rules or deletion of or meaning change to existing rules), but with a lot of cleanup:
- Took the scattered and hard-to-find material on when exceptions are made and put it into a section, "Unusual exceptions", with the existing examples plus some new ones (actual cases, not made-up).
- Improved cross-referencing to various other guidelines & policies.
- Fixed a number of markup/code errors.
- Normalized the cross-referencing style.
- Patched up the Genghis Khan example to use a footnote at its own example location instead of commingled with the page-wide footnotes about the guideline.
- Various markup consistency tweaks.
- Replaced one or two bad examples (pages that have since moved, etc.), and fixed some other links.
- Added a couple of anchors and shortcuts.
- Cleaned up links further, so that we are not linking to shortcut targets (those are for editorial convenience not for trying to educate new editors what is what and where it is), but without spamming a visual "Wikipedia:" all over the page when "WP:" will do.
- Trimmed some redundant or blathery wording.
- Cleaned up headings to be more readable in the code by moving anchor spans inside them to the end of the heading instead of the start; also removed a case of a template used inside a heading.
- Minor copyediting for clarity and grammar.
- MOS:LISTGAPS repair.
- Semantic markup.
- Normalized to a single dash style per MOS:DASH; went with spaced en dashes since it strongly dominates throughout the MoS pages, over unspaced em dashes which are harder to read.
- For post-nominal punctuation, I changed "If discussion cannot determine which style to use in an article, defer to the style used by the first major contributor" to instead read "... the style used in the first post-stub version of the article to include a post-nominal", since this is actually how we do such things, the original wording wasn't actually logical for this kind of case (major contributors for years could have been editing an article before any post-nom was added to it), the revised wording doesn't confuse anyone into thinking some particular editor has more say in the matter (historically a frequent confusion about "first major contributor" wording, despite WP:OWN policy), and it is more consistent with most other *VAR provisions' wording (any stragglers in this regard should be revised).
I don't think any of this will be controversial, but of course feel free to raise an objection if I've broken something (or just go fix it). — SMcCandlish ☏ ¢ 😼 15:37, 12 December 2023 (UTC)
Nothing wastes more editor time than WP:JOBTITLES
Just look at this talk page. Look at the archives. JOBTITLES is constantly discussed. Not even people familiar with MOS understand it. Alternatively, pay attention to Wikipedia:Main Page/Errors: the most common point of contention there is capitalization because mere mortals cannot wrap their minds around what JOBTITLES is trying to say. It is absurdly convoluted, to the point that it does not reflect either academic and journalistic usage or government usage.
To illustrate, this mumble is the only correct way to capitalize per MOS:JOBTITLES:
John F. Kennedy was President of the United States. He was the president of the United States from 1961 to 1963. Before he became president, Kennedy served in both houses of the U.S. Congress. The President served at the height of the Cold War. In 1963, President Kennedy was assassinated.
We will all be spared the eyesore of apparently random capitalization as well as the incessant questions about the intention of MOS:JOBTITLES if we just adopt the style that is almost universally used in academic and journalistic writing, namely:
John F. Kennedy was president of the United States. He was the president of the United States from 1961 to 1963. Before he became president, Kennedy served in both houses of the U.S. Congress. The president served at the height of the Cold War. In 1963, President Kennedy was assassinated.
Only capitalize job titles when preceding the person's name. That's it. No "when not in plural", "when not preceded by a modifier", "when not a reworded description" and all those other conditions that make MOS look like a computer code. Just do as academic and journalistic style guides do.
So, to spare us yet another unproductive discussion about this, I beg your answer to two questions:
- Would a proposal to simplify JOBTITLES have a chance of succeeding or are we stuck with this horrid halfway that none of us actually likes?
- How would one go about officially proposing a change such as this one in the most clear, succinct manner?
Thanks and bear with me. Surtsicna (talk) 19:47, 5 November 2023 (UTC)
- A proposal like this could probably grow legs, since the section in question has mutated over time into a palimpsestuous mess. I think workshopping it here and seeing what the general reaction is will be a good first step. If it comes to a local consensus, I think I would propose it at WP:VPPOL, because the change would affect a wide swath of articles. For my part, I'm in favor of the idea, because I agree the current system is complicated and confusing and produces text that might be reader-confusing (at least as to whether any rationale is at work); WP, like Chicago Manual and various academic-leaning publishers has a default-toward-lower-case or "downcasing" position across the board already; and we have too much of a MOS:BLOAT problem with tiny nitpicks being added all the time instead of sticking to general principles and not making exceptions unless a need for one seems overwhelming.That said, there are apt to be some tweaks and codicils, e.g. some titles come after instead of before names, so it's really a matter of the title being directly attached to the name, fore or aft. (But then people will argue about whether a comma makes a difference, as in "John James Jingleheimer-Schmidt, Baron" versus "Baron John James Jingleheimer-Schmidt". So, we'll have to settle that. I'm not sure there are lot of other complications; "Kennedy was the 35th president of the United States" but "when President Kennedy was". And "according to Queen Elizabeth II" and "when the queen wrote". One of our confusing practices is writing "king" or "duke" when refering to such a position in the abstract but "King" or "Duke" when used as a stand-in for a specific person's name. While the practice is certainly attested elsehwere, it's arguably not helpful to the reader in any way, and just leads to needlessly distracted readers wondering why the case keeps changing.One bit of advice: When proposing such changes, it is good to do to a
{{tqb}}of what the current guideline wording is, and another showing what the proposed wording would be, so people don't have to try to compare text in two different browser windows and whatnot. — SMcCandlish ☏ ¢ 😼 20:33, 5 November 2023 (UTC)- Demanding consistency via one size fits all simple rules is superficially attractive but cannot work. And using only super-famous job titles like PrEsIdEnT oF tHe Us or qUeEn Of EnGlAnD (random capitalization chosen to avoid bias in favor of any specific capitalization) as your starting examples is a really bad way of matching how job titles are used more widely. Job titles like "Florida Photonics Center of Excellence (FPCE) Endowed Professor" must be capitalized, for instance; no source uses any other capitalization. —David Eppstein (talk) 21:04, 5 November 2023 (UTC)
- Yeah, there are always wrinkles like named endowment chairs. Though "no source uses any other capitalization" by itself is not always a good argument. No independent source, among many independent sources using any other capitalization would matter, but what would not matter would be whether non-independent sources like to capitalize something, or when there are nearly no independent sources to examine, or hardly any sources at all to examine. — SMcCandlish ☏ ¢ 😼 14:07, 6 November 2023 (UTC)
- Um. Basic logic. If "no source uses any other capitalization" then it is also automatically true that "no independent source uses any other capitalization". Also, why the fetish for independence in this context? Sources can be reliable for matters like "what is the job title of this organization's employee" without being independent. —David Eppstein (talk) 07:30, 7 November 2023 (UTC)
- Because internal sources have an overwhelming tendency to capitalize everything to do with the company (or school, or whatever it is). From job titles down to "Staff Break Room". They are not reliable sources for English-language norms, even if they are valid primary sources for someone's job title being "assitant custodian" versus "assitant janitor". — SMcCandlish ☏ ¢ 😼 17:58, 7 November 2023 (UTC)
- Um. Basic logic. If "no source uses any other capitalization" then it is also automatically true that "no independent source uses any other capitalization". Also, why the fetish for independence in this context? Sources can be reliable for matters like "what is the job title of this organization's employee" without being independent. —David Eppstein (talk) 07:30, 7 November 2023 (UTC)
- Yeah, there are always wrinkles like named endowment chairs. Though "no source uses any other capitalization" by itself is not always a good argument. No independent source, among many independent sources using any other capitalization would matter, but what would not matter would be whether non-independent sources like to capitalize something, or when there are nearly no independent sources to examine, or hardly any sources at all to examine. — SMcCandlish ☏ ¢ 😼 14:07, 6 November 2023 (UTC)
- Demanding consistency via one size fits all simple rules is superficially attractive but cannot work. And using only super-famous job titles like PrEsIdEnT oF tHe Us or qUeEn Of EnGlAnD (random capitalization chosen to avoid bias in favor of any specific capitalization) as your starting examples is a really bad way of matching how job titles are used more widely. Job titles like "Florida Photonics Center of Excellence (FPCE) Endowed Professor" must be capitalized, for instance; no source uses any other capitalization. —David Eppstein (talk) 21:04, 5 November 2023 (UTC)
- FWIW - I try my best to abide by WP:JOBTITLES, even though I disagree with its lower-casing preferences. IMHO, we should've stayed with capitalising. But, I doubt the community will choose to return to those days. GoodDay (talk) 16:36, 6 November 2023 (UTC)
- JOBTITLES will continue to be a time sink no matter what we say… because someone will always disagree with it, no matter what we say. The capitalization rules vary depending on a) the style guide you prefer, b) when you went to school (I grew up at a time when it was standard to capitalize almost most job titles, but today that is considered over-capitalization). Personally, I just want it to be consistent within an article. I’m not overly concerned if one article capitalizes where another does not. Blueboar (talk) 17:21, 6 November 2023 (UTC)
- I understand what you mean. Unfortunately, correctly applying JOBTITLES leads to internal inconsistency. See my examples above. The correct application of JOBTITLES leads to capitalization that must seem entirely random to a casual reader. Surtsicna (talk) 18:10, 6 November 2023 (UTC)
- And a side concern is that various editors do care about consistency across articles on such matters, both for reducing recurrent editorial strife about them, and for presenting content that doesn't stylistically veer all over the place from page to page, for the reader. But anyway, having a simpler MOS:JOBTITLES, even if like most style rules it's ultimately pretty arbitrary, is surely preferable to the current complex mess. It is correct that someone will disagree with it no matter what it says (this is true of pretty much every style rule anyone has ever written, here or elsewhere), but we can at least in theory reduce the number of things to object to, while also just making it simpler. PS: I share Blueboar's generational experience, but am nevertheless in favor of downcasing. Just because I was taught to do something in 7th grade doesn't mean it was a good idea at the time much less that it remains one in 2023. Lots and lots of what was taught to us in elementary and secondary schools was nonsense, and we need to not hold onto it as if it's somewhow precious. This stuff is not religious doctrine or a core element of cultural identity. — SMcCandlish ☏ ¢ 😼 19:17, 6 November 2023 (UTC)
- if you want a simpler MOS, how about: never use capitals for any purpose ever. there. done. simplicity is not always best. there is a reason we went from having a single case in classical latin to using mixed cases in modern languages, and that reason is that capitals convey a certain amount of extra information, lost from intonation in spoken speech. information like: this is the official title used for a certain job and not merely the colloquial meaning that the same words would have if they were lower case. "Head Doctor" means the chief physician (or would, if anyone actually used that as a job title). "head doctor" could be a low-level psychiatrist. —David Eppstein (talk) 07:36, 7 November 2023 (UTC)
- Which of the two capitalization styles shown in the sample paragraphs in my opening comment do you prefer? Surtsicna (talk) 15:45, 7 November 2023 (UTC)
- Neither. They are both far too repetitively worded. The capitalization is a secondary issue that calls attention to the problem but is not the real problem. —David Eppstein (talk) 16:32, 7 November 2023 (UTC)
- The capitalization is the issue we are discussing here. You can find these styles of capitalization in a four-paragraph section but having four-paragraph samples here would not help illustrate the issue or the proposal. I am quite sure that this is clear to you, so I am left with the impression that you do not wish to address the issue. That is fine as well. Surtsicna (talk) 16:45, 7 November 2023 (UTC)
- To put it more bluntly, your examples at the lead of this thread are bad examples. One can get the same haphazard-capitalization effect in any sentence crafted to use a proper noun and the corresponding improper nouns in close alternation. For instance, "Lotus cars are cars made by Lotus Cars. Lotus Cars is named for the lotus flower, and Lotus cars are named for their manufacturer, Lotus Cars." Getting that effect does not mean we need to change our capitalization rules for corporations and the brand names they manufacture; it means we need to not put prose like that into our articles. —David Eppstein (talk) 16:51, 7 November 2023 (UTC)
- In none of those instances is the word "president" a proper noun; and the problem highlighted here is the difficulty of interpreting JOBTITLES's random (and elsewhere unattested) capitalization instructions even for short text such as the Main Page blurbs. Surtsicna (talk) 17:00, 7 November 2023 (UTC)
- To put it more bluntly, your examples at the lead of this thread are bad examples. One can get the same haphazard-capitalization effect in any sentence crafted to use a proper noun and the corresponding improper nouns in close alternation. For instance, "Lotus cars are cars made by Lotus Cars. Lotus Cars is named for the lotus flower, and Lotus cars are named for their manufacturer, Lotus Cars." Getting that effect does not mean we need to change our capitalization rules for corporations and the brand names they manufacture; it means we need to not put prose like that into our articles. —David Eppstein (talk) 16:51, 7 November 2023 (UTC)
- The capitalization is the issue we are discussing here. You can find these styles of capitalization in a four-paragraph section but having four-paragraph samples here would not help illustrate the issue or the proposal. I am quite sure that this is clear to you, so I am left with the impression that you do not wish to address the issue. That is fine as well. Surtsicna (talk) 16:45, 7 November 2023 (UTC)
- Neither. They are both far too repetitively worded. The capitalization is a secondary issue that calls attention to the problem but is not the real problem. —David Eppstein (talk) 16:32, 7 November 2023 (UTC)
- Unhelpful snarky silliness like "how about: never use capitals for any purpose ever. there. done." just short-circuits meaningful discussion. — SMcCandlish ☏ ¢ 😼 18:59, 12 November 2023 (UTC)
- Which of the two capitalization styles shown in the sample paragraphs in my opening comment do you prefer? Surtsicna (talk) 15:45, 7 November 2023 (UTC)
- if you want a simpler MOS, how about: never use capitals for any purpose ever. there. done. simplicity is not always best. there is a reason we went from having a single case in classical latin to using mixed cases in modern languages, and that reason is that capitals convey a certain amount of extra information, lost from intonation in spoken speech. information like: this is the official title used for a certain job and not merely the colloquial meaning that the same words would have if they were lower case. "Head Doctor" means the chief physician (or would, if anyone actually used that as a job title). "head doctor" could be a low-level psychiatrist. —David Eppstein (talk) 07:36, 7 November 2023 (UTC)
- And a side concern is that various editors do care about consistency across articles on such matters, both for reducing recurrent editorial strife about them, and for presenting content that doesn't stylistically veer all over the place from page to page, for the reader. But anyway, having a simpler MOS:JOBTITLES, even if like most style rules it's ultimately pretty arbitrary, is surely preferable to the current complex mess. It is correct that someone will disagree with it no matter what it says (this is true of pretty much every style rule anyone has ever written, here or elsewhere), but we can at least in theory reduce the number of things to object to, while also just making it simpler. PS: I share Blueboar's generational experience, but am nevertheless in favor of downcasing. Just because I was taught to do something in 7th grade doesn't mean it was a good idea at the time much less that it remains one in 2023. Lots and lots of what was taught to us in elementary and secondary schools was nonsense, and we need to not hold onto it as if it's somewhow precious. This stuff is not religious doctrine or a core element of cultural identity. — SMcCandlish ☏ ¢ 😼 19:17, 6 November 2023 (UTC)
- I understand what you mean. Unfortunately, correctly applying JOBTITLES leads to internal inconsistency. See my examples above. The correct application of JOBTITLES leads to capitalization that must seem entirely random to a casual reader. Surtsicna (talk) 18:10, 6 November 2023 (UTC)
- This is what consistent rules that are consistent with the linked articles would look like:
I agree with the suggestions for simplifying the existing rules, which would be in line with a few style guides. But a lot of capitalization will still look weird and inconsistent since in the end we're at the mercy of the articles. SamuelRiv (talk) 12:15, 4 December 2023 (UTC)JFK was the president of the United States. He was elected to the office of the President of the United States. (Note that President JF Kennedy should not be confused with President of Ireland JF Kennedy or the president of Kennedy, Ireland, which maybe exist at some point.) On his best days as president, President (of the US) Kennedy wore silly hats with his crayon-drawn personal presidential seal on them {not the official seal of the president of the United States or the Great Seal of the United States -- but the one emblazoned on his pajamas nonetheless}. The first lady that JFK married became his first lady for his presidency, First Lady Jacqueline Kennedy, who would be seen to embody the Office of the First Lady and the public role the first lady of the United States should take.
- We're not at the mercy of our own articles. No one is expected to read and memorize MoS or any other guideline here before editing. Our guidelines and even several of our policies exist primarily as reference works for later cleanup (and for settling disputes). Articles that don't comply with guidelines should be gradually edited to comply with them. WP:CONTENTAGE is not a factor; a article that has for a long time been non-compliant is not magically immune to conformance cleanup. And a non-trivial frequency of non-comformance isn't a factor either. A very large number of editors over-capitalize all sorts of things because of a feeling they are "important" (MOS:SIGCAPS behavior, and often MOS:DOCTCAPS and MOS:SPORTCAPS in particular). It's easily the no. 1 style error I fix in articles, and I'm sure others have the same experience. But this is not a rationale to delete MOS:CAPS or alter it to permit a whole bunch more capitalization of things that are not proper names. — SMcCandlish ☏ ¢ 😼 02:45, 5 December 2023 (UTC)
- I wish we had stuck with using 'uppercase', fwiw. But, enough editors wanted to go 'lowercase', so that's the result. GoodDay (talk) 16:42, 4 December 2023 (UTC)
- It's not just about something like random editorial whim; we have a general principle at MOS:CAPS: "only words and phrases that are consistently capitalized in a substantial majority of independent, reliable sources are capitalized in Wikipedia", and the rest of the style guidelines that involve letter case have to descend from that, or we end up with a WP:POLICYFORK. The real-world fact is that capitalization of these things varies widely by publisher, and use of the capitalization is decreasing in more and more publications over time, especially when the title is not directly attached to a name. So, this necesssarily means our default is to lower-case them except when attached to a name, a circumstance in which the dominant practice in English usage remains to capitalize them. — SMcCandlish ☏ ¢ 😼 02:45, 5 December 2023 (UTC)
JOBTITLES simplification proposal
Following on the suggestion above to workshop specific reivsion ideas, and drawing on Surtsicna's sound idea to "just adopt the style that is almost universally used in academic and journalistic writing", I will propose [this is workshopping, not an RfC!] that the way to fix MOS:JOBTITLES to be easy to remember, and more importantly to produce less reader-confusing results, is to simplify it down to something like:
... They are capitalized only in the following cases:
- When they are directly attached to a person's name (with no modifiers, including an ordinal number or a definite or indefinite article, and no intervening interpolations, including punctuation), and are not descriptive re-wordings.
- Even then, do not capitalize them if they are commercial jobs (chief operating officer) or are non-unique, non-administrative governmental roles (sherrif's deputy, building inspector, but Chief of Police, Minister of Finance).
- When a title is used to refer to a specific person as a substitute for their name during their time in office ... [keep existing examples].
Then eliminate the third extant bullet point and the table that follows it, this material being almost the entire source of confusion and strife. (Honestly, I think the second item, about use of a title as a name substitute, could also go, but some people are probably in favour of retaining it.)
Also remove the now-redundant "Even when used with a name, capitalization is not required for commercial and informal titles ...." sentence below the list. Alternatively, keep this line but remove the simpler but stricter indented sub-bullet from the proposal above.
If we used this replacement material in the sectional introduction, we could possibly also pare down the material that follows into more concise sets of examples of what to do and not do, and spend less verbiage on covering various types of titles. But the main point is eliminating the material causing confusion and impractical complexity.
The current wording, for comparison | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Offices, titles, and positions such as president, king, emperor, grand duke, lord mayor, pope, bishop, abbot, prime minister, leader of the opposition, chief financial officer, and executive director are common nouns and therefore should be in lower case when used generically: Mitterrand was the French president or There were many presidents at the meeting. They are capitalized only in the following cases:
Even when used with a name, capitalization is not required for commercial and informal titles: OtagoSoft vice-president Chris Henare; team co-captain Chan. The formality (officialness), specificity, or unusualness of a title is not a reason to capitalize it. Note that for "president of the United States" or "prime minister of the United Kingdom", the name of the country remains capitalized even when the title is not, as it is always a proper noun. When writing "minister of foreign affairs" or "minister of national defence", the portfolio should be lower cased as it is not a proper noun on its own (i.e. write minister of foreign affairs or, as a proper noun, Minister of Foreign Affairs; do not write minister of Foreign Affairs). [Subsections follow on various title/role types.] |
To be clear, this proposal would completely eliminate the weird "half-way" provision that is confusing people, the notion of capitalizing:
- "When a formal title for a specific entity (or conventional translation thereof) is addressed as a title or position in and of itself, is not plural, is not preceded by a modifier (including a definite or indefinite article), and is not a reworded description".
This is something many people have had difficulty parsing, and there is no question that the results are confusingly inconsistent for readers. The long-contentious examples like:
- "Richard Nixon was President of the United States", "Theresa May became Prime Minister of the United Kingdom", and "Louis XVI became King of France and Navarre, later styled King of the French"
would all become lower-cased to match:
- "Richard Nixon was the 37th president of the United States", "Theresa May was the prime minister of the United Kingdom", and "Louis XVI was a king of France".
It would also eliminate the confusing conflict between:
- "Richard Nixon was the 37th president of the United States" style and (still common in our articles on people with peerage titles) "Richard Walter John Montagu Douglas Scott is the 10th Duke of Buccleuch" style.
All of this would also be consistent with our move to writing, e.g., "president of the United States" at the article on the title (President of the United States), moving "List of Lord Mayors of London" to List of lord mayors of London, etc., etc. (though there are a few straggler articles still at over-capitalized page titles).
This would mean writing "Micaela, countess of Paris," instead of the style "Micaela, Countess of Paris," that presently dominates in articles on people with nobility titles, due almost entirely to the preferences and activities of WikiProject Royalty and Nobility (and technically against the guideline even as it currently stands). If we didn't want that result, then "including punctuation" in the above wording could be replaced perhaps with "other than a comma conventionally placed between the name and the title". But I think it would actually be better to use lower-case here for increased consistency and less confusion potential. It will be weird to have text like "Foo Bar, 7th Baron of Elbonia, met with Baz Quux, the prime minister of Kerblachistan", which also has the WP:NPOV problem of treating people with noble titles as somehow better and more important than everyone else, even when their notability and relative social stature are actually lesser that those of the other, non-ennobled, party.
This proposal is obviously moving in the direction of less not more capitalization, because this site (like Chicago Manual of Style and others) is "down-casing" where possible, using lowercase as the default which should only be diverged from when necessary. In particular, the guiding principle here is the lead of MOS:CAPS: "only words and phrases that are consistently capitalized in a substantial majority of independent, reliable sources are capitalized in Wikipedia." All of our guideline sections that apply capitalization need to descend from this principle and not contradict it. Consequently, WP should not be capitalizing titles except when they are directly attached to names as if they've become part of the name, because that is the only situation in which usage across English-language writing consistently applies capital letters to them, and even that is becoming less common with corporate and low-end governmental role titles. (And the argument can maybe still be made to keep things like "the Queen" when Elizabeth II is the specific referent.)
PS: It used the wording "directly attached to a person's name" rather than "followed by a person's name" to account for cases of titles (mostly from other languages) that are post-nominal in position. It is not a reference to constructions like "Micaela, countess of Paris" which has a parenthetical title divided from the name by a comma.
— SMcCandlish ☏ ¢ 😼 04:35, 5 December 2023 (UTC)
- The form "US president Nixon" & "US president Richard Nixon" always was a toe banger for me. I'd of thought "US President Nixon" & "US President Richard Nixon" would've been the correct form. Nevertheless, I support your proposal. GoodDay (talk) 04:45, 5 December 2023 (UTC)
- One might suggest axing the "modifiers" clause, but that still wouldn't result in capitalization here since "US president" isn't the actual title but a "descriptive re-wording" (or in the original material, "reworded description"), like "French king". There seems to be a general understanding that conventional truncations like just "President" are treated as if the full title. There might be a "devil in the disamiguation details", though. A modifier might be added to the entire title+name phrase to distinguish two or more people of similar titles, e.g. "the first meeting of Scottish Queen Mary and English Queen Elizabeth I", but that would surely be better rewritten in other wording ("of Scots", "of England"). That "of" style would seem to work for president and PMs and premiers and such, too. Maybe address it in a footnote? — SMcCandlish ☏ ¢ 😼 14:21, 5 December 2023 (UTC)
- Perhaps you could explain how this proposal would affect academic job titles, as in sentences like (current capitalization):
She is Marjorie Roberts Professor of statistics and chair of the Department of Statistics at the University of Illinois Urbana-Champaign, and a professor in the National Center for Supercomputing Applications.
In this case the Marjorie Roberts Professorship does not appear to be attached to the department of statistics, hence the choice to use lowercase for the first "statistics"; the second "professor" is just an ordinary English-word job title hence lowercase. I'm hoping the answer is no intended change to this capitalization, but you can see that "Marjorie Roberts Professor" is a job title, is not grammatically attached to the person's name in the sentence (as the name does not even appear), and yet is capitalized. A literal reading of this proposal would seem to imply that in such sentences we should write "marjorie roberts professor" instead, a nonsensical outcome. —David Eppstein (talk) 07:27, 5 December 2023 (UTC)- Well, the proposed changes above wouldn't seem to affect this at all. There appears to be a consenus (not just here but in the real world) that named endowment chairs like "Marjorie Roberts Professor" (which, yes, does not include "of statistics") and "Alfred Fitler Moore Professor of Telecommunications" (there are several AFM professorships that do have "of [Something]" in them) are proper names. They're more like awards, while simply being a professor at, and a department chair at, the university are job titles. If this needs to be addressed somewhere, it should probably be in "#Academic or professional titles and degrees" a bit lower down. Suprised it's not in there already. Maybe we'd probably need to note that WP would not refer to this person as "Marjorie Roberts Professor Bo Li", but maybe that would already be obvious enough since we wouldn't do "Professor Bo Li", either. (As for "the Department of [Subject] at [Institution]", that should only be capitalized, per MOS:FIELD, when it's the actual department name, and sometimes it's not in various cases I've seen, but just a descriptive phrase for something the real name of which might be "College of [Subject]" or "[Memorialized Person] [Subject] School", or "Department of [Subject1] and [Subject2]" or whatever.) — SMcCandlish ☏ ¢ 😼 15:01, 5 December 2023 (UTC)
- Two comments:
- There's still going to be confusion about which "high-end" roles are entitled to retain capitalisation when attached to a name. The idea that a chief of police is
somehow better and more important than
a chief executive officer seems contrary to the NPOV position you are advocating. - Suggesting lower case for substantive titles (which are traditionally comma-separated after the person's name) is likely to be a blocking point.
- There's still going to be confusion about which "high-end" roles are entitled to retain capitalisation when attached to a name. The idea that a chief of police is
- Rosbif73 (talk) 07:40, 5 December 2023 (UTC)
- I knew there would be wrinkles, which is why to workshop this instead of just launch a !voting RfC. In the same order:
- I'm just trying to reflect where sources are leaning and where consensus is likely to lean. Governmental job titles of an administrative nature are generally capitalized in sources, commercial ones (even "chief executive officer" and "executive director") increasingly are not, and more generic job titles like "night-shift manager" and "animal control officer" increasingly are not regardless of sector. But it does result in a conflict and potential NPoV issue, I guess.
- Maybe we'd need to suggest capitalizing or lowercasing them consistently in the same construction?
- Maybe the change from "capitalization is not required for commercial and informal titles" to "do not capitalize them if they are commercial jobs" was too much?
- And I suppose re-integrating the bit about "informal titles" like being an amateur sport team co-captain is worth retaining; I missed that.
- I suspected that it could be, especially with regard to British subjects with nobility titles. But it's worth talking about, and at least seeing what rationales pro and con might emerge. If there would be no budging toward writing "Infanta Elena, duchess of Lugo", then:
- Maybe substantive titles is clear enough. But given the complicated definition of "to be distinguished from a title shared among cadets, borne as a courtesy title by a peer's relatives, or acquired through marriage", having a specific rule about STs in particular might be too much complication, of just the sort we're trying to avoid here.
- We might could go with something like "post-nominal titles conventionally separated from the name by a comma" and just live with the fact that a form of interpolation has slipped in (but is distinguished clearly from using a comma to separate different clauses, as in "Barack Obama, president through January 20, 2017".) Not sure if this would result in capitalization of some other kind of post-nominal, comma-separated title we'd rather was not capitalized.
- I'm just trying to reflect where sources are leaning and where consensus is likely to lean. Governmental job titles of an administrative nature are generally capitalized in sources, commercial ones (even "chief executive officer" and "executive director") increasingly are not, and more generic job titles like "night-shift manager" and "animal control officer" increasingly are not regardless of sector. But it does result in a conflict and potential NPoV issue, I guess.
- — SMcCandlish ☏ ¢ 😼 15:01, 5 December 2023 (UTC)
- I knew there would be wrinkles, which is why to workshop this instead of just launch a !voting RfC. In the same order:
- Firstly, I appreciate the work you've put into this proposal. The topic is a longstanding sticking point, and you've given it the attention it requires.
- I do have a query – does the first bullet effectively prohibit capitalising titles after a person's name, and would it therefore be clearer to state that explicitly? I'm struggling to think of an example of a title attached after a person's name which isn't modified. A.D.Hope (talk) 22:11, 5 December 2023 (UTC)
- Well, see a bit above for some discussion of "substantive titles" of nobility and possibly some other classes that are comma-separated. — SMcCandlish ☏ ¢ 😼 06:26, 6 December 2023 (UTC)
- Maybe I've missed something, but could all three bullet points not be condensed to something like:
- They are capitalised only when used as a proper noun, i.e. when they directly precede a person's name without intervening punctuation.
- That would lead to Pope Francis, President Biden, and Admiral Nelson, but 'Francis, the pope', 'Joe Biden, president of the United States', and 'Felipe, the king of Spain'. This could also solve the issue of which titles deserve to be capitalised, since the titles which can be placed before a name are also the ones which tend to be capitalised anyway. A.D.Hope (talk) 09:33, 6 December 2023 (UTC)
- See above about post-nominal substantive titles; while some of us might like to see them lowercased ("Felipe, king of Spain") it is unlikely that anyone from WP:ROYALTY will go along with it. And if we've learned one thing through years of MoS and RM agony, it is that Wikipedians will ever, ever agree on what "proper name" means (in part because there are conflicting linguistic and philosophical definitions, and in part because of a very common misunderstanding that anything capitalized [in whatever someone is used to reading] is a proper name and that all proper names are capitalized. It would also confuse the title with the name (which is definitely a proper name) that the title is attached to, and probably further the nonsense argument that a title juxtaposed with a name "becomes" a new unitary proper name unto itself. — SMcCandlish ☏ ¢ 😼 10:48, 6 December 2023 (UTC)
- Sorry if I'm stating the obvious, but the policy as re-written by you mandates 'Felipe, king of Spain' as there is an 'intervening interpolation, including punctuation' between the name and title. A.D.Hope (talk) 10:58, 6 December 2023 (UTC)
- Yes, and someone pointed out an objection, and I've acknowledged the objection and suggested two potential revisions paths in response to it. I'm getting the impression you didn't actually read the thread but are just responding to points in isolation. :-) — SMcCandlish ☏ ¢ 😼 04:13, 7 December 2023 (UTC)
- My suggestion is not related to the objections raised above; my original comment is a direct response to your proposal rather than a continuation of the earlier conversation. A.D.Hope (talk) 10:16, 7 December 2023 (UTC)
- Okay. It's noted in conjunction with the similar comment above; next draft will try to address this with something like "or a post-nominal title conventionally separated from the name by a comma", since the odds of a consensus against capitalizing substantive titles is very low. — SMcCandlish ☏ ¢ 😼 23:39, 7 December 2023 (UTC)
- Would that be added to the first or second bullet point? A.D.Hope (talk) 23:46, 7 December 2023 (UTC)
- Likely the first; the bit about "no intervening interpolations, including punctuation" would seem to have been an over-simplification. — SMcCandlish ☏ ¢ 😼 00:12, 8 December 2023 (UTC)
- Would that be added to the first or second bullet point? A.D.Hope (talk) 23:46, 7 December 2023 (UTC)
- Okay. It's noted in conjunction with the similar comment above; next draft will try to address this with something like "or a post-nominal title conventionally separated from the name by a comma", since the odds of a consensus against capitalizing substantive titles is very low. — SMcCandlish ☏ ¢ 😼 23:39, 7 December 2023 (UTC)
- My suggestion is not related to the objections raised above; my original comment is a direct response to your proposal rather than a continuation of the earlier conversation. A.D.Hope (talk) 10:16, 7 December 2023 (UTC)
- Yes, and someone pointed out an objection, and I've acknowledged the objection and suggested two potential revisions paths in response to it. I'm getting the impression you didn't actually read the thread but are just responding to points in isolation. :-) — SMcCandlish ☏ ¢ 😼 04:13, 7 December 2023 (UTC)
- Sorry if I'm stating the obvious, but the policy as re-written by you mandates 'Felipe, king of Spain' as there is an 'intervening interpolation, including punctuation' between the name and title. A.D.Hope (talk) 10:58, 6 December 2023 (UTC)
- See above about post-nominal substantive titles; while some of us might like to see them lowercased ("Felipe, king of Spain") it is unlikely that anyone from WP:ROYALTY will go along with it. And if we've learned one thing through years of MoS and RM agony, it is that Wikipedians will ever, ever agree on what "proper name" means (in part because there are conflicting linguistic and philosophical definitions, and in part because of a very common misunderstanding that anything capitalized [in whatever someone is used to reading] is a proper name and that all proper names are capitalized. It would also confuse the title with the name (which is definitely a proper name) that the title is attached to, and probably further the nonsense argument that a title juxtaposed with a name "becomes" a new unitary proper name unto itself. — SMcCandlish ☏ ¢ 😼 10:48, 6 December 2023 (UTC)
- Maybe I've missed something, but could all three bullet points not be condensed to something like:
- Well, see a bit above for some discussion of "substantive titles" of nobility and possibly some other classes that are comma-separated. — SMcCandlish ☏ ¢ 😼 06:26, 6 December 2023 (UTC)
Sincere thanks, SMcCandlish, for taking this up. I strongly believe that we should propose removing the second point as well. Surely we have had enough of this neither-here-nor-there attempt at a style. We should take the opportunity to go all the way towards matching this guideline with well-established modern practices. "The Queen" vs "the queen". "The President" vs "the president". "The Professor" vs "the professor". "The Bishop" vs "the bishop". Wikipedia is the only publication that I know of that makes an exception for titles "used to refer to a specific person as a substitute for their name during their time in office". This produces text that looks internally inconsistent. We have "the queen" in one sentence and "the Queen" in the next for reasons that are unclear even to most editors, let alone readers. I also find it jarring to have to use "the King" when writing about a historical figure when all the books I am citing use "the king". I do not think we have a valid reason to retain this. Surtsicna (talk) 20:36, 5 December 2023 (UTC)
- The style is actually pretty common (perhaps more common in British writing, and less common than it used to be), but I'm not aware of a style guide that specifically enumerates it. Then again, I have not gone looking for it yet, and while I don't have a huge style guide collection any longer, I do keep some major ones around (and there are various of them online now), so it might be worth looking into to see what they say. Personally, I would like to do away with the 2nd bullet and stop capitalizing such things, but here I'm trying to massage into shape something that will actually pass consensus muster, and that probably is ultimately going to boil down to removing the material everyone hates and leaving the rest of it alone (at least in a first pass) even if some particular subset of editors hate it. :-) — SMcCandlish ☏ ¢ 😼 06:26, 6 December 2023 (UTC)
- It is fairly common in British English to capitalise certain offices when they're effectively proper nouns. Fowler goes into it:
Titles of office-holders. In certain cases and certain contexts these are virtually proper names of persons: HM the Queen, the Prime Minister, the Archbishop of Canterbury. The extension of this principle depends on the context: the President (of the USA, of Magdalen College, Oxford, etc.). Similarly, the Bishop of Hereford, the Dean of Christ Church; and in a particular diocese, the Bishop, or within a particular cathedral or college, the Dean (referring to a particular individual, or at least a holder of a particular office: the Bishop is ex officio chairman of many committees). But in contexts like when he became bishop, the bishops of the Church of England, appointment of bishops—such instances are better printed in lower case, and the same applies to other office-holders.
- The rule is essentially to capitalise when the title unambigiously refers to a single person or office. It's worth noting that Fowler also says:
Apart from certain elementary rules that everyone knows and observes, such as that capitals are used to begin a new sentence after a full stop, for the initial letter of quoted matter (but see punctuation), and for proper names like John Smith (with rare exceptions like the idiosyncratic e. e. cummings) and those of the days and months, their present-day use shows wide variation from one publishing house to another, and even within the pages of the same book, newspaper, etc.
- This is borne out in practice, with the BBC and gov.uk capitalising:
- ...and the Guardian and some academic books not:
- A.D.Hope (talk) 09:03, 6 December 2023 (UTC)
- A.D.Hope, I do not think that this capitalization is more common in British English than in US English. Rather it appears that in both the US and the UK, as well as in other English-speaking countries, government websites and government-affiliated media capitalize titles, obviously out of deference, while academic publications have not done so for over half a century. But interestingly enough, the BBC only capitalizes titles of Brits; US presidents, foreign kings, and foreign clergy apparently have to contend themselves with lower case. Obviously Wikipedia should neither be seen as deferring nor as preferring. Surtsicna (talk) 15:44, 6 December 2023 (UTC)
- Yes, all of that, exactly. — SMcCandlish ☏ ¢ 😼 04:39, 7 December 2023 (UTC)
- Personally I'd be quite happy to use lowercase for all titles except when directly preceding a person's name (e.g. President Macron, Pope Francis, Sir Winston). It will simplify the rules considerably, and if Fowler is anything to go by even the style guides admit capitalisation is largely arbitrary, so we may as well set our own standard. A.D.Hope (talk) 18:10, 6 December 2023 (UTC)
- One thing with your third example is that it refers to the office itself, not the office title in substitution for someone's name. So for example there is a president of the United States, and there is an elected office known as the President of the United States. Also when I said in my previo0us post that we defer to articles (and their sources), I mean in particular that they guide such capitalizations, as in the case of the first lady, which despite having an official office, still does not have her office title capitalized in official publications (except as attached to her name, so e.g. "the first lady of the United States is First Lady Jill Biden.")
- I support breaking down the convoluted grammar rules, but there should be some good examples of how to give deference to sources as established in our main articles. SamuelRiv (talk) 15:57, 6 December 2023 (UTC)
- "there is a president of the United States, and there is an elected office known as the President of the United States" is one of the notions that has been the most contentious and which has caused the most confusion. It has proven difficult to write in a way that consistently follows this distinction, readers generally do not understand it (it just looks like random, inconsistent typographical chaos to most of them), many editors do not agree that the distinction exists (as a typographic matter), and off-site usage of English doesn't consistently support such a typographic distinction. That's why the thrust of this proposal, whatever other revising it may need, is deletion of the bullet point about this alleged distinction and the huge, confusing list of examples that follows it.I have no idea what "how to give deference to sources as established in our main articles" is supposed to mean. Our style manual is informed by external style guides and by demonstrable patterns of usage that are overwhelmingly consistent across English, but we are not in any way obligated to adopt a particular style just because particular newspapers or other publishers are fond of it, and most especially not when we have years of discord and confusion resulting from doing something along those lines. If what you wrote has something to do with whether some title/role is "official" in some way (or officially named a particular way, or officially style a particular way with capital letters in specific places in governmental or other non-independent source material), that's a primary-source matter, and we do not defer to assertions in primary sources about official names and mandatorily use that exact string that stylization of it (see MOS:TM, WP:OFFICIALNAME, MOS:DOCTCAPS, etc.). — SMcCandlish ☏ ¢ 😼 04:39, 7 December 2023 (UTC)
- This is why I gave the example of the seal of the president of the United States versus the Great Seal of the United States, the former of which I would not have guessed was not given some formal title. Whatever debate there was over capitalization has already happened in its article/talk space, and that should be respected elsewhere. And for something like a president or sheriff, referring to the office means referring to the office, not the job, so I don't see how any confusion an editor would have would be typographical and not semantic.
- For the MOS you might clarify that you get elected or appointed or hired for a job, not an office (or vice versa -- that would indeed be an MOS decision). Thus "Andrew Jackson was elected the 7th president of the United States. He increased the relative power of the office of the President of the United States. He also left the office of the president of the United States in the White House (the Oval Office) in a pigsty that the cleaning staff absolutely did not appreciate." SamuelRiv (talk) 14:43, 7 December 2023 (UTC)
- Original-research opinion that doesn't seem to be based on anything. Most sources I've familiar with (and I have a history as a professional activist in US politics) treat "the Office of the President of the United States" as a proper name (and not meaning "the room, the Oval Office, in which the president works", of course). — SMcCandlish ☏ ¢ 😼 23:33, 7 December 2023 (UTC)
- I'm not sure if you mean something synonymous with the Executive Office of the President of the United States. I was referring to the elected office as a government institution and unit of power, which may or may not (you would know the convention) have the word "office" in something like "the elected Constitutional office of the President of the United States" capitalized. (For these examples I've been specifically trying to not name a specific bureaucracy called the "Office of X", but rather an institution in the abstract.) (And again, the first lady example I gave is notable because it has a official bureaucracy called the Office of the First Lady, but per the convention of our article the institution of the first lady of the United States is not capitalized.) SamuelRiv (talk) 00:10, 8 December 2023 (UTC)
- Original-research opinion that doesn't seem to be based on anything. Most sources I've familiar with (and I have a history as a professional activist in US politics) treat "the Office of the President of the United States" as a proper name (and not meaning "the room, the Oval Office, in which the president works", of course). — SMcCandlish ☏ ¢ 😼 23:33, 7 December 2023 (UTC)
- "there is a president of the United States, and there is an elected office known as the President of the United States" is one of the notions that has been the most contentious and which has caused the most confusion. It has proven difficult to write in a way that consistently follows this distinction, readers generally do not understand it (it just looks like random, inconsistent typographical chaos to most of them), many editors do not agree that the distinction exists (as a typographic matter), and off-site usage of English doesn't consistently support such a typographic distinction. That's why the thrust of this proposal, whatever other revising it may need, is deletion of the bullet point about this alleged distinction and the huge, confusing list of examples that follows it.I have no idea what "how to give deference to sources as established in our main articles" is supposed to mean. Our style manual is informed by external style guides and by demonstrable patterns of usage that are overwhelmingly consistent across English, but we are not in any way obligated to adopt a particular style just because particular newspapers or other publishers are fond of it, and most especially not when we have years of discord and confusion resulting from doing something along those lines. If what you wrote has something to do with whether some title/role is "official" in some way (or officially named a particular way, or officially style a particular way with capital letters in specific places in governmental or other non-independent source material), that's a primary-source matter, and we do not defer to assertions in primary sources about official names and mandatorily use that exact string that stylization of it (see MOS:TM, WP:OFFICIALNAME, MOS:DOCTCAPS, etc.). — SMcCandlish ☏ ¢ 😼 04:39, 7 December 2023 (UTC)
- A.D.Hope, I do not think that this capitalization is more common in British English than in US English. Rather it appears that in both the US and the UK, as well as in other English-speaking countries, government websites and government-affiliated media capitalize titles, obviously out of deference, while academic publications have not done so for over half a century. But interestingly enough, the BBC only capitalizes titles of Brits; US presidents, foreign kings, and foreign clergy apparently have to contend themselves with lower case. Obviously Wikipedia should neither be seen as deferring nor as preferring. Surtsicna (talk) 15:44, 6 December 2023 (UTC)
- SMcCandlish, I understand the desire to change something rather than nothing. I would suggest asking the community whether they would support a) removing second point, b) removing third point, c) removing both second and third point. That way there is a good chance that either or both would be dealt with. Surtsicna (talk) 15:44, 6 December 2023 (UTC)
- Maybe, but my instinct and experience in MoS RfCs that would affect a large number of articles strongly tells me to approach this one major change at a time. We'll see, though. This is all still in a workshopping phase, the main point of which is to identify conflicts with other practice, loopholes, exceptions, inclarities, and other problems that need to be addressed before opening any RfC at all. Maybe there really is sufficient disapproval of writing "according to a letter from the Premier", with "Premier" standing in for a specific officeholder's name, to include it, but it would complicate the proposal, and increase the likelihood of anyone not patient enough to parse it all in detail to reflexively !vote "No change". Cf. recent failure of the ISBN formatting proposal at VPPOL to come to a clear consensus; that unhelpful "I'm confused, so change nothing!" reaction is exactly what happened. — SMcCandlish ☏ ¢ 😼 04:39, 7 December 2023 (UTC)
- If we are looking for a single incremental change, I would be much more inclined to support removing the second point (when a title is used to refer to a specific person as a substitute for their name...). "The king met with the pope..." isn't how I personally would style it, but looks quite natural to me. If I am understanding the current proposal correctly, it would mandate "Louis XVI became king of France and Navarre in 1774, later styled king of the French," which I find borders on confusing. Our current guideline already requires, "The Parliament of Ontario consists of the lieutenant governor of Ontario and the Legislative Assembly of Ontario," on the questionable conclusion that the definite article indicates "lieutenant governor of Ontario" is merely a description and not the proper name of an office. I think there is a lot of room to improve the third point, but oppose getting rid of it.--Trystan (talk) 20:09, 7 December 2023 (UTC)
- Then how would you improve it, in a way or in ways that counter the growing concern that it is not only confusing to try to understand and abide by, it produces confusing output for all the readers who've never read the rule and the big table of examples below it? The idea that this material is reparable at all seem fairly dubious. — SMcCandlish ☏ ¢ 😼 23:39, 7 December 2023 (UTC)
- Plot twist, SmcCandlish 😄 Surtsicna (talk) 06:44, 8 December 2023 (UTC)
- My suggestion would be to more closely adopt the approach used in the Chicago style. That would get rid of points 2 and 3. (Chicago does allow for “the King” in BrE, but I won’t argue for it here.) The major exception Chicago carves out is to capitalize noble titles when given in full. I think that would address a common point of contention here. I would also get rid of the justification wording about common nouns, as it is debatable and just encourages justifying a departure from the style. The rule is always going to be somewhat arbitrary and that is fine. That would leave us with:
Possible wording |
|---|
|
Offices, titles, and positions such as president, king, emperor, grand duke, lord mayor, pope, bishop, abbot, prime minister, leader of the opposition, chief financial officer, and executive director should be in lower case: François Mitterrand, president of France. They are capitalized in two cases:
|
- I think the nobility exception is justified both by common usage and the need for clarity. (William is undoubtedly the Prince of Wales, but I would argue Llywelyn ap Gruffudd was the last prince of Wales.)
- I don’t think it will be possible to get rid of all exceptions and complexity, but as a general rule I think the above would be much simpler to apply than what we have. It has some aspects I don't personally like (like the lower case LGs I mention above), but nothing that I can't live with.--Trystan (talk) 16:07, 8 December 2023 (UTC)
- It's funny you mention the Prince of Wales, because both the Oxford Dictionary of National Biography and the Encyclopaedia Britannica use '[Name], prince of Wales'. I think that just goes to show that, outside a few universal examples such as days of the week, capitalisation is largely arbitrary. A.D.Hope (talk) 17:26, 8 December 2023 (UTC)
- What are "LGs"? Llywelyn ap Gruffudds? I'm going to repeat that language like "when the title can be considered to have become part of the name" has previously caused great confusion and strife, and we need to stay far, far away from it. Something like "A title is capitalized when immediately followed by a person's name, without any interpolations" is sufficient and precise. — SMcCandlish ☏ ¢ 😼 04:29, 9 December 2023 (UTC)
- I would be fine with that. "Without any intervening words or punctuation" might be a little more accessible language. LGs are lieutenant governors.--Trystan (talk) 16:43, 9 December 2023 (UTC)
- Oh, right. And "without any intervening words or punctuation" sounds good. Reads well, whatever. — SMcCandlish ☏ ¢ 😼 01:19, 11 December 2023 (UTC)
- I would be fine with that. "Without any intervening words or punctuation" might be a little more accessible language. LGs are lieutenant governors.--Trystan (talk) 16:43, 9 December 2023 (UTC)
- I am uneasy about the "noble titles are capitalized when not abbreviated". It complicates matters, which is the opposite of what we are trying to achieve. What should be lower case per the present JOBTITLES becomes upper case according to that proposal ("He became a prince of Wales", "He was the last prince of Wales" → "He became a Prince of Wales", "He was the last Prince of Wales") while simultaneously what should be upper case per current reading becomes lower case ("the Prince" → "the prince"). Moreover, it will lead to discussions about what is an abbreviated title. Is "king of the United Kingdom" an abbreviation of "by the Grace of God, of the United Kingdom of Great Britain and Northern Ireland and of His other Realms and Territories King, Head of the Commonwealth, Defender of the Faith"? It also does not lead to a style more in line with modern academic practice. I believe that point #1 should be a sufficient exception to the general "use lower case" rule. Surtsicna (talk) 09:30, 11 December 2023 (UTC)
- I do appreciate simplifying the guidance on capitalizations… however, I am getting a little worried that we are oversimplifying. Blueboar (talk) 17:56, 11 December 2023 (UTC)
- Well, this is just a Gedankenexperiment stage, the purpose of which is to figure out what might break and how before launching something for anyone to !vote on. It's still all rough draft. — SMcCandlish ☏ ¢ 😼 00:08, 13 December 2023 (UTC)
MOS:GIVENNAME needs an entry for Meitei names (Manipur)
MOS:GIVENNAME clearly overrides Wikipedia:Manual of Style/Biography#People with the same surname (currently MOS:SAMESURNAME), but we don't have an entry to recommend usage for the Meitei people, typically from Manipur. See Talk:Licypriya Kangujam#First name/second name where it's unclear what to choose. Any advice, preferably based on good sources, would be welcome. Boud (talk) 19:43, 12 December 2023 (UTC)
- Something I said over there that is actually more relevant here: MOS:SAMESURNAME probably needs some clarification, like a footnote that says something like
For non-Western cultures that have different namving conventions, substitute for "surname", in "use just the surname", whatever portion of the name would be conventionally used in that culture for references to a person in a semi-formal register. [examples here]
"Culture-specific usages" = MOS:GIVENNAME a.k.a. MOS:PATRONYMIC. And obviously that section needs expansion to cover more cultures (possibly even a split-out to a sub-page after significant development; back in 2018, I loosely proposed centralizing this sort of thing at what is now WP:Categorization/Sorting names, or having some kind of shared transclusion or something between that page and an MoS page – see Wikipedia talk:Categorizing articles about people/Archive 10#A point needs clarification into guidance instead of non-guiding observation (and tacit approval) of conflict) – but in several years there has been no progress yet in this direction. It would take significant RS research. — SMcCandlish ☏ ¢ 😼 00:35, 13 December 2023 (UTC)- Sure, I sort of realised that without saying it so neatly. Here's the same thing with a few minor corrections and adding one example.
For non-Western cultures that have different naming conventions, instead of "surname" in the recommendation "use just the surname", use whatever portion of the name would be conventionally used in that culture for references to a person in a semi-formal register. [For example, Abiy became prime minister in 2018, per the Eritrean/Ethiopian convention; other examples here]
Boud (talk) 19:36, 13 December 2023 (UTC)- Seems good, though it would be nice to have an additional example. — SMcCandlish ☏ ¢ 😼 21:27, 17 December 2023 (UTC)
- Sure, I sort of realised that without saying it so neatly. Here's the same thing with a few minor corrections and adding one example.
Talking about a person’s “former” gender
There is a disagreement at Talk:Isla Bryson case § Reverted edit over the language we use to describe a person’s pre-transition gender:“while a man”or
“when she was a man”or similar, vs
“while presenting as a man”or similar. While this is both an ideological and a personal question, it seems that it might be helpful for the MOS to either proscribe or permit such wording.…Alternatively, if we don’t feel like wading into that quagmire, it might be nice to guide editors towards using language as is used by the subject themselves, or, where no evidence is found, to avoid either philosophical attitude, as seems to be the interim solution at that article (and the one I personally think works best). — HTGS (talk) 04:30, 15 December 2023 (UTC)
- Most trans people, but certainly not all trans people, will describe themselves as having always been their post-transition gender and just not realizing it earlier. Is it worth putting this in the MOS in general? I would say probably not, but my personal inclination is definitely to lean towards it until proven otherwise. Loki (talk) 04:54, 15 December 2023 (UTC)
- Also, like @LokiTheLiar said above, "but certainly not all trans people" oppose the idea of a "former" gender; some may embrace it. Therefore, I don't think it's correct to universalise here, but go by how sources generally refer; taking it with a pinch of salt, especially British media. Zilch-nada (talk) 05:21, 15 December 2023 (UTC)
- I understand that this is a very controversial topic and I shall try to be careful with my speech here. The sources used universally employ language such as "while still a man" to describe this:
- "Bryson, 31, was convicted last month of raping two women in the Glasgow area while still a man known as Adam Graham" - The Sunday Times https://archive.ph/20230212180036/https://www.thetimes.co.uk/article/isla-brysons-mother-says-rapist-should-never-have-been-held-in-womens-prison-w2wpxgqtl
- "A transgender woman has been found guilty of raping two women when she was a man." - The Guardian https://www.theguardian.com/uk-news/2023/jan/24/glasgow-court-convicts-trans-woman-of-raping-two-women-before-her-transition
- "Isla Bryson was convicted last month of raping two women – one in Clydebank in 2016 and one in Glasgow in 2019 – while still a man known as Adam Graham." - The Guardian https://www.theguardian.com/uk-news/2023/feb/28/trans-woman-isla-bryson-jailed-raping-two-women
- "Isla Bryson raped two women when she was a man" - Belfast Telegraph https://www.belfasttelegraph.co.uk/news/uk/estranged-wife-accuses-rapist-of-transgender-sham/1406606772.html
- Transgender woman found guilty of raping two women while a man - STV https://news.stv.tv/west-central/transgender-woman-isla-bryson-guilty-of-raping-two-women-in-clydebank-while-a-man
- "Isla Bryson was remanded to Cornton Vale women's prison in Stirling after being convicted of the rapes when she was a man called Adam Graham" - BBC News https://www.bbc.co.uk/news/uk-scotland-64413242
- "Transgender rapist Isla Bryson jailed for eight years for attacks on two women when she was a man" - Sky News https://news.sky.com/story/transgender-rapist-isla-bryson-jailed-for-eight-years-for-attacks-on-two-women-when-she-was-a-man-12821513
- "...who was convicted earlier this week of raping two women when she was a man" - The National https://www.thenational.scot/news/23278119.nicola-sturgeon-trans-rapist-isla-bryson-wont-jailed-womens-prison/
- The issue I don't think is necessarily with the language of "while still a man" but the logic behind it. The article makes no reference to this person previously being a man, only with limited references to "assigned male at birth". Now, I am fine with this usually as I understand that many trans folks prefer to be acknowledged as their post-transition gender, as mentioned by @LokiTheLiar above. However, the nature of this news, in which the police report described the crime in question as being committed by a male, and indeed the abundant sources cited above referring to "while still a man", leads me to believe that I think that the logic of "former gender" should be considered in some circumstances, particularly in such circumstances of abundant sourcing. That's my two cents. Zilch-nada (talk) 05:19, 15 December 2023 (UTC)
- Like Sideswipe said several times in the original argument that prompted this, the wording of sources doesn't dictate our wording. That's why we have the MOS. Loki (talk) 06:14, 15 December 2023 (UTC)
- Yes, but I'm not talking about the wording, but the actual logic employed in the sources; that is eschewed here. Zilch-nada (talk) 06:20, 15 December 2023 (UTC)
- What logic? The language is clearly different, but how is the logic different? Loki (talk) 15:06, 15 December 2023 (UTC)
- The idea of a "former" gender, which this talk is about. Zilch-nada (talk) 16:02, 15 December 2023 (UTC)
- What logic? The language is clearly different, but how is the logic different? Loki (talk) 15:06, 15 December 2023 (UTC)
- Yes, but I'm not talking about the wording, but the actual logic employed in the sources; that is eschewed here. Zilch-nada (talk) 06:20, 15 December 2023 (UTC)
- Like Sideswipe said several times in the original argument that prompted this, the wording of sources doesn't dictate our wording. That's why we have the MOS. Loki (talk) 06:14, 15 December 2023 (UTC)
- "language as is used by the subject themselves"
- This case is much more complicated as it is revealed that this particular person "decided to transition while awaiting trial for rape" and has been described by politicians such as Nicola Sturgeon (who is generally pro-trans) as "faking it". Basically, why does - in this particular case - the rapist - who clearly has very bad intentions - have a greater say over police, the media, mainstream political opinion, the courts, and the prisons? In other cases I can absolutely support the fact that someone has transitioned, but this is clearly more complex than that.
- The police say that the crime was committed by a man yet the article makes no reference to them as a man; reference to them as a man is even more scarce when we avoid "either philosophical attitude", which, as the article currently stands, has precisely one reference; that they were assigned male at birth. Zilch-nada (talk) 06:46, 15 December 2023 (UTC)
- Remember that (as with all of our guidelines) this MOS begins with a statement that common sense should be applied and that occasional exceptions can exist. We can’t (and don’t need to) account for every possibility where an exception might be made. We just need to reach a consensus as to WHY, in a specific article an exception is appropriate, and then make the exception. Blueboar (talk) 12:57, 15 December 2023 (UTC)
- It'd be easiest just to write "before his/her/their [gender] transition". Largoplazo (talk) 13:42, 15 December 2023 (UTC)
- Is "when she was a man" seriously scary to you people? What's wrong with it? It's abundantly sourced. Zilch-nada (talk) 16:04, 15 December 2023 (UTC)
- Because it's redundant, when we already say that the crimes she was convicted for happened prior to her transition. Sideswipe9th (talk) 18:16, 15 December 2023 (UTC)
- "prior to her transition": yes, when "she" was a man. Jesus Christ. Zilch-nada (talk) 00:08, 16 December 2023 (UTC)
- If I understand your meaning correctly... I don't think it's appropriate to put she in scare quotes like that; WP:BLPTALK applies even to people who have done terrible things. In context it also seems like it might be a bit uncivil towards trans editors. --Aquillion (talk) 05:08, 16 December 2023 (UTC)
- Weird accusation. The article uses "she"; that's fine. But I'm not respecting a rapist in talk - I have mostly used the term "they" -, nor am I even remotely suggesting to misgender the average trans person. Nonsense. Zilch-nada (talk) 05:21, 16 December 2023 (UTC)
- Unfortunately, while you can feel however you wish about them, we're required to maintain at least a bare modicum of decorum even when discussing people who have committed serious crimes. As I said, BLPTALK doesn't contain an exception that allows us to insinuate uncited accusations against living people just because they've done unrelated bad things. No matter how you feel about their actions, putting scare quotes around their gender on talk (which obviously goes beyond just misgendering them and makes a serious insinuation that you haven't backed up with any sort of source) is still completely unacceptable. --Aquillion (talk) 10:00, 24 December 2023 (UTC)
- Not all "transitions" deserve equal respect - a view clearly espoused by the police, the prisons, politicians like Sturgeon, etc. etc.; that's how I'll refer to this "person" in talk. Is me putting scare quotes around "person" insulting all "persons"? Give it a break. Zilch-nada (talk) 10:05, 24 December 2023 (UTC)
- Unfortunately, while you can feel however you wish about them, we're required to maintain at least a bare modicum of decorum even when discussing people who have committed serious crimes. As I said, BLPTALK doesn't contain an exception that allows us to insinuate uncited accusations against living people just because they've done unrelated bad things. No matter how you feel about their actions, putting scare quotes around their gender on talk (which obviously goes beyond just misgendering them and makes a serious insinuation that you haven't backed up with any sort of source) is still completely unacceptable. --Aquillion (talk) 10:00, 24 December 2023 (UTC)
- Weird accusation. The article uses "she"; that's fine. But I'm not respecting a rapist in talk - I have mostly used the term "they" -, nor am I even remotely suggesting to misgender the average trans person. Nonsense. Zilch-nada (talk) 05:21, 16 December 2023 (UTC)
- If I understand your meaning correctly... I don't think it's appropriate to put she in scare quotes like that; WP:BLPTALK applies even to people who have done terrible things. In context it also seems like it might be a bit uncivil towards trans editors. --Aquillion (talk) 05:08, 16 December 2023 (UTC)
- "prior to her transition": yes, when "she" was a man. Jesus Christ. Zilch-nada (talk) 00:08, 16 December 2023 (UTC)
- Because it's redundant, when we already say that the crimes she was convicted for happened prior to her transition. Sideswipe9th (talk) 18:16, 15 December 2023 (UTC)
It'd be easiest just to write "before his/her/their [gender] transition"
Yup. And that is what the article says, specificallyprior to Bryson's gender transition
. Sideswipe9th (talk) 18:16, 15 December 2023 (UTC)- Yes, my thinking is that that's just obviously neutral wording - no one doubts that Bryson transitioned. Describing it as a "former" gender is taking a clear position on the "underlying logic", as Zilch-nada, the main proponent of using that language, seems to concede above; whereas I don't see how the alternative wording contains any ideological implications. I don't think the simple existence of sources that use that wording is sufficient (especially since the sources also use phrasing like "before transitioning", including in some of the ones linked above.) That said I'm not sure the MoS needs to be too prescriptive, especially since - how often has this come up? It seems to be one dispute, on one page, which is a WP:ONEAGAINSTMANY situation, where the outcome it's obviously headed for seems to be the one a hypothetical MOS change would encourage anyway - that is to say, it seems like our existing policies and guidelines are handling it fine. Since the core issue is WP:IMPARTIAL, I suppose something about "former gender" or constructions of that nature could be added to WP:WTW somewhere, as a heads-up to people who might not understand the relevant implications, but that page is already glutted beyond the point of usefulness, and I think everyone in this discussion understands the implications already anyway. --Aquillion (talk) 05:08, 16 December 2023 (UTC)
- I agree very much with your last few sentences about WP:WTW, as the logic of "former gender" should not be prohibited outright, only generally discouraged, and used when abundantly sourced. In this case it is abundantly sourced, and so that's why I'm arguing for its usage. Zilch-nada (talk) 05:23, 16 December 2023 (UTC)
- I'm not even sure we'd need any addition to WTW to be honest. An insource search for "formerly a man" has only two hits of relevance to this topic. One for a biography where it's quoting verbatim from a newspaper in a footnote, and the other in Piers Morgan about a social media spat between Morgan and Janet Mock where the phrase was used as a quote. Everything else there is unrelated. The related "formerly a woman" search has one case of an article whose language needs updating, and one translated quote from 1403. Everything else there is mythology or fiction. Related searches on phrase variations also seem to bring up very little of interest. Sideswipe9th (talk) 05:33, 16 December 2023 (UTC)
- I would agree with you if not for how the Bryson case was reported. Because this case has seen dozens of mainstream news sources employ this logic, even if it is logic that has previously been scarce, as you say. Zilch-nada (talk) 05:37, 16 December 2023 (UTC)
- Do you understand though why I described the reporting by UK media as sensationalist when looking at those search results? It is entirely out of the norm for this topic area. Sideswipe9th (talk) 06:03, 16 December 2023 (UTC)
- Just because something has scarcely been said before does not mean that it's current usage is in any way sensationalistic. Like I've said, much of the press is of high-quality broadsheets, the BBC, and papers of record, none of whom are ascribing their own logic of "former gender", but reporting descriptively on what police, the courts, and the prisons have said. Zilch-nada (talk) 06:10, 16 December 2023 (UTC)
- Do you understand though why I described the reporting by UK media as sensationalist when looking at those search results? It is entirely out of the norm for this topic area. Sideswipe9th (talk) 06:03, 16 December 2023 (UTC)
- I would agree with you if not for how the Bryson case was reported. Because this case has seen dozens of mainstream news sources employ this logic, even if it is logic that has previously been scarce, as you say. Zilch-nada (talk) 05:37, 16 December 2023 (UTC)
- Yes, my thinking is that that's just obviously neutral wording - no one doubts that Bryson transitioned. Describing it as a "former" gender is taking a clear position on the "underlying logic", as Zilch-nada, the main proponent of using that language, seems to concede above; whereas I don't see how the alternative wording contains any ideological implications. I don't think the simple existence of sources that use that wording is sufficient (especially since the sources also use phrasing like "before transitioning", including in some of the ones linked above.) That said I'm not sure the MoS needs to be too prescriptive, especially since - how often has this come up? It seems to be one dispute, on one page, which is a WP:ONEAGAINSTMANY situation, where the outcome it's obviously headed for seems to be the one a hypothetical MOS change would encourage anyway - that is to say, it seems like our existing policies and guidelines are handling it fine. Since the core issue is WP:IMPARTIAL, I suppose something about "former gender" or constructions of that nature could be added to WP:WTW somewhere, as a heads-up to people who might not understand the relevant implications, but that page is already glutted beyond the point of usefulness, and I think everyone in this discussion understands the implications already anyway. --Aquillion (talk) 05:08, 16 December 2023 (UTC)
- Is "when she was a man" seriously scary to you people? What's wrong with it? It's abundantly sourced. Zilch-nada (talk) 16:04, 15 December 2023 (UTC)
- "The wording of sources doesn't dictate our wording" is right, so various sources using wording that might be insensitive doesn't mean we can't do better. But also right is "I don't think it's correct to universalise here". If MoS were to address something like this at all (and an isolated dispute that is not part of an established, long-term pattern of such dispute at many articles, typically resolving a single, codifiable way, is not cause for MoS to do so – see WP:MOSBLOAT), it could not be with a one-size-fits-all approach that imposed wording that would not suit various trans or enby persons. There is already too much over-generalizing assumption going on throughout this topic area. I would think that "before his/her/their [gender] transition" would generally work, and agree that wording like "former gender" and "when they were a [wo]man" seems to be asserting something socio-political about gender questions. In some cases "when they identified as a [wo]man" could work, but only in some cases, and only when we have specific information about how they actually identified (if we don't have it, e.g. for some WP:BLP1E case where the subject is not someone extensively interviewed or self-publishing about such matters, the assumption would basically be WP:OR). — SMcCandlish ☏ ¢ 😼 21:24, 17 December 2023 (UTC)