Protocol

Keep the unit attached when moving the number

The number 500 is impressively precise about almost nothing on its own.

About 1 min read

Before you use it

Use when
  • A value crosses a system boundary, report or manual calculation.

Keep this limit in mind

  • Currencies, temperature scales and business-specific units may need context beyond a simple multiplier. Do not improvise safety-critical conversions.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Carry the unit and the quantity definition with the value. Convert only after confirming that both sides measure the same kind of quantity. A correct conversion cannot repair a comparison between different business definitions.

Steps

  1. Record value, unit and what was measured together.
  2. Name the target unit and the documented conversion rule.
  3. Check one known example and preserve the original value for reconciliation.

An example

A duration of 500 milliseconds becomes 0.5 seconds, not 500 seconds. Separately confirm whether both systems include waiting time.

Check your result

The receiver can reconstruct the value's meaning and distinguish conversion from a changed measurement definition.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingKeep the unit attached when moving the number

Evidence and sources
Supports

UCUM distinguishes unit symbols, prefixes and semantic equivalence so numeric quantities can be interpreted with their units.

Compatible physical dimensions do not establish matching business definitions, measurement conditions or conversion dates.

The Unified Code for Units of Measure · Unit terms and semantic rules

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details