EventDetails
RIXML 2.5 Element
Specialized container providing event-specific information when research products focus on events rather than static analysis. Specifies event type and sponsoring organization as mandatory elements.
Usage
Optional element used when Product.eventIndicator is set to Yes or when the product category is Event. Must include EventType and EventSponsor as required attributes with optional venue, host, and registration details.
Business Context
Critical for research covering conferences, earnings calls, investor meetings, and other time-sensitive events. Supports event management workflows and helps subscribers identify participation requirements and logistics.
Specification Guide
Overview
EventDetails is a specialised container within Context that supplies structured metadata when a research product describes or accompanies a specific event (conference, earnings call, roadshow, investor meeting, corporate action, etc.) rather than traditional analytical content. It carries the event's classification and sponsor as required attributes and aggregates optional sub-elements describing the venue, host, registration logistics, and contact information needed for participation (sources: data-dictionary-2.4 p.43, data-dictionary-2.5.1 p.45, user-guide-2.1 p.29).
Usage
EventDetails is an optional child of Context, but is expected whenever the surrounding Product has eventIndicator set to Yes or its productCategory indicates an Event (sources: user-guide-2.1 p.29, user-guide-2.2 p.30, user-guide-2.3.1 p.30, data-dictionary-2.5.1 p.45).
The element requires EventType (drawn from EventTypeEnum) and EventSponsor (drawn from OrganizationTypeEnum). Optional child aggregations include EventVenue, EventHost, EventDate, RegistrationInformation, and ContactInfo for coordinating attendance, replays, and inquiries (sources: data-dictionary-2.4 p.43, user-guide-2.1 p.29, data-dictionary-v3-draft p.78).
Typical use cases are earnings calls, analyst days, broker conferences, roadshows, and webinars, where the research deliverable is the event itself or an artefact tightly bound to it. The element is not designed to be a full event-management record; in v3 the RIXML Interactions standard is positioned as the richer alternative for comprehensive event description.
Rules
- INFORMATIVEEventDetails is not required by RIXML Level One. Level One implementations may omit it as a child of Context without breaking compliance, but its inclusion is not prohibited.[RIXML Level One Addendum v2.2 p.17] [RIXML Level One Addendum v2.3 p.12] [RIXML Level One Addendum v2.3.1 p.12] [RIXML Level One Addendum v2.5 p.12]
- SHOULDWhen eventIndicator is set to
Yes(or productCategory denotes an Event), EventDetails should be populated so that downstream parsers can route and present the event content correctly.[RIXML User Guide v2.1 p.15] [RIXML User Guide v2.2 p.30] [RIXML Research Data Dictionary v2.5.1 p.22] - SHOULDFor comprehensive event description in RIXML v3, the RIXML Interactions standard should be used in preference to EventDetails; the tag set is retained primarily for backwards compatibility and small amounts of event context embedded in research items.[RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.10]↗ [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.78]↗
- INFORMATIVEEventDetails and its sub-structure were proposed for removal in RIXML v3.0 on the basis that publishers were not populating it and consuming portals were not expecting it; the final disposition (full removal versus retention for compatibility) varies between draft sources.[RIXML All-Member Meeting June 2023 p.33]↗ [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.78]↗
Relationships
- child-ofContext — EventDetails appears as an optional child of Context in the Context Package, scoping event metadata to the surrounding research product.
- triggered-byProduct.eventIndicator — When eventIndicator is
Yes, EventDetails is expected to be supplied so that the event nature of the product is fully described. - aggregatesEventVenue — EventDetails optionally aggregates EventVenue to describe the physical or virtual location of the event.
- aggregatesEventHost — EventDetails optionally aggregates EventHost to identify the hosting organization or individual.
- aggregatesEventDate — EventDetails aggregates EventDate entries giving the event's scheduling information.
- aggregatesRegistrationInformation — EventDetails optionally carries RegistrationInformation for participants to sign up or obtain credentials.
- aggregatesContactInfo — EventDetails may include one or more ContactInfo entries for event coordination, registration help, or replay access.
- qualified-byContactInfoPurposeEnum — Within EventDetails, ContactInfoPurposeEnum qualifies the role of phone or email contacts (e.g. registration vs. replay access) on contained ContactInfo children.
- qualified-byRoleEnum — Most values of RoleEnum are scoped to event and interaction records and are used to characterise participants associated with EventDetails.
Where It Fits
Definition
| Type | EventDetailsType |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
No attributes defined for this element
Children
EventTypeEventTypeEnum1..1 |
Indicates the type of the event. requiredSince 2.1 |
EventSponsorOrganizationTypeEnum1..1 |
requiredSince 2.1 |
EventVenue(complex)0..1 |
optionalSince 2.1 |
EventHost(complex)0..1 |
optionalSince 2.1 |
RegistrationInformation(complex)0..1 |
optionalSince 2.1 |
ContactInfoContactInfoType0..unbounded |
optionalSince 2.1 |
Example
<EventDetails>
<EventType> ... </EventType>
<EventSponsor> ... </EventSponsor>
</EventDetails>Version History
Unchanged since introduction in RIXML 2.1
Present in RIXML 2.x (documented at least from v2.1 through v2.5.1) as an optional child of Context with required EventType and EventSponsor attributes and optional venue/host/registration/contact aggregations (sources: user-guide-2.1 p.29, data-dictionary-2.4 p.43, data-dictionary-2.5.1 p.45). Across all 2.x Level One profiles, EventDetails is consistently listed as not required by Level One (sources: level-one-2.2 p.17, level-one-2.3 p.12, level-one-2.3.1 p.12, level-one-2.5 p.12).
In the RIXML v3.0 development cycle, the June 2023 working-group meeting proposed removing EventDetails and its sub-structure entirely on the grounds that publishers were not populating it and consuming portals were not expecting it [meeting-2023-06 p.33]. The v3 draft data dictionary takes a softer line: the tag set is retained for backwards compatibility, but the RIXML Interactions standard is positioned as the recommended mechanism for full event description, with EventDetails reserved for minimal event context inside research items [data-dictionary-v3-draft p.10 p.78]. Implementers targeting v3 should treat EventDetails as legacy and plan migration to Interactions.
Design Decisions
Level One excludes EventDetails elements as children of Context
To simplify Level One implementations by removing event-specific metadata
RIXML Level One Addendum v2.5, p.12
Semantic Relationships
Implies1 relationship
Event indicator serves as a processing cue that the product is about an event, enabling more effective downstream parsing and handling of event-related content
RIXML Research Data Dictionary v2.5.1, p.22— eventIndicator (Strongly Recommended, YesNoEnum)