Advice for Implementers 

This document offers advice to implementers looking to take advantage of the eduPersonDisplayPronouns attribute. This attribute offers a way of transmitting (and storing if used in a directory context) personal pronouns as a human being would like them to be displayed to support their use in applications that are capable of consuming it for display purposes to other human beings. In English, this pattern commonly has the pronouns following one's name (eg: "he/him/his"  following "Ashe Winters"). The attribute value, while in some languages written as "subject/object/possessive" (e.g., "she/her/hers" or "ella/la/su"), is a free-form string and must not be assumed to take any particular form or set of values.  Other values could include (but are not limited to): "ask me" or "prefer not to state" or "use first name."

Different languages treat the entire concept of pronouns differently, and the group who contributed to this document do not represent experience with all languages. Additional feedback representing additional language behaviors is more than welcome; please submit an issue to GitHub.  The guidance offered here regarding where and how to store pronoun choice for use in third-party services is intended to apply internationally and so does not make any specific recommendation regarding which pronouns an organization should support. That must be a decision made locally and in accordance with local language and cultural requirements.

Specific Guidance

FAQ

My institution wants to use a predefined list of pronouns, how should I implement this?