gender-formats - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:22:42Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:22, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~gender formats~~</entry-title>~~		{{DISPLAYTITLE:gender formats}}

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

Tantek: add ISO/IEC 5218, list for the vCard4 properties to make them more obvious

2013-01-30T21:21:44Z

add ISO/IEC 5218, list for the vCard4 properties to make them more obvious

← Older revision		Revision as of 21:21, 30 January 2013
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===

Tantek: entry-title, autotoc

2012-11-20T17:29:52Z

entry-title, autotoc

← Older revision		Revision as of 17:29, 20 November 2012
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.

Tantek: 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

2012-11-20T17:29:29Z

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

← Older revision		Revision as of 17:29, 20 November 2012
Line 4:		Line 4:

	==specs==		==specs==
	=== ~~OpenID sreg~~===		=== vCard ===
	* [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>~~		Listing vCard first as vCard4 has the most up to date, modern, and inclusive notion of "gender".

			==== 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.

			As such, 'p-sex' and 'p-gender-identity' properties are defined in [[uf2#h-card\|h-card]] for [[microformats2]].

	=== ~~vCard~~ ===		==== x-gender ====
	~~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].		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 ===		==== Microsoft vCard ====
	* [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.		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] — 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"

			=== 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 ===		=== OpenSocial ===

TomMorris: /* FOAF */ expanding

2012-11-20T14:06:42Z

FOAF: expanding

← Older revision		Revision as of 14:06, 20 November 2012
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 ===

Tantek: /* OpenSocial */ typo

2011-07-25T07:05:44Z

OpenSocial: typo

← Older revision		Revision as of 07:05, 25 July 2011
Line 17:		Line 17:

	=== OpenSocial ===		=== 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 ~~fiels~~ 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:		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>		<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>

Kevin Marks: add PoCo

2010-11-30T09:20:39Z

add PoCo

← Older revision		Revision as of 09:20, 30 November 2010
Line 19:		Line 19:
	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 fiels 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:		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 fiels 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>		<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 ==

Kevin Marks: add OpenSocial

2010-11-30T09:15:02Z

add OpenSocial

← Older revision		Revision as of 09:15, 30 November 2010
Line 15:		Line 15:
	=== FOAF ===		=== FOAF ===
	*[http://xmlns.com/foaf/spec/#term_gender FOAF: Gender]		*[http://xmlns.com/foaf/spec/#term_gender FOAF: Gender]

			=== 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 fiels 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>

	== see also ==		== see also ==

TobyInk: /* vCard */

2008-03-16T22:57:38Z

vCard

← Older revision		Revision as of 22:57, 16 March 2008
Line 8:		Line 8:

	=== 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-". [[~~User~~:~~TobyInk\|TobyInk]~~] ~~15:55, 16 Mar 2008 (PDT)~~		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 ===		=== Microsoft vCard ===

TobyInk at 22:55, 16 March 2008

2008-03-16T22:55:53Z

← Older revision		Revision as of 22:55, 16 March 2008
Line 6:		Line 6:
	=== OpenID sreg===		=== 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>		* [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 ===
			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-". [[User:TobyInk\|TobyInk]] 15:55, 16 Mar 2008 (PDT)

	=== Microsoft vCard ===		=== Microsoft vCard ===