Section 5 of 102
4. Language Philosophy
Stable section ID: S05-CON-007-SECTION-5 · 11 content blocks
BDL shall be based on the following language philosophy.
Declarative Rather Than Procedural BDL describes what exists, what is required, and what relationships are permitted. Execution belongs to the Engineering Compiler, Building BIOS, manufacturing systems, controllers, or robots.
Semantic Rather Than Drawing-Dependent An entity’s meaning shall not depend solely upon its graphical appearance, layer name, or drawing location.
Typed Rather Than Informal Every engineering entity and property shall have a defined type.
Unit-Aware Rather Than Unit-Assumed Engineering quantities shall carry explicit units or inherit them only through a formally declared unit context.
Identity-Centered Rather Than Name-Centered Persistent identity shall remain distinct from human-readable names and temporary authoring aliases.
Relationship-Oriented Rather Than File-Oriented The building shall be represented as entities connected through explicit spatial, structural, utility, control, dependency, and lifecycle relationships.
Extensible Without Semantic Conflict New domains may extend BDL through governed namespaces without redefining existing core meanings.
Human-Readable and Machine-Deterministic A qualified reader shall be able to inspect BDL, while independent compliant tools shall interpret the same valid document consistently.
Evidence-Aware Engineering statements shall be connected to their source, authority, uncertainty, and supporting evidence.
Lifecycle-Persistent BDL shall support evolution from design through manufacturing, construction, operation, modification, reuse, and decommissioning.