RIXML Documentation

PersonGroup

RIXML 2.5 Element

Level OneRequired

Optional container element for specifying research product authors within an organization. Level One excludes ContactInfo child elements. Can be omitted entirely when no author tagging is needed.

The PersonGroup element is used to hold the name(s) of the individual person(s) and/or the name of the group. In the case of an individual person, the person tag and its associated personID are used (no personGroupID or description is needed). PersonGroups can be formally organized groups or they can be fluid groups that come together to deliver content. If the "group" consists of only one person, there is no need to define a group ID and description; it is sufficient to have the 'person' tag and the associated personID under the 'group' tag.

Usage

Optional element within Organization, appearing at most once. When present, must contain at least one PersonGroupMember element. Omit completely when not tagging authors.

Business Context

Supports author attribution for research products, enabling proper crediting and expertise tracking for research analysts and contributors in distribution workflows.

Source:level-one-2.5
Schema:RIXML-Common-2_5.xsd:752

Where It Fits

Definition

Type
Namespacehttp://www.rixml.org/2017/9/RIXML
Min Occurs1
Max Occurs1

Attributes

Some unique label used to reference a particular group of people.

optionalSince 2.1
sequenceinteger

Used to indicate any meaningful ordering of the Products contained in this Research item. Particularly useful in publishing compendium products made up of multiple sub-products. Ordering is ascending.

optionalSince 2.1

Indicates the primary PersonGroup, when more than one are specified.

optionalSince 2.1
roleRoleEnum

The role of the group relative to this research item. This is especially useful if only the group is specified without any members or if all members share the same role -- as in a group of document authors or meeting attendees.

optionalSince 2.1

Children

Namestring0..1

Indicates the name of the group. This is not required, but can be used where groups are formally named or if there is a name created for the group involved with a publication or event.

optionalSince 2.1

If the role attribute has the value PublisherDefined, this element is used to hold the publisher's own description of the role.

optionalSince 2.1
PersonGroupMember(complex)0..unbounded
optionalSince 2.1
ContactInfoContactInfoType0..unbounded
optionalSince 2.1
optionalSince 2.5

Example

<PersonGroup />

Version History

2.1
+Introduced
2.5
+Added children: PersonGroupDetailsAlternativeLanguages

Business Rules

MUST

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

author-categorizationgroup-individual-separation
MUST

Level One compliance excludes ContactInfo elements inside PersonGroup

validationlevel-one-complianceexclusion
MUST

For Level One compliance, PersonGroup must contain at least one PersonGroupMember element when present

validationlevel-one-compliance
MAY

When a PersonGroup consists of only one person, there is no need to define a group ID and description; only the person tag and associated personID are sufficient

simplificationconditional-requirement

Semantic Relationships

Contrasts With1 relationship

Group names should be tagged in PersonGroup.Name while individual names should be tagged in PersonGroupMember.Person, maintaining separation between groups and individuals

RIXML Research Data Dictionary v2.5.1, p.15Which Analysts to include in the RIXML File

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.27PersonGroup

Constrains2 relationships

When multiple PersonGroups exist, the primaryIndicator attribute determines which one takes precedence

RIXML Research Data Dictionary v2.5.1, p.28primaryIndicator (Optional, YesNoEnum)

For Level One compliance, when PersonGroup is present, it must contain at least one PersonGroupMember element

RIXML Level One Addendum v2.5, p.7Research.Product.Source.Organization.PersonGroupMember

Broadens1 relationship

The PersonGroup role attribute is particularly valuable when all members share the same role or when only the group is specified without individual members

RIXML Research Data Dictionary v2.5.1, p.28primaryIndicator (Optional, YesNoEnum)

Qualifies1 relationship

PersonGroupMember primaryIndicator identifies which individual member has primary status within a group, allowing multiple primary members per group

RIXML Research Data Dictionary v2.5.1, p.29Elements and Attributes: