Expertise
RIXML 2.5 Element
Defines the areas of specialized knowledge and research capabilities offered by the publishing organization. Focuses on the institutional expertise profile rather than describing the specific content of individual research products.
Usage
Optional element within Organization. Use to describe the publisher's general research capabilities across languages, specialties, asset classes, regions, and other dimensions. Helps consumers understand the organization's overall research scope.
Business Context
Important for research provider evaluation and vendor selection processes. Enables institutional clients to assess whether a research provider's expertise aligns with their coverage needs and investment focus areas.
Specification Guide
Overview
Expertise is a container element that profiles the specialized knowledge areas and research capabilities of a research-publishing Organization. Unlike ProductClassifications, which classifies the content payload of a specific research product, Expertise describes the institutional competencies of the publisher itself — the languages it publishes in, the specialties it practices, the asset classes and security types it covers, the geographic regions and sectors it follows, and the analytical disciplines it applies (sources: data-dictionary-2.4 p.26, release-notes-2.4 p.17, data-dictionary-2.5.1 p.26). It exists primarily to support vendor selection, content routing, and capability discovery, enabling consumers to match research needs to provider strengths.
Usage
Expertise appears as an optional child of Organization with cardinality 0..1 [RIXML Release Notes v2.4 p.17]. It groups a set of optional child containers, each describing one dimension of organizational capability: - PublishingLanguages — languages in which the organization publishes - Specialties — analytical or methodological specialties - AssetClasses — asset classes covered - AssetTypes — finer-grained asset types - SecurityTypes — types of securities covered - Regions — geographic regions covered - Countries — countries covered - SectorIndustries — sectors and industries followed - Disciplines — analytical disciplines applied All children are optional, but when Expertise is included it should carry at least one populated child to be meaningful (sources: data-dictionary-interactions-2.0 p.17, example-company-advanced-2.4, data-dictionary-2.4 p.26). Use it to characterise the publisher's overall scope, not to describe the subject matter of a single research product.
Rules
- MUSTExpertise describes the expertise areas of the research-publishing Organization and should not be used to describe the content payload of a product; use ProductClassifications for content classification.[RIXML Release Notes v2.4 p.18] [RIXML Research Data Dictionary v2.5.1 p.26]
- SHOULDWhen Expertise is included, it should populate the relevant child containers (PublishingLanguages, Specialties, AssetClasses, Disciplines, etc.) so that consumers can meaningfully assess the organization's capabilities.[Company Report (Advanced) Sample v2.4]↗ [Morning Call Report (Advanced) Sample v2.4]↗ [Roster Updates Sample v2.4]↗
- INFORMATIVEPublisher-level tags such as Expertise should be conceptually distinguished from document-level metadata; the 2.4 review noted that mixing publisher-wide expertise into every document risks consumers misinterpreting omissions as capability losses, and a future direction may move publisher-specific tags into side-car schemas.[RIXML Quarterly Update 2012 Q4 p.2]↗
Relationships
- child-ofOrganization — Expertise is an optional child of Organization (cardinality 0..1) and qualifies that organization by describing its institutional capabilities and coverage areas.
- contrasts-withProductClassifications — Expertise describes the publisher's areas of expertise, whereas ProductClassifications classifies the content of a specific research product. The two should not be conflated.
- containsPublishingLanguages — Expertise may contain PublishingLanguages to declare the languages in which the organization publishes research.
- containsSpecialties — Expertise may contain Specialties, whose Specialty entries narrow the organization's expertise to specific analytical or methodological focus areas.
- containsAssetClasses — Expertise may contain AssetClasses to indicate which asset classes the organization covers.
- containsAssetTypes — Expertise may contain AssetTypes to indicate finer-grained asset-type coverage.
- containsSecurityTypes — Expertise may contain SecurityTypes to indicate the types of securities covered.
- containsRegions — Expertise may contain Regions to indicate geographic regional coverage.
- containsCountries — Expertise may contain Countries to indicate country-level coverage.
- containsSectorIndustries — Expertise may contain SectorIndustries to indicate sector and industry coverage.
- containsDisciplines — Expertise may contain Disciplines to indicate analytical disciplines applied by the organization.
Where It Fits
Definition
| Type | |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
No attributes defined for this element
Children
PublishingLanguages(complex)0..1 |
optionalSince 2.4 |
Specialties(complex)0..1 |
optionalSince 2.4 |
AssetClasses(complex)0..1 |
optionalSince 2.4 |
AssetTypes(complex)0..1 |
optionalSince 2.4 |
SecurityTypes(complex)0..1 |
optionalSince 2.4 |
Regions(complex)0..1 |
optionalSince 2.4 |
Countries(complex)0..1 |
optionalSince 2.4 |
SectorIndustries(complex)0..1 |
optionalSince 2.4 |
Disciplines(complex)0..1 |
optionalSince 2.4 |
Example
<Expertise />Version History
Unchanged since introduction in RIXML 2.4
2.0 — An Expertise-style container of organizational capability child elements is documented as an optional element under Organization, grouping PublishingLanguages, Specialties, AssetClasses, AssetTypes, SecurityTypes, Regions, Countries, SectorIndustries, and Disciplines [RIXML Interactions Data Dictionary v2.0 p.17]. 2.4 — Release notes describe Expertise as a newly emphasised child of Organization, explicitly framed as a publisher-capability profile distinct from product content (source: release-notes-2.4, p.17–18). The Q4 2012 review flagged a design concern: because Expertise currently travels on every document, consumers may misread omissions as the publisher withdrawing capability. The committee discussed eventually splitting publisher-level from document-level tagging via side-car schemas [RIXML Quarterly Update 2012 Q4 p.2]↗. 2.5 — Expertise is retained unchanged in semantics in the 2.5.1 data dictionary; its role as an organization-level capability profile is reaffirmed [RIXML Research Data Dictionary v2.5.1 p.26]. Globalization-focused release notes highlight PublishingLanguages within Expertise as the mechanism for declaring multilingual capability [RIXML Release Notes v2.5 p.24]. 3.0 (draft) — The element is slated to be replaced by a streamlined Specialties element to give a cleaner representation of individual specialisations (sources: meeting-2025-01 p.35, meeting-2025-06 p.22). Implementers tracking the v3 draft should expect Expertise to be removed in favour of Specialties.
Semantic Relationships
Contrasts With1 relationship
Expertise element describes the research publisher's areas of expertise rather than classifying the specific content payload of individual products
RIXML Research Data Dictionary v2.5.1, p.26— Expertise
Qualifies1 relationship
Publishing languages can be specified as forms of organizational expertise to indicate multilingual capabilities
RIXML Release Notes v2.5, p.24— Toward improved globalization