Goal
Improve coverage against the QUDT (Quantities, Units, Dimensions, and Types) mapping table.
Purpose
Align Veggerby.Units with the QUDT ontology to ensure interoperability with scientific and engineering systems using QUDT standards. Fill gaps in quantity kind coverage and validate canonical unit alignment for existing mappings.
Scope
- Map remaining unmapped kinds (e.g., radiation dose equivalents)
- Add validation tests to confirm canonical unit alignment
- Document any deliberate exclusions
Deliverables
- Expanded QUDT mapping table with new quantity kinds
- Validation tests confirming canonical unit alignment for all mappings
- Documentation of deliberate exclusions with rationale
- Updated
docs/qudt-mapping-table.md with complete coverage status
- Inference rules for newly mapped kinds (where applicable)
Acceptance Criteria
Technical Notes
- See
docs/qudt-alignment.md and docs/qudt-mapping-table.md for current status
- See
docs/quantity-kind-governance.md for tag naming rules
- Prioritize common/scientifically important kinds over obscure ones
- Validate dimension consistency with QUDT definitions
Risk & Mitigation
Risk: QUDT definitions may conflict with existing library semantics
Mitigation: Document conflicts clearly; prefer library consistency; provide mapping guidance
Risk: Too many quantity kinds may complicate the API surface
Mitigation: Focus on commonly used kinds; ensure each addition has clear use case and demand
Goal
Improve coverage against the QUDT (Quantities, Units, Dimensions, and Types) mapping table.
Purpose
Align Veggerby.Units with the QUDT ontology to ensure interoperability with scientific and engineering systems using QUDT standards. Fill gaps in quantity kind coverage and validate canonical unit alignment for existing mappings.
Scope
Deliverables
docs/qudt-mapping-table.mdwith complete coverage statusAcceptance Criteria
Technical Notes
docs/qudt-alignment.mdanddocs/qudt-mapping-table.mdfor current statusdocs/quantity-kind-governance.mdfor tag naming rulesRisk & Mitigation
Risk: QUDT definitions may conflict with existing library semantics
Mitigation: Document conflicts clearly; prefer library consistency; provide mapping guidance
Risk: Too many quantity kinds may complicate the API surface
Mitigation: Focus on commonly used kinds; ensure each addition has clear use case and demand