Context
RIXML 2.5 Element
Required container element for research product metadata with mandatory external attribute indicating whether content is for internal or external organizational use. Level One excludes EventDetails.
Usage
Required element within Product, appearing exactly once. Must have external attribute set to 'Yes' if reaching organizations outside the publisher. Contains IssuerDetails and ProductClassifications.
Business Context
Critical for content access control and distribution targeting, ensuring research reaches appropriate audiences while maintaining compliance with internal/external usage policies.
Specification Guide
Overview
Context is the top-level container for research product categorization and classification metadata within RIXML documents. It serves as the primary source of searchable and filterable information that enables consumers to discover, categorize, and route research based on multiple classification dimensions including issuer details, product characteristics, event information, and various taxonomic schemes.
Usage
Context is a required child element of Product that appears exactly once. It must include the external attribute to indicate whether the research is intended for internal or external distribution. Optionally, it can include a priority attribute to highlight important products. The element can contain four optional child element categories: EventDetails, IssuerDetails, ProductDetails, and ProductClassifications.
Rules
- MUSTContext requires the external attribute to indicate whether research is for internal or external use[RIXML Level One Addendum v2.3.1 p.11]
- INFORMATIVELevel One compliance excludes EventDetails as a child of Context[RIXML Level One Addendum v2.5 p.12] [RIXML Level One Addendum v2.3 p.11] [RIXML Level One Addendum v2.3.1 p.11]
- SHOULDDocument-specific elements like Context should remain in RIXML proper while publisher-specific elements should be communicated through side-car schemas[RIXML Quarterly Update 2012 Q4 p.2]↗
- SHOULDEvent-driven tags should utilize common identifiers for major events to enable consistent cross-platform recognition[RIXML Quarterly Update 2013 Q4 p.3]↗
Relationships
- contained-byProduct — Context is a required child element of Product
- containsEventDetails — Context may contain EventDetails to provide event-specific information
- containsIssuerDetails — Context may contain IssuerDetails to provide issuer-specific information
- containsProductDetails — Context may contain ProductDetails to provide product-specific characteristics
- containsProductClassifications — Context may contain ProductClassifications to provide taxonomic classification information
Where It Fits
Definition
| Type | ContextType |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
Children
EventDetailsEventDetailsType0..1 |
optionalSince 2.1 |
IssuerDetailsIssuerDetailsType0..1 |
optionalSince 2.1 |
ProductDetailsProductDetailsType0..1 |
optionalSince 2.1 |
ProductClassificationsProductClassificationsType0..1 |
optionalSince 2.1 |
Example
<Context external="Yes" />Version History
Unchanged since introduction in RIXML 2.1
Context has been present since RIXML 2.1 as a required container for research product metadata. The element maintained consistent structure through versions 2.2 and 2.3, with the external attribute remaining mandatory for distribution control. In Level One compliance specifications across versions, EventDetails is consistently excluded as a child element to maintain schema simplification. Version 3.0 discussions have proposed removing package layer components including Context due to lack of adoption [RIXML All-Member Meeting Winter 2024 p.22]↗, though alternative proposals suggest using Context for section-level tagging within research reports for more granular content identification [RIXML All-Member Meeting March 2023 p.12]↗.
Business Rules
Context external attribute is required and should be set to Yes when RIXML reaches organizations outside the publisher
Level One compliance excludes EventDetails element as a child of Context
Semantic Relationships
Requires1 relationship
If this particular RIXML Research instance document is reaching an organization outside the publisher, the external value should be Yes
RIXML Level One Addendum v2.5, p.11— Research.Product.Context