✅ Collection of validations
You are answering multiple related questions about the same filtered elements.
“Does this element comply with rule X, Y, and Z?”
Characteristics:
- Same filter
- Multiple validations
- Each validation can fail independently
- Multiple error messages per element
This is not for convenience. It is for cohesion.
2. The mental model users must learn
remember:
One validation = one contractual requirement
If you break that rule, your rule design is wrong.
Correct grouping
Use a collection only when:
- All validations belong to the same standard clause
- All validations target the same responsibility
- All validations should be read together in a report
Example (good):
-
NLRS Door Type:
-
Required shared parameters
- Correct data types
- Allowed values
That’s one conceptual requirement → multiple checks.
Incorrect grouping (very common mistake)
❌ “Let’s just add another check while we’re here”
Bad examples:
- Naming + fire rating + material + IFC export flag
- Geometry + parameters + classification
- Type rules mixed with instance rules
That creates:
- Unclear ownership
- Unclear fixes
- Angry BIM coordinators