Hedge
RIXML 2.5 Element
Contains hedge clauses noting historical business relationships like managing public offerings within specified timeframes or other stock-specific legal clauses. Required Description element with optional code attribute for categorization.
Hedge is a clause that notes if firm acted as manager or co-manager of a public offering of a company within the past three years, or some other stock-specific clause. This section changes less frequently.
Usage
Optional within IssuerSecurityID elements, multiples allowed. Used for less frequently changing disclosures about historical business relationships and standardized legal clauses.
Business Context
Supports regulatory compliance by documenting historical business relationships that could create perceived conflicts of interest, providing transparency about past involvement in securities transactions.
Specification Guide
Overview
Hedge contains historical legal hedge clauses that document past firm involvement with a security — typically prior roles such as manager or co-manager in public offerings within a defined lookback period, or other security-specific protective legal language. It complements Disclosure within the legal package of an IssuerSecurityID, capturing relatively static historical context rather than current relationships.
Usage
Hedge is an optional child of IssuerSecurityID and may occur multiple times (maxOccurs="unbounded") to cover several historical relationships or standard clauses. It carries an optional code attribute for publisher-defined hedge categorization and a required Description containing the hedge clause text. Because hedge content describes historical relationships and standardized legal language, it changes less frequently than Disclosure entries and is typically reused across many products covering the same security (sources: data-dictionary-2.5.1 p.68, user-guide-2.2 p.47, user-guide-2.3 p.48, data-dictionary-2.4 p.65).
Relationships
- child-ofIssuerSecurityID — Hedge appears as an optional, repeatable child of IssuerSecurityID, forming part of the security-level legal package.
- contrasts-withDisclosure — Disclosure captures current/proactive relationships and changes relatively frequently, whereas Hedge documents historical involvement (e.g. past public offering roles) and is comparatively static.
Where It Fits
Canonical Path
Definition
| Type | |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
codestring |
Indicates the publisher defined hedge code for a specific hedge. For example, a publisher may need to disclose a banking relationship with a company, and may call this hedge code A. optional |
Children
Descriptionstring1..1 |
A description of the hedge. requiredSince 2.1 |
Example
<Hedge>
<Description> ... </Description>
</Hedge>Version History
Unchanged since introduction in RIXML 2.1
Hedge is present in RIXML 2.2 through 2.5 as an optional, repeatable child of IssuerSecurityID within the legal package, with consistent structure (optional code attribute and required Description) across these versions (sources: user-guide-2.2 p.47, user-guide-2.3 p.48, data-dictionary-2.4 p.65, data-dictionary-2.5.1 p.68). The v3 draft removes Hedge from the schema as part of streamlining the legal package by eliminating unused elements [RIXML Research Suite Data Dictionary v3.0 (DRAFT) p.20]↗.
Semantic Relationships
Contrasts With1 relationship
Disclosure information changes relatively frequently as it covers current involvement, while Hedge information changes less frequently covering historical relationships
RIXML Research Data Dictionary v2.5.1, p.68— Disclosure