Frameworks & Standards
FIBO
FIBO is the EDM Association's Financial Industry Business Ontology. EDM describes FIBO as defining the things that are of interest in financial business applications and the ways those things relate to one another.
OMG describes FIBO as an Object Management Group standard for financial business terms and relationships, including financial contracts and related concepts.
FIBO is useful when buyers need a common, machine-readable financial language for data governance, reporting, lineage, analytics, AI context, and cross-system interoperability.
Buyer question
"Can Legra operationalize FIBO as a governed financial knowledge layer, instead of leaving it as a reference ontology on the side?"
Legra fit
| FIBO assessment area | Legra fit | Status |
|---|---|---|
| Financial vocabulary | Legra can store, query, version, and govern FIBO terms as RDF/OWL vocabulary data. | Native fit |
| Cross-system meaning | FIBO can give common meaning to spreadsheets, relational data, XML, messages, and APIs once those sources are mapped into Legra. | Partial fit |
| Regulatory and reporting semantics | Legra can link reporting data, controls, provenance, and validation rules to FIBO concepts. | Partial fit |
| Reasoning over financial concepts | Supported RDFS and OWL-RL rules can derive relationships in FIBO-aligned data, with explanations for review. | Native fit |
| Data quality and conformance | SHACL validation, staging branches, and production enforcement can check FIBO-aligned data before promotion. | Native fit |
| Change governance | Branches, commits, provenance, and review workflows can manage changes to FIBO mappings, extensions, and local profiles. | Native fit |
What Legra can say
Legra is a natural operating layer for FIBO because both are RDF-native. FIBO can be more than documentation or a modeling artifact: it can become part of the live financial knowledge graph.
Legra can support FIBO evidence such as:
- Which business terms and ontology modules are in use.
- Which local concepts map to FIBO concepts.
- Which datasets, reports, contracts, trades, products, parties, or risk records use those concepts.
- Which validation rules protect FIBO-aligned data.
- Which branches introduced or changed FIBO mappings.
- Which commits and actors approved semantic changes.
- Which provenance explains where a financial fact came from.
This lets financial institutions assess semantic governance with evidence from the operational graph, not only from architecture diagrams or offline model repositories.
Assessment boundary
FIBO adoption still requires domain modeling decisions, source-system mapping, stewardship, local extensions, regulatory interpretation, and data-quality rules. Legra provides queries, version history, and access controls for that work, but the buyer's financial data-management program determines how complete the FIBO adoption is.
For finance buyers, Legra is best positioned as the place where FIBO, local financial semantics, validation rules, provenance, and operational data meet.