Title
RIXML 2.5 Element
Required string element containing the primary headline or title of the research product. Combined with SubTitle, represents the complete headline presentation of the research piece.
This is the primary title of the product. No markup permitted.
Usage
Required as child of Content element in all Level One implementations. Contains string value representing the main title without markup, such as 'Insights on Flash Memory Prices'.
Business Context
Primary discovery and identification mechanism for research content, essential for cataloging, searching, and user interface presentation in research distribution platforms and databases.
Specification Guide
Overview
Title is a required string element that carries the primary headline of a research product, identifying the content to readers and downstream systems. Together with the optional SubTitle it forms the complete headline shown in research catalogues, search results and distribution interfaces (sources: level-one-2.2 p.14, level-one-2.4 p.9, level-one-2.5 p.9). Through v2.5 it appears as a single plain-text child of Content; alternative-language variants are carried in ContentDetailsAlternativeLanguages, and a formatted equivalent is available in TitleFormatted [RIXML Release Notes v2.5 p.24].
Usage
Title is mandatory within Content and must occur exactly once (cardinality 1..1) in the document's default language (sources: level-one-2.4 p.9, release-notes-2.5 p.24, getting-started-guide p.8). It contains a plain text string with no embedded markup — when HTML formatting is required, publishers should additionally supply TitleFormatted alongside the plain Title so that consumers requiring plain text and those rendering formatted content are both supported (source: data-dictionary-2.5.1, p.37; release-notes-2.4, p.20).
From v2.5 onward, additional language variants are supplied by placing alternative Title elements inside ContentDetailsAlternativeLanguages under ContentDetails [RIXML Release Notes v2.5 p.24]. The language attribute identifies the language of each variant.
Authors should write descriptive titles that clearly communicate the report's focus (e.g. company or industry), the specific subject, and the report's main message — for example "Company Update – XYZ Corp. – Downgraded on Worse-than-Expected Results" — rather than relying on cryptic or purely creative headlines that obscure relevance [Best Practices for Publishing RIXML p.19].
In the v3.0 draft, Title is repositioned as a repeatable child of a TitleList container so multiple variants can coexist, each distinguished by language, an audienceType attribute, an includesFormatCoding flag and a primaryIndicator marking the default variant (sources: data-dictionary-v3-draft p.24, meeting-2023-06 p.25, p.29).
Rules
- MUSTTitle is mandatory and must appear exactly once within Content in the document's default language.[RIXML Level One Addendum v2.4 p.9] [RIXML Release Notes v2.5 p.24] [RIXML Getting Started Guide p.13]
- MUSTTitle must not contain markup; formatted variants of the headline are carried in TitleFormatted.[RIXML Release Notes v2.5 p.24] [RIXML Research Data Dictionary v2.5.1 p.37]
- SHOULDTitles should identify three things: the focus of the report, the specific item of focus, and the report's main thrust, rather than relying on cryptic or purely creative wording.[Best Practices for Publishing RIXML p.19]
- SHOULDPublishers should provide both plain-text Title and formatted TitleFormatted (along with the equivalent pairings for Abstract/AbstractFormatted and Synopsis/SynopsisFormatted) so that consumers requiring either form can render the content.[Company Report (Advanced) Sample v2.4]↗ [RIXML Release Notes v2.4 p.20]
- INFORMATIVEFrom v2.5, Title supports multi-language presentation through alternative variants carried in ContentDetailsAlternativeLanguages alongside SubTitle, Synopsis and Abstract.[RIXML Quarterly Update 2017 Q2 p.8]↗ [RIXML Release Notes v2.5 p.24]
- MUSTWhen embedded HTML markup is used in title-style text elements (in the formatted variants), only the approved subset is permitted: P, UL, OL, LI, B, U and I; markup must be properly escaped or wrapped in CDATA to preserve XML validity.[RIXML Quarterly Update 2012 Q3 p.3]↗
- INFORMATIVEIn the v3.0 draft, multiple Title variants are managed inside a
TitleListcontainer and may be differentiated byaudienceType, language,includesFormatCodingandprimaryIndicatorattributes.[RIXML All-Member Meeting June 2023 p.25]↗ [RIXML All-Member Meeting June 2023 p.29]↗ [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.24]↗
Relationships
- child-ofContent — Title is a required child of Content, appearing exactly once and forming the headline of the research product.
- complemented-bySubTitle — SubTitle is an optional companion to Title; together they represent the complete headline of the research product.
- alternative-formTitleFormatted — TitleFormatted provides an HTML-formatted alternative to the plain-text Title; the two contain equivalent content with TitleFormatted permitting a limited markup subset that Title disallows.
- extended-byContentDetailsAlternativeLanguages — Alternative-language variants of Title are supplied within ContentDetailsAlternativeLanguages (introduced in v2.5) to support multilingual research distribution.
- qualified-byTitle.language — The language attribute identifies the language of a Title instance, enabling language-specific variants alongside the default-language title.
- contrasts-withSynopsis — Synopsis is intended to be longer than Title but shorter than Abstract, providing a brief summary of the research.
Where It Fits
Definition
| Type | string |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
No attributes defined for this element
Children
No child elements defined
Example
<Title />Version History
Unchanged since introduction in RIXML 2.2
v2.2–v2.3: Title is defined as a required, single-occurrence string child of Content, paired with optional SubTitle to form the headline (sources: level-one-2.2 p.14, level-one-2.3 p.9).
v2.4: TitleFormatted is introduced as a parallel formatted variant, allowing a constrained subset of HTML markup (P, UL, OL, LI, B, U, I) while Title itself remains plain text (sources: release-notes-2.4 p.20, quarterly-2012-q3 p.3).
v2.5: Multi-language support is added for Title alongside SubTitle, Synopsis and Abstract, with alternative variants carried in ContentDetailsAlternativeLanguages. A cardinality bug affecting TitleFormatted in v2.4 is also fixed in this release (sources: release-notes-2.5 p.24, quarterly-2017-q2 p.8, quarterly-2017-q3 p.8).
v3.0 (draft): Title is restructured as a repeatable element inside a TitleList container. Optional attributes include language, includesFormatCoding (replacing the separate formatted element pattern), audienceType and a publisher-defined audience value, plus a primaryIndicator to designate the default variant — enabling audience-segmented and multilingual title sets in a single structure (sources: data-dictionary-v3-draft p.24, meeting-2023-06 pp.25, 29, meeting-2024-spring p.23).
Semantic Relationships
Replaces1 relationship
TitleFormatted serves as an alternative to Title when HTML formatting is needed, containing identical content with markup
RIXML Research Data Dictionary v2.5.1, p.12— Embedding HTML content
Contrasts With1 relationship
TitleFormatted permits limited HTML markup for the product title while Title prohibits all markup
RIXML Research Data Dictionary v2.5.1, p.37— TitleFormatted (Optional, String)