Skip to main content

FIBO Mapping

The Financial Industry Business Ontology (FIBO) is an industry-standard, machine-readable ontology for the financial services industry. This page documents how Triodian domains map to FIBO concepts, enabling semantic interoperability and linked data capabilities.

Mapping file: triodian-FIBO.context.jsonld
Mapping Version: 1.0.0
Format: JSON-LD graph (RDF)

Overview​

What is FIBO?​

FIBO is developed by the EDM Council and Object Management Group (OMG) to provide:

  • Standardized definitions — Consistent meaning for financial concepts
  • Semantic relationships — Machine-readable connections between concepts
  • Regulatory alignment — Concepts aligned with financial regulations
  • Data interoperability — Enable data sharing across organizations

FIBO Modules​

ModuleAbbreviationScope
FoundationsFNDBasic concepts (parties, dates, agreements)
Business EntitiesBELegal entities, ownership, control
Financial Business & CommerceFBCProducts, services, transactions
SecuritiesSECSecurities instruments, markets
DerivativesDERDerivative instruments
LoansLOANLoan products and processes
Indices & IndicatorsINDMarket indices, economic indicators

Why Map to FIBO?​

BenefitDescription
Semantic precisionUnambiguous definitions for financial concepts
Regulatory complianceAlignment with regulatory reporting requirements
Data integrationEnable data exchange using common ontology
AI/ML readinessMachine-readable knowledge graphs

Domain Mappings​

The mapping file maps Triodian properties to FIBO terms (see Property Mappings). The domain-level alignments below are indicative: they show which FIBO classes a domain's records correspond to, and are not statements in the mapping file.

Core Domain Mappings​

Triodian DomainFIBO ModuleFIBO Class
OrganizationBEfibo-be-le-lei:LegalEntity
StakeholderFNDfibo-fnd-pty-pty:Party
ProductsFBCfibo-fbc-pas-pas:Product
ServicesFBCfibo-fbc-pas-pas:Service
InformationFNDfibo-fnd-arr-doc:Document
CustomerFBCfibo-fbc-pas-pas:Customer
PolicyFNDfibo-fnd-law-lcap:Policy

Extended Mappings​

Triodian DomainFIBO ClassNotes
Risk Managementfibo-fnd-gao-gl:RiskRisk concepts
Marketfibo-fbc-fi-fi:MarketMarket entities
Performancefibo-ind-ind-ind:IndicatorPerformance indicators
Value Streamfibo-fnd-gao-otp:ProcessProcess concepts

Property Mappings​

Every mapping in the file is a node stating that a Triodian property (triodian:<name>, an rdf:Property) corresponds to a FIBO term (triodian:mappedToFIBO), with the domains it is used in (triodian:domain). The table lists all 60 mappings in the file's order.

