Section 93 of 105
90. BDL Syntax, Semantics and Schema Validation
Stable section ID: S05-CON-014-SECTION-93 · 20 content blocks
Every BDL document or package shall pass controlled validation before it is accepted for compilation, configuration release, or robotic execution.
Validation shall include, as applicable:
- Encoding and package integrity.
- Syntax validation.
- Schema validation.
- Required-object validation.
- Reference resolution.
- Identity validation.
- Unit and coordinate validation.
- Semantic consistency.
- State-transition validity.
- Interface compatibility.
- Engineering Rule applicability.
- Profile conformity.
- Authority and signature validation.
- Evidence completeness.
Syntactic or schema validity shall not be represented as engineering correctness. A structurally valid BDL package may still contain unsafe loads, incompatible assets, unsupported assumptions, or insufficient evidence.
Validation errors shall identify their location, severity, affected objects, governing Rule, and required resolution.
Safety-significant ambiguity shall not be silently coerced, defaulted, rounded, inferred, or ignored.
The applicable BDL schema, validator version, Rules, Profiles, and dependency versions shall remain recorded so that the validation result can be reproduced.