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

A.18:9 - Rationale

Defining a measurement template makes the aspect, Scale and value meaning available for later use. The receiving practitioner can reuse that definition instead of reconstructing it from the reported number. The following choices support that result:

  • Shared structure, distinct domain rules: a usability rating and a throughput measurement both identify an aspect, Scale and reading. Their common structure exposes the difference rather than supplying a common calculation or evidence rule.

  • Comparison and preference: Measurement comparison needs a common interpretation of the Characteristic, Scale and measurement conditions. A unit conversion can establish that interpretation across compatible presentations. Preference answers a further question: which result serves the intended use? The same temperature Scale supports identifying the hotter sample, choosing a cooling intervention or maintaining a target. Only the latter uses add a preferred direction or target rule.

  • Preserved information: an ordinal Scale states order without asserting distances. An interval or ratio model can support further calculations only when its additional assumptions are justified; wanting an average is not a reason to assume such a model.

  • Optional Levels: named tiers make category boundaries recoverable where the Scale uses them. A continuous measurement needs no Level labels unless a categorization is introduced.

  • Separate structure and method: the same CSLC structure can describe measurements made through different methods. Domain measurement patterns supply their procedures, applicability and evidence conditions; sharing the template does not make those methods interchangeable.