Specialty

Overview

Specialty identifies a specific area of analytical or research specialisation — such as fundamental analysis, quantitative methods, ESG, technical analysis, or distressed situations — associated with a research-publishing organisation, a specific product, or an analyst's coverage. It is an enumeration-based element: each occurrence carries a required specialty attribute whose value is drawn from SpecialtyEnum, providing a standardised vocabulary for declaring expertise across the research ecosystem (sources: data-dictionary-2.4 p.30, release-notes-2.4 p.18, v3-enumlist-set5-subject-specialty p.1). The element bridges organisational capability declarations and content classification: it describes both *what* methodologies a publisher offers and *which* of those methodologies were applied to a given research product [release-notes-2.4 p.18].

Usage

Specialty appears in multiple contexts across RIXML versions: - Organisation/publisher profiling — as a child of a Specialties container (typically reached via Expertise on an Organization) to declare the publisher's areas of expertise. Cardinality is 1..n inside the container, allowing organisations to enumerate diverse capabilities [release-notes-2.4 p.18]. - Product classification — as an optional child of ProductClassifications with 0..n cardinality, indicating which organisational specialty was applied in creating the parent Product [release-notes-2.4 p.19]. This usage was added in RIXML 2.4. - Coverage updates — from RIXML 2.5 onward, Specialty is a valid choice within CoveredEntitiesType inside CoveragePairing, so a CoverageUpdate can declare that an analyst or firm covers a particular specialty (e.g. small-cap equity, ESG research). Cardinality is 0..unbounded within CoveredEntities [release-notes-2.5 p.29]. In all contexts the specialty attribute is required and must hold a SpecialtyEnum value.

Rules

• MUSTEach Specialty instance MUST carry a specialty attribute whose value is drawn from SpecialtyEnum.[RIXML Research Data Dictionary v2.4 p.30] [RIXML Release Notes v2.4 p.18] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.80]↗
• MAYPublishers MAY include Specialty elements under ProductClassifications (cardinality 0..n) to indicate which organisational specialty was applied in creating the parent Product.[RIXML Release Notes v2.4 p.19] [RIXML Quarterly Update 2012 Q4 p.3]↗
• MAYFrom RIXML 2.5, Specialty MAY appear within CoveredEntities (via CoveredEntitiesType) to declare specialties as a covered entity in CoverageUpdate messages, with cardinality 0..unbounded.[RIXML Release Notes v2.5 p.29]
• SHOULDWhen used to profile an organisation, at least one Specialty SHOULD appear inside the Specialties container (1..n cardinality in that context).[RIXML Release Notes v2.4 p.18]

Relationships

• contained-bySpecialties — Specialty is the repeating child of the Specialties container used to enumerate an organisation's areas of expertise.
• narrowsExpertise — Specialty classifications provide specific focus areas within the broader Expertise description of a research organisation.
• qualifiesProductClassifications — Inside ProductClassifications, Specialty tags a Product with the organisational specialty applied in its creation.
• extendsCoveredEntitiesType — RIXML 2.5 added Specialty as a choice option inside CoveredEntitiesType, broadening coverage-update messages to track specialties as covered entities alongside AssetClass, SecurityType, Issuer, Security, SectorIndustry, Region, Country, Index, and Discipline.
• constrained-bySpecialtyEnum — The value space of the required specialty attribute is SpecialtyEnum.
• contrasts-withSubject — Specialty is intended to describe author/firm expertise, whereas Subject describes the actual content topics of a research product. The distinction was clarified in v3 taxonomy discussions.