In the current h-card spec, there are two fields, p-sex and p-gender-identity. In both of their descriptions, they refer to "vCard4 (RFC 6350)":
p-sex - biological sex, new in vCard4 (RFC 6350)
p-gender-identity - gender identity, new in vCard4 (RFC 6350)
However, after looking at vCard4/RFC 6350, it is not clear how they should be used, as there is no explicit "sex" property, but rather a single property for both gender and sex:
6.2.7. GENDER
Purpose: To specify the components of the sex and gender identity of the object the vCard represents.
Value type: A single structured value with two components. Each component has a single text value.
Cardinality: *1
Special notes: The components correspond, in sequence, to the sex (biological), and gender identity. Each component is optional.
Sex component: A single letter. M stands for "male", F stands for "female", O stands for "other", N stands for "none or not applicable", U stands for "unknown".
Gender identity component: Free-form text.
ABNF:
GENDER-param = "VALUE=text" / any-param
GENDER-value = sex [";" text]
sex = "" / "M" / "F" / "O" / "N" / "U"
Examples:
GENDER:M
GENDER:F
GENDER:M;Fellow
GENDER:F;grrrl
GENDER:O;intersex
GENDER:;it's complicated
However, based on these descriptions, I would have expected there to be separate properties for gender & sex, however as they are both merged into one property causing the usage of them to be a bit unclear. (ie. it could easily be interpreted that p-gender-identity should be sex [";" text], eg. F;grrrl or ;it's complicated)
I'm assuming that p-sex is intended to be the sex value for the GENDER property and the p-gender-identity is intended to be the text value for the GENDER property.
I think a better description for these might be something like:
p-sex - biological sex, one of: M (male), F (female), O (other), N (none/not applicable), or U (unknown). See: RFC 6350
p-gender-identity - gender identity, freeform text. See: RFC 6350
This would help clarify what values should be used in the field.
In the current h-card spec, there are two fields,
p-sexandp-gender-identity. In both of their descriptions, they refer to "vCard4 (RFC 6350)":However, after looking at vCard4/RFC 6350, it is not clear how they should be used, as there is no explicit "sex" property, but rather a single property for both gender and sex:
However, based on these descriptions, I would have expected there to be separate properties for gender & sex, however as they are both merged into one property causing the usage of them to be a bit unclear. (ie. it could easily be interpreted that
p-gender-identityshould besex [";" text], eg.F;grrrlor;it's complicated)I'm assuming that
p-sexis intended to be thesexvalue for theGENDERproperty and thep-gender-identityis intended to be thetextvalue for theGENDERproperty.I think a better description for these might be something like:
This would help clarify what values should be used in the field.