Financial Enterprise Ontology
Loads the full domain import closure through one governed enterprise module.
Download enterprise.ttl → SDS ontology distribution · 2026.08
The architecture is now a machine-readable ontology.
Download a reference financial enterprise ontology with a shared upper model, ten domain modules, executable SHACL constraints, SKOS vocabularies, industry mapping candidates, JSON-LD context, fictional sample graph and SPARQL queries.
16 Turtle files10 domain modules7 SHACL node shapes4 SPARQL queries
Ontology architecture
Modular for teams. Unified for AI.
Departments can evolve their own modules while every concept inherits shared identity, time, event, evidence and governance semantics.
Upper ontology
Identity, organization, events, observations, evidence, systems, policy, control and provenance.
Download upper.ttl →SHACL shapes
Constraints for market data, orders, holdings, signals, LEIs and cyber incidents.
Download shapes →SKOS taxonomies
Asset classes, order sides, signal directions and NIST CSF 2.0 functions.
Download vocabularies →Industry mappings
Reviewable candidates for FIBO, FIX, ISO 20022 and MITRE ATT&CK.
Download mappings →Sample graph and queries
Fictional signal, portfolio, order and cyber-impact data with four competency queries.
Download sample data →Domain ontology library
Every major financial data domain has a formal module.
Party & OrganizationIssuer · investor · broker · regulator · LEIFinancial InstrumentEquity · ETF · debt · option · listingMarket DataQuote · trade · order book · venue · timeCorporate EventEarnings · dividend · split · filing · newsPortfolioAccount · holding · position · benchmarkTradingOrder · execution · allocation · settlementRiskExposure · factor · limit · scenario · breachRegulatory & ComplianceObligation · control · evidence · reportingPrediction & SignalFeature · forecast · model · explanationCybersecurityAsset · threat · technique · incident · control
Evaluation workflow
Open, validate, query, then adapt.
Load the catalog and enterprise entrypoint in Protégé or an RDF tool.
Run the SHACL shapes against the fictional sample graph.
Execute the evidence, risk, cyber-impact and lineage queries.
Add client namespaces, source mappings, ownership and security policies.
Reference implementation, not a certified standard extension.
Production use requires client domain review, authoritative identifier decisions, mapping validation, external-license review, access-control design and regression testing. The sample is fictional and is not investment advice.
Need the enterprise version?
We tailor the ontology to your decisions and data.
Start with one domain and leave with a governed foundation your teams can extend.