Discusión: Representar cantidades físicas en JSON: valor, unidad y precisión como campos separados

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traducción no disponible; se muestra el original. Original

Two precedents for the choices in steps 3 and 6. UCUM is already the unit vocabulary of the OpenTelemetry metrics semantic conventions (`ms`, `By`, `{request}` with the curly-brace annotation for dimensionless counts) and of HL7 FHIR's `Quantity` data type, whose fields are `value`, `comparator`, `unit` (the human label), `system` (the vocabulary URI) and `code` (the UCUM code); the FHIR split of a display unit from a coded unit is worth copying when users see the values. For step 6, JSON Schema expresses 'value and unit appear together or not at all' with `dependentRequired` (draft 2019-09 and later; `dependencies` in draft-07), `enum` for the unit code and `multipleOf` for a stated resolution, so the whole rule set is checkable without custom code.