7.0.0-dev.71
Ingestion Framework for FpML - Mapping Coverage: Credit Default Swaption Underlier
Background
Ingestion functions for FpML Confirmation to CDM have mapping coverage gaps for some products or test packs compared to the legacy Synonym mapping coverage. For further information, see #4260.
What is being released?
This release maps the Underlier field for Credit Default Swaption products, as per #4293.
Updates to mapping of CreditDefaultSwapOption to map the underlier field.
Review Directions
Changes can be reviewed in PR: #4291
Reference Data – Externalized FpML Coding Scheme Validation
Background
The Common Domain Model (CDM) historically integrates FpML coding schemes by compiling them into static enumerations via docReference annotations in Rune DSL. While this approach simplifies code generation, it tightly couples reference data updates with full CDM releases. This dependency increases maintenance overhead for CDM contributors and complicates adoption for end users, who must upgrade the entire CDM stack—even for minor reference data changes.
Some FpML code lists change frequently (historical records show 140+ updates over the past decade), this coupling slows adoption and risks misalignment with regulatory, legal, and market standards.
The enhancement decouples CDM releases from FpML updates by enabling validation against externalized code list resources. This ensures flexibility for implementers, while maintaining data integrity and alignment with industry-maintained references.
Further background is available in Issue #3512.
A detailed contribution document is available here.
What is being released?
This release introduces support for externalized code list validation through the new FpMLCodingScheme type alias and a supporting validation function ValidateFpMLCodingSchemeImpl.
Key technical improvements include:
- Extensible validation: validation logic is now independent from CDM release cycles. It is driven by type alias condition and can be extended to user-defined code lists.
- Automated transformation: FpML XML code lists are converted to CDM-ready JSON resources via a Maven-based process.
- Runtime availability: generated JSON resources are bundled into project resources, eliminating the need for recompilation.
Detailed changes include:
-
New Namespace:
cdm.base.staticdata.codelist-
Introduced types:
CodeList,CodeListIdentification,CodeValue. -
Added type aliases:
FpMLCodingScheme(validation wrapper).BusinessCenter(extension ofFpMLCodingScheme, replacingBusinessCenterEnum).
-
New functions:
LoadCodeList(load external JSON resources into aCodeList).ValidateFpMLCodingSchemeDomain(run validation against external resources).
-
-
Java Runtime
- Default validation implementation:
ValidateFpMLCodingSchemeImpl(bound inCdmRuntimeModule).
- Default validation implementation:
-
Testing Enhancements
- Standard validation scenarios:
FpMLCodingSchemeTests. - Custom list validation:
CodeValidationTest. - JSON resource loading:
LoadCodeListTest.
- Standard validation scenarios:
-
Migration Updates
- All references to
BusinessCenterEnummigrated to the new model and validation approach.
- All references to
-
Build Process Enhancements
-
Maven execution added for:
- XML-to-JSON code list transformation.
- Relocating generated resources to
src/main/resources/codelistfor consistent runtime access.
-
Review Directions
Full implementation details and review discussion can be found in PR #4227.