The issues raised by the fuzzy region between the well-defined genders is a complex one. We tend, maybe especially us in the software world, to build systems t

The issues raised by the fuzzy region between the well-defined genders is a complex one. We tend, maybe especially us in the software world, to build systems that cater for definitions that neatly fit into specific boxes (M/F), or that rely on simplified models ("sex at birth is all you'll ever be"). Despite the fact that transgenders people have always existed, we are only starting to acknowledge their existence and recognise that they are citizen that have the same rights and duties as anyone else and that they should be treated with the same respect and consideration as anyone else. I think we, as creators of systems that model the world, should be more knowledgeable and have more consideration for the complexities of dealing with sex and gender. We can ask ourselves whether asking someone's M/F status is really necessary (what do we need it for?), whether we can allow at least a third option where neither are selected or present a perfectly valid "Prefer not to say/I don't fit in a box" option. This also affects how we choose to address people with Mr/Mrs/Ms/etc. Allowing no title to be selected (or a title of the user's choosing) should also be possible, as well as selecting a title that doesn't traditionally fit with the selected sex (like choosing Mr even if the user selected F as their sex). We then have to assume that these attributes can change over time and allow users to redefine them at will, without hindrance. There is a lot more to be done but these simple steps, all fairly easy to implement, are a start in the right direction.