Things to think about:
- As nice and simple as it would be for our genealogy programs, Sex is not always boolean in humans. It just isn't. The number of people who are intersex to some degree is between 0.1%-0.2%, which means over three million people in the US. If it were not for the invention of karyotype (chromosome) testing in recent years to reveal things like Klinefelter's Syndrome (people who are XXY but phenotypically male, but occasionally with gynecomastia) or Androgen Insensitivity Syndrome (people who are XY but phenotypically female, albeit minus a uterus), many more cases would never get recognized at all; many of these cases never get noticed until the person is of childbearing age and is trying to find out why they or their partner cannot become pregnant. Obviously, most men with Klinefelter's will choose to keep identifying legally and personally as male, and the same for women with AIS, regardless of their chromosomes. But some people would choose to identify as Intersex, and they should have the right to that option, especially since it's technically biologically true! So, my proposal: genealogical programs should be able to model M, F, U (or blank) for Unknown, or I for Intersex.
- And then things get more complicated with transsexuals -- a not insignificant number of whom, by the way, also have or had intersex conditions. The right to legally correct a birth certificate and other government identification varies from place to place, even from state to state. And it's orthogonal to the choice of the individual to also have had surgery or other medical interventions -- some places require the person to have had surgery in order to update legal documents (i.e. North Dakota) and some places do not (i.e. South Dakota). So really there are two different Events that need to be modeled here for genealogy programs: Legal Change of Gender/Sex and Medical Change of Gender/Sex. Although frankly, I can't think of any other kinds of medical Events that are tracked in a genealogy program, other than birth and death, so perhaps just noting the legal formalities would be sufficient, since that creates a paper trail. It would definitely be a thing I would want to keep track of in the research process, to be able to document that John Doe in census #1 is the same as Jane Doe in census #2, just to reduce confusion. But on the other hand, I also know that many transsexuals absolutely hate reminders of their previous name and gender status, and really would not want any genealogy program, even one run by a well-meaning relative, to list any documentation of their previous status, especially if that family tree might ever go online in any way.
- A not-too-uncommon scenario: John Doe marries and has biological children with his wife, then legally and medically transitions to female and becomes Jane Doe. In that scenario, doing a genealogical pedigree of one of their children should show there to be two mothers. Luckily, this one is a solved problem since every single genealogy program on the planet, offline or online, is able to handle a tree with a same-sex couple in it and could draw the pedigree correctly…oh wait, no, my bad, there's still one online tree program that's a hold-out about that kind of thing. Well, maybe they'll come around eventually.
Short answer: this is all a little tricky, and has some privacy implications to boot…but it's still not as hard as having to deal with multiple date formats or names in non-Latin characters. :-)
- Brooke