Difference between revisions of "gender-formats"

From Microformats Wiki
gender-formats
Jump to navigation Jump to search
(→‎FOAF: expanding)
Line 14: Line 14:
  
 
=== 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"
  
 
=== OpenSocial ===
 
=== OpenSocial ===

Revision as of 14:06, 20 November 2012

gender formats

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

specs

OpenID sreg

vCard

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

  • vcard_name Property. Gender seems to be supported in Internet Explorer; vCard.Gender is Gender mapped to the vCard.Gender schema.

FOAF

  • FOAF: Gender — a plain string with two blessed values "male" and "female"

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