RIXML Documentation

Abstract

RIXML 2.5 Element

Level OneRequired

Optional string element providing detailed summary of the research product content. Intended to be longer and more comprehensive than Synopsis, offering substantive overview of research findings and analysis.

A summary of the information contained in the product. Highlights the salient issues in the document or provides a brief description of the event. Suggested maximum length is 3000 characters. No markup permitted.

Usage

Optional child of Content element that can appear at most once. Contains extended string description of product content, longer than synopsis but shorter than full content.

Business Context

Enables efficient content evaluation and filtering in research workflows by providing substantive previews that help consumers determine relevance before accessing full research documents.

Source:level-one-2.5
Schema:RIXML-Common-2_5.xsd:2309

Specification Guide

Overview

Abstract is an optional plain-text element within Content that holds a comprehensive summary of a research product, intended to be longer and more detailed than Synopsis but substantially shorter than the full content. It typically conveys key findings, conclusions, recommendations, or highlights — often a few paragraphs or bullet points repurposed from the report's own executive summary — and serves as the primary discovery surface that lets consumers evaluate research relevance before opening the full document (sources: data-dictionary-2.5.1 p.18, level-one-2.5 p.9, release-notes-2.5 p.24). A parallel AbstractFormatted element exists for cases where embedded markup is required; Abstract itself is plain text only [data-dictionary-2.5.1 p.37].

Usage

Abstract is an optional child of Content with cardinality 0..1 through RIXML 2.x, containing plain-text content with a suggested maximum length of 3000 characters (sources: data-dictionary-2.5.1 p.36, user-guide-2.1 p.22, level-one-2.5 p.9). Typical practice is to copy the report's existing summary, highlights, or key-points section verbatim, keeping the content to a few paragraphs or bullets that capture the primary investment thesis, findings, or conclusions [data-dictionary-2.5.1 p.18]. The element is well suited to search indexing, content previews, alert systems, and any workflow where consumers need to triage research before committing to a full read. Where formatted (HTML) markup is required for display, publishers should supply AbstractFormatted alongside (or instead of) Abstract; the two are content-equivalent variants distinguished only by markup support (sources: data-dictionary-2.5.1 p.37, release-notes-2.4 p.20). From v2.5 onward, multilingual abstracts are carried via ContentDetailsAlternativeLanguages, each language variant tagged accordingly [release-notes-2.5 p.24].

Rules

Relationships

Where It Fits

Canonical Path

Definition

Typestring
Namespacehttp://www.rixml.org/2017/9/RIXML
Min Occurs1
Max Occurs1

Attributes

No attributes defined for this element

Children

No child elements defined

Example

<Abstract />

Version History

Unchanged since introduction in RIXML 2.2

Abstract has been present since at least RIXML 2.1, where it was defined as an optional child of Content with a suggested 3000-character maximum [user-guide-2.1 p.22]. Through 2.2, 2.3, and 2.4 the element retained the same optional 0..1 cardinality and plain-text semantics (sources: level-one-2.2 p.14, level-one-2.3 p.9, level-one-2.4 p.9). RIXML 2.4 introduced the parallel AbstractFormatted element to carry the same content with a limited HTML subset (P, UL, OL, LI, B, U, I), formalising the separation between plain-text and formatted variants and reinforcing that Abstract itself must remain plain text (sources: release-notes-2.4 p.20, quarterly-2012-q3 p.3). RIXML 2.5 added multi-language support: Abstract (along with Title, Synopsis, and other narrative elements) can be supplied in multiple languages via ContentDetailsAlternativeLanguages, each variant tagged with its language code (sources: quarterly-2017-q2 p.8, release-notes-2.5 p.24). The v3.0 draft proposes a more substantial restructuring: Abstract becomes a required child of an AbstractList container permitting multiples, and gains attributes for language, format coding (includesFormatCoding), and audience targeting so that publishers can issue distinct abstracts for different client segments (sources: data-dictionary-v3-draft p.25, meeting-2023-06 pp.25, 29, meeting-2024-spring p.23).

Business Rules

SHOULD

Abstract content must be limited to a few paragraphs or bullets highlighting key points covered in the report

content-guideline
SHOULD

Abstract element should have a maximum length of 3000 characters

best-practicelength-constraint

Design Decisions

The Abstract element should highlight key points and be limited to no longer than a few paragraphs or bullet points

This constraint ensures the Abstract provides meaningful summary content without becoming overly lengthy, and allows reuse of existing report summary sections

RIXML Research Data Dictionary v2.5.1, p.18

Semantic Relationships

Replaces1 relationship

AbstractFormatted serves as an alternative to Abstract when HTML formatting is needed, containing identical content with markup

RIXML Research Data Dictionary v2.5.1, p.12Embedding HTML content

Narrows1 relationship

SynopsisINFORMATIVE

Synopsis provides a very brief overview suitable for abbreviated displays, while Abstract offers a more detailed summary with key points and highlights

RIXML Research Data Dictionary v2.5.1, p.18Synopsis

Contrasts With2 relationships

AbstractFormattedINFORMATIVE

AbstractFormatted supports limited HTML markup for product summaries while Abstract restricts all markup

RIXML Research Data Dictionary v2.5.1, p.37AbstractFormatted (Optional, String)

AbstractFormattedINFORMATIVE

AbstractFormatted permits HTML markup while Abstract does not, representing formatted and unformatted versions of the same content

RIXML Research Data Dictionary v2.5.1, p.38AbstractFormatted (Optional, String)