Skip to content

Epic: QUDT Coverage & Validation #52

@veggerby

Description

@veggerby

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

  1. Expanded QUDT mapping table with new quantity kinds
  2. Validation tests confirming canonical unit alignment for all mappings
  3. Documentation of deliberate exclusions with rationale
  4. Updated docs/qudt-mapping-table.md with complete coverage status
  5. Inference rules for newly mapped kinds (where applicable)

Acceptance Criteria

  • Mapping table expanded with supporting tests for new kinds
  • Alignment tests fail on mismatched canonical units (fail-fast validation)
  • All deliberate exclusions are documented with clear rationale
  • New quantity kinds follow existing tag governance rules
  • Inference rules added for kinds that interact with existing kinds
  • No semantic conflicts introduced by new mappings

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

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions