HR-XML 3.0 Standards, 2009  September  23.

Menu: [ Guidelines  |  BODs  |  Nouns  |  Global Elements  |  WSDL  |  Packages  |  Code Lists  |  Master Index ]

Element: FamilyName

Name FamilyName
Type FamilyNameType
Documentation Contains a non-given name. This is an inherited name or one representing a family relationship or in some cultural contexts a "Place Name" (where someone is from). In some cultural contexts, a single family name is typical, while in others there may be multiple family names. A "primary" attribute may be used in the case where there are multiple last names. A family name can have a "prefix," such as Von, De, Van, Al, etc. These can be represented using the FamilyName "prefix" attribute. Not all implementers may find it necessary to separate prefixes from the family name itself. Capturing the prefix and FamilyName as discrete fields can become important when formatting or appearance may vary based on context. For example, in some cultural contexts it may be common to use a blank space as the delimiter between the prefix and the family name, while in others a hyphen might be used. Separating the prefix from FamilyName allows such formatting requirements to be handled flexibly.
Documentation (of type) This contains the name or names that generally would be inherited or indicative of a person's family. In Western contexts, this is what is commonly referred to as a "last name." If a person has multiple family names, the order in which the names appear is deemed significant. Generally, that order should correspond to the order in which the names would appear in a typical formatted representation. The order may be specifically identified by the sequence. A "primary" family name may be indicated using the attribute supplied for this purpose. Where multiple family names are presented, only a single name may be designated as primary = "true" Note that the attribute "prefix" may optionally contain a part of the person’s name that precedes the family name. For example: Van den, Von, Al, de, etc. Some implementers may choose not to represent a prefix separately from a Family Name. However, it may be desirable to do so for a number of reasons: 1. name sorting. For example, to support sorting on first letter of prefix and then by first letter of the family name. 2. formatting. For example, depending on the cultural context in which the name is presented, the type of delimiter (e.g., a space or a hyphen) between the prefix and the family name (or whether a delimiter appears at) all may depend on the "alphabet" and/or cultural context in which the name is presented.
XML Instance Representation
<FamilyName

primaryIndicator="oa: IndicatorType [0..1]"

sequence="oa: PositiveIntegerNumericType [0..1]"

prefix="oa: StringType [0..1]">

oa: TextType

</FamilyName>
Schema Component Representation
<xsd:element name="FamilyName" type=" FamilyNameType"/>