Smart Data Models’ Candidates repository now includes a new candidate standard translated from the Financial Industry Business Ontology (FIBO) of the EDM Council: fibo, with 5 candidate models for legal entities, their Legal Entity Identifiers (LEI), parent relationships, listed shares and loans. FIBO is published under the MIT licence. Like every candidate, each model comes with a JSON Schema, an NGSI-LD @context and all four example serializations (NGSI-v2 and NGSI-LD, key-values and normalized), each validated against its schema.
About FIBO
FIBO is the EDM Council’s formal OWL ontology of the financial industry: business entities and identifiers (including the ISO 17442 LEI), ownership and control, contracts, financial instruments and securities, loans, derivatives, indices and corporate actions. It is released quarterly; this translation uses the Production release 2026Q3, which builds on the OMG Commons Ontology Library.
The models
| Model | FIBO class | Attributes | Example |
|---|---|---|---|
LegalEntity |
legal entity (Commons, with FIBO’s LEI axioms) | 24 | Real (GLEIF) |
LegalEntityIdentifierRegistryEntry |
LEI registry entry: status, dates, managing LOU, validation | 9 | Real (GLEIF) |
RelationshipRecord |
LEI relationship record (direct / ultimate parent, branch) | 8 | Real (GLEIF Level 2) |
ListedShare |
listed share | 23 | Synthetic |
Loan |
loan | 24 | Synthetic |
Grounded in open LEI data
Three examples use one real record from the GLEIF Global LEI Index (CC0): Siemens Healthineers AG (LEI 529900QBVWXMWANH7H45), its legal and headquarters addresses, legal form (ISO 20275 code 6QQB, Aktiengesellschaft), its LEI registration (issued, fully corroborated), and its Level 2 relationship to its direct parent Siemens AG, with the accounting and filing periods. The share and loan examples are synthetic and use fictitious companies.
Translation notes
- Derived from OWL restrictions. FIBO defines classes through restrictions. Each model’s attributes come from the restrictions on the class and its superclasses, and every description quotes the restriction it comes from.
- FIBO names, verbatim. Classes and properties keep their FIBO names (
hasLegalAddress,isDirectlyConsolidatedBy,hasPrincipalAmount…), and each@contextmaps them to the FIBO or Commons IRI. - Parties as relationships. Lenders, borrowers, issuers and owners are links to
LegalEntityentities. Identifiers, addresses, legal forms, periods, amounts and payment terms stay nested. - FIBO code lists. Registration status, entity status, validation level and similar values are FIBO individuals (compact IRIs), with the GLEIF codes listed alongside.
- Few additions. The only non-FIBO terms are a
relationshipTypeon relationship records and the class of nested identifiers and classifiers.
Try it, and tell us what’s missing
These are Candidates: first, carefully sourced translations that are not yet official Smart Data Models subjects. Before that step, the main open questions are the overlap with the LegalEntity model of dataModel.VerifiableCredentials and with the Beneficial Ownership (BODS) candidate, and how strictly FIBO’s open-world axioms should become required fields. Natural next steps are accounts, listings and exchanges, bonds, collateral, and the ACTUS contract types.
Browse the models, open an issue, or send a PR:
👉 https://github.com/smart-data-models/Candidates/tree/master/standards/fibo

