Organization
RIXML 2.5 Element
Identifies the primary publishing organization for the research product. Requires type attribute from OrganizationTypeEnum and primaryIndicator set to 'Yes'. Level One excludes ContactInfo child elements.
Describes an organization related to the research item. Multiple organizations may be related to one research item. These organizations can be subsidiaries of the same parent or different organizations (as in a joint venture) working together on a publication or event. However, there can only be one primary publisher organization, which is captured by the primaryIndicator, when contained by the Source element.
Usage
Required element within Source, appearing exactly once. Must have type and primaryIndicator='Yes' attributes. Contains OrganizationID, OrganizationName, and optional PersonGroup elements.
Business Context
Essential for publisher identification and categorization, enabling research consumers to filter and organize content by institutional source and organizational characteristics.
Specification Guide
Overview
Organization describes an institutional entity — typically a publishing firm, research house, joint-venture partner, subsidiary or other body — that participates in the creation, publication or distribution of a research item. It is the primary mechanism in RIXML for attributing research to its source(s), establishing publisher identity, and carrying organisation-level metadata such as identifiers, names, personnel groupings, contact details and (from v2.4) areas of expertise.
Through RIXML 2.x, Organization appears directly under Source (and optionally inside other contexts such as EventHost / EventVenue). In the draft v3.0 model it has been moved beneath a new OrganizationList container, consistent with the v3 pattern of grouping repeating elements into explicit lists (source: meeting-2025-01, p.35; data-dictionary-v3-draft, p.36).
Usage
Use Organization to identify every institution involved in a research item. Multiple instances are permitted to model joint ventures, co-publishing arrangements, parent–subsidiary structures and other multi-party collaborations; when more than one is present, exactly one must be flagged as the primary publisher (sources: user-guide-2.2 p.16, user-guide-2.3 p.16, data-dictionary-2.5.1 p.25).
Required attributes (RIXML 2.x):
- type — drawn from OrganizationTypeEnum (e.g. SellSideFirm).
- primaryIndicator — YesNoEnum; exactly one Organization under a given Source must carry Yes.
Optional attributes: sequence for display ordering when multiple organisations are present, plus a publisher-defined value field for custom type extensions.
Typical children: OrganizationID, OrganizationName (at least one, with multiple nameType variants permitted), PersonGroup, ContactInfo, and from v2.4 Expertise (sources: data-dictionary-2.4 p.25, data-dictionary-2.5.1 p.25).
v3.0 draft: the element is contained by OrganizationList, the primary-publisher flag is renamed isPrimary (boolean), and children are themselves wrapped in list aggregations (OrganizationIDList, OrganizationNameList, PersonGroupList, ContactInfoList), plus optional Description and LogoURL elements (sources: data-dictionary-v3-draft p.36, meeting-2025-06 p.24).
Because organisation-level data tends to be stable across many research items from the same publisher, it is generally safe to automate population of this element from a publisher's master data [RIXML Research Data Dictionary v2.4 p.13].
Rules
- MUSTWhen more than one Organization appears under a Source, exactly one MUST be designated the primary publisher via primaryIndicator =
Yes(v3.0 uses the boolean isPrimary).[RIXML User Guide v2.2 p.16] [RIXML User Guide v2.3 p.16] [RIXML Research Data Dictionary v2.4 p.13] [RIXML Research Data Dictionary v2.5.1 p.25] [RIXML All-Member Meeting June 2025 p.24]↗ [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.36]↗ - MUSTOrganization MUST carry a type value from OrganizationTypeEnum and MUST contain at least one OrganizationName.[RIXML Research Data Dictionary v2.4 p.25] [RIXML Research Data Dictionary v2.5.1 p.25] [RIXML Implementation Guide v2.5.1 p.25]
- MUSTAt least one Organization is required within Source; multiple instances are permitted to represent joint ventures and subsidiaries.[RIXML User Guide v2.1 p.16] [RIXML User Guide v2.3.1 p.16] [RIXML Research Data Dictionary v2.4 p.25]
- MUSTFor Level One compliance, Source MUST contain exactly one Organization (a single primary publisher), rather than multiple collaborating organisations.[RIXML Level One Addendum v2.2 p.11] [RIXML Level One Addendum v2.3 p.25] [RIXML Level One Addendum v2.4 p.25] [RIXML Level One Addendum v2.5 p.6]
- MUSTFor Level One compliance, the Organization MUST contain exactly one OrganizationID and exactly one OrganizationName.[RIXML Level One Addendum v2.5 p.7]
- INFORMATIVEContactInfo children of Organization are not required by Level One; they may be omitted in Level One implementations but their presence is not itself a compliance violation in most readings.[RIXML Level One Addendum v2.2 p.12] [RIXML Level One Addendum v2.5 p.6]
- SHOULDFrom RIXML v2.5, Organization names SHOULD support multiple languages via the language attribute to enable international distribution and localisation.[RIXML Quarterly Update 2017 Q2 p.8]↗ [RIXML Quarterly Update 2017 Q3 p.8]↗
- SHOULDOrganization SHOULD include ContactInfo with at least an email address when contact routing is required for business or roster-update use cases.[Roster Updates Sample v2.4]↗
- MUSTA personID MUST be unique within the scope of a given publisher Organization; the format of the identifier is left to the publisher.[RIXML User Guide v2.1 p.19] [RIXML User Guide v2.3 p.18] [RIXML Research Data Dictionary v2.5.1 p.31]
Relationships
- contained-bySource — Organization is a required child of Source throughout RIXML 2.x and identifies the publishers of the research item.
- requiresOrganizationName — Organization requires at least one OrganizationName; additional names with different
nameTypevalues are permitted for legal, marketing or localised naming. - containsOrganizationID — Organization contains zero or more OrganizationID elements; OrganizationID was made optional from v2.3 onward to accommodate internal-use cases.
- containsPersonGroup — Organization may contain one or more PersonGroup elements to associate analyst teams and other personnel groupings with the publishing entity.
- containsContactInfo — Organization may contain ContactInfo for organisation-level address, website, phone and email details; not required by Level One.
- qualifiesExpertise — From v2.4, Expertise qualifies the publishing Organization by describing specialty areas, asset-class focus, regional coverage and research approach — distinct from describing the content of any one research item.
- constrainsOrganization.primaryIndicator — primaryIndicator (renamed
isPrimaryin v3.0 draft) identifies the single primary publisher when multiple organisations are present. - constrainsOrganization.type — type classifies the organisation using OrganizationTypeEnum (e.g.
SellSideFirm), with an optional publisher-defined-value attribute for custom types.
Where It Fits
Definition
| Type | OrganizationType |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
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 |
primaryIndicatorYesNoEnum |
Indicates the primary organization relative to others that may be specified. When multiple organizations (subsidiaries of the same organization or different organizations) come together on a product, one must be listed as primary (generally the parent organization or the name of the joint venture). required |
typeOrganizationTypeEnum |
The type of the organization. requiredSince 2.1 |
Children
LogoURLanyURI0..1 |
Indicates the URL location of the logo of the organization. optionalSince 2.1 |
PublisherDefinedValuestring0..1 |
For the cases in which the type attribute has the value PublisherDefined, the PublisherDefinedValue element is used to hold the organization's own description of the type. optionalSince 2.1 |
OrganizationIDstring0..unbounded |
optionalSince 2.1 |
OrganizationNamestring1..unbounded |
requiredSince 2.1 |
PersonGroup(complex)0..unbounded |
optionalSince 2.1 |
ContactInfoContactInfoType0..unbounded |
optionalSince 2.1 |
Descriptionstring0..1 |
Optional description of the organization. Used to include any additional information about the organization. optionalSince 2.1 |
Expertise(complex)0..1 |
optionalSince 2.4 |
Example
<Organization primaryIndicator="Yes"
type="SellSideFirm">
<OrganizationName> ... </OrganizationName>
</Organization>Version History
Expertisev2.1–v2.2: Organization is a required, repeatable child of Source with required type and primaryIndicator attributes, and optional sequence. Children include OrganizationID, OrganizationName, PersonGroup and ContactInfo (sources: user-guide-2.1 p.16, user-guide-2.2 p.16).
v2.3: OrganizationID became optional within Organization to better support internal use and consumers that do not require explicit identifiers [RIXML Release Notes v2.3 p.2].
v2.4: Introduced the Expertise sub-element, allowing organisations to declare publishing languages, specialties, asset classes, security types, sectors, regions and research approach independent of any single research item (sources: quarterly-2012-q2 p.3, release-notes-2.4 p.18). Community feedback at the time flagged that mixing publisher-level expertise with document-level metadata could confuse consumers and proposed migrating durable organisation data to side-car schemas — this was deferred (sources: quarterly-2012-q4 p.2, quarterly-2013-q1 p.2).
v2.5: Added multi-language support for OrganizationName, allowing organisation names to be expressed in multiple languages within a single document for international distribution (sources: quarterly-2017-q2 p.8, quarterly-2017-q3 p.8).
v3.0 (draft): Organization is restructured to live inside a new OrganizationList container, in line with the list-based pattern applied across v3. The primary-publisher flag is renamed isPrimary (boolean), typePublisherDefinedValue is added as an optional attribute, and children move into explicit list aggregations (OrganizationIDList, OrganizationNameList, PersonGroupList, ContactInfoList), plus optional Description and LogoURL elements. The committee has also flagged the v2.4 Expertise feature as a candidate for removal or splitting out due to limited uptake (sources: data-dictionary-v3-draft p.36, meeting-2025-01 p.35, meeting-2025-06 p.24, meeting-2024-winter p.22).
Level One profile (all versions): Restricts Source to a single Organization with primaryIndicator = Yes, requires exactly one OrganizationID and one OrganizationName, and does not require ContactInfo children (sources: level-one-2.2 p.11, level-one-2.3 p.25, level-one-2.4 p.25, level-one-2.5 p.6).
Business Rules
When multiple organizations collaborate on a product, exactly one must be designated as the primary publisher using primaryIndicator
For Level One compliance, Organization primaryIndicator attribute must be present and set to Yes
Level One compliance excludes ContactInfo elements as children of Organization
Design Decisions
The primaryIndicator attribute must be present and set to 'Yes' for Organization elements in Level One
To ensure proper identification of the primary publisher organization
RIXML Level One Addendum v2.5, p.6
Only a single primary publisher organization is allowed in Level One Source element
Level One does not support complex inter-organizational collaboration projects to reduce implementation complexity
RIXML Level One Addendum v2.5, p.25
Semantic Relationships
Constrains7 relationships
When multiple organizations collaborate on a product, exactly one must be designated as primary, typically the parent organization or joint venture name
RIXML Research Data Dictionary v2.5.1, p.25— Organization
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 type attribute of Organization elements must use values from the OrganizationTypeEnum enumeration to ensure consistent categorization of publishing firms
RIXML Implementation Guide v2.5.1, p.25— EXAMPLE:
Only one organization can be marked as primary publisher when contained within the Source element
RIXML Implementation Guide v2.5.1, p.34— The corresponding information in the Data Dictionary looks like this:
For Level One compliance, the Source element must contain exactly one Organization element
RIXML Level One Addendum v2.5, p.6— Research.Product.Source
For Level One compliance, the Organization element must contain exactly one OrganizationID element
RIXML Level One Addendum v2.5, p.7— Research.Product.Source.Organization.OrganizationID
For Level One compliance, the Organization element must contain exactly one OrganizationName element
RIXML Level One Addendum v2.5, p.7— Research.Product.Source.Organization.OrganizationName
Requires3 relationships
Content producers must write once and send everywhere, maintaining a single process for transmitting research content to all aggregation vendors and clients
RIXML Implementation Guide v2.5.1, p.22— Content producers must be able to write once, send everywhere
For Level One compliance, the Organization primaryIndicator attribute must be present and set to Yes
RIXML Level One Addendum v2.5, p.6— Research.Product.Source.Organization
When the type attribute has a value of PublisherDefined, the PublisherDefinedValue element is necessary to hold the off-list entry
RIXML Level One Addendum v2.5, p.7— Research.Product.Source.Organization.PublisherDefinedValue