RIXML Documentation

AssetType

RIXML 2.5 Element

Level OneRequired

Required element specifying security's asset type using assetType attribute from AssetTypeEnum. In Level One, serves as container for the attribute value with Rating and Weighting children excluded.

Indicates the asset type. Typically used in conjunction with AssetClass and SecurityType. Can be attached to a Context element or to a Security element. For equities, examples include stocks, convertibles, warrants and preferred stocks. For bonds, examples include the major fixed income sectors typically used in major fixed income index benchmarks. These include U.S. Treasuries, Corporate High Yield and Municipals, among others.

Usage

Required element within Security, appearing exactly once. Must have assetType attribute with value from enumerated list. Acts primarily as attribute container.

Business Context

Provides detailed investment instrument categorization beyond asset class, supporting precise portfolio analysis and research filtering by specific security characteristics.

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

Specification Guide

Overview

AssetType provides granular classification of a financial instrument within a broader asset class, such as distinguishing stocks, convertibles, warrants, and preferred stocks within equities, or U.S. Treasuries, Corporate High Yield, and Municipals within fixed income. It works alongside AssetClass and SecurityType to form a complete taxonomy for securities and research focus areas, and supports publisher-defined extensions when the standard enumeration is insufficient (sources: data-dictionary-2.4 p.53, data-dictionary-2.5.1 p.56, user-guide-2.3.1 p.39).

Usage

AssetType appears most commonly as a child of Security (within SecurityDetails), where it is required exactly once, and may also be used inside Context / ProductClassifications to classify the research focus itself (sources: data-dictionary-2.4 p.53, user-guide-2.2 p.38). The required assetType attribute carries a value from AssetTypeEnum (e.g. Stock, Convertible, USTreasuries, CorporateHighYield). The optional publisherDefinedValue is used together with the enum value PublisherDefined to convey a custom type, and the optional weightingAction tracks publisher changes to the asset-type weighting [RIXML User Guide v2.2 p.38]. In full-schema usage the element may carry Rating and Weighting children to express ratings or weightings scoped to the asset type. In RIXML Level One the element is reduced to a pure container for the assetType attribute and these children are not used (sources: level-one-2.2 p.20, level-one-2.5 p.15). Typical pattern: - Pair AssetClass (broad bucket, e.g. Equity) with AssetType (narrower bucket, e.g. Stock) and optionally SecurityType for instrument-level detail. - For specialised fixed-income research, AssetType is the key discriminator driving credit, duration, and sector workflows [RIXML Research Data Dictionary v2.5.1 p.56].

Rules

  • MUSTEach Security element must contain exactly one AssetType child carrying a required assetType attribute valued from AssetTypeEnum.[RIXML Level One Addendum v2.2 p.21] [RIXML Level One Addendum v2.3 p.15] [RIXML Level One Addendum v2.3.1 p.15] [RIXML Level One Addendum v2.5 p.15] [RIXML Research Data Dictionary v2.5.1 p.56]
  • MUSTWhen assetType is set to PublisherDefined, the publisherDefinedValue attribute must be populated with a description of the custom asset type.[RIXML User Guide v2.2 p.38] [RIXML Research Data Dictionary v2.5.1 p.56]
  • SHOULDWhen classifying securities, both AssetClass and AssetType should be provided to form a complete hierarchical classification (e.g. Equity / Stock).[Company Report (Basic) Sample v2.4] [Industry Report (Basic) Sample v2.4] [Morning Call Report (Basic) Sample v2.4] [RIXML Level One Addendum v2.3.1 p.15]
  • INFORMATIVEUnder RIXML Level One, Rating and Weighting are not required as children of AssetType; the element functions as a pure container for the assetType attribute.[RIXML Level One Addendum v2.2 p.20] [RIXML Level One Addendum v2.3 p.15] [RIXML Level One Addendum v2.3.1 p.15] [RIXML Level One Addendum v2.5 p.15]
  • INFORMATIVEUnder RIXML Level One, AssetType as a child of ProductClassifications is not required, since asset-type information is conveyed at the security level.[RIXML Level One Addendum v2.3.1 p.18]

Relationships

Where It Fits

Definition

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

Attributes

assetTypeAssetTypeEnum

Indicates the asset type.

requiredSince 2.1

For specifying other IM systems.

optionalSince 2.1
weightingActionWeightingActionEnum

Highlights an action taken by the publisher. Indicates that the publisher is changing the weighting of the security type.

optionalSince 2.1

Children

Rating(complex)0..unbounded
optionalSince 2.1
Weighting(complex)0..unbounded
optionalSince 2.1

Example

<AssetType assetType="Value" />

Version History

Unchanged since introduction in RIXML 2.1

AssetType is present from at least RIXML 2.2 onward and has remained structurally stable through 2.5. Across 2.2–2.5 the element consistently requires the assetType attribute, with optional publisherDefinedValue and weightingAction, and optional Rating and Weighting children (sources: user-guide-2.2 p.38, user-guide-2.3.1 p.39, data-dictionary-2.5.1 p.56). Level One profiles from 2.2 through 2.5 consistently treat AssetType as a simple attribute container and drop Rating and Weighting children; Level One 2.3.1 additionally notes that the element is not required as a child of ProductClassifications (sources: level-one-2.2 p.20, level-one-2.3 p.15, level-one-2.3.1 p.15, level-one-2.3.1 p.18, level-one-2.5 p.15). The 2012-Q2 schema build-out work refined the AssetTypeEnum value list, settling on a curated set of intermediate categories vetted for publisher and consumer utility [RIXML Quarterly Update 2012 Q2 p.3]. For RIXML v3.0, working-group discussion proposes consolidating AssetClass, AssetType and SecurityType into a single hierarchical asset-class taxonomy modelled on the sector/industry list, which would supersede the separate AssetType element (sources: meeting-2024-spring p.23, meeting-v3-key-changes p.1).

Business Rules

MUST

Security element must contain single AssetType element that acts as container for the assetType attribute

validationrequired-element
MUST

Level One compliance excludes Rating and Weighting elements as children of AssetType

validationlevel-one-complianceexclusion

Design Decisions

In Level One, the AssetType element acts merely as a container for the assetType attribute rather than supporting child elements

To simplify the AssetType structure by removing Rating and Weighting child elements for Level One compliance

RIXML Level One Addendum v2.5, p.15

Semantic Relationships

Qualifies2 relationships

AssetClassSHOULD

Asset class works in conjunction with asset type to provide comprehensive asset classification

RIXML Research Data Dictionary v2.5.1, p.56AssetClass

SecurityTypeSHOULD

Asset type works in conjunction with security type to provide comprehensive asset classification

RIXML Research Data Dictionary v2.5.1, p.56AssetType

Requires1 relationship

Publisher-defined value is used when asset type value is set to PublisherDefined to specify custom asset types

RIXML Research Data Dictionary v2.5.1, p.56Elements and Attributes

Constrains1 relationship

SecurityMUST

The Security element must contain a single AssetType element

RIXML Level One Addendum v2.5, p.15Research.Product.Context.IssuerDetails.Issuer.SecurityDetails.Security.AssetType