Jump to text
On this page
Copy and source
Published source confirmed at last check

Source changed 2026-11-18 21:11:39 UTC · snapshot created 2026-11-18 21:12:35 UTC · last check 2026-11-18 22:30:10 UTC

C.21:4.0a - One replay basis for every persisted coordinate

Every persisted, compared, aggregated or published C.16 measurement coordinate makes the following values recoverable. This is a field group, not another public kind. An ordinary non-measurement health claim retains its own support; writing or publishing it does not create a measurement chain:

DHCReplayBasis := <DisciplineRef, IntendedUse, ClaimScopeRef, ComparisonBasis, CharacteristicRef.edition, ScaleRef.edition, UnitRef.edition?, DHCMethodRef.edition, MethodRef, MethodDescriptionRef.edition?, MeasurementModelRef.edition?, CalibrationBasisRef?, TimeOrPopulationBasis, DHCDefinitionSetRef.edition?, TargetSliceRef?, DistanceDefRef.edition?>

  • DHCMethodRef.edition resolves the same Characteristic, Scale, Method, MethodDescription, model, calibration, and uncertainty semantics named by the active fields. A mismatch is not repaired by choosing one field as “primary.”
  • DHCDefinitionSetRef.edition appears only when a named reusable definition selection exists.
  • TargetSliceRef appears only when the named computation or publication consumes an A.2.6 selection. Every selected slice must be shown to belong to, or otherwise be covered by, the authoritative ClaimScope; the slice never substitutes for that scope.
  • DistanceDefRef.edition appears only when the Scale comparison or target-distance rule uses a separately declared distance.
  • Evidence paths, lane tags, currentness, assurance, acceptance, public names, and publication refs are added only when the receiving use consumes those separate results.