gender formats

(Difference between revisions)

Jump to: navigation, search
(vCard)
Current revision (21:21, 30 January 2013) (view source)
(add ISO/IEC 5218, list for the vCard4 properties to make them more obvious)
 
(6 intermediate revisions not shown.)
Line 1: Line 1:
-
<h1>gender formats</h1>
+
<entry-title>gender formats</entry-title>
-
{{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.
==specs==
==specs==
-
=== OpenID sreg===
 
-
* [http://openid.net/specs/openid-simple-registration-extension-1_0.html OpenID Simple Registration Extension 1.0] <blockquote><div>openid.sreg.gender:</div><div>The End User's gender, "M" for male, "F" for female.</div></blockquote>
 
-
 
=== vCard ===
=== vCard ===
-
Some vCards [http://www.google.com/search?q=vcard+x-gender 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 [http://buzzword.org.uk/cognition/uf-plus.html implemented] in [http://buzzword.org.uk/cognition/ Cognition].
+
Listing vCard first as vCard4 has the most up to date, modern, and inclusive notion of "gender".
-
=== Microsoft vCard ===
+
==== vCard4 ====
-
* [http://msdn2.microsoft.com/en-us/library/ms535130.aspx vcard_name Property]. Gender seems to be supported in Internet Explorer; <code>vCard.Gender</code> is Gender mapped to the vCard.Gender schema.
+
[[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]].
 +
 
 +
==== x-gender ====
 +
Since [[vCard3]] had no gender feature, some vCards [http://www.google.com/search?q=vcard+x-gender 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 [http://buzzword.org.uk/cognition/uf-plus.html implemented] in [http://buzzword.org.uk/cognition/ Cognition].
 +
 
 +
==== Microsoft vCard ====
 +
Circa 2000:
 +
* [http://msdn2.microsoft.com/en-us/library/ms535130.aspx vcard_name Property]. Gender seems to be supported in Internet Explorer (appears related to AutoComplete functionality). They define <code>vCard.Gender</code> 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 ===
-
*[http://xmlns.com/foaf/spec/#term_gender FOAF: Gender]
+
*[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===
 +
* [http://openid.net/specs/openid-simple-registration-extension-1_0.html OpenID Simple Registration Extension 1.0] <blockquote><div>openid.sreg.gender:</div><div>The End User's gender, "M" for male, "F" for female.</div></blockquote>
 +
 
 +
=== OpenSocial ===
 +
First included in [http://wiki.opensocial.org/index.php?title=Opensocial.Enum_(v0.8)#opensocial.Enum.Gender.MALE OpenSocial 0.7 as an ENUM], which is a string field that has some predefined values. current spec text in [http://opensocial-resources.googlecode.com/svn/spec/1.1/Social-Data.xml OpenSocial 1.1] is:
 +
<blockquote>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.</blockquote>
 +
 
 +
=== Portable Contacts ===
 +
Same as OpenSocial, in the [http://portablecontacts.net/draft-spec.html current 'C' spec]:
 +
<blockquote>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.</blockquote>
== see also ==
== see also ==

Current revision


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

Contents

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:

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:

FOAF

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

gender formats was last modified: Wednesday, January 30th, 2013

Views