This page lists existing format(s) which represent gender in their schema.
Listing vCard first as vCard4 has the most up to date, modern, and inclusive notion of "gender".
- 'sex' enum
- N=none or not applicable,
- and 'gender-identity' plain text
fields, thanks in great part to this research and the advocacy of the microformats community on the VCARDDAV IETF list.
Since vCard3 had no gender feature, some vCards seem to contain an X-GENDER property. This is in line with RFC 2426 which allows applications to define their own properties, prefixed with "X-". class="x-gender" has been implemented in Cognition.
- vcard_name Property. Gender seems to be supported in Internet Explorer (appears related to AutoComplete functionality). They define
vCard.Genderas "Gender mapped to the vCard.Gender schema." (despite no such feature in the vCard standard of the time). Though it's not explicit on the page, this documentation is from the early 2000s, presumably documenting support in Windows Internet Explorer version 5+ or perhaps 6+.
- FOAF: Gender — a plain string with two blessed values "male" and "female"
ISO IEC 5218
The ISO/IEC 5218 standard specifies a standard for the "SEX" field:
The four codes specified in ISO/IEC 5218 are:
- 0 = not known,
- 1 = male,
- 2 = female,
- 9 = not applicable.
- OpenID Simple Registration Extension 1.0 openid.sreg.gender:The End User's gender, "M" for male, "F" for female.
The gender of this person. Service Providers SHOULD return one of the following Canonical Values, if appropriate:male, female, or undisclosed, and MAY return a different value if it is not covered by one of these Canonical Values.
Same as OpenSocial, in the current 'C' spec:
The gender of this contact. Service Providers SHOULD return one of the following Canonical Values, if appropriate: male, female, or undisclosed, and MAY return a different value if it is not covered by one of these Canonical Values.