SecurityDetails

Overview

SecurityDetails is a container element that groups all information about specific securities issued by a particular issuer and discussed in a research product. It functions purely as an organisational wrapper — it carries no attributes or text content of its own — and exists to host one or more Security child elements within an Issuer context (sources: data-dictionary-2.5.1 p.54, level-one-2.5 p.13, user-guide-2.3.1 p.37). By nesting security-level data beneath the issuer that produced it, SecurityDetails preserves the issuer → security hierarchy required for accurate routing, filtering, and analytical processing of research that addresses individual financial instruments such as share classes, bond issues, or derivatives.

Usage

SecurityDetails appears within Issuer (itself a child of IssuerDetails, inside Context) and may occur zero or one times per issuer. When present, it MUST contain at least one Security element; additional Security children may follow to describe multiple instruments from the same issuer (sources: level-one-2.2 p.18, level-one-2.5 p.13). Include SecurityDetails when the research discusses specific tradable instruments — for example, equity research with target prices and ratings, fixed-income coverage of particular bond issues, or analysis of companies with multiple share classes. Omit it when the research addresses only issuer-level topics (e.g. corporate strategy, sector positioning) without instrument-level recommendations (sources: example-company-basic-2.4, data-dictionary-2.5.1 p.54). Because SecurityDetails has no attributes or direct content, all identification, classification, financial metrics, ratings, and target-price information are carried on the nested Security elements.

Rules

• MUSTWhen SecurityDetails is present, it MUST contain at least one Security child element.[RIXML Level One Addendum v2.2 p.18] [RIXML Level One Addendum v2.3 p.13] [RIXML Level One Addendum v2.3.1 p.13] [RIXML Level One Addendum v2.4 p.13] [RIXML Level One Addendum v2.5 p.13]
• SHOULDSecurityDetails itself is optional within Issuer and SHOULD be omitted entirely if no security-level information is being conveyed, rather than included as an empty container.[RIXML Level One Addendum v2.4 p.13] [RIXML Level One Addendum v2.5 p.13]

Relationships

• child-ofIssuer — SecurityDetails is an optional child of Issuer, appearing at most once and inheriting the issuer context for all nested securities.
• requiresSecurity — When present, SecurityDetails requires at least one Security child; it acts purely as a grouping wrapper for one or more Security descriptions.
• nested-inIssuerDetails — SecurityDetails sits at the path Research.Product.Context.IssuerDetails.Issuer.SecurityDetails, scoping its Security children to the parent Issuer within IssuerDetails.