Definition Type: ComplexType
Name: PersonNameType
Namespace: http://www.hr-xml.org/3
Type: nsA:PersonNameBaseType
Containing Schema: Components.xsd
Abstract
Documentation:
Person Name. Details A collection of data representing a person name. Various uses and options are supported. The person name model is intended to be useful across many cultural contexts. The ordering and presentation of given names and family names may vary by cultural custom. A person name can be represented as a formatted string "Mr. John L Smith III, Phd" or represented as discretely fielded data or both. An option to present a name in an alternative "alphabet" or script is supported. For example the same name might be presented using Roman, Kanji, Arabic, or other character sets. Note the term "script" versus "character set" is used so as not to confuse this issue with concepts such as "character encoding".
Collapse XSD Schema Diagram:
Drilldown into UserArea in schema fields_xsd Drilldown into AlternateScriptPersonName in schema components_xsd Drilldown into PersonNameInitials in schema fields_xsd Drilldown into TitleAffixCode in schema fields_xsd Drilldown into QualificationAffixCode in schema fields_xsd Drilldown into GenerationAffixCode in schema fields_xsd Drilldown into PreferredSalutationCode in schema fields_xsd Drilldown into FormerFamilyName in schema fields_xsd Drilldown into FamilyName in schema fields_xsd Drilldown into MiddleName in schema fields_xsd Drilldown into PreferredName in schema fields_xsd Drilldown into GivenName in schema fields_xsd1 Drilldown into LegalName in schema fields_xsd Drilldown into FormattedName in schema fields_xsd Drilldown into PersonNameBaseType in schema components_xsd Drilldown into legalNameIndicator in schema components_xsd Drilldown into nameTypeCode in schema components_xsd Drilldown into validTo in schema fields_xsd Drilldown into validFrom in schema fields_xsd Drilldown into EffectiveDateAttributeGroup in schema fields_xsd Drilldown into scriptCode in schema components_xsdXSD Diagram of PersonNameType in schema components_xsd (HR-XML - Human Resources XML)
Collapse XSD Schema Code:
<xsd:complexType name="PersonNameType">
    <xsd:annotation>
        <xsd:documentation source="http://www.hr-xml.org" xml:lang="en">
            <ccts:DictionaryEntryName xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">Person Name. Details</ccts:DictionaryEntryName>
            <ccts:DefinitionText xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">A collection of data representing a person name. </ccts:DefinitionText>
            <ccts:UsageRule xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">Various uses and options are supported. 
				
				The person name model is intended to be useful across many cultural contexts.
				The ordering and presentation of given names and family names may vary by 
				cultural custom. 

				A person name can be represented as a formatted string "Mr. John L Smith III, Phd" or 
				represented as discretely fielded data or both.
				
				An option to present a name in an alternative "alphabet" or script is supported. For
				example the same name might be presented using Roman, Kanji, Arabic, or
				other character sets. Note the term "script" versus "character set" is used so as not 
				to confuse this issue with concepts such as "character encoding". 
				</ccts:UsageRule>
        </xsd:documentation>
    </xsd:annotation>
    <xsd:complexContent>
        <xsd:extension base="PersonNameBaseType">
            <xsd:sequence>
                <xsd:element ref="AlternateScriptPersonName" minOccurs="0" maxOccurs="unbounded" />
                <xsd:element ref="UserArea" minOccurs="0" />
            </xsd:sequence>
            <xsd:attribute name="scriptCode" type="oa:NormalizedStringType" use="optional" />
            <xsd:attributeGroup ref="EffectiveDateAttributeGroup" />
            <xsd:attribute name="nameTypeCode" type="NameTypeCodeContentType" use="optional" />
            <xsd:attribute name="legalNameIndicator" type="oa:IndicatorType" use="optional">
                <xsd:annotation>
                    <xsd:documentation>Indicates whether or not the PersonName represents
a "legal" or "official" name. Note that in some business contexts, a legal name is a formatted name. For example, 
the exact way that a person's name is represented within contracts and legal documents. Note that
for this second use, LegalName is optionally available within PersonName. The legalNameIndicator 
is used when there is the need to distinquish the entire collection of information as
a legalName. This second use case may be less common the first, but both are supported.</xsd:documentation>
                </xsd:annotation>
            </xsd:attribute>
        </xsd:extension>
    </xsd:complexContent>
</xsd:complexType>
Collapse Child Elements:
Name Type Min Occurs Max Occurs
FormattedName nsA:FormattedName 0 (1)
LegalName nsA:LegalName 0 (1)
GivenName oa:GivenName 0 unbounded
PreferredName nsA:PreferredName 0 (1)
MiddleName nsA:MiddleName 0 (1)
FamilyName nsA:FamilyName 0 unbounded
FormerFamilyName nsA:FormerFamilyName 0 (1)
PreferredSalutationCode nsA:PreferredSalutationCode 0 (1)
GenerationAffixCode nsA:GenerationAffixCode 0 (1)
QualificationAffixCode nsA:QualificationAffixCode 0 unbounded
TitleAffixCode nsA:TitleAffixCode 0 unbounded
PersonNameInitials nsA:PersonNameInitials 0 (1)
AlternateScriptPersonName nsA:AlternateScriptPersonName 0 unbounded
UserArea nsA:UserArea 0 (1)
Collapse Child Attributes:
Name Type Default Value Use
scriptCode nsA:scriptCode Optional
validFrom nsA:validFrom Optional
validTo nsA:validTo Optional
nameTypeCode nsA:nameTypeCode Optional
legalNameIndicator nsA:legalNameIndicator Optional
Collapse Derivation Tree:
Collapse References:
nsA:ContactPersonName, nsA:FatherName, nsA:MotherName, nsA:ParticipantName, nsA:PersonName, nsA:SignedByName, nsA:WrittenByName