I am modeling a database that should be used as generic non-functional requisite for all services of the startup company, like persons, users, services and commercial data like coupons, signature packages, etc.
I am thinking about the Gender model. In these modern days and with different laws across countries about subjective identity, should I take that into consideration and model my Person entity with more than just the male and female options?
Options are: undefined, not-answered, other, transgender... or any other industry standard that I am unaware of...
Or does this offend LGBT people by saying that they are not truly male or female?