Triodian PropertyFIBO TermTriodian DomainDescription
titleskos:prefLabelAll DomainsPreferred label or name for concept or individual
descriptiondct:description / skos:definitionAll DomainsDescription or formal definition
orgUnitTitlefibo-be-oac-cpty:hasOrganizationalUnitOrganizationOrganisational division or unit
ownerfibo-fnd-rel-rel:isOwnedByOrganizationOwnership relationship
purposefibo-fnd-utl-av:hasPurposeAll DomainsGoal or intended outcome
inputsfibo-fnd-rel-rel:consumesValue Stream, ProcessRequired resources
outputsfibo-fnd-rel-rel:producesValue Stream, ProcessGenerated deliverables or results
performanceIndicatorsfibo-fnd-utl-alx:hasPerformanceIndicatorPerformanceKPI or other performance measure
strategicAlignmentfibo-fnd-utl-alx:isAlignedWithStrategyAlignment with strategic goals
dependenciesfibo-fnd-rel-rel:dependsOnCapabilities, InitiativesDependency relationship
relatedStrategiesfibo-fnd-rel-rel:isRelatedToCapabilities, InitiativesRelated strategy reference
risksfibo-fnd-gao-obj:hasRiskInitiativesAssociated risk
improvementOpportunitiesfibo-fnd-utl-alx:hasImprovementOpportunityPerformanceSuggested as a custom or annotation property
timelinefibo-fnd-dt-fd:hasDatePeriodInitiatives, StrategyProject or strategy duration
costfibo-fbc-pas-caa:hasMonetaryAmountFinance, InitiativesFinancial association
maturityLevelfibo-fnd-arr-asmt:hasAssessmentRatingCapabilitiesAssessment of maturity or readiness
goalsfibo-fnd-gao-obj:hasObjectiveStrategyStrategic goals
relatedValueStreamsfibo-bp-evd:isLinkedToProcessCapabilitiesSupporting or related processes
stakeholdersfibo-fbc-pas-fpas:hasStakeholderStakeholderInvolved or impacted parties
rolefibo-fnd-pty-rl:hasRoleStakeholderOrganisational or stakeholder role
channelfibo-fbc-pas-caa:hasCommunicationChannelChannelInteraction or delivery channel
serviceLevelAgreementsfibo-fbc-fct-fse:hasServiceLevelAgreementServicesDelivery expectations
processesfibo-bp-evd:hasProcessStepValue StreamComponent steps in a process
relatedPoliciesfibo-fnd-law-lcap:isConstrainedBy / fibo-fnd-law-cor:hasPolicyPolicyRelated governance policy
customerSegmentTypefibo-fbc-pas-fpas:hasCustomerClassificationCustomerSegmentation logic
acquisitionChannelsfibo-fbc-pas-caa:hasMarketingChannelCustomerLead generation source
customerLifetimeValuefibo-fbc-fct-fse:hasCustomerValueMetricPerformance, CustomerDerived financial metric
marketTrendsfibo-ind-ei-ei:exhibitsTrendMarketTrend insight
effectiveDatefibo-fnd-dt-fd:hasEffectiveDateAll DomainsDate when an entity or agreement becomes effective.
statusfibo-fnd-utl-av:hasStatusAll DomainsCurrent state or condition of an entity.
typefibo-fnd-utl-av:hasCategoryAll DomainsGeneral classification or category of an entity.
parentOrgUnitIDfibo-be-oac-cpty:hasParentUnitOrganizationHierarchical relationship to a superior organizational unit.
subOrgUnitIDsfibo-be-oac-cpty:hasSubUnitOrganizationHierarchical relationship to a subordinate organizational unit.
emailfibo-fnd-plc-loc:hasEmailAddressOrganization, StakeholderEmail address for contact.
phonefibo-fnd-plc-loc:hasTelephoneNumberOrganization, StakeholderTelephone number for contact.
expectedBenefitsfibo-fnd-agr-agr:hasBenefitsInitiativesExpected advantages or positive outcomes of an initiative.
completionDatefibo-fnd-dt-fd:hasCompletionDateInitiativesPlanned or actual date of completion for an initiative.
currencyfibo-fnd-acc-cur:hasCurrencyFinance, ProductsThe currency in which a financial instrument or amount is denominated.
dataTypefibo-fnd-agr-agr:hasRepresentationInformationThe format or type of data (e.g., text, numeric, date).
dataClassificationfibo-fnd-utl-av:hasSecurityClassificationInformationClassification of data based on its sensitivity or confidentiality.
policyTypefibo-fnd-agr-agr:hasAgreementTypePolicyThe category or nature of a policy.
riskTypefibo-fnd-ris-ris:hasRiskTypeRisk ManagementThe category or nature of a risk (e.g., operational, credit).
riskSeverityfibo-fnd-ris-ris:hasImpactRisk ManagementThe level of potential harm or consequence of a risk.
riskProbabilityfibo-fnd-ris-ris:hasProbabilityRisk ManagementThe probability or frequency of a risk occurring.
controlsfibo-fnd-agr-agr:hasControlMechanismRisk ManagementA mechanism or measure to reduce or manage a risk.
productFeaturesfibo-fbc-fep-rsvc:hasFeatureProductsKey characteristics or functionalities of a product.
pricingModelfibo-fbc-fep-rsvc:hasPricingMechanismProducts, ServicesMethod or structure used to determine the price of a product or service.
channelsfibo-fbc-fep-rsvc:isProvidedThroughProducts, Services, ChannelThe channel through which a product or service is delivered.
industryAnalysisfibo-ind-ei-ei:hasMarketInsightMarketAggregated market intelligence
identifierfibo-fnd-utl-av:hasTagAll DomainsUnique identifier for any entity
validUntilfibo-fnd-dt-fd:hasExpirationDateTriggerDate when an entity or agreement ceases to be effective
legalNamefibo-be-le-fbo:hasLegalNameOrganizationFormal legal name of an organization
registeredAddressfibo-fnd-plc-loc:hasPhysicalAddressOrganizationOfficial physical address for an organization
incorporationDatefibo-be-le-fbo:dateOfFormationOrganizationDate an organization was legally formed
jurisdictionOfEstablishmentfibo-fnd-plc-loc:hasJurisdictionOrganizationLegal jurisdiction where the organization is established
sourcesfibo-fnd-agr-agr:isProducedByInformationSystem that originates or produces information
scopefibo-fnd-agr-agr:appliesToInitiatives, PolicyThe range or extent of an initiative or policy
dataOwnerfibo-fnd-rel-rel:isOwnedByInformationThe party responsible for the data
dataStewardfibo-fnd-rel-rel:hasStewardInformationThe party responsible for the quality and governance of data
enforcedByfibo-fnd-agr-agr:hasPartyResponsibleForPolicyThe party responsible for enforcing the policy

