Weighting

Overview

Weighting expresses a portfolio allocation recommendation — typically overweight, underweight, or equal-weight — for an investment entity such as a country, region, asset class, asset type, sector/industry, security type, or index. It carries the research provider's relative positioning guidance versus a benchmark, together with optional temporal context (time frame, prior vs. current) so that recipients can interpret allocation changes over time. The element's value space is governed by the required weighting attribute, which draws from WeightingEnum. Optional attributes refine the recommendation with timing (timeFrame, priorCurrent) and publisher-specific extensions.

Usage

Use Weighting wherever the research conveys a benchmark-relative allocation view. Across v2.x it appears as a repeatable child of allocation-bearing entities including Country, Region, AssetClass, AssetType, SecurityType, SectorIndustry, Security, Issuer, and (from 2.1 onwards) Index [RIXML Release Notes v2.1 p.3]. The weighting attribute is required; typical values include OverWeight, UnderWeight, and EqualWeight from WeightingEnum. Optional attributes provide: - timeFrame — short-term vs. long-term scope, drawn from TermEnum in v3. - priorCurrent — flags whether the weighting represents the current recommendation or a prior one, supporting before/after comparisons via PriorCurrentTypeEnum. - A publisher-defined value attribute and (in v2.4+ and v3) an optional Description child for human-readable context. Multiple Weighting instances may appear under the same parent to express, for example, both a prior and a current recommendation, or differing short- and long-term views [RIXML Research Data Dictionary v2.4 p.63].

Rules

• MUSTThe weighting attribute is required and must contain a value from WeightingEnum (typically OverWeight, UnderWeight, or EqualWeight).[RIXML Research Data Dictionary v2.5.1 p.66] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.71]↗
• SHOULDModel portfolio research products (identified by ModelPortfolio) should include security-level Weighting entries communicating allocation versus the benchmark.[RIXML Research Data Dictionary v2.5.1 p.130]
• INFORMATIVEWeighting as a child of Country, Region, Issuer, Security, AssetClass, or AssetType is not required by RIXML Level One compliance — Level One implementations may omit it to reduce complexity, but inclusion does not break the full schema.[RIXML Level One Addendum v2.2 p.25] [RIXML Level One Addendum v2.3.1 p.12] [RIXML Level One Addendum v2.3.1 p.14] [RIXML Level One Addendum v2.3.1 p.15] [RIXML Level One Addendum v2.5 p.20]
• SHOULDIn RIXML 3.0, individual Weighting children are grouped under a WeightingList container, aligning with the standardised *List container pattern adopted across other repeating elements such as Rating and ProductCategory.[RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.69]↗ [RIXML All-Member Meeting Winter 2024 p.21]↗

Relationships

• constrainsWeightingEnum — The required weighting attribute draws its value from WeightingEnum (OverWeight, UnderWeight, EqualWeight, etc.).
• qualifiesTermEnum — TermEnum qualifies Weighting via the timeFrame attribute, allowing publishers to indicate whether a recommendation is short-term or long-term in nature.
• qualifiesPriorCurrentTypeEnum — priorCurrent uses PriorCurrentTypeEnum to flag whether a weighting represents the current or a prior recommendation, supporting change tracking.
• contained-byIndex — From RIXML 2.1 onwards, Weighting may appear as a child of Index to express benchmark-relative or index-based positioning.
• contained-byCountry — Weighting may appear under Country to express country-level allocation recommendations (not required in Level One).
• contained-byRegion — Weighting may appear under Region to express regional allocation recommendations (not required in Level One).
• contained-byAssetClass — Weighting may appear under AssetClass to express asset-class allocation recommendations.
• contained-byAssetType — Weighting may appear under AssetType to express asset-type allocation recommendations.
• contained-bySectorIndustry — Weighting may appear under SectorIndustry to express sector- or industry-level allocation recommendations.
• contained-bySecurity — Weighting may appear under Security to express security-level allocation views, particularly within model-portfolio products.
• related-toIssuer — The weightingAction attribute on Issuer signals that the publisher is changing the issuer's weighting; the actual values are carried by Weighting children.