Index

Overview

Index references a market, industry, or country index that is mentioned, analysed, or used as a benchmark within a research product. It provides a structured way to associate research content with specific indices so that consumers can filter, route, and contextualise content relative to standard market benchmarks. The element supports both standard index identification (via IndexID child elements) and descriptive metadata (via type and displayName attributes), and it can aggregate additional context through Country, Region, SectorIndustry, Weighting and Rating children.

Usage

Index appears as an optional child of ProductClassifications in RIXML 2.x, with multiple instances allowed when a research product references several indices (sources: user-guide-2.1 p.31, user-guide-2.3.1 p.32, data-dictionary-2.5.1 p.48). In the v3 draft it moves under an IndexList container, where instances are required when the container is present and multiples remain allowed [data-dictionary-v3-draft p.48]. Key attributes: - A type attribute (drawn from IndexTypeEnum) classifies the index as market, industry, or country. - A displayName attribute provides a presentation-friendly label. - A name attribute (using IndexEnum) plus PublisherDefinedValue was the original identification mechanism in RIXML 2.1 but is deprecated from RIXML 2.3 onward in favour of IndexID child elements, which support multiple identifier schemes (sources: user-guide-2.1 p.31, user-guide-2.3 p.32, data-dictionary-2.4 p.45, data-dictionary-2.5.1 p.48). Typical usage is to include one Index per referenced benchmark, populate one or more IndexID children with standard identifiers, and add Country, Region, SectorIndustry, Weighting or Rating children where they add useful context for downstream filtering and performance attribution. Note that "Index" also appears elsewhere in the schema as an enumeration value — for example as a Index value for index-tracking instruments such as index funds and ETFs [data-dictionary-2.4 p.106], and as a Index value on ProductFocus to indicate research whose analytical focus is index methodology or performance [data-dictionary-2.4 p.81]. These uses are distinct from the Index element itself.

Rules

• SHOULDPublishers should identify indices using IndexID child elements rather than the deprecated name and PublisherDefinedValue attributes.[RIXML User Guide v2.3 p.32] [RIXML User Guide v2.3.1 p.32] [RIXML Research Data Dictionary v2.4 p.45] [RIXML Research Data Dictionary v2.5.1 p.48]
• INFORMATIVEIndex as a child of ProductClassifications is not required by RIXML Level One compliance; Level One focuses on core product categorization and does not mandate index classification. The element MAY still be included without breaking Level One compliance.[RIXML Level One Addendum v2.3.1 p.18]
• SHOULDWhen an Index element is present, the issuerType (IssuerType) attribute should be supplied wherever an identifier is associated with the topic of the report, alongside any Issuer or Security tag sets.[RIXML v3 Taxonomy Review Summary: Identifiers p.4]↗
• MUSTIn the v3 draft, Index is required within an IndexList container when indices are referenced, and multiple instances are permitted.[RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.48]↗

Relationships

• child-ofProductClassifications — In RIXML 2.x, Index is an optional child of ProductClassifications with multiples allowed.
• aggregatesIndexID — Index contains IndexID children (multiples allowed) as the preferred mechanism for identifying the index using standard identifier schemes.
• aggregatesCountry — Index can include Country children to associate the index with one or more geographic countries.
• aggregatesRegion — Index can include Region children to associate the index with one or more geographic regions.
• aggregatesSectorIndustry — Index can include SectorIndustry children to associate the index with one or more sectors or industries (renamed to Industry in the v3 draft).
• aggregatesWeighting — Index can include Weighting children to express weighting recommendations relative to the index.
• aggregatesRating — Index can include Rating children to express ratings on the index.
• typed-byIndexTypeEnum — The optional type attribute on Index takes values from IndexTypeEnum (market, industry, or country).
• typed-byIndexEnum — In RIXML 2.1, the (now deprecated) name attribute on Index was constrained to values from IndexEnum.