TradingExchange
RIXML 2.5 Element
Identifies the exchange where a security trades, with an optional tradingExchangeCode attribute that uses ISO 10383 Market Identifier Codes (MIC) for precise exchange identification.
Usage
Used within SecurityID elements to specify trading venue. Optional tradingExchangeCode provides standardized exchange identification using four-character MIC codes.
Business Context
Important for security identification and trading context, enabling research consumers to understand where securities can be accessed and traded, supporting execution and market access decisions.
Specification Guide
Overview
TradingExchange identifies the financial exchange or trading venue where a security is traded. It appears inside SecurityID to qualify a security identifier with the venue on which the security is listed, which is essential when the same ticker symbol can refer to different securities on different exchanges. Since RIXML 2.3, the element carries an optional tradingExchangeCode attribute that accepts a four-character ISO 10383 Market Identifier Code (MIC) for standardized exchange identification (sources: release-notes-2.3 p.2, best-practices-guide p.11).
Usage
Use TradingExchange as an optional child of SecurityID to record where the referenced security trades. The element's text content typically carries the human-readable exchange name (e.g. NASDAQ, NYSE), while the optional tradingExchangeCode attribute carries the ISO 10383 MIC for machine-readable, unambiguous venue identification (sources: data-dictionary-2.5.1 p.64, user-guide-2.3 p.44).
It is particularly valuable when:
- The security is dual- or multi-listed and the ticker alone is ambiguous.
- Downstream consumers need to route, match or reconcile securities against market data systems.
- Regulatory or settlement context depends on the specific venue.
Pair TradingExchange with an exchange-scoped identifier (such as a ticker captured via the appropriate IssuerSecurityIDTypeEnum value) so that the combination uniquely resolves the security [best-practices-guide p.16].
Rules
- SHOULDWhen a security is exchange-traded and ticker-based identifiers are used, include TradingExchange inside SecurityID so the security can be disambiguated across venues.[Industry Report (Advanced) Sample v2.4]↗ [Company Report (Advanced) Sample v2.4]↗ [Best Practices for Publishing RIXML p.16]
- SHOULDWhen populating tradingExchangeCode, use a four-character ISO 10383 Market Identifier Code (MIC) rather than a proprietary or free-text exchange code.[RIXML Release Notes v2.3 p.2] [RIXML Research Data Dictionary v2.5.1 p.64] [RIXML User Guide v2.3 p.44]
- MAYTradingExchange is optional within SecurityID; it may be omitted when venue information is not relevant (for example, for OTC instruments or where the identifier type is already globally unique such as ISIN or CUSIP).[RIXML Research Data Dictionary v2.4 p.61] [Company Report (Advanced) Sample v2.4]↗
Relationships
- child-ofSecurityID — TradingExchange is an optional child of SecurityID that qualifies the identifier value with the venue on which the security trades.
- carriesTradingExchange.tradingExchangeCode — TradingExchange carries the optional tradingExchangeCode attribute (introduced in RIXML 2.3) which provides the ISO 10383 MIC for the venue.
- typed-byISO10383ExchangeType — The tradingExchangeCode attribute is constrained by ISO10383ExchangeType, which enforces the four-uppercase-character MIC format.
- describesSecurity — Through its enclosing SecurityID, TradingExchange contributes venue context to the description of a Security.
Where It Fits
Canonical Path
Definition
| Type | |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
| Content Model | Text content (string) |
Attributes
ISO 10383 Market Identifier Code (MIC) used to precisely identify the exchange upon which the security trades. optionalSince 2.3 |
Children
Contains text content (type: string)
This element's value is its text content. Attributes provide additional context.
Example
<TradingExchange>ABC-123</TradingExchange>Version History
Unchanged since introduction in RIXML 2.3
TradingExchange has existed since the early 2.x line as a free-text container for the exchange name on which a security trades. In RIXML 2.3 it was extended with the optional tradingExchangeCode attribute, typed by ISO10383ExchangeType, to carry an ISO 10383 Market Identifier Code (four uppercase alpha characters). This change addressed the well-known ambiguity of ticker symbols, which are only unique within a single exchange (sources: release-notes-2.3 p.2, best-practices-guide p.11, best-practices-guide p.16). The element and its attribute are unchanged in structure through versions 2.4 and 2.5 (sources: data-dictionary-2.4 p.61, data-dictionary-2.5.1 p.64).