Legal
RIXML 2.5 Element
Top-level container for legal information required to accompany research products. Contains optional Copyright and Disclaimer elements for generic legal text, with IssuerSecurityID aggregations linking specific legal disclosures to particular securities or issuers.
Usage
Optional element in Product structure, can appear multiple times. Use for copyright notices, generic disclaimers, and security-specific legal disclosures. IssuerSecurityID children link disclosures to specific entities.
Business Context
Essential for regulatory compliance in research distribution, ensuring proper legal disclosures accompany research products and protecting publishers from liability while meeting regulatory requirements.
Specification Guide
Overview
Legal is the top-level container for legal information that accompanies a research product, including copyright notices, generic disclaimers, and security-specific disclosures. It sits within Product and groups boilerplate legal text together with IssuerSecurityID aggregations that bind specific legal statements to particular securities or issuers mentioned in the research (sources: data-dictionary-2.5.1 p.67, data-dictionary-2.4 p.64, user-guide-2.3 p.47).
Usage
Legal is an optional child of Product and MAY appear multiple times to accommodate different legal contexts within a single product (sources: data-dictionary-2.4 p.64, user-guide-2.2 p.46, user-guide-2.3 p.47).
Typical children include:
- An optional Copyright text element for copyright notices.
- An optional Disclaimer text element for generic legal disclaimers addressing liability and regulatory requirements.
- One or more IssuerSecurityID elements to link specific disclosures (e.g. Disclosure, Hedge) to individual securities or issuers covered in the research, rather than applying a single blanket disclaimer to the entire product (sources: data-dictionary-2.5.1 p.67, user-guide-2.2 p.46).
Use multiple Legal blocks when different disclosures apply to different subsets of covered securities, or when separating publisher-wide boilerplate from security-specific disclosures.
Rules
- INFORMATIVELegal is not required by RIXML Level One compliance; Level One implementations need not include Legal as a child of Product, in order to reduce implementation complexity for publishers and vendors.[RIXML Level One Addendum v2.5 p.6] [RIXML Level One Addendum v2.5 p.24]
- MUSTIn the RIXML v3 draft, Legal is renamed to
DisclosureListwith a simplified option set to better reflect real-world disclosure usage; consumers and producers targeting v3 should migrate references accordingly.[Key Changes in RIXML v3 p.1]↗ - SHOULDPackage-layer containers including Legal, Source, Context, and Content are candidates for removal in v3 due to insufficient adoption; existing usage should be migrated to alternative structures before v3 adoption.[RIXML All-Member Meeting Winter 2024 p.22]↗
Relationships
- child-ofProduct — Legal is an optional, repeatable child of Product, providing the legal package that accompanies the research product.
- containsIssuerSecurityID — Legal contains optional IssuerSecurityID children that bind specific legal disclosures to individual securities or issuers mentioned in the research.
- associatesDisclosure — Security-specific Disclosure statements are associated with securities through IssuerSecurityID elements inside Legal.
- associatesHedge — Hedge disclosures may be associated with specific issuers/securities via IssuerSecurityID children of Legal.
- replaced-by
DisclosureList— In the v3 draft, Legal is replaced by a renamed and simplifiedDisclosureListelement that better reflects how disclosures are used in practice.
Where It Fits
Children
Definition
| Type | LegalType |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
No attributes defined for this element
Children
Copyrightstring0..1 |
Copyright information relating to the product. optionalSince 2.1 |
Disclaimerstring0..1 |
Disclaimer is the long generic legalese that automatically gets pasted into a note/report that 'disclaims' against liabilities for losses associated with buying/selling stocks etc. This could also include generic disclaimers when a report discusses MSCI indexes. This section changes infrequently. optionalSince 2.1 |
IssuerSecurityID(complex)0..unbounded |
optionalSince 2.1 |
Example
<Legal />Version History
Unchanged since introduction in RIXML 2.1
Legal is present across the RIXML 2.x line (2.2 through 2.5) with a stable structure: optional Copyright, optional Disclaimer, and zero or more IssuerSecurityID children, repeatable within Product (sources: user-guide-2.2 p.46, user-guide-2.3 p.47, data-dictionary-2.4 p.64, data-dictionary-2.5.1 p.67).
At RIXML 2.5, the Level One compliance profile defines Legal as not required under Product in order to simplify Level One implementations (source: level-one-2.5 pp.6, 24); the element remains valid in the full 2.5 schema.
In the v3 draft, Legal is renamed to DisclosureList and its options are simplified to reflect real-world usage; v3 working-group discussions also list Legal among package-layer components considered for removal due to limited adoption (sources: meeting-v3-key-changes p.1, meeting-2024-06 p.28, meeting-2024-winter p.22).
Design Decisions
Level One excludes Legal elements as children of Product
To simplify the Level One implementation by removing non-essential legal elements
RIXML Level One Addendum v2.5, p.6
Legal elements are not permitted in Level One
To substantially reduce complexity for both publishers and vendors, alleviating implementation costs
RIXML Level One Addendum v2.5, p.24