17
Status undeclaredS05-CON-007UndeclaredSource imported
Section 29 of 102
28. Error and Validation Model
Stable section ID: S05-CON-007-SECTION-29 · 36 content blocks
- BDL validation shall occur in defined stages.
- Lexical Validation Verifies valid characters, tokens, literals, and comments.
- Syntax Validation Verifies grammar and document structure.
- Reference Validation Resolves identifiers, imports, namespaces, and versions.
- Type Validation Checks property Types, cardinality, and Entity classification.
- Unit Validation Checks physical dimensions and conversions.
- Semantic Validation Checks the engineering meaning of declarations and relationships.
- Profile Validation Applies applicable universal, regional, and project requirements.
- Configuration Validation Checks topology, dependencies, capabilities, states, and completeness.
- Evidence Validation Checks whether required claims are supported.
Errors shall have structured records containing:
Error ID;
error code;
severity;
document and source location;
affected Entity;
validation stage;
message;
violated rule;
proposed corrective guidance;
blocking status.
Severity levels shall include:
information;
advisory;
warning;
error;
critical error.
Example:
- BDL-E-UNIT-001
- Entity: Beam_B01
- Property: length
- Error: Expected Quantity<Length>; received Quantity<Force>.
- Location: structural.bdl:48:12
- Validation shall not silently correct engineering values.
Automatic corrections may be proposed, but the original value, proposed correction, responsible tool, and approval status shall remain visible.
A BDL document may be syntactically valid while remaining unsuitable for compilation, manufacturing, installation, or BIOS activation. Each validation stage shall therefore report its own status independently.