EventVenue

Overview

EventVenue specifies the location and format of an event covered by a research product, supporting both physical venues (such as in-person meetings, analyst conferences, or one-on-ones) and virtual platforms (such as conference calls or webcasts). It carries a required type attribute (drawn from EventVenueTypeEnum) that categorises the venue format, and aggregates optional Organization, EventDate, ContactInfo, and EntitlementGroup children to convey logistical, scheduling, contact, and access-control details. Within the RIXML document hierarchy, EventVenue sits inside EventDetails in the Context package and is the focal point for describing where and how participants can engage with research-related events such as earnings calls, investor meetings, and analyst conferences.

Usage

EventVenue is an optional child of EventDetails but is strongly recommended whenever the research product describes a location-based event, and is conditionally required when the product is explicitly event-categorised (see Rules below). Typical patterns: - Set type from EventVenueTypeEnum to distinguish physical from virtual formats (e.g. conference call, webcast, in-person meeting). - Use child Organization aggregations to name the hosting or sponsoring organisations. - Use child EventDate aggregations to convey start/end times and registration deadlines. - Use ContactInfo for dial-in details, registration URLs, or venue contact addresses. - Use EntitlementGroup to express access restrictions for invitation-only or otherwise restricted events. Multiple organisations, dates, and contact methods may be supplied to describe events with several hosts, sessions, or access channels.

Rules

• MUSTEventVenue MUST be included when eventIndicator equals Yes or when productCategory equals Event.[RIXML User Guide v2.1 p.31] [RIXML User Guide v2.3 p.32] [RIXML User Guide v2.3.1 p.32] [RIXML Research Data Dictionary v2.4 p.45] [RIXML Research Data Dictionary v2.5.1 p.47]
• SHOULDEventVenue SHOULD be supplied for any location-based event, even when not strictly required by eventIndicator or ProductCategory, so consumers receive complete venue context.[RIXML User Guide v2.1 p.31] [RIXML User Guide v2.3 p.32] [RIXML Research Data Dictionary v2.4 p.45] [RIXML Research Data Dictionary v2.5.1 p.47]
• MUSTThe type attribute MUST be specified using a value from EventVenueTypeEnum to distinguish physical from virtual venue formats.[RIXML User Guide v2.3 p.32] [RIXML Research Data Dictionary v2.4 p.45] [RIXML Research Data Dictionary v2.5.1 p.47] [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.78]↗
• INFORMATIVEIn the v3.0 draft, EventDetails and its sub-structure — including EventVenue, EventDate, EventHost, and RegistrationInformation — were proposed for removal from the schema as unused by publishers and research portals; the proposal noted that any event-related elements consumed by the RIXML Interaction Standard should be preserved.[RIXML All-Member Meeting June 2023 p.33]↗

Relationships

• contained-byEventDetails — EventVenue appears as an optional child within EventDetails in the Context package.
• requiresEventVenue.type — EventVenue requires a type attribute drawn from EventVenueTypeEnum to identify the venue format.
• uses-enumerationEventVenueTypeEnum — The required type attribute takes its value from EventVenueTypeEnum, which enumerates physical and virtual venue categories.
• conditionally-required-byProduct.eventIndicator — EventVenue becomes required when eventIndicator is set to Yes.
• conditionally-required-byProductCategoryEnum.Event — EventVenue becomes required when productCategory equals Event.
• aggregatesOrganization — EventVenue may aggregate one or more Organization elements to identify hosts, sponsors, or venue operators.
• aggregatesEventDate — EventVenue may include one or more EventDate children to convey scheduling information.
• aggregatesContactInfo — EventVenue may include ContactInfo children for dial-in details, registration URLs, or venue contact addresses.
• aggregatesEntitlementGroup — EventVenue may include EntitlementGroup children to express access restrictions and participant entitlements for the event.