Section 54 of 104
52. BDL Reference Documents and Libraries
Stable section ID: S05-CON-016-SECTION-54 · 18 content blocks
System05 shall publish Reference BDL Documents and Libraries representing valid, invalid, incomplete, boundary, and historically versioned Building definitions.
Reference materials should include:
simple test Assemblies;
the Reference Building Configuration;
phased-expansion examples;
Node and Cartridge libraries;
Interface and Profile declarations;
Smart Module and sensor configurations;
manufacturing and assembly metadata;
lifecycle replacement examples;
controlled Deviations;
intentionally incompatible configurations.
Each reference document shall identify its schema, language Profile, governing rule set, intended outcome, and authority status.
Valid examples shall demonstrate recommended language use but shall not become hidden requirements beyond the normative BDL Specification.
Invalid examples shall identify the expected errors and whether they arise from syntax, schema, Compatibility, engineering rules, missing authority, or unresolved information.
Libraries shall preserve stable identifiers and semantic meaning across Versions. Deprecated entities shall remain interpretable for the required historical period.
Reference documents should be suitable for Compiler testing, education, software development, certification, and independent implementation.
No reference library shall include an unsafe default merely because it simplifies demonstration or reduces the number of required fields.