RIXML 2.5 Element
Electronic mail address information for digital communication. Contains the email address value as string content without additional attributes.
Strongly Recommended. Indicates the email address.
Usage
Strongly recommended optional element within ContactInfo that can appear multiple times. Use to provide email addresses for direct electronic communication with research contributors or organizations.
Business Context
Primary digital communication method in modern research distribution, enabling direct client contact, research delivery notifications, and general business correspondence between research providers and consumers.
Specification Guide
Overview
Email holds a single electronic mail address as string content, providing the primary digital communication channel for research contributors and organisations within RIXML contact information structures. It is a simple text-only element with no attributes, valued for its role in enabling direct correspondence, automated notifications, and digital research delivery between producers and consumers (sources: data-dictionary-2.4 p.32, data-dictionary-2.5.1 p.34).
Usage
Email is an optional but strongly recommended child of ContactInfo in RIXML 2.x, where it may appear multiple times to capture different addresses for the same contact (sources: user-guide-2.1 p.21, user-guide-2.2 p.21, user-guide-2.3 p.21, data-dictionary-2.4 p.32, data-dictionary-2.5.1 p.34).
The content is a plain xs:string. The schema does not enforce email-address syntax, so producers should validate format at the application layer before serialisation [Company Report (Advanced) Sample v2.4]↗.
In the RIXML v3 draft, Email is instead nested inside a dedicated EmailList container element, with multiples allowed inside that container (sources: data-dictionary-v3-draft p.29, meeting-2025-01 p.35). Note that EmailList does not appear in the published entity index for 2.x and is a v3-draft concept.
Rules
- SHOULDInclude Email within ContactInfo whenever an email address is available; it is strongly recommended across all 2.x versions.[RIXML User Guide v2.1 p.21] [RIXML User Guide v2.2 p.21] [RIXML User Guide v2.3 p.21] [RIXML Research Data Dictionary v2.4 p.32] [RIXML Research Data Dictionary v2.5.1 p.34]
- SHOULDAuthor and analyst contact blocks should provide both Email and Phone so that consumers can reach contributors through their preferred channel.[Company Report (Advanced) Sample v2.4]↗ [Economics Report (Basic) Sample v2.4]↗ [Industry Report (Basic) Sample v2.4]↗ [Morning Call Report (Basic) Sample v2.4]↗
- MUSTIn the RIXML v3 draft, each Email must be carried inside an
EmailListcontainer element rather than directly under ContactInfo.[RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.29]↗ [RIXML All-Member Meeting January 2025 p.35]↗
Relationships
- child-ofContactInfo — In RIXML 2.x, Email is an optional, repeatable child of ContactInfo used to record one or more email addresses for the contact.
- complementsPhone — Email is typically paired with Phone inside ContactInfo to give consumers multiple ways to reach a contributor.
- appears-inPerson — Used (via ContactInfo) to provide email contact details for individual research contributors represented by Person.
- appears-inOrganization — Used (via ContactInfo) to provide email contact details for an Organization.
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
No attributes defined for this element
Children
Contains text content (type: string)
This element's value is its text content. Attributes provide additional context.
Example
<Email>ABC-123</Email>Version History
Unchanged since introduction in RIXML 2.1
Email is present from at least RIXML 2.1 onward as a simple string child of ContactInfo, with multiples allowed and a consistent "strongly recommended" disposition (sources: user-guide-2.1 p.21, user-guide-2.2 p.21, user-guide-2.3 p.21). Its definition is unchanged through versions 2.4 and 2.5.1 (sources: data-dictionary-2.4 p.32, data-dictionary-2.5.1 p.34).
In the v3 draft, the RIXML committee decided to wrap Email inside a new EmailList container element to better represent multiple addresses per contact; the Email element itself remains a simple string but is no longer a direct child of ContactInfo (sources: data-dictionary-v3-draft p.29, meeting-2025-01 p.35).