AssetClasses
RIXML 2.5 Element
Container element for one or more individual AssetClass elements.
Container element for one or more individual AssetClass elements..
Specification Guide
Overview
AssetClasses is a container element that groups one or more AssetClass children to declare the broad investment categories — such as equity, fixed income, currencies, commodities, and real estate — in which an organization has research expertise. It exists to provide a structured aggregation point for asset-class classifications within an organization's capability profile, enabling consumers to identify and filter publishers by the asset classes they cover (sources: data-dictionary-2.4 p.27, example-company-advanced-2.4, example-rosterupdates-2.4).
Usage
AssetClasses appears as an optional child of Expertise and, when present, must contain at least one AssetClass child. Use it to declare the asset-class coverage scope of a research organization — typically as part of source/roster metadata that describes provider capabilities. Omit the container entirely if no asset-class expertise is being declared rather than including it empty.
Rules
- MUSTWhen AssetClasses is present, it must contain at least one AssetClass child element.[RIXML Research Data Dictionary v2.4 p.27] [Company Report (Advanced) Sample v2.4]↗ [Roster Updates Sample v2.4]↗
Relationships
- child-ofExpertise — AssetClasses is an optional child of Expertise, narrowing the declared expertise to specific asset categories.
- containsAssetClass — Aggregates one or more AssetClass elements, each identifying a single investment category.
Where It Fits
Canonical Path
Children
Definition
| Type | |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
No attributes defined for this element
Children
AssetClass(complex)1..unbounded |
requiredSince 2.4 |
Example
<AssetClasses>
<AssetClass> ... </AssetClass>
</AssetClasses>Version History
Unchanged since introduction in RIXML 2.4
Documented in the RIXML 2.4 data dictionary as a container within Expertise. No version-specific changes are recorded in the gathered sources.