gender-formats: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(note vCard4 has a gender property with fields sex and gender-identity, pull it to the top since as the most recent/modern gender related format, influenced by this page and proposed by this community)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
<h1>gender formats</h1>
{{DISPLAYTITLE:gender formats}}
{{TOC-right}}
 
This page lists existing format(s) which represent [[gender]] in their schema.
This page lists existing format(s) which represent [[gender]] in their schema.


Line 8: Line 8:


==== vCard4 ====
==== vCard4 ====
[[vCard4]] has a '[http://tools.ietf.org/html/rfc6350#section-6.2.7 gender]' property with 'sex' enum (M=male, F=female, O=other, N=none or not applicable, U=unknown) 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.
[[vCard4]] has a '[http://tools.ietf.org/html/rfc6350#section-6.2.7 gender]' property with:
* 'sex' enum  
** M=male,  
** F=female,  
** O=other,  
** N=none or not applicable,  
** U=unknown
* and 'gender-identity' plain text  
fields, thanks in great part to [[gender|this research]] and the advocacy of the microformats community on the VCARDDAV IETF list.


As such, 'p-sex' and 'p-gender-identity' properties are defined in [[uf2#h-card|h-card]] for [[microformats2]].
As such, 'p-sex' and 'p-gender-identity' properties are defined in [[uf2#h-card|h-card]] for [[microformats2]].
Line 21: Line 29:
=== FOAF ===
=== FOAF ===
*[http://xmlns.com/foaf/spec/#term_gender FOAF: Gender] — a plain string with two blessed values "male" and "female"
*[http://xmlns.com/foaf/spec/#term_gender FOAF: Gender] — a plain string with two blessed values "male" and "female"
=== ISO IEC 5218 ===
The [http://en.wikipedia.org/wiki/ISO/IEC_5218 ISO/IEC 5218] standard specifies a standard for the "SEX" field:
<blockquote>The four codes specified in ISO/IEC 5218 are: <ul><li>0 = not known,</li><li>1 = male,</li><li>2 = female,</li><li>9 = not applicable.</li></ul></blockquote>


=== OpenID sreg===
=== OpenID sreg===

Latest revision as of 16:22, 18 July 2020


This page lists existing format(s) which represent gender in their schema.

specs

vCard

Listing vCard first as vCard4 has the most up to date, modern, and inclusive notion of "gender".

vCard4

vCard4 has a 'gender' property with:

  • 'sex' enum
    • M=male,
    • F=female,
    • O=other,
    • N=none or not applicable,
    • U=unknown
  • 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.

As such, 'p-sex' and 'p-gender-identity' properties are defined in h-card for microformats2.

x-gender

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.

Microsoft vCard

Circa 2000:

  • vcard_name Property. Gender seems to be supported in Internet Explorer (appears related to AutoComplete functionality). They define vCard.Gender as "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

  • 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 sreg

OpenSocial

First included in OpenSocial 0.7 as an ENUM, which is a string field that has some predefined values. current spec text in OpenSocial 1.1 is:

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.

Portable Contacts

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.

see also