S1000D Schema, BREX and Completeness Validation
S1000D quality control normally combines structural validation, business-rule validation, reference and media completeness checks, and professional technical review.
How do the validation layers differ?
| Layer | Finds | Does not replace |
|---|---|---|
| Schema | Element order, required nodes, data types and structural constraints. | Technical correctness or safety review. |
| BREX and business rules | Project-specific values, coding restrictions and content constraints. | Every engineering exception or professional judgment. |
| Reference completeness | Missing objects, broken links, wrong versions, media and applicability gaps. | Field execution and maintainability assessment. |
| Technical review | Procedure sequence, warnings, diagrams, terminology and usability. | Bulk machine checks that can be automated. |
A practical quality gate
- Validate the module structure against the adopted Schema.
- Apply BREX and project code-list rules.
- Resolve references, media, versions and applicability.
- Review safety-critical and configuration-sensitive content.
- Record findings, corrections, rechecks and approval evidence.
A module that passes Schema is not automatically technically correct. Keep automated results and human approval records together so that a delivery baseline can be explained later.
Continue with DMC, CSDB and the publication guide.
Scope note: Validation behavior is determined by the adopted Issue, schemas, BREX, data dictionary, code lists and contract requirements.
Frequently asked questions
Does Schema validation prove that a manual is correct?
No. Schema checks structure. BREX checks project rules, while references, media, applicability and technical content require additional checks.
Can BREX replace technical review?
No. BREX can automate defined constraints, but professional review remains necessary for safety, sequence and engineering meaning.