Subject
RIXML 2.5 Element
Element indicating research subject or topic using required subjectValue attribute from SubjectEnum. Optional publisherDefinedValue attribute holds custom subjects when subjectValue is 'PublisherDefined'.
Strongly recommended. Indicates the subject of the product. There is a standard set of subjects defined by RIXML including market opening comments, accounting and tax policy, and earnings surprise. If these do not fully represent the subject, the publisher may use a publisher defined Subject value.
Usage
Optional element within ProductClassifications, can appear zero or more times. Must have subjectValue attribute, publisherDefinedValue required for custom subjects.
Business Context
Critical for research topic identification and filtering, helping investment professionals locate content by specific subjects like earnings reviews, policy changes, or market commentary.
Specification Guide
Overview
Subject is a classification element that identifies the primary topics, themes, or triggering events addressed by a research product, drawn from a standardised vocabulary (SubjectEnum) with a publisher-defined extension mechanism. It provides granular topical categorisation that complements broader classifiers such as Discipline, AssetClass, and ProductFocus, enabling event-driven discovery (e.g. earnings reviews, M&A activity, policy analysis, market commentary) and topic-based routing across research distribution workflows. The element sits within the Context package of a research product, specifically inside ProductClassifications (sources: level-one-2.2 p.25, level-one-2.5 p.19, data-dictionary-2.5.1 p.51). It is officially optional in the schema but is consistently described as *strongly recommended* across user guides and data dictionaries from v2.1 through v3.0 (sources: user-guide-2.1 p.33, user-guide-2.3 p.35, data-dictionary-2.4 p.48, data-dictionary-2.5.1 p.51, data-dictionary-v3-draft p.61).
Usage
Subject appears as a zero-or-more child of ProductClassifications, allowing a research product to carry several subject tags when its content genuinely spans multiple topics (sources: level-one-2.2 p.25, level-one-2.3.1 p.19, level-one-2.4 p.19, level-one-2.5 p.19).
Each instance requires a subjectValue drawn from SubjectEnum (e.g. MarketOpeningComments, AccountingPolicy, EarningsSurprise, MergerAcquisitionDivestiture, Politics, Event, SurveyAnalysisAndResults). When no enumerated value fits, set subjectValue to PublisherDefined and supply the custom label in publisherDefinedValue (sources: data-dictionary-2.4 p.48, level-one-2.5 p.19, user-guide-2.3.1 p.35).
A core best-practice constraint is the critical-mass principle: only tag a subject when it is substantially discussed in the report, not when it is merely mentioned in passing. The test is whether someone searching for that subject would find the report genuinely useful (sources: best-practices-guide p.24, data-dictionary-2.4 p.18, data-dictionary-2.5.1 p.18, implementation-guide-2.5.1 p.24).
Typical patterns include:
- An earnings-driven note tagged with the appropriate earnings-related subject alongside an Issuer in IssuerDetails.
- A merger note tagged with MergerAcquisitionDivestiture and multiple issuers each carrying primaryIndicator = Yes [implementation-guide-2.5.1 p.24].
- A thematic piece tagged with one or more subjects in addition to Discipline and AssetClass — these classifiers work in conjunction rather than independently [v3-taxonomy-publishing-summary p.4].
Rules
- SHOULDSubject should be included in ProductClassifications to classify the product's main topic.[RIXML User Guide v2.1 p.33] [RIXML User Guide v2.3 p.35] [RIXML Research Data Dictionary v2.4 p.48] [RIXML Research Data Dictionary v2.5.1 p.51] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.61]↗
- SHOULDApply a Subject tag only when that subject has critical mass in the report — i.e. sufficient coverage that a searcher for the topic would find the report genuinely useful. Do not tag mere mentions.[Best Practices for Publishing RIXML p.24] [RIXML Research Data Dictionary v2.4 p.18] [RIXML Research Data Dictionary v2.5.1 p.18] [RIXML Implementation Guide v2.5.1 p.24]
- MUSTEach Subject instance MUST carry a subjectValue selected from SubjectEnum.[RIXML Level One Addendum v2.2 p.25] [RIXML Level One Addendum v2.4 p.19] [RIXML Level One Addendum v2.5 p.19] [RIXML Research Data Dictionary v2.4 p.48]
- MUSTWhen subjectValue is set to
PublisherDefined, the custom subject label MUST be supplied in publisherDefinedValue.[RIXML Level One Addendum v2.2 p.25] [RIXML Level One Addendum v2.3.1 p.19] [RIXML Research Data Dictionary v2.4 p.48] [RIXML User Guide v2.3.1 p.35] - MAYMultiple Subject elements MAY be included on a single product to capture multi-themed content.[RIXML Level One Addendum v2.2 p.25] [RIXML Level One Addendum v2.5 p.19] [RIXML User Guide v2.3.1 p.35] [RIXML Research Data Dictionary v2.5.1 p.51]
- SHOULDReports providing detailed merger coverage should be tagged with MergerAcquisitionDivestiture and may carry multiple issuers with primaryIndicator set to
Yes; reports that only mention mergers in passing should not be tagged with this subject.[RIXML Implementation Guide v2.5.1 p.24]
Relationships
- child-ofProductClassifications — Subject is an optional, repeatable child of ProductClassifications within the Context package, providing topical classification alongside other classifiers in that container.
- constrained-bySubjectEnum — The required subjectValue is constrained to values in SubjectEnum, with
PublisherDefinedas the escape hatch for custom subjects. - qualifiesProductFocus — Subject qualifies ProductFocus by identifying the specific topics or triggering events that prompted the report, beyond the broader focus classification.
- complementsDiscipline — Subject works in conjunction with Discipline and AssetClass tags; discipline and research approach do not convey the topic independently and rely on Subject and asset-class tags for full classification.
- contrasts-withSpecialty — Specialty was intended to describe the author's area of expertise, whereas Subject describes the content of the research itself.
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
subjectValueSubjectEnum |
The main topic covered in the product. requiredSince 2.1 |
publisherDefinedValuestring |
For specifying other IM systems. optionalSince 2.1 |
Children
Contains text content (type: string)
This element's value is its text content. Attributes provide additional context.
Example
<Subject subjectValue="Value">ABC-123</Subject>Version History
Unchanged since introduction in RIXML 2.1
Subject is present from at least RIXML v2.1 onward, consistently positioned as an optional, repeatable child of ProductClassifications with a required subjectValue attribute drawn from SubjectEnum and an optional publisherDefinedValue extension (sources: user-guide-2.1 p.33, level-one-2.2 p.25, level-one-2.3.1 p.19, level-one-2.4 p.19, level-one-2.5 p.19).
- v2.1 – v2.5: Structurally stable. Each version reinforced the *strongly recommended* status and the critical-mass best practice was made explicit in the v2.4 and v2.5 data dictionaries (sources: data-dictionary-2.4 p.18, data-dictionary-2.5.1 p.18).
- 2012–2013 quarterly discussions: The committee discussed expanding the enumeration to ~15 standardised values and explored a spot-tagging registry that would let publishers introduce new Subject tags between formal releases, with registry lookups to avoid duplicate variants (sources: quarterly-2012-q2 p.3, quarterly-2013-q2 p.2).
- v3.0 (draft): Two notable changes are proposed. First, the ESG value is removed from SubjectEnum and superseded by a dedicated top-level ESG Dimension element to enable more granular ESG classification [meeting-2024-winter p.13]. Second, Subject is identified as a key tag that gains optional tagSource and tagConfidence attributes to support automated/AI-assisted tagging workflows, alongside Company, Industry, Region, Country, Asset Class, ESG Dimension and Search Term (sources: meeting-2023-09 pp.27,31, data-dictionary-v3-draft p.61). The draft also references a SubjectList container as the parent in v3 [data-dictionary-v3-draft p.61].
Business Rules
When Subject.Value equals PublisherDefined, the publisherDefinedValue element must be provided to specify the custom subject
When Subject subjectValue attribute has value PublisherDefined, the publisherDefinedValue attribute is used to hold the custom subject
Subject tags should only be added when the subject has critical mass in the report and would be useful for someone searching for that subject
The Subject element is strongly recommended to be included in product classifications
Reports covering mergers should use the Subject tag MergerAcquisitionDivestiture and may have multiple companies tagged with primaryIndicator set to Yes
Reports that only mention mergers in passing should not be tagged with the MergerAcquisitionDivestiture subject
Design Decisions
Subject tags should only be added when the subject has critical mass in the report
This ensures that reports returned in subject-based searches contain substantial useful information about that subject, avoiding clutter in search results
RIXML Research Data Dictionary v2.5.1, p.18
Semantic Relationships
Qualifies1 relationship
Subject identifies triggering events or topics that led to report creation, requiring critical mass presence in the report to justify inclusion, complementing the product focus classification
RIXML Research Data Dictionary v2.5.1, p.18— Subject
Requires4 relationships
Research reports analyzing survey results must use this subject tag when discussing survey findings, analysis, or respondent data
RIXML Research Data Dictionary v2.5.1, p.127— SurveyAnalysisAndResults
Research reports discussing political conditions in geographic areas must use this subject classification for political analysis content
RIXML Research Data Dictionary v2.5.1, p.127— Politics
Research reports discussing events or key points from meetings, conferences, seminars must use this subject tag
RIXML Research Data Dictionary v2.5.1, p.127— Event
The publisherDefinedValue attribute is used to hold the publisher's own subject when the subjectValue attribute has a value of PublisherDefined
RIXML Level One Addendum v2.5, p.19— Research.Product.Context.ProductClassifications.Subject