Person
RIXML 2.5 Element
Represents individual product author with required personID attribute containing UUID value. Level One excludes ContactInfo child elements. UUID differs from organization and product identifiers.
Usage
Required element within PersonGroupMember, appearing exactly once. Must have personID attribute with UUID value unique to the person. Contains name elements.
Business Context
Provides precise individual identification for research authors, enabling author tracking, expertise mapping, and proper attribution across research distribution networks.
Where It Fits
Canonical Path
Definition
| Type | PersonType |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
personIDstring |
An identifier used to identify the person. For accurate identification it is required that the personID be unique for a given publisher, but the implementation of the ID is left to the publishers to implement as they deem fit. Examples: combination of LastName and FirstName, combination of internal employee ID and RIXML publisher ID. requiredSince 2.1 |
Children
JobRolestring0..1 |
Indicates the functional role played by the person relative to his/her job in the organization, for example, analyst, strategist, economist, etc. optionalSince 2.1 |
FamilyNamestring1..1 |
Indicates the family name of the person. requiredSince 2.1 |
GivenNamestring0..1 |
Indicates the given name of the person. optionalSince 2.1 |
MiddleNamestring0..1 |
Indicates the middle name of the person. optionalSince 2.1 |
DisplayNamestring0..1 |
Strongly Recommended. Indicates how the publisher or person wants the name to be presented, for example: Dr. John Doe Sr. CPA, CFA. optionalSince 2.1 |
JobTitlestring0..1 |
Indicates the official title of the person within an organization -- e.g. Managing Director, Vice President, etc. optionalSince 2.1 |
Divisionstring0..1 |
Indicates the division that the person officially works for within an organization. optionalSince 2.1 |
FamilyNameSuffixstring0..1 |
An accommodation for family name modifiers traditionally appearing after the person's name -- e.g. Jr., Sr., III.. optionalSince 2.4 |
Credentialsstring0..1 |
An accommodation for credentials traditionally appearing after the person's name -- e.g. C.F.A., Ph.D., Esq.. optionalSince 2.4 |
Biographystring0..1 |
Biographical information about the person. No markup permitted. optionalSince 2.4 |
BiographyFormattedstring0..1 |
Biographical information about the person. Limited markup permitted - HTML code for paragraph, ordered lists and unordered lists with list items, bold, underline, and italics. optionalSince 2.4 |
PhotoResourceIdRefstring0..1 |
An XML Schema keyref that will link to a Resource element representing a small photograph image of the person. Value must match a Resource.resourceID in this Product. optionalSince 2.4 |
ContactInfoContactInfoType0..unbounded |
optionalSince 2.1 |
PersonLabelstring0..unbounded |
optionalSince 2.3 |
PersonDetailsAlternativeLanguages(complex)0..1 |
optionalSince 2.5 |
Example
<Person personID="example">
<FamilyName> ... </FamilyName>
</Person>Version History
PersonLabelFamilyNameSuffix, Credentials, Biography, BiographyFormatted, PhotoResourceIdRefPersonDetailsAlternativeLanguagesBusiness Rules
Group names should appear in the Name element within PersonGroup, while individual names should appear in PersonGroupMember.Person element, with groups and people tagged separately
For Level One compliance, personID must be a UUID and must be unique from other identifier UUIDs
Level One compliance excludes ContactInfo elements inside Person
Person element must contain exactly one FamilyName element
The personID should be used for the unique identifier used by the author's firm, while PersonLabel elements should be added as required by each aggregation vendor or distribution channel
Design Decisions
The personID attribute must be a UUID for Level One compliance
To ensure unique identification of person elements using standardized UUID format
RIXML Level One Addendum v2.5, p.8
Semantic Relationships
Qualifies1 relationship
PersonLabel elements provide vendor-specific author codes while personID serves as the firm's internal unique identifier
RIXML Research Data Dictionary v2.5.1, p.15— Author identification
Mutually Exclusive With1 relationship
For single-person groups, the Person element with personID suffices without needing a personGroupID or group description
RIXML Research Data Dictionary v2.5.1, p.27— PersonGroup
Constrains3 relationships
The personID must be unique within the scope of a given publisher organization to ensure accurate person identification
RIXML Research Data Dictionary v2.5.1, p.31— personID (Required, String)
The PersonGroupMember element must contain exactly one Person element
RIXML Level One Addendum v2.5, p.8— Research.Product.Source.Organization.PersonGroupMember.Person
The Person element must contain exactly one FamilyName element
RIXML Level One Addendum v2.5, p.8— Research.Product.Source.Organization.PersonGroupMember.Person.FamilyName
Contrasts With3 relationships
The UUID for OrganizationID will not be the same as the one used for personID
RIXML Level One Addendum v2.5, p.7— Research.Product.Source.Organization.OrganizationID
The UUID for personID will not be the same as the one used for OrganizationID
RIXML Level One Addendum v2.5, p.8— Research.Product.Source.Organization.PersonGroupMember.Person
The UUID for personID will not be the same as the one used for resourceID
RIXML Level One Addendum v2.5, p.8— Research.Product.Source.Organization.PersonGroupMember.Person