RIXML Documentation

IssuerDetails

RIXML 2.5 Element

Level OneRequired

Optional container element for issuer-related information. When present, must contain at least one Issuer element describing companies or entities featured in the research.

Usage

Optional element within Context, appearing at most once. When included, must contain at least one Issuer child element.

Business Context

Enables research categorization and filtering by company or issuer focus, supporting targeted content discovery and portfolio-specific research distribution workflows.

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

Specification Guide

Overview

IssuerDetails is a container element within the Context package that groups all information about the companies, governments, or other entities that issue the securities discussed in a research product. It acts as the aggregation point for one or more Issuer children, each of which carries identification, classification, financial, and security-level detail for a single issuing entity. By collecting issuer information in a single, well-defined container, IssuerDetails enables downstream systems to attribute research to specific companies, filter and route content by issuer coverage, and integrate research with portfolio management, compliance, and entitlement systems.

Usage

IssuerDetails is an optional child of Context and appears at most once per Product. When present, it must contain at least one Issuer child; multiple Issuer elements are permitted when the research covers several issuing entities (sources: level-one-2.2 p.17, level-one-2.3 p.12, level-one-2.3.1 p.12, level-one-2.5 p.12, data-dictionary-2.5.1 p.46). Typical usage patterns: - Single-company research — one IssuerDetails containing one Issuer for the covered company. - Multi-company or industry research — one IssuerDetails containing several Issuer elements (e.g. peer comparisons, sector notes, morning calls). - Non-issuer-focused researchIssuerDetails is omitted entirely when the product does not discuss specific issuing entities (e.g. macro or strategy pieces classified primarily via ProductClassifications). Detailed issuer attributes (identifiers, names, financials, ratings, securities) are carried on the Issuer child and its descendants such as IssuerID, IssuerName, IssuerFinancials, and SecurityDetails — not directly on IssuerDetails itself, which carries no attributes of its own.

Rules

  • MUSTWhen IssuerDetails is present, it MUST contain at least one Issuer element.[RIXML Level One Addendum v2.2 p.17] [RIXML Level One Addendum v2.3 p.12] [RIXML Level One Addendum v2.3.1 p.12] [RIXML Level One Addendum v2.5 p.12]
  • SHOULDIssuerDetails is optional within Context and SHOULD be omitted entirely when the research product does not discuss specific issuing entities, rather than included as an empty container.[RIXML Research Data Dictionary v2.5.1 p.46] [RIXML Level One Addendum v2.5 p.12] [RIXML Level One Addendum v2.3.1 p.12]

Relationships

Where It Fits

Canonical Path

Research/Product/Context/IssuerDetails

Children

Definition

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

Attributes

No attributes defined for this element

Children

Issuer(complex)1..unbounded
requiredSince 2.1

Example

<IssuerDetails>
  <Issuer> ... </Issuer>
</IssuerDetails>

Version History

Unchanged since introduction in RIXML 2.1

IssuerDetails has been a stable part of the Context package since at least RIXML 2.1, with consistent semantics across 2.2, 2.3, 2.3.1, 2.4, and 2.5: an optional container that, when present, must hold one or more Issuer elements (sources: user-guide-2.1 p.30, level-one-2.2 p.17, level-one-2.3 p.12, level-one-2.3.1 p.12, data-dictionary-2.4 p.43, data-dictionary-2.5.1 p.46, level-one-2.5 p.12). No structural changes to the element itself are recorded across these versions; evolution has occurred within its Issuer child (for example expansion of IssuerFinancials and SecurityDetails content).

Business Rules

MUST

When IssuerDetails element is present, it must contain at least one Issuer element

validationconditional-requirement

Semantic Relationships

Constrains1 relationship

IssuerMUST

If IssuerDetails element is present, this element must contain at least one Issuer element

RIXML Level One Addendum v2.5, p.12Research.Product.Context.IssuerDetails