CoveragePairing
RIXML 2.5 Element
An element that establishes relationships between covering entities and covered entities, interpreted to mean each covering entity provides coverage for all specified covered entities
An element to pair coverers with the covered. Interpretted to mean that each of the covering entities covers all of the covered entities.
Usage
Required child element of CoverageUpdate with multiple instances allowed, containing exactly one CoveringEntities and one CoveredEntities element
Business Context
Core mechanism for expressing coverage relationships in research distribution, enabling automated routing of research content based on analyst assignments and coverage areas
Specification Guide
Overview
CoveragePairing establishes a many-to-many relationship between a set of covering entities (analysts, teams, or organizations) and a set of covered entities (securities, sectors, issuers, regions, etc.) within a CoverageUpdate. Each pairing is interpreted such that every covering entity listed covers every covered entity listed, providing a compact way to express coverage assignments in the Coverage Updates sidecar schema (sources: data-dictionary-2.4 p.133, data-dictionary-2.5.1 p.137).
Usage
CoveragePairing appears as a child of CoverageUpdate, where one or more pairings can be supplied. Each pairing contains exactly one CoveringEntities block and one CoveredEntities block, which together define the full coverage matrix represented by the pairing. Use multiple CoveragePairing instances within a single CoverageUpdate when distinct groupings of analysts cover distinct groupings of entities, since the cross-product semantics apply only within a single pairing. This structure supports automated routing of research content based on analyst assignments and coverage areas [RIXML Research Data Dictionary v2.5.1 p.137].
Rules
- MUSTA CoveragePairing must be interpreted as a cross-product: each entity listed in CoveringEntities covers every entity listed in CoveredEntities within the same pairing.[RIXML Research Data Dictionary v2.5.1 p.137] [RIXML Research Data Dictionary v2.4 p.133]
- MUSTCoveragePairing must contain exactly one CoveringEntities child and exactly one CoveredEntities child.[RIXML Research Data Dictionary v2.5.1 p.137] [RIXML Research Data Dictionary v2.4 p.133]
- SHOULDTo represent coverage relationships that do not follow a uniform cross-product (for example, different analysts covering different subsets), publishers should emit multiple CoveragePairing elements within a CoverageUpdate rather than combining them into one.[RIXML Research Data Dictionary v2.5.1 p.137]
Relationships
- child-ofCoverageUpdate — CoveragePairing is a required child of CoverageUpdate, with multiple instances allowed per update.
- requiresCoveringEntities — CoveragePairing requires a CoveringEntities element identifying the analysts, teams, or organizations providing coverage.
- requiresCoveredEntities — CoveragePairing requires a CoveredEntities element identifying the securities, issuers, sectors, or other targets being covered.
Where It Fits
Canonical Path
Children
Definition
| Type | CoveragePairingType |
| Namespace | http://www.rixml.org/2017/9/RIXML |
| Min Occurs | 1 |
| Max Occurs | 1 |
Attributes
No attributes defined for this element
Children
CoveringEntitiesCoveringEntitiesType1..1 |
requiredSince 2.5 |
CoveredEntitiesCoveredEntitiesType1..1 |
requiredSince 2.5 |
Example
<CoveragePairing>
<CoveringEntities> ... </CoveringEntities>
<CoveredEntities> ... </CoveredEntities>
</CoveragePairing>Version History
Unchanged since introduction in RIXML 2.5
CoveragePairing is documented in the Coverage Updates sidecar schema in RIXML 2.4 (p.133) and 2.5 / 2.5.1 (p.137). The semantics and structural requirements are consistent across both versions: a required child of CoverageUpdate containing one CoveringEntities and one CoveredEntities, with cross-product interpretation.
Business Rules
Coverage pairings must be interpreted such that each covering entity covers all of the covered entities within the pairing
Design Decisions
Coverage relationships should be modeled as pairings where each covering entity covers all covered entities in the pairing
Provides a clear semantic model for expressing many-to-many coverage relationships between analysts and their coverage universe
RIXML Research Data Dictionary v2.5.1, p.137
Semantic Relationships
Requires2 relationships
Coverage pairings establish the relationship where each covering entity provides research coverage for all specified covered entities
RIXML Research Data Dictionary v2.5.1, p.137— CoveragePairing
Coverage pairings establish the relationship where all covering entities provide research coverage for each specified covered entity
RIXML Research Data Dictionary v2.5.1, p.137— CoveragePairing