"uid":"The 'UID' is an identifier associated with the user. It may be the users login name. It may be multi-valued.<br/>Examples: 's9709015', 'admin', and 'Administrator'.",
"uid":"The 'UID' is an identifier associated with the user. It may be the users login name. It may be multi-valued.\\n\\nExamples: 's9709015', 'admin', and 'Administrator'.",
"schacHomeOrganization":"A person's home organization using the domain name of the organization.<br/>Example: 'universityofharderwijk.nl'.",
"schacHomeOrganization":"A person's home organization using the domain name of the organization.\\n\\nExample: 'universityofharderwijk.nl'.",
"cn":"The 'cn' ('commonName') attribute contains names of an person. Each name is one value of this multi-valued attribute. It is typically the person's full name.<br/>Example: 'Carl' 'von Linné'.",
"cn":"The 'cn' ('commonName') attribute contains names of an person. Each name is one value of this multi-valued attribute. It is typically the person's full name.\\n\\nExample: 'Carl' 'von Linné'.",
"givenName":"The 'givenName' attribute contains name strings that are the part of a person's name that is not their surname. Each string is one value of this multi-valued attribute.<br/>Example: 'Carl'",
"givenName":"The 'givenName' attribute contains name strings that are the part of a person's name that is not their surname. Each string is one value of this multi-valued attribute.\\n\\nExample: 'Carl'",
"sn":"Surname or family name. This attribute contains name strings for the family names of a person. Each string is one value of this multi-valued attribute. If the surname contains hypens, each component of the name may also be stored seperately. Example: 'von Linné'",
"sn":"Surname or family name. This attribute contains name strings for the family names of a person. Each string is one value of this multi-valued attribute. If the surname contains hypens, each component of the name may also be stored seperately.\\n\\nExample: 'von Linné'",
"displayName":"The preferred name(s) that should appear when when displaying entries for this person.<br/>Example: 'Carolus Linnaeus'",
"displayName":"The preferred name(s) that should appear when when displaying entries for this person.\\n\\nExample: 'Carolus Linnaeus'",
"mail":"The internet email addresses for this user, may be multi-valued.<br/>Example: c.vonlinne@universityofharderwijk.nl'",
"mail":"The internet email addresses for this user, may be multi-valued.\\n\\nExample: c.vonlinne@universityofharderwijk.nl'",
"eduPersonAffiliation":"Specifies the person's relationship(s) to the institution in broad categories. Only permissable values are: faculty, student, staff, alum, member, affiliate, employee, library-walk-in.<br/>Example: 'member', 'faculty'",
"eduPersonAffiliation":"Specifies the person's relationship(s) to the institution in broad categories. Only permissable values are: faculty, student, staff, alum, member, affiliate, employee, library-walk-in.\\n\\nExample: 'member', 'faculty'",
"eduPersonScopedAffiliation":"Specifies the person's affiliation within a particular security domain in broad categories. The values consist of a left and right component separated by an '@' sign, The left component is one of the values from the eduPersonAffiliation controlled vocabulary.This right-hand side syntax of eduPersonScopedAffiliation intentionally matches that used for the right-hand side values for eduPersonPrincipalName. The 'scope' portion MUST be the administrative domain to which the affiliation applies.<br/>Example: 'member@@universityofharderwijk.nl', 'faculty@@universityofharderwijk.nl'",
"eduPersonScopedAffiliation":"Specifies the person's affiliation within a particular security domain in broad categories. The values consist of a left and right component separated by an '@' sign, The left component is one of the values from the eduPersonAffiliation controlled vocabulary.This right-hand side syntax of eduPersonScopedAffiliation intentionally matches that used for the right-hand side values for eduPersonPrincipalName. The 'scope' portion MUST be the administrative domain to which the affiliation applies.\\n\\nExample: 'member@@universityofharderwijk.nl', 'faculty@@universityofharderwijk.nl'",
"eduPersonEntitlement":"A URI (either URN or URL) that indicates a set of roles or rights to specific resources.<br/>Example: 'urn:mace:washington.edu:confocalMicroscope' 'http://xstor.com/contracts/HEd123'",
"eduPersonEntitlement":"A URI (either URN or URL) that indicates a set of roles or rights to specific resources.\\n\\nExample: 'urn:mace:washington.edu:confocalMicroscope' 'http://xstor.com/contracts/HEd123'",
"isMemberOf":"The values of isMemberOf are identifiers for groups to which the containing person belongs.<br/>Example: 'https://toolbox.switch.ch/sig-mobile-wg', 'Stanford:faculty:emeritus', 'admin'",
"isMemberOf":"The values of isMemberOf are identifiers for groups to which the containing person belongs.\\n\\nExample: 'https://toolbox.switch.ch/sig-mobile-wg', 'Stanford:faculty:emeritus', 'admin'",
"eduPersonPrincipalName":"A scoped identifier for a person. It is represented in the form 'user@scope' where 'user' is a name-based identifier for the person and where the 'scope' portion MUST be the administrative domain of the identity system where the identifier was created and assigned. Note this idenitfier might be reassigend over time. Values of eduPersonPrincipalName are often, but not required to be, human-friendly, and may change as a result of various business processes. Possibilities of changes and reassignments make this identifier unsuitable for many purposes. As a result, eduPersonPrincipalName is NOT RECOMMENDED for use by applications that provide separation between low-level identification and more presentation-oriented data such as name and email address. Common identity protocols provide for a standardized and more stable identifier for such applications, and these protocol-specific identifiers should be used whenever possible; where using a protocol-specific identifier is not possible, the eduPersonUniqueId attribute may be an appropriate neutral form. Syntactically, ePPN looks like an email address but is not intended to be a person’s published email address, or to be used as an email address. Consumers must not assume this is a valid email address for the individual. <br/>Examples: 'niels@surf.nl', 's4928467@student.universityofharderwijk.nl'"
"eduPersonPrincipalName":"A scoped identifier for a person. It is represented in the form 'user@scope' where 'user' is a name-based identifier for the person and where the 'scope' portion MUST be the administrative domain of the identity system where the identifier was created and assigned. Note this idenitfier might be reassigend over time. Values of eduPersonPrincipalName are often, but not required to be, human-friendly, and may change as a result of various business processes. Possibilities of changes and reassignments make this identifier unsuitable for many purposes. As a result, eduPersonPrincipalName is NOT RECOMMENDED for use by applications that provide separation between low-level identification and more presentation-oriented data such as name and email address. Common identity protocols provide for a standardized and more stable identifier for such applications, and these protocol-specific identifiers should be used whenever possible; where using a protocol-specific identifier is not possible, the eduPersonUniqueId attribute may be an appropriate neutral form. Syntactically, ePPN looks like an email address but is not intended to be a person’s published email address, or to be used as an email address. Consumers must not assume this is a valid email address for the individual.i\\n\\nExamples: 'niels@surf.nl', 's4928467@student.universityofharderwijk.nl'",
