001 · MODEL
IFC
4.3.2.0 · ADD2
Canonical model format. Buildings, bridges, road, rail, tunnel, ports. Identical to ISO 16739-1:2024.
Final · Apr 2024The standards we follow.
Gemeinwert pins the open standards the BIM-CVP protocol depends on: IFC for the model, BCF for coordination, IDS for requirements, ISO 19650 for the lifecycle. We don’t replace any of them.
We pin exact versions instead of generic ones, because “IFC4” isn’t specific enough to write test vectors against, and we want every implementer to know exactly which release we mean. The list below is the canonical choice. Legacy versions are supported on a read path; future versions are watched but not used until they are stable.
Pinned versions.
002 · COORDINATION
BCF API
3.0 · XML 3.0
Topics, comments, viewpoints, audit. Server speaks 3.0 native; 2.1 round-trip for legacy tools.
Final · Jun 2021003 · REQUIREMENTS
IDS
1.0
Machine-checkable information requirements. Replaces EIR PDFs. Versionable like code.
Final · Jun 2024004 · LIFECYCLE
ISO 19650
parts 1–5
WIP · Shared · Published · Archive. Approver authority encoded as a separate permission, not a write right.
Adopted005 · CDE
openCDE
Foundation 1.1
OAuth2, ETags, RFC3339, OData. Documents API 1.0 for binary handover. Client Credentials Grant intentionally not supported.
Final · Dec 2023006 · DICTIONARY
bSDD
live service
Multilingual classifications, properties, materials. Referenced by URI — we never fork the dictionary.
Live007 · INFORMATION NEED
EN 17412 / LOIN
project profile
Defines the right information at the right time. Regional templates can adapt it without changing the core event model.
Final008 · USE CASES
IDM / UCM
process references
Use cases and information exchanges explain why a model, IDS check or BCF topic exists in the workflow.
buildingSMARTWhy we pin versions.
Implementers stay in sync.
Two BCF clients both claiming to be “BCF 3.0 compatible” can still fail to round-trip if one was written against an early draft and the other against the final release. Pinning to 3.0 final, 18 June 2021, ends the argument.
Test vectors actually mean something.
You can’t write a conformance test against “IFC4.” You can write one against 4.3.2.0. The pinned version is what the test vectors validate.
Legacy projects still open.
IFC 2x3 TC1 and IFC4 ADD2 TC1 remain on the read path. A model from 2009 still opens in a modern reader. We don’t cut you off from your own building stock.
The full profile.
The complete standards profile lists every MVD, the conditional support cases for infrastructure projects, the openCDE API stack, the role model on both ISO 19650 and discipline axes, the rights and policy model, the audit and privacy obligations, and optional regional profile adapters. About fifteen pages.
Read the full profile →