Skip to main content

Module version

Module version 

Source
Expand description

Which IFC schema version a file declares.

The token comes from the FILE_SCHEMA entry in a STEP header. Real files carry variants (IFC4X3_ADD2 as well as IFC4X3), so matching is explicit rather than a prefix test: IFC4X1 and IFC4X2 are their own releases, never a prefix match onto IFC4. Each release’s accepted tokens are its SCHEMA name as declared in its normative EXPRESS file (SCHEMA IFC4X1;, SCHEMA IFC4X2;), which is what ISO 10303-21 writes into FILE_SCHEMA.

§Known releases without a published schema

IFC4X3_TC1 (IFC 4.3.0.1) and IFC4X3_ADD1 (IFC 4.3.1.0) are real identifiers: buildingSMART’s IFC4.x-development generator wrote them as the SCHEMA name of the ISO build before IFC4X3_ADD2 (4.3.2.0). buildingSMART publishes no EXPRESS file for either, and their content differs from ADD2 (TC1 predates IfcGeographicCRS, IfcWellKnownText and others), so neither can have tables of its own nor be read as ADD2 by assumption. SchemaVersion::from_header_token does not recognise them; UnpublishedRelease::from_header_token names them, so a caller can refuse them precisely rather than as an unknown token (#467). A caller that chooses to read such a file as IFC4X3 ADD2 does so explicitly, by passing UnpublishedRelease::superseded_by’s tables itself, and owns that choice.

Enums§

SchemaVersion
Which IFC schema version a table describes.
UnpublishedRelease
An IFC release whose identifier is known but whose normative EXPRESS schema buildingSMART does not publish (#467).