Namespaces​

The file declares one Triodian namespace and the published FIBO module namespaces:

PrefixNamespace
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfshttp://www.w3.org/2000/01/rdf-schema#
skoshttp://www.w3.org/2004/02/skos/core#
dcthttp://purl.org/dc/terms/
fibo-behttps://spec.edmcouncil.org/fibo/ontology/BE/
fibo-fndhttps://spec.edmcouncil.org/fibo/ontology/FND/
fibo-fbchttps://spec.edmcouncil.org/fibo/ontology/FBC/
fibo-bphttps://spec.edmcouncil.org/fibo/ontology/BP/
fibo-indhttps://spec.edmcouncil.org/fibo/ontology/IND/
triodianhttps://triodian.com/ontology#

Concepts Not Mapped​

Ten financial-account and transaction concepts from earlier versions of the mapping are deliberately not mapped: accountHolder, accountType, assetClass, balance, customerData, marketQuote, maturityDate, transactionAmount, transactionDate and transactionType. They describe individual financial instruments, accounts and transactions. These are operational data rather than business architecture, so the metamodel has no fields for them. The repository's interoperability README records this and the other corrections to the file.

JSON-LD Examples​

Mapping Entries​

Each entry in the mapping file has this form. These are the Risk Management entries, copied from the file's @graph:

{
"@graph": [
{
"@id": "triodian:riskType",
"@type": "rdf:Property",
"rdfs:label": "riskType",
"rdfs:comment": "The category or nature of a risk (e.g., operational, credit).",
"triodian:domain": "Risk Management",
"triodian:mappedToFIBO": "fibo-fnd-ris-ris:hasRiskType"
},
{
"@id": "triodian:riskSeverity",
"@type": "rdf:Property",
"rdfs:label": "riskSeverity",
"rdfs:comment": "The level of potential harm or consequence of a risk.",
"triodian:domain": "Risk Management",
"triodian:mappedToFIBO": "fibo-fnd-ris-ris:hasImpact"
},
{
"@id": "triodian:riskProbability",
"@type": "rdf:Property",
"rdfs:label": "riskProbability",
"rdfs:comment": "The probability or frequency of a risk occurring.",
"triodian:domain": "Risk Management",
"triodian:mappedToFIBO": "fibo-fnd-ris-ris:hasProbability"
},
{
"@id": "triodian:controls",
"@type": "rdf:Property",
"rdfs:label": "controls",
"rdfs:comment": "A mechanism or measure to reduce or manage a risk.",
"triodian:domain": "Risk Management",
"triodian:mappedToFIBO": "fibo-fnd-agr-agr:hasControlMechanism"
}
]
}

