SecurityID

Overview

SecurityID provides a standardised, machine-readable identifier for a financial security within an RIXML research product. It carries the identification scheme (e.g. CUSIP, ISIN, RIC, Bloomberg, ExchangeTicker, DUNS) in idType and the actual symbol value in idValue, optionally qualified by trading venue context. SecurityID is the fundamental anchor that links research content to market data feeds, trading platforms, and reference databases, allowing consumers to unambiguously map a report to specific instruments in their own systems (sources: data-dictionary-2.5.1 p.59, user-guide-2.3.1 p.41).

Usage

In RIXML 2.x, SecurityID appears within Security (under the Research → Product → Context → IssuerDetails → Issuer → SecurityDetails → Security path). It has a cardinality of one-or-more: every Security must carry at least one SecurityID, and publishers are encouraged to include several instances using different schemes (e.g. CUSIP plus RIC plus Bloomberg) to maximise cross-vendor matching certainty (sources: level-one-2.5 p.14, data-dictionary-2.5.1 p.59). Required attributes are idType (a value from IssuerSecurityIDTypeEnum) and idValue (the symbol itself). Optional attributes include publisherDefinedValue (used when idType is PublisherDefined) and tradingCountryCode for jurisdictional context. A child TradingExchange element may be included to specify the venue [user-guide-2.2 p.40]. SecurityID is required for company-focused research where a specific instrument is discussed, and is typically omitted for pure macro, economic, or industry-overview reports that do not reference individual securities (source: implementation-guide-2.5.1 p.17, getting-started-guide p.12). SecurityID values are also referenced from other parts of the document — for example IssuerSecurityID inside legal disclosures uses securityID to point at a SecurityID declared elsewhere in the product metadata [data-dictionary-2.5.1 p.67]. In the v3 draft, the structural location changes: SecurityID is housed within a SecurityIDList container, tradingCountryCode is renamed marketCountryCode, publisherDefinedValue becomes idTypePublisherDefinedValue, and an optional MarketID child aggregation is added [data-dictionary-v3-draft p.54].

Rules

• MUSTEach Security element must contain at least one SecurityID, and that SecurityID must carry both idType (from IssuerSecurityIDTypeEnum) and idValue.[RIXML Level One Addendum v2.2 p.19] [RIXML Level One Addendum v2.3 p.14] [RIXML Level One Addendum v2.3.1 p.14] [RIXML Level One Addendum v2.5 p.14]
• SHOULDPublishers should include multiple SecurityID instances using different symbol schemes (e.g. CUSIP, RIC, Bloomberg) so consumers can match the security regardless of which vendor symbology they use.[RIXML Level One Addendum v2.4 p.14] [RIXML Level One Addendum v2.5 p.14] [RIXML Research Data Dictionary v2.5.1 p.59]
• MUSTWhen idType is set to PublisherDefined, the publisherDefinedValue attribute must be supplied to describe the custom identifier scheme.[RIXML User Guide v2.2 p.40]
• MUSTBloomberg symbols carried in idValue must use an @ separator between ticker and country/exchange designator (e.g. IBM@US, not IBM US) and must be supplied exactly with correct case.[RIXML Research Data Dictionary v2.5.1 p.16]
• MUSTReuters RIC symbols in idValue must be case-sensitive, must use a period separator between root and exchange code (e.g. IBM.N), and may omit the exchange designation only for U.S. issues.[RIXML Research Data Dictionary v2.5.1 p.16]
• SHOULDSecurityID should be accompanied by a TradingExchange child (and/or tradingCountryCode) when the security trades on a specific venue, in order to disambiguate cross-listed or similarly named instruments.[Company Report (Advanced) Sample v2.4]↗ [Morning Call Report (Advanced) Sample v2.4]↗ [Industry Report (Basic) Sample v2.4]↗
• SHOULDSecurityID is typically included only when the product discusses specific securities; pure economic or company-agnostic research need not include it.[RIXML Implementation Guide v2.5.1 p.17] [RIXML Getting Started Guide p.12]
• SHOULDIn the v3 draft, when RelatedProduct uses a relationship type that requires security context (e.g. Model, IndustryReport, InitiationReport), a SecurityID should be included to identify the related security.[RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.64]↗

Relationships

• child-ofSecurity — SecurityID is a required child of Security with cardinality 1..unbounded; every Security must declare at least one identifier.
• qualified-byTradingExchange — An optional child TradingExchange qualifies the SecurityID by naming the venue where the security trades, providing market context to the identifier.
• constrained-byIssuerSecurityIDTypeEnum — idType is constrained to values from IssuerSecurityIDTypeEnum, which enumerates the supported identifier schemes (CUSIP, ISIN, RIC, Bloomberg, ExchangeTicker, DUNS, PublisherDefined, etc.).
• referenced-byIssuerSecurityID — IssuerSecurityID (used inside legal disclosures) references a SecurityID declared elsewhere in the same product via securityID, linking disclosures to the specific instruments they concern.
• constrained-byProductFocus — Whether SecurityID is required, recommended, or optional depends on the report's ProductFocus: company-focused products require it, industry- or macro-focused products typically do not.