This document is a static snapshot of the public FireBIM ontology registry page firebim.org/documentation/ontologies, taken on 7 September 2026. It is produced for ITEA progress reporting only.
Further ontology releases are in the pipeline. Version numbers, term counts and release statuses shown below will change. The newest version is always available online at firebim.org/documentation/ontologies.
All links in this file are live hotlinks to firebim.org — the version links point to the specific releases listed here, the “Browse latest version” buttons always resolve to the newest release.
The FireBIM Building Ontology (FBO) – the shared vocabulary that bridges national fire-safety regulations and building information models.
Every release is versioned and permanently available. Newest versions are listed first.
| Ontology | Role | Latest release | Status | Classes | Properties | Individuals | Triples | Releases |
|---|---|---|---|---|---|---|---|---|
| FBO — core | umbrella | 2026.09.04 | draft | 18 | 70 | 19 | 786 | 1 |
| FBO-BE — Belgium | national module | 2026.09.04 | draft | 21 | 42 | 9 | 977 | 2 |
| FBO-DK — Denmark | national module | 2026.09.04 | draft | 17 | 90 | 21 | 2 120 | 2 |
| FBO-LT — Lithuania | national module | 2026.09.04 | draft | 31 | 31 | 9 | 1 272 | 2 |
| FBO-NL — Netherlands | national module | 2026.09.04 | draft | 29 | 80 | 5 | 2 056 | 2 |
| FBO-PT — Portugal | national module | 2026.09.04 | draft | 44 | 93 | 7 | 2 394 | 2 |
| FBO → IFC 4.3 | alignment | 2026.09.04 | draft | 0 | 9 | 76 | 766 | 1 |
Summary compiled from the registry index; it is not part of the live page. Ontology names link to the live “latest version” page.
FBO covers national fire-safety terms and their legal definitions and serves as a bridge
between the terminology in regulatory documents and (BIM) modelling practice. Its core principle is an
overarching European umbrella ontology (fbo:) with national sub-ontologies
(fbo-be:, fbo-dk:, fbo-lt:, fbo-nl:,
fbo-pt:, …) underneath it. National terms are linked to the umbrella concepts with
fbo:isLinkedTo, which makes similarities and differences between countries explicit
without overwriting local legal definitions.
IFC is deliberately not inferred by default. How a fire-safety concept is expressed in IFC is kept in a separate alignment module, the FBO → IFC mapping, so that modellers can follow the official mapping or use their own.
One European umbrella, one module per country. Legal definitions stay national.
Releases are identified as YYYY.MM.DD with a status (draft, candidate, stable,
deprecated, withdrawn) – the same scheme as the FireBIM API.
app.firebim.org can pull these releases into your own FireBIM API with one click – no credentials needed to read this registry.
The European umbrella ontology. Country-agnostic fire-safety concepts (zones, elements,
systems, functions, quantities, fire-safety properties) that the national modules link back to via
fbo:isLinkedTo / fbo:hasSubitem.
Belgian fire-safety vocabulary with legal definitions, regulation references and links to the core FBO concepts and to IFC.
Danish fire-safety vocabulary (BR18 and guidelines) with Danish and English labels and definitions, regulation references and links to the core FBO concepts and to IFC.
Lithuanian fire-safety vocabulary with legal definitions, regulation references and links to the core FBO concepts and to IFC.
Dutch fire-safety vocabulary (Bbl) with legal definitions, regulation references and links to the core FBO concepts and to IFC.
Portuguese fire-safety vocabulary with legal definitions, regulation references and links to the core FBO concepts and to IFC.
Official mappings from FBO to other standards. Other mappings may exist – in the FireBIM platform every user can maintain their own.
The official alignment module. Each named individual describes how an FBO term is expressed in IFC 4.3: IFC class and predefined type, property set and property, data type, expected value and whether it is a buildingSMART standard property.
Everything on this page is generated from a small set of static JSON and Turtle files. They
are open, need no credentials, allow cross-origin requests and follow the URL structure of the FireBIM API
(/ontologies/{family}/{country}/versions/{version}). Versions are always sorted newest first.
| Resource | URL |
|---|---|
| Registry (all ontologies, all versions) | https://firebim.org/documentation/ontologies/index.json |
| One ontology (summary) | https://firebim.org/documentation/ontologies/{family}/{country}/index.json |
| Version list | https://firebim.org/documentation/ontologies/{family}/{country}/versions.json |
| Version metadata | https://firebim.org/documentation/ontologies/{family}/{country}/versions/{version}/metadata.json |
| Turtle file | https://firebim.org/documentation/ontologies/{family}/{country}/versions/{version}/{file}.ttl |
| Parsed terms (used by this viewer) | https://firebim.org/documentation/ontologies/{family}/{country}/versions/{version}/terms.json |
latest and stable are not folders on this static site: read
latest_version / latest_stable_version from the summary and follow
ttl_url. Each version carries a sha256 so a client can detect changes without
downloading the Turtle.
# list everything curl -s https://firebim.org/documentation/ontologies/index.json | jq '.ontologies[] | {ontology_family, country, latest_version}' # download the latest FBO-DK release curl -s https://firebim.org/documentation/ontologies/fbo/dk/index.json | jq -r .latest_ttl_url | xargs curl -sO # sync into your own FireBIM API (authenticated; see the API docs) curl -X POST https://api.firebim.org/ontologies/sync \ -H "Authorization: Bearer <token>" -H "Content-Type: application/json" \ -d '{"source_url": "https://firebim.org/documentation/ontologies/index.json"}'
The sync endpoint of the FireBIM API accepts any source_url that serves an index
in this format, so the same mechanism works for registries hosted elsewhere.