Organization Entity​

An Organization record's legal details expressed with the FIBO terms its properties map to (legalName, registeredAddress, incorporationDate, jurisdictionOfEstablishment):

{
"@context": {
"fibo-be-le-lei": "https://spec.edmcouncil.org/fibo/ontology/BE/LegalEntities/LEIEntities/",
"fibo-be-le-fbo": "https://spec.edmcouncil.org/fibo/ontology/BE/LegalEntities/FormalBusinessOrganizations/",
"fibo-fnd-plc-loc": "https://spec.edmcouncil.org/fibo/ontology/FND/Places/Locations/",
"skos": "http://www.w3.org/2004/02/skos/core#",
"triodian": "https://triodian.com/ontology#"
},
"@type": "fibo-be-le-lei:LegalEntity",
"@id": "https://example.com/organizations/ORG-001",
"triodian:organizationID": "ORG-001",
"skos:prefLabel": "ACME Financial Services",
"fibo-be-le-fbo:hasLegalName": "ACME Financial Services Ltd",
"fibo-fnd-plc-loc:hasPhysicalAddress": "1 Collins Street, Melbourne VIC 3000",
"fibo-be-le-fbo:dateOfFormation": "1998-03-01",
"fibo-fnd-plc-loc:hasJurisdiction": "Australia"
}

SPARQL Query Examples​

Find Organizations by Jurisdiction​

PREFIX fibo-be-le-lei: <https://spec.edmcouncil.org/fibo/ontology/BE/LegalEntities/LEIEntities/>
PREFIX fibo-be-le-fbo: <https://spec.edmcouncil.org/fibo/ontology/BE/LegalEntities/FormalBusinessOrganizations/>
PREFIX fibo-fnd-plc-loc: <https://spec.edmcouncil.org/fibo/ontology/FND/Places/Locations/>

SELECT ?org ?legalName ?jurisdiction
WHERE {
?org a fibo-be-le-lei:LegalEntity .
?org fibo-be-le-fbo:hasLegalName ?legalName .
?org fibo-fnd-plc-loc:hasJurisdiction ?jurisdiction .
}

List the Mappings for a Domain​

Loaded into a triple store, the mapping file itself can be queried, for example for every Risk Management property and its FIBO term:

PREFIX triodian: <https://triodian.com/ontology#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>

SELECT ?property ?fiboTerm
WHERE {
?p rdfs:label ?property ;
triodian:domain ?domain ;
triodian:mappedToFIBO ?fiboTerm .
FILTER(CONTAINS(?domain, "Risk Management"))
}

Usage Guidelines​

When to Use FIBO Mappings​

  • Regulatory reporting — BCBS 239, MiFID II, Dodd-Frank data requirements
  • Data exchange — Industry data sharing initiatives
  • Knowledge graphs — Building semantic financial knowledge bases
  • AI/ML applications — Training models with standardized concepts

Implementation Considerations​

  1. Namespace management — Use the published FIBO namespace URIs (https://spec.edmcouncil.org/fibo/ontology/…) and the Triodian namespace https://triodian.com/ontology#
  2. Version tracking — FIBO releases quarterly; track version alignment
  3. Extension patterns — Extend FIBO classes for Triodian-specific properties
  4. Validation — Use OWL reasoners to validate mappings
For Data Engineers

FIBO provides the semantic foundation for financial data catalogs. When integrating with OpenMetadata, FIBO classes can serve as business glossary terms, enabling consistent definitions across technical and business metadata.