Umi‑Time Technical Specification

Version 1.0

Status
Candidate
Date
2026-11-01
License
Creative Commons Attribution 4.0 International Public License (see Licensing)

  1. Overview

    Umi‑Time is a UTC‑based standard that represents the UTC day as a continuous 360‑umi cycle. This uniform mapping ensures that umi values advance at a constant rate everywhere on Earth, independent of the varying length of the physical solar day. Umi‑Time does not define a new time scale; it provides an alternative representation of UTC in which every Umi‑Time value corresponds exactly to one UTC time of day.

    Umi‑Time is organized as a layered representation model. UTC provides the underlying universal time reference. Umi‑Time expresses that reference as a continuous 360‑umi cycle. Additional layers may then provide local interpretation and optional solar context without altering the underlying Umi‑Time value.

    Local interpretation is determined solely by the observer's longitude. Longitude establishes the relationship between the universal Umi‑Time coordinate and the observer's local day, while preserving the same Umi‑Time value for all observers.

    Solar geometry—including sunrise and sunset, twilight phases, and physical solar noon—is computed independently from the Umi‑Time coordinate. Solar context may be used to enrich local interpretation but does not affect the rate of Umi‑Time progression or the longitude‑based local interpretation.

    Together, these layers allow Umi‑Time to be both globally uniform and locally meaningful: a single universal time representation enriched by geographic and astronomical context. This specification defines:

    • the Umi‑Time standard
    • the layered representation model
    • the computational model
    • the local interpretation rules
    • the solar context model
    • reference presentation guidance
    • the textual representation and conformance requirements

    Umi‑Time is an open standard. Anyone may implement it.

    The key words “shall”, “should”, and “may” in this specification are to be interpreted as in the ISO/IEC Directives, Part 2: “shall” denotes a requirement, “should” a recommendation, and “may” a permission. Examples, notes, and text marked informative impose no requirements.

  2. Definitions

    1. Umi‑Time Umi

      Umi is the basic unit of Umi‑Time, denoted by ᵘ. The UTC day is divided into 360 equal umi units, which advance uniformly over the 24‑hour UTC reference day.

      The continuous Umi‑Time coordinate (UT) may assume fractional values. Integer umi values represent the whole‑umi component of UT and form the basis of standard Umi‑Time representations.

      Umi units are a rescaling of UTC. They do not measure Earth's actual rotation and do not vary with the length of the physical solar day. They provide a universal, constant measure of progress through the UTC day.

    2. Umi‑Time Second

      The subdivision of an umi used in textual representations, equal to 1/240 of an umi. One Umi‑Time second (umi‑second) corresponds to exactly one SI second. Umi‑seconds are numbered 000–239 within each umi and may carry a decimal fraction.

    3. UT

      UT is the canonical continuous representation of Umi‑Time and the standard abbreviation used throughout this specification.

      UT may assume fractional values and retains the precision of the underlying UTC timestamp. Integer umi values and umi‑seconds are derived representations of this continuous coordinate.

    4. Umi‑Time Noon

      The longitude‑dependent umi value corresponding to the midpoint of the local Umi‑Day.

    5. Umi‑Time Midnight

      The longitude‑dependent umi value corresponding to the boundary between consecutive Umi‑Day cycles.

    6. Umi‑Day

      The continuous time span between one Umi‑Time Midnight and the next Umi‑Time Midnight at a given longitude. It represents the complete longitude‑aligned cycle of Umi‑Time for that location.

    7. Umi‑Date

      The civil calendar date associated with a specific Umi‑Day. The Umi‑Date for a given Umi‑Day is the UTC calendar date in effect at Umi‑Time Noon for that longitude. Each Umi‑Day has exactly one Umi‑Date.

    8. Physical Solar Noon

      The moment when the Sun reaches its highest altitude relative to the horizon at a given location. This moment may not coincide with Umi‑Time noon due to the equation of time.

    9. Physical Solar Midnight

      The moment when the Sun reaches its lowest altitude relative to the horizon at a given location. This moment may not coincide with Umi‑Time midnight due to the equation of time.

    10. Physical Solar Day

      The interval between two successive physical solar noons at a given longitude.
      Its length varies slightly throughout the year due to orbital eccentricity and axial tilt.

      Umi‑Time does not adjust its umi progression based on the varying length of the physical solar day. However, the physical solar‑day variation affects sunrise and sunset times slightly.

    11. Sunrise / Sunset

      The moments when the Sun’s upper limb crosses the horizon, corrected for atmospheric refraction.

  3. Core Concepts

    Umi‑Time is organized as a layered representation model. Each layer adds meaning without modifying the information contained in the layers below it. This separation allows a single universal time value to coexist with locally meaningful interpretation and optional solar context.

    • Layer 0 — UTC: The universal time reference.
    • Layer 1 — Umi‑Time Representation: A continuous 360‑umi representation of the UTC day.
    • Layer 2 — Local Interpretation: Longitude‑based local context that relates the universal Umi‑Time value to an observer's day.
    • Layer 3 — Solar Context: Optional astronomical context derived from location and date.

    Higher layers may add interpretation, but shall not modify information contained in lower layers.

    1. UTC Layer

      UTC provides the underlying universal time reference from which Umi‑Time is derived. It remains the authoritative temporal coordinate and is shared identically by all observers.

      Umi‑Time does not replace UTC and does not define a new time scale. Instead, it provides an alternative representation of the UTC day.

    2. Umi‑Time Representation Layer

      The UTC day is represented as a continuous 360‑umi cycle mapped uniformly across a 24‑hour UTC day.

      1 umi = 1/360 of a 24‑hour UTC day

      This uniform mapping ensures that Umi‑Time advances at a constant rate, remains intuitive, and maintains an exact correspondence with UTC.

      The resulting Umi‑Time coordinate is universal. Every observer shares the same Umi‑Time value at the same moment regardless of location.

    3. Local Interpretation Layer

      Longitude provides local context without altering the underlying Umi‑Time value. This layer relates the universal Umi‑Time coordinate to an observer's local day.

      Different forms of presentation may realize this layer in different ways. Analog, digital, textual, and cartographic representations can all express the same longitude‑derived local interpretation.

    4. Solar Context Layer

      Solar context provides optional astronomical information derived from the observer's location and date. This context may include sunrise, sunset, twilight, daytime, nighttime, and related solar events.

      Solar context augments interpretation but never alters either the universal Umi‑Time value or the longitude‑based local interpretation.

    5. Derived Local Concepts

      Umi‑Time does not define a global solar‑day boundary. When a calendar date is combined with a Umi‑Time value, the date may be interpreted either as the universal UTC calendar date or as the observer's Umi‑Date, depending on whether local context is included.

      Umi‑Day, Umi‑Date, Umi‑Time noon, and Umi‑Time midnight are longitude‑dependent local interpretations derived from the universal UT coordinate.

  4. Umi‑Time Transformation

    This section defines the requirements for Layer 1 of the Umi‑Time model: the transformation of UTC into a continuous Umi‑Time coordinate.

    Umi‑Time uses a direct, uniform mapping from the UTC day into a continuous 360‑umi cycle. This mapping ensures that Umi‑Time advances at a constant rate, remains easy to reason about, and maintains an exact correspondence with UTC.

    1. Direct UTC Mapping

      Umi‑Time uses SI seconds as its underlying physical time unit. All computations are performed using UTC seconds-of-day.

      The continuous Umi‑Time coordinate (UT) is computed as:

      UT = 360ᵘ × (UTC_seconds_of_day / 86400s)

      Where:

      • UTC_seconds_of_day is the number of elapsed SI seconds since 00:00:00 UTC.
      • 86400 is the number of SI seconds in a nominal UTC day.

      This mapping establishes a direct correspondence between UTC and Umi‑Time, allowing conversion in either direction without loss of precision.

    2. Textual Representation Components

      For textual representations, the umi and umi‑second components are derived from the same continuous coordinate:

      umi        = ⌊UTC_seconds_of_day / 240⌋
      umi-second = UTC_seconds_of_day mod 240

      When UTC_seconds_of_day includes a fractional part, that fraction is carried by the umi‑second.

      The inverse conversion is exact:

      UTC_seconds_of_day = umi × 240 + umi-second
    3. Continuous Cycle

      UT is a continuous value that increases smoothly throughout the day. To keep it within a single 360‑umi cycle, it is normalized using:

      UT = UT mod 360ᵘ

      This wrap‑around ensures that the measure remains continuous, with no discontinuity as the value transitions from the end of one cycle to the beginning of the next.

    4. Layer Independence

      The Layer 1 Umi‑Time coordinate is universal and location‑independent. Local interpretation and solar context are defined by higher layers of the Umi‑Time model and do not affect the computation, progression, or rate of change of UT.

      This separation ensures that all observers share the same Umi‑Time value at the same moment regardless of longitude, latitude, or local solar conditions.

  5. Local Longitude‑Based Presentation

    This section defines the requirements for Layer 2 of the Umi‑Time model: the derivation of local context from longitude.

    Umi‑Time values are universal and remain identical for all observers at the same moment. Layer 2 provides local interpretation by relating the universal Umi‑Time coordinate to an observer's longitude.

    Longitude alone determines local interpretation. Solar geometry, date, season, sunrise, sunset, twilight, and other astronomical events have no influence on Layer 2 calculations.

    1. Longitude Relationship

      Local interpretation is derived directly from the observer's longitude. Longitude establishes the relationship between the universal UT coordinate and the observer's local day.

      This relationship defines:

    2. Independence from Solar Context

      Local interpretation is determined solely by longitude and remains independent of Layer 3 solar context.

      Solar events such as sunrise and sunset, twilight phases, physical solar noon, and physical solar midnight do not affect the computation of Umi‑Time noon, Umi‑Time midnight, Umi‑Day, or Umi‑Date.

    3. Presentation Flexibility

      Implementations may present Layer 2 local interpretation using analog, digital, textual, cartographic, or other visual forms.

      Regardless of presentation format, all conforming implementations shall preserve the same longitude-derived relationship between the universal UT coordinate and the observer's local day.

  6. Solar Context

    This section defines the requirements for Layer 3 of the Umi‑Time model: optional solar context derived from the observer's location, date, and the apparent position of the Sun.

    Solar context enriches local interpretation by providing information about daylight, twilight, and solar events. It does not affect the computation of UT or the longitude‑based local interpretation defined by Layer 2.

    1. Solar Geometry Inputs

      The Umi‑Time coordinate itself requires only UTC. Solar context requires the following astronomical inputs:

      • Latitude (\(\phi\)) — Observer's north-south position on Earth.
      • Longitude (\(\lambda\)) — Observer's east-west position on Earth.
      • Solar declination (\(\delta\)) — Sun's angular position north or south of the celestial equator.
      • Equation of Time (EoT) — Difference between apparent solar time and mean solar time.
      • Solar hour angle (H) — Angular distance of the Sun east or west of physical solar noon.
      • Solar altitude (\(\alpha\)) — Angle of the Sun above the horizon.
      • Solar azimuth (A) — Compass direction of the Sun along the horizon.
      • Julian date (JD) — Continuous astronomical day count used for solar calculations.

      These values may be obtained from standard solar-position algorithms, including:

      • NOAA Solar Calculator
      • NREL SPA (Solar Position Algorithm)
      • Meeus Astronomical Algorithms
    2. Solar Geometry

      This section defines the solar-geometry quantities required for computing solar events and periods. All formulas are self-contained and require only the observer's location and the UTC date and time.

      Note on trigonometric notation: Trigonometric functions written with a degree symbol (e.g. sin°(x), cos°(x), tan°(x)) interpret their arguments as degrees rather than radians. Inverse trigonometric functions likewise return degrees. Programming implementations will typically require conversion to radians when using standard library functions.

      Evaluation time: Time-dependent quantities below (particularly \(\delta\) and EoT) shall be evaluated at the UTC instant of the event being computed. Implementations shall first evaluate them at 12:00 UTC on the date of interest to obtain an initial estimate of the event time, then re-evaluate at the estimated event time and recompute the event. One such iteration is sufficient to meet the accuracy requirements of this specification.

      1. Julian Date

        The Julian Date (JD) is the continuous count of days since noon on 1 January 4713 BC (proleptic Julian calendar); the Julian Century \(T\) is measured from the J2000.0 epoch. Start by separating the date into year, month, day, hour, minutes and seconds components, combining the hours, minutes and seconds into a value representing a partial day. The symbols in this subsection are local to the Julian Date computation.

        \[ Y = \text{year} \] \[ M = \text{month (1-12)} \] \[ D = \text{day (1-31)} \] \[ h = \text{hour (0-23)} \] \[ m = \text{minutes (0-59)} \] \[ s = \text{seconds (0-59)} \] \[ t = h + \frac{m}{60} + \frac{s}{3600} \]

        If the month is January or February, treat it as the 13th or 14th month of the previous year:

        \[ \text{if } M \leq 2, \text{ then } Y' = Y - 1, M' = M + 12 \text{, else } Y' = Y, M' = M \]

        Next, compute the factors A, B, C and E as follows:

        \[ A = \left\lfloor \frac{Y'}{100} \right\rfloor \] \[ B = 2 - A + \left\lfloor \frac{A}{4} \right\rfloor \] \[ C = \left\lfloor 365.25 \cdot (Y' + 4716) \right\rfloor \] \[ E = \left\lfloor 30.6001 \cdot (M' + 1) \right\rfloor \]

        Finally, compute the Julian Date:

        \[ JD = D + B + C + E - 1524.5 + \frac{t}{24} \]

        For convenience, the Julian Century is:

        \[ T = \frac{JD - 2451545.0}{36525} \]

      2. Solar Mean Longitude

        \[ L_0 = 280.46646^\circ + 36000.76983^\circ \cdot T + 0.0003032^\circ \cdot T^2 \]

      3. Solar Mean Anomaly

        \[ M = 357.52911^\circ + 35999.05029^\circ \cdot T - 0.0001537^\circ \cdot T^2 \]

      4. Earth Orbit Eccentricity

        \[ e = 0.016708634 - 0.000042037 \cdot T - 0.0000001267 \cdot T^2 \]

      5. Sun’s Equation of Center

        \[ C = \sin^\circ(M) \cdot (1.914602 - T \cdot (0.004817 + 0.000014 \cdot T)) + \sin^\circ(2M) \cdot (0.019993 - 0.000101 \cdot T) + \sin^\circ(3M) \cdot 0.000289 \]

      6. Ecliptic Longitude of the Sun

        \[ \lambda_\odot = L_0 + C \]

      7. True Anomaly of the Sun

        \[ \nu = M + C \]

      8. Radius Vector of the Sun

        \[ r = \frac{1.000001018 \cdot (1 - e^2)}{1 + e \cdot \cos^\circ(\nu)} \]

      9. Apparent Longitude of the Sun

        \[ \lambda_{\text{sun}} = \lambda_\odot - 0.00569^\circ - 0.00478^\circ \cdot \sin^\circ(125.04^\circ - 1934.136^\circ \cdot T) \]

      10. Mean Obliquity of the Ecliptic

        \[ \epsilon_0 = 23 + \frac{26 + \frac{21.448 - T \cdot (46.815 + T \cdot (0.00059 - T \cdot 0.001813))}{60}}{60} \]

      11. Obliquity Correction

        \[ \epsilon = \epsilon_0 + 0.00256^\circ \cdot \cos^\circ(125.04^\circ - 1934.136^\circ \cdot T) \]

      12. Right Ascension of the Sun

        \[ \alpha = \operatorname{atan2}^\circ\left( \cos^\circ(\epsilon) \cdot \sin^\circ(\lambda_{\text{sun}}), \cos^\circ(\lambda_{\text{sun}}) \right) \]

      13. Solar Declination

        \[ \delta = \arcsin^\circ\left( \sin^\circ(\epsilon) \cdot \sin^\circ(\lambda_{\text{sun}}) \right) \]

      14. Obliquity Coefficient

        \[ y = \left( \tan^\circ\left( \frac{\epsilon}{2} \right) \right)^2 \]

      15. Equation of Time

        The Equation of Time (EoT) expresses the difference between apparent solar time and mean solar time, in minutes. The bracketed term is an angle in radians; the factor \(180/\pi\) converts it to degrees and the factor 4 converts degrees to minutes of time:

        \[ \text{EoT} = 4 \cdot \frac{180}{\pi} \left( y \sin^\circ(2L_0) - 2e \sin^\circ M + 4ey \sin^\circ M \cos^\circ(2L_0) - 0.5y^2 \sin^\circ(4L_0) - 1.25 e^2 \sin^\circ(2M) \right) \]

    3. Solar Events

      Solar events are expressed as UT values and therefore relate directly to the universal Umi‑Time coordinate.

      1. Sunrise / Sunset Hour Angle

        The sunrise/sunset hour angle \(H_0\) is computed using standard solar‑position equations:

        \[ H_0 = \arccos^\circ\left( \frac{\sin^\circ h_0 - \sin^\circ\phi \cdot \sin^\circ\delta} {\cos^\circ\phi \cdot \cos^\circ\delta} \right) \]

        Where:

        • \(\phi\) = latitude
        • \(\delta\) = solar declination
        • \(h_0\) = altitude threshold (≈ −0.833° including refraction)

        Note: The hour angle is undefined when the argument of \(\arccos^\circ\) lies outside \([-1, 1]\), i.e. when the Sun is circumpolar at the threshold \(h_0\). If the argument is less than \(-1\) the Sun remains above \(h_0\) for the whole day (no sunset); if it is greater than \(+1\) the Sun remains below \(h_0\) for the whole day (no sunrise). Implementations shall detect both cases, skip the sunrise/sunset calculations, and distinguish them as continuous daylight or continuous darkness conditions.

      2. Physical Solar Midnight (Umi‑Time)

        \[ UT_{\text{solar\,mid}} = \left( \left( -\lambda - \left( \text{EoT} \times \frac{1^\circ}{4\ \text{min}} \right) \right) \times \frac{1^\mathrm{u}}{1^\circ} + 360^\mathrm{u} \right) \bmod 360^\mathrm{u} \]

        This is distinct from Umi‑Time midnight \(UT_{\text{mid}}\), which depends on longitude only.

      3. Physical Solar Noon (Umi‑Time)

        \[ UT_{\text{noon}} = \left( \left( 180^\circ - \lambda - \left( \text{EoT} \times \frac{1^\circ}{4\ \text{min}} \right) \right) \times \frac{1^\mathrm{u}}{1^\circ} + 360^\mathrm{u} \right) \bmod 360^\mathrm{u} \]

      4. Sunrise Time (Umi‑Time)

        Sunrise occurs \(H_0\) degrees before physical solar noon, converted to umi:

        \[ UT_{\text{sunrise}} = \left( UT_{\text{noon}} - \left( H_0 \times \frac{1^\mathrm{u}}{1^\circ} \right) + 360^\mathrm{u} \right) \bmod 360^\mathrm{u} \]

      5. Sunset Time (Umi‑Time)

        Sunset occurs \(H_0\) degrees after physical solar noon, converted to umi:

        \[ UT_{\text{sunset}} = \left( UT_{\text{noon}} + \left( H_0 \times \frac{1^\mathrm{u}}{1^\circ} \right) + 360^\mathrm{u} \right) \bmod 360^\mathrm{u} \]

      6. Daylight Length (Umi‑Time)

        Daylight length is twice the sunrise/sunset hour angle, expressed in umi:

        \[ \text{Daylight Length} = 2 H_0 \times \frac{1^\mathrm{u}}{1^\circ} \]

    4. Twilight Periods

      Twilight boundaries are defined using solar-altitude thresholds:

      • Astronomical: \( h = -18^\circ \)
      • Nautical: \( h = -12^\circ \)
      • Civil: \( h = -6^\circ \)
      • Blue hour (informative convention): \( h \approx -4^\circ \)
      • Golden hour (informative convention): \( h \approx +6^\circ \)

      The general hour-angle formula is:

      \[ H(h) = \arccos^\circ\!\left( \frac{ \sin^\circ h - \sin^\circ\phi \cdot \sin^\circ\delta }{ \cos^\circ\phi \cdot \cos^\circ\delta } \right) \]

      Morning and evening event times are derived from physical solar noon using the formulas defined below.

      Morning event (Umi‑Time):

      \[ UT_{\text{event, AM}} = \left( UT_{\text{noon}} - \left( H(h) \times \frac{1^\mathrm{u}}{1^\circ} \right) + 360^\mathrm{u} \right) \bmod 360^\mathrm{u} \]

      Evening event (Umi‑Time):

      \[ UT_{\text{event, PM}} = \left( UT_{\text{noon}} + \left( H(h) \times \frac{1^\mathrm{u}}{1^\circ} \right) + 360^\mathrm{u} \right) \bmod 360^\mathrm{u} \]

      Circumpolar behavior shall be handled as specified in the Polar Conditions section.

    5. Polar Conditions

      At extreme latitudes, some solar events may not occur on a particular date. Sunrise, sunset, and twilight boundaries become undefined when the corresponding hour-angle calculation falls outside the valid domain of the inverse cosine function.

      For any hour-angle calculation of the form:

      \[ H = \arccos^\circ(x) \]

      the result is defined only when:

      \[ -1 \le x \le 1 \]

      Implementations shall detect and distinguish the following conditions:

      • Continuous daylight — the argument is less than \(-1\), indicating that the Sun remains above the relevant altitude threshold throughout the entire day.
      • Continuous darkness — the argument is greater than \(+1\), indicating that the Sun remains below the relevant altitude threshold throughout the entire day.

      When either condition occurs, the corresponding solar event or boundary shall be treated as undefined and shall not be computed.

      This behavior applies to sunrise, sunset, and all twilight boundaries defined by this specification.

  7. Accuracy Requirements

    1. Solar Position Accuracy

      Solar-position accuracy affects the computation of sunrise, sunset, physical solar noon, physical solar midnight, twilight boundaries, and other solar-context information defined by this specification.

      Implementations should achieve:

      • ±0.1° solar azimuth accuracy
      • ±0.1° solar altitude accuracy
      • ±10 second sunrise/sunset accuracy

      These values are achievable using the self-contained solar-geometry formulas provided in this specification and are sufficient for accurate computation and presentation of solar context in conforming implementations.

    2. Time Synchronization

      UTC time input should be synchronized to a reliable time source such as:

      • NTP
      • GPS
      • Operating-system system clocks

      Accurate UTC synchronization is required to ensure correct computation of UT and all derived Umi‑Time values.

  8. Textual representation of Umi‑Time

    1. Scope

      This section specifies the textual representations of Umi‑Time for use in data interchange, documentation, and user interfaces. It defines the normative formats for expressing Umi‑Time as a standalone value, as well as its combination with a calendar date. The formats described herein include both basic and extended representations, optional local context suffixes, and rules for disambiguation when Umi‑Time and UTC time may appear in the same context.

      The representations defined in this section are patterned after the conventions of ISO 8601 and are intended to be compatible with future extensions of that standard. These representations do not redefine UTC time, do not modify the semantics of ISO 8601 date formats, and do not impose requirements on systems that do not implement Umi‑Time.

      This section does not specify computational methods for determining Umi‑Time, nor does it define algorithms for converting between Umi‑Time and UTC time. Such methods are defined elsewhere in this specification. The present section concerns only the normative syntax, structure, and interpretation of Umi‑Time textual formats.

    2. Normative references

      The following referenced documents are indispensable for the application of this section. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies.

      • ISO 8601‑1, Date and time — Representations for information interchange — Part 1: Basic rules
      • ISO 8601‑2, Date and time — Representations for information interchange — Part 2: Extensions
      • ISO 80000‑3, Quantities and units — Part 3: Space and time
      • ISO/IEC 14977, Extended Backus–Naur Form (EBNF) — Syntax notation
      • ITU‑R Recommendation TF.460, Standard‑frequency and time‑signal emissions (definition of UTC)

      Informative references to astronomical models, solar ephemerides, or computational methods for determining Umi‑Time may be provided elsewhere in this specification, but they are not required for interpreting the textual formats defined in this section.

    3. Terms and definitions

      For the purposes of this section, the following terms and definitions apply. Terms defined elsewhere in this specification, or in ISO 8601, shall retain their established meanings unless explicitly redefined here.

      • Umi‑Time
        A representation of the position within the UTC day expressed in Umi‑Time umi and umi‑seconds. Umi‑Time is a global, location‑independent representation of UTC time of day.
      • Umi‑Time umi
        A unit representing one three‑hundred‑and‑sixtieth of a UTC day. Umi‑Time umi are numbered from 000 to 359, increasing monotonically through the UTC day.
      • Umi‑Time second
        A subdivision of a Umi‑Time umi equal to 1/240 of that umi. Umi‑Time seconds are numbered from 000 to 239 and may carry an optional decimal fraction. One Umi‑Time second corresponds to exactly one SI second.
      • Basic Umi‑Time format
        A fixed‑width textual representation of Umi‑Time consisting of a three‑digit Umi‑Time umi field followed by a three‑digit Umi‑Time second field, without separators, optionally followed by a fraction.
      • Extended Umi‑Time format
        A textual representation of Umi‑Time in which the Umi‑Time umi and Umi‑Time second fields are separated by a colon (:), improving human readability while preserving fixed‑width fields, optionally followed by a fraction.
      • Fraction
        An optional decimal fraction of the Umi‑Time second, consisting of a full stop (.) followed by one or more digits, appended to the Umi‑Time second field.
      • U‑separator
        The literal character U used to separate a UTC calendar date from a Umi‑Time value. The U‑separator distinguishes Umi‑Time from UTC time in combined date–time representations.
      • Local context suffix
        An optional annotation appended to a Umi‑Time value that conveys location‑dependent or observer‑dependent information, such as longitude or segment‑of‑day classification. Local context suffixes do not alter the umi or umi‑second fields, but their presence determines how an accompanying calendar date is interpreted.
      • Longitude offset suffix
        A local context suffix expressing the observer’s longitude in degrees, using a sign (+ east, - west) followed by a three‑digit value.
      • Day‑phase suffix
        A local context suffix identifying which of twenty‑four equal phases of the Umi‑Day contains the value, expressed as P<k> where k is the zero‑based phase index.
      • Segment code suffix
        A local context suffix identifying the observer’s position within a geometric subdivision of the Umi-Day. Segment codes are expressed as S<k>/<n>, where k is the zero‑based index of the segment, and n is the number of segments. An optional refinement (+u) may indicate umi into the segment.
      • Disambiguation
        The process of determining whether a six‑digit time value represents an ISO 8601 time (hhmmss) or a Umi‑Time (uuusss). Disambiguation may rely on context, the presence of the U‑separator, or the use of extended Umi‑Time formats.
    4. General principles

      Umi‑Time expresses the position within the UTC day using two fixed‑width numeric fields: a three‑digit umi value and a three‑digit umi‑second value, the latter optionally followed by a decimal fraction. These fields form a continuous, cyclic, location‑independent representation of the 24‑hour UTC day.

      Textual representations of Umi‑Time shall use fixed‑width, zero‑padded decimal fields to ensure unambiguous interpretation and compatibility with ISO 8601‑style parsing. The umi field spans \(000\text{–}359\) and the umi‑second field spans \(000\text{–}239\), with any fraction keeping the umi‑second strictly below 240. These ranges are normative.

      Umi‑Time may appear either as a standalone value or combined with a calendar date. When combined with a date, the literal character U shall introduce the Umi‑Time component, ensuring clear distinction from ISO 8601 UTC date–time formats. Because a Umi‑Time value is always UTC, no zone designator (such as ISO 8601 Z or ±hh:mm) shall appear in any Umi‑Time representation.

      Optional local‑context suffixes—such as longitude offsets or segment codes—may follow a Umi‑Time value. These suffixes shall not modify the underlying umi or umi‑second fields; their effect on the interpretation of an accompanying calendar date is defined in Date interpretation.

      In contexts where both UTC time and Umi‑Time may appear, implementations shall apply the disambiguation rules defined in this section. The presence of the U‑separator or the extended Umi‑Time format shall be used to avoid ambiguity.

      This section defines only the textual representation of Umi‑Time. Computational methods for determining Umi‑Time or converting between Umi‑Time and UTC are specified elsewhere in this document.

    5. Basic Umi‑Time format

      The basic Umi‑Time format provides a compact, machine‑oriented representation of a Umi‑Time moment. It consists of two numeric fields presented as a single contiguous value. The structure and interpretation of these fields are defined in the following subsections.

      1. Field definitions

        The basic Umi‑Time format consists of two numeric fields. The first field is the Umi‑Time umi value, representing the position within the 360‑umi cycle. The second field is the Umi‑Time umi‑second value, representing the fractional subdivision of a single umi. The umi‑second field may be followed by an optional decimal fraction. These fields together express a complete Umi‑Time moment.

      2. Basic format

        The basic Umi‑Time format is a six‑digit representation consisting of the Umi‑Time umi field followed immediately by the Umi‑Time umi‑second field. No separators or additional symbols appear between the fields, and the two fields are presented as a single contiguous numeric value, optionally followed by a fraction.

        Because this six‑digit structure is syntactically identical to the ISO 8601 basic UTC time format \((hhmmss)\), standalone Umi‑Time values may require contextual information to avoid ambiguity. When a calendar date is present, the required U separator provides explicit disambiguation.

        Examples: 235198, 235198.25

      3. Zero‑padding rules

        The umi and umi‑second fields in the basic and extended Umi‑Time formats shall use fixed‑width, zero‑padded decimal integers. The umi field and the umi‑second field shall each contain exactly three digits, and values below \(100\) shall be left‑padded with zeros. Zero‑padding is mandatory and ensures that Umi‑Time values remain machine‑readable and compatible with fixed‑width parsing conventions. Zero‑padding does not apply to the fraction, which may have any number of digits.

        Zero‑padding requirements apply equally to both the basic six‑digit representation and the extended representation that uses a colon separator.

        Examples: 007003, 042:058, 359239, 042:058.5

      4. Fraction

        The umi‑second field may be followed by a fraction consisting of a single full stop (.) and one or more decimal digits. The full stop is the only permitted decimal mark; the comma permitted by ISO 8601 shall not be used. A full stop without at least one following digit is invalid. The fraction applies to both the basic and the extended format and shall appear immediately after the third digit of the umi‑second field.

        There is no upper limit on the number of fractional digits. A generating implementation should emit only as many digits as its time source resolves; a parsing implementation shall accept at least nine fractional digits and should preserve all digits presented. Trailing zeros carry no meaning beyond indicating precision.

        Examples: 235:038.25, 235038.250, 359:239.999

      5. Comparison with UTC time formats

        The basic Umi‑Time format and the ISO 8601 basic UTC time format are both six‑digit numeric representations without separators. Although the two formats differ semantically—Umi‑Time expresses umi and umi‑seconds, while UTC expresses hours, minutes, and seconds—their syntactic similarity means that a standalone six‑digit Umi‑Time value may be indistinguishable from a six‑digit UTC time value.

        Because of this ambiguity, implementations shall rely on explicit disambiguation when both formats may appear in the same context. The extended Umi‑Time format (uuu:sss) and the mandatory U separator in combined date–Umi‑Time representations provide clear syntactic markers that distinguish Umi‑Time from UTC time.

        Examples: 235198 (ambiguous), 235:198 (unambiguous Umi‑Time), 2026-08-24U235:198 (unambiguous date–Umi‑Time).

    6. Extended Umi‑Time format

      The extended Umi‑Time format provides a more readable presentation of Umi‑Time for user‑facing contexts, offering a clearer visual separation between the umi value and its fractional subdivision. It is intended for interfaces, documentation, and any situation where human clarity is preferred over compactness, while retaining the same underlying numeric fields defined for the basic format.

      1. Separator rules

        In the extended Umi‑Time format, the umi and umi‑second fields shall be separated by exactly one colon. The colon is the only permitted field separator in conforming extended‑format data. It shall appear immediately after the umi field and shall not be repeated, omitted, or replaced by any other character. No whitespace or additional punctuation may appear around the separator. The optional fraction, when present, follows the umi‑second field as defined for the basic format.

      2. Symbol variant (informative)

        For illustrative or decorative purposes, user interfaces and diagrams may display a compact Umi symbol in place of the colon. This symbol variant is non‑normative and shall not be interpreted as a valid extended Umi‑Time representation.

        Example using Umi glyph: 247198

        When the custom glyph is unavailable, a superscript “u” may be used as a fallback. These presentations do not alter the underlying numeric fields or their interpretation.

        Example using superscript fallback: 247u197

    7. Local context suffixes

      A Umi‑Time value may be followed by a local context suffix to indicate the observer’s position within the Umi-Day at the moment represented by that Umi‑Time value.

      Local context suffixes do not modify the underlying Umi‑Time value. Instead, they supply the local interpretation that cannot be inferred from the global Umi‑Time value alone. The subsections that follow define the permitted suffix forms and the rules governing their attachment to Umi‑Time values.

      1. General syntax

        A local context suffix is an optional textual element appended directly to a Umi‑Time value to indicate the observer’s position within the Umi‑Day. A suffix shall appear immediately after the final digit of the Umi‑Time value, with no intervening whitespace or punctuation.

        A suffix system shall define a finite set of suffixes, each corresponding to a distinct partition of the Umi‑Day. The suffixes in a system shall be unambiguous, deterministic, and representable in plain text. A suffix system shall not modify the underlying Umi‑Time value and shall not conflict with the syntax of the Umi‑Time fields defined elsewhere in this specification.

        A suffix system shall define a syntactically distinguishable pattern that allows a conforming implementation to identify the suffix system in use without out‑of‑band information.

        Longitude suffixes, day‑phase suffixes, and segment suffixes are mutually exclusive. Only one suffix system may be applied to a Umi‑Time value. The Umi‑offset refinement is not a suffix system; it is an optional extension that may be applied only to compatible suffix systems as defined in their respective sections.

        Only the suffix systems defined in the following subsections are valid. Implementations shall reject any other suffix.

      2. Longitude offset suffix

        The longitude offset suffix identifies the observer's geographic longitude relative to the prime meridian. It provides longitude‑derived local context and allows the reader to infer the observer's approximate position within the local Umi‑Day.

        The longitude offset suffix is syntactically distinguished by a leading plus or minus sign (+ or -) followed by a three-digit, zero-padded integer in the range 000–180. Positive values represent degrees east of the prime meridian; negative values represent degrees west. The observer’s longitude shall be rounded to the nearest integer degree. The forms +000 and +180 shall be used in preference to -000 and -180.

        The suffix does not modify the underlying Umi‑Time value and shall not be used as a substitute for the computational longitude parameter defined elsewhere in this specification.

        Example (informative): 235:198+123

      3. Day‑phase suffix (P‑suffix)

        The day‑phase suffix is an optional local‑context indicator that divides the observer’s Umi‑Time day into twenty‑four equal phases. Each phase represents one twenty‑fourth of the Umi‑Time cycle at the observer’s longitude, measured from Umi‑Time midnight. The P‑suffix provides a compact indication of the observer’s current position within the Umi‑Time day and shall not modify the interpretation of the umi or umi‑second fields.

        A day‑phase suffix shall begin with the uppercase letter P followed by an integer in the inclusive range 0–23. Phase P0 corresponds to the interval beginning at Umi‑Time midnight, phase P12 corresponds to the interval beginning at Umi‑Time noon, and phase P23 corresponds to the final interval ending at the next Umi‑Time midnight. These phases are fixed subdivisions of the local Umi‑Day and do not depend on physical solar noon or physical solar midnight.

        A conforming implementation shall compute the day phase by determining the elapsed fraction of the Umi‑Day at the observer’s longitude and multiplying that fraction by twenty‑four. The resulting value shall be truncated toward zero to obtain an integer in the required range. Because Umi‑Time noon and Umi‑Time midnight generally occur within minutes of their physical solar counterparts, these subdivisions provide a practical approximation of local time-of-day progression while remaining simple to compute.

        The P‑suffix is a distinct suffix system and shall not be combined with any other suffix type. When present, the P‑suffix shall appear immediately after the Umi‑Time value with no intervening whitespace. A conforming implementation shall not alter the underlying Umi‑Time fields when parsing or validating a value that carries a P‑suffix.

        Examples (informative):

        
        235198P0      (Umi‑Time midnight phase)
        042057P6      (morning phase)
        183144P12     (Umi‑Time noon phase)
        183144P23     (final phase before next Umi‑Time midnight)
          

        Display variant (informative): for human‑facing displays such as digital clock faces, user interfaces may present the day phase using the Greek capital phi (Φ, U+03A6) in place of the letter P, and may separate it from the umi value with a space — for example 105ᵘ Φ9. Like the Umi glyph variant of the extended format, this presentation is non‑normative and shall not be interpreted as a valid textual representation; conforming interchange shall use P. Implementers should note that this specification uses lowercase \(\phi\) for latitude in the solar‑geometry formulas; the display glyph is unrelated to that quantity.

      4. Segment code suffix

        The segment code suffix identifies the observer’s position within the Umi‑Day by dividing the day into a fixed number of contiguous segments beginning at Umi‑Time midnight. Each segment represents an equal portion of the Umi‑Day, and the suffix indicates which segment contains the observer’s current Umi‑Time value.

        The segment code suffix is syntactically distinguished by the letter S followed by two integers separated by a slash. The first integer is the zero‑based segment index, and the second integer is the total number of segments in the system. The segment count shall be positive; the segment index shall be non‑negative and less than the segment count. Neither integer shall carry leading zeros.

        A segment code system may define any finite number of segments. The choice of segmentation granularity affects only the resolution of the local context information and does not modify the underlying Umi‑Time value. The suffix shall not be used as a substitute for solar position calculations defined elsewhere in this specification.

        Example (informative): 235:198S3/8

      5. Optional umi‑offset refinement

        The umi‑offset refinement is an optional textual extension that may be applied to certain local context suffix systems to provide additional precision within the Umi‑Day. It is intended for suffix systems whose primary divisions are coarse or symbolic, such as segment suffixes or day‑phase suffixes. The refinement is not applicable to longitude offset suffixes, which already provide precise positional information.

        The refinement specifies an offset, measured in umi, from the beginning of the segment or phase indicated by the preceding suffix. This allows an implementation or reader to express a more precise position within the Umi‑Day without increasing the granularity of the underlying suffix system.

        The umi‑offset refinement is syntactically distinguished by a leading plus sign (+) followed by a non‑negative integer without leading zeros. The value shall be less than the width of one segment or phase in umi: less than \(360/n\) for an \(n\)‑segment system, and less than 15 for the day‑phase suffix. The refinement shall appear immediately after a compatible local context suffix. A refinement shall not appear without a preceding suffix, as its syntax would otherwise be ambiguous with the longitude offset suffix system.

        The refinement does not modify the underlying Umi‑Time value and shall not be used as a substitute for solar position calculations defined elsewhere in this specification. A conforming implementation shall not alter the underlying Umi‑Time fields when parsing or validating a value that carries a refinement.

        Example (informative): 235:198S3/8+12 indicates that the observer’s position within the Umi‑Day is 12 umi past the start of segment 3 in an eight‑segment system.

    8. Date–Umi‑Time combination

      A calendar date may be combined with a Umi‑Time value when both a date and a Umi‑Time reading must be recorded together. This combined form is useful in contexts such as logging, data interchange, archival records, and any application where events are associated with both a calendar date and a precise timestamp.

      1. Use of the U‑separator

        When a calendar date is combined with a Umi‑Time value, the two components shall be separated by the literal character U. The separator shall appear immediately after the final digit of the calendar date, with no intervening whitespace or punctuation.

        The U separator ensures that a combined date–Umi‑Time expression cannot be misinterpreted as an ISO 8601 UTC date–time, which uses the T separator. Its use provides a clear and unambiguous distinction between the two representations in contexts where both may appear.

        The same separator may also be used to introduce a standalone Umi‑Time value when disambiguation is required.

        Examples:

        • 2026-08-24U235:198
        • U235198
      2. Calendar date formats

        The calendar date used in a combined date–Umi‑Time representation shall conform to ISO 8601, in either basic form (YYYYMMDD) or extended form (YYYY-MM-DD). This specification does not alter the semantics of ISO 8601 calendar dates.

      3. Date interpretation

        The interpretation of the calendar date in a combined date–Umi‑Time representation depends on whether local context suffixes are present.

        When no local context suffixes are present, the calendar date shall be interpreted as the UTC calendar date.

        When local context suffixes are present, the calendar date shall be interpreted as the Umi‑Date, defined as the UTC calendar date in effect at Umi-Time noon for the observer’s longitude.

        When a longitude offset suffix is present, the Umi‑Day boundary used to assign the Umi‑Date shall be computed from the suffix value \(\lambda_s\) (an integer in degrees), not from the observer’s exact longitude. The UTC calendar date of the instant is then recovered as follows, where \(u\) is the umi field and \(D\) the Umi‑Date:

        • if \(\lambda_s > 0\) and \(u \geq 360 - \lambda_s\): UTC date is \(D - 1\);
        • if \(\lambda_s < 0\) and \(u < -\lambda_s\): UTC date is \(D + 1\);
        • otherwise: UTC date is \(D\).

        Ordering and comparison of combined representations shall be performed on the UTC instant. A representation without a suffix, or with a longitude offset suffix, determines the UTC instant uniquely. Day‑phase and segment suffixes determine the UTC instant only to within the resolution of the phase or segment, and the UTC date may be ambiguous when the value lies near a UTC day boundary; such representations should not be used where ordering across observers is required.

      4. Combined representations

        A combined date–Umi‑Time representation consists of a valid ISO 8601 calendar date followed by the separator defined above and a Umi‑Time value in either basic or extended format. Together, these components form a single textual value that records both the calendar date and the corresponding Umi‑Time reading.

        The two components are interpreted independently, except for the date interpretation rule described in the preceding subsection.

        Examples:

        
        Basic date + Umi‑Time:    20260824U235198
        Extended date + Umi‑Time: 2026-08-24U235:198
              
    9. Parsing and validation rules

      A conforming implementation shall parse Umi‑Time values strictly according to the formats defined in this specification. Parsing shall not rely on heuristics, inference, or contextual guessing. Any deviation from the required structure, field widths, numeric ranges, or suffix syntax shall cause the entire value to be rejected as invalid.

      1. Core field validation

        The Umi‑Time umi field shall consist of exactly three decimal digits in the range 000–359. The Umi‑Time second field shall consist of exactly three decimal digits in the range 000–239, optionally followed by a fraction consisting of a full stop and one or more decimal digits. Both integer fields shall be zero‑padded to fixed width. Implementations shall reject values that contain non‑digit characters outside the permitted separators, incorrect field widths, out‑of‑range values, a full stop not followed by a digit, or more than one full stop.

        In the extended format, the umi and umi‑second fields shall be separated by a single colon (:). The colon shall appear exactly once and only in this position. No other separators are permitted within the Umi‑Time value.

      2. Combined date and Umi‑Time

        When a date is combined with a Umi‑Time value, the date shall conform to the formats defined in Date and Umi‑Time combination. The date and Umi‑Time components shall be separated by a single uppercase letter U. Implementations shall reject combined representations that omit the separator, use a lowercase variant, or contain additional separators or whitespace.

      3. Suffix parsing

        Local context suffixes shall be parsed only if present and shall conform exactly to the syntax defined in Local context suffixes. A suffix shall appear immediately after the Umi‑Time value with no intervening whitespace. Suffix systems are mutually exclusive. The Umi‑offset refinement may only be applied to a compatible suffix system as defined in its section. Implementations shall reject values containing malformed suffixes, incorrect ordering, or ambiguous patterns.

        The presence of any suffix shall not modify the underlying Umi‑Time fields. Ordering and comparison of combined representations shall follow Date interpretation.

      4. Whitespace and invalid characters

        No internal whitespace is permitted within a Umi‑Time value, its suffixes, or any combined representation. Leading or trailing whitespace may be removed by the implementation but shall not appear within the value itself. Any character outside the permitted digits, the hyphen of an extended calendar date, colon, full stop of a fraction, U separator, or suffix syntax defined in Local context suffixes shall cause the value to be rejected.

      5. Error handling

        A conforming implementation shall treat any malformed, partially conforming, or ambiguous representation as invalid. Implementations shall not attempt to infer missing fields, reinterpret ambiguous numeric sequences, or recover from structural errors. Only fully conforming Umi‑Time values shall be accepted.

    10. Formal grammar (informative)

      The following grammar, in the notation of ISO/IEC 14977, summarises the textual formats defined in this section. The prose requirements are normative; where the grammar and the prose differ, the prose prevails. Hyphens are used within meta‑identifiers for readability. Range constraints that the grammar cannot express (a valid calendar date, segment index less than segment count, refinement less than the segment or phase width) are semantic constraints defined in the corresponding subsections.

      digit             = "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" ;
      non-zero-digit    = "1" | "2" | "3" | "4" | "5" | "6" | "7" | "8" | "9" ;
      integer           = "0" | non-zero-digit, { digit } ;
      
      umi-field         = ( "0" | "1" | "2" ), digit, digit
                        | "3", ( "0" | "1" | "2" | "3" | "4" | "5" ), digit ;
      second-field      = ( "0" | "1" ), digit, digit
                        | "2", ( "0" | "1" | "2" | "3" ), digit ;
      fraction          = ".", digit, { digit } ;
      
      basic-umi-time    = umi-field, second-field, [ fraction ] ;
      extended-umi-time = umi-field, ":", second-field, [ fraction ] ;
      umi-time          = basic-umi-time | extended-umi-time ;
      
      longitude-value   = "0", digit, digit
                        | "1", ( "0" | "1" | "2" | "3" | "4" | "5" | "6" | "7" ), digit
                        | "180" ;
      longitude-suffix  = ( "+" | "-" ), longitude-value ;
      
      refinement        = "+", integer ;
      phase-index       = digit | "1", digit | "2", ( "0" | "1" | "2" | "3" ) ;
      phase-suffix      = "P", phase-index, [ refinement ] ;
      segment-suffix    = "S", integer, "/", integer, [ refinement ] ;
      
      suffix            = longitude-suffix | phase-suffix | segment-suffix ;
      local-umi-time    = umi-time, [ suffix ] ;
      
      basic-date        = 8 * digit ;
      extended-date     = 4 * digit, "-", 2 * digit, "-", 2 * digit ;
      calendar-date     = basic-date | extended-date ;
      
      standalone        = [ "U" ], local-umi-time ;
      combined          = calendar-date, "U", local-umi-time ;
      umi-representation = standalone | combined ;
    11. Examples

      The following examples illustrate valid Umi‑Time representations and the use of optional local context suffixes. All examples are informative only and do not introduce additional normative requirements.

      1. Basic Umi‑Time

        The basic format consists of six digits: three for the umi field and three for the umi‑second field.

        Example: 235198

      2. Extended Umi‑Time

        The extended format separates the umi and umi‑second fields with a colon.

        Example: 235:198

      3. Fractional umi‑seconds

        A fraction may follow the umi‑second field in either format, and may be combined with a date or suffix.

        Examples: 235:038.25, 2026-08-24U235038.250, 235:038.25+012

      4. Combined date and Umi‑Time

        A date may be combined with a Umi‑Time value using the U separator, as defined in Date and Umi‑Time combination.

        Example: 2026-09-23U235:198

      5. Longitude offset suffix

        A longitude offset suffix indicates the observer’s longitudinal displacement from the reference meridian, as defined in Longitude offset suffix.

        Example: 235:198+012 (observer is 12° east of the reference meridian)

      6. Segment code suffix

        A segment code suffix identifies the segment of the solar day containing the observer’s current Umi‑Time value, as defined in Segment code suffix.

        Example: 235:198S3/8 (segment index 3 of 8; the fourth segment, zero‑based indexing)

      7. Segment code with umi‑offset refinement

        An umi‑offset refinement provides additional precision within a segment or other coarse division, as defined in Optional umi‑offset refinement.

        Example: 235:198S3/8+12 (12 umi past the start of segment index 3 of 8)

  9. Conformance

    A conforming implementation shall correctly interpret, validate, and generate Umi‑Time values according to the normative requirements defined in this specification. The required behavior includes correct handling of the fixed‑width umi and umi‑second fields, adherence to the permitted textual formats, and strict application of the parsing and validation rules defined in Parsing and validation rules.

    Implementations that provide a visual representation of Umi‑Time shall ensure that the positions of solar events (such as sunrise, physical solar noon, sunset, and other defined reference points) are consistent with the Umi‑Time model and the solar-context relationships defined by this specification. Visual elements shall not contradict the underlying Umi‑Time value, local interpretation, or computed solar context.

    Implementations shall not reinterpret umi values as solar time. Solar context provides additional information about the observer's solar environment but shall not modify the underlying Umi‑Time coordinate, the computation of UT, or the longitude‑based local interpretation defined by Layer 2. Likewise, solar events and solar conditions shall not be used to redefine, adjust, or override any Umi‑Time value.

    Optional features, such as local context suffixes, shall be supported when present and shall conform exactly to the syntax and semantics defined in Local context suffixes. The presence or absence of any suffix shall not alter the underlying Umi‑Time value.

    Informative text, examples, and explanatory notes do not impose additional conformance requirements. Only the normative statements in this specification define the criteria for conformance.

    1. Conformance Classes

      An implementation may claim conformance to one or more of the following classes. A claim shall identify the class or classes to which it applies.

      • Layer 1 — Umi‑Time Transformation — computes and/or represents UT, umi, and umi‑second values according to the Umi‑Time Transformation requirements. A Layer 1 implementation need not provide local interpretation or solar context.
      • Layer 2 — Local Longitude‑Based Presentation — implements longitude‑derived local interpretation as defined in Local Longitude‑Based Presentation , including Umi‑Time noon, Umi‑Time midnight, Umi‑Day, and Umi‑Date. Layer 2 conformance implies Layer 1 conformance.
      • Layer 3 — Solar Context — computes solar events and related solar-context information as defined in Solar Context and meets the Accuracy Requirements. Layer 3 conformance implies Layer 1 and Layer 2 conformance.
      • Textual Representation — parses and/or generates Umi‑Time values according to Textual Representation of Umi‑Time , including formatting, parsing, validation, and date-interpretation rules. Textual conformance is independent of Layer 2 and Layer 3 conformance.
  10. Reference Implementations

    This section is informative and does not define conformance requirements. It describes reference implementations that illustrate recommended ways to present Umi‑Time while remaining consistent with the requirements defined elsewhere in this specification.

    Implementations may use other visual, textual, cartographic, or application‑specific representations provided they remain consistent with the Umi‑Time model.

    1. Analog Representation

      The reference analog representation uses a circular dial and hand to display the continuous Umi‑Time coordinate.

      The dial represents a complete 360‑umi cycle and increases clockwise. The hand completes one full revolution per UTC day, providing a direct geometric representation of the continuous UT coordinate.

      Dial Orientation

      The reference analog implementation expresses Layer 2 local interpretation through dial orientation.

      Before applying longitude, the dial places 0ᵘ at the bottom and increases clockwise.

      The dial is then rotated by the observer's longitude:

      \[ \theta_{\text{rotation}} = \lambda \]

      Positive longitudes rotate clockwise and negative longitudes rotate counterclockwise.

      This places Umi‑Time noon near the top of the dial and Umi‑Time midnight near the bottom, creating a longitude‑aligned local interpretation while preserving the universal UT value.

      Solar Ring

      The reference analog implementation expresses Layer 3 solar context using a fixed solar ring surrounding the dial.

      Solar events are first computed as UT values and then mapped to angles relative to Umi‑Time midnight.

      \[ \theta_{\text{event}} = \left( \left( (UT_{\text{event}} - UT_{\text{mid}}) + 360^\mathrm{u} \right) \times \frac{1^\circ}{1^\mathrm{u}} \right) \bmod 360^\circ \]

      This places solar events at their corresponding positions relative to the observer's local day.

      Solar Context Features

      Common solar-context features include:

      • sunrise and sunset markers
      • daytime and nighttime regions
      • civil, nautical, and astronomical twilight
      • optional blue-hour and golden-hour indications

      Because physical solar noon and physical solar midnight generally remain close to the top and bottom of the display, implementations typically do not need to mark them explicitly.

      Optional Auxiliary Indicators

      Analog implementations may optionally include:

      Such indicators provide additional context but do not alter the underlying Umi‑Time representation.

    2. Digital Representation

      Digital implementations commonly display Umi‑Time using the standard textual representations defined by this specification.

      The simplest form consists only of the umi and umi‑second fields:

      251:055

      Digital implementations may optionally provide Layer 2 local context through:

      • day‑phase suffixes
      • longitude offset suffixes
      • local Umi‑Date displays

      Layer 3 solar context is commonly omitted from textual and compact digital displays to preserve clarity and legibility.

      Larger digital interfaces may optionally provide solar context through additional indicators, charts, maps, timelines, or graphical visualizations.

    3. Cartographic Representation

      Maps provide another effective representation of Umi‑Time.

      A cartographic implementation may display the universal Umi‑Time value together with geographic location and optional day/night boundaries.

      Such representations emphasize the relationship between a shared UT coordinate and its varying local interpretations across Earth's longitudes.

  11. Test Vectors (Informative)

    The following values were computed with the formulas in Solar Context, including one re‑evaluation of \(\delta\) and EoT at the estimated event time and \(h_0 = -0.833^\circ\). Umi values are given to four decimal places; textual values are rounded to the nearest umi‑second. Implementations should reproduce the textual values to within ±1 umi‑second.

    1. UTC to umi

      15:40:38 UTC      = 56438 s      →  UT = 235.1583ᵘ  →  235:038
      15:40:38.250 UTC  = 56438.25 s   →  UT = 235.1594ᵘ  →  235:038.25
      08:00:00 UTC      = 28800 s      →  UT = 120.0000ᵘ  →  120:000
      23:59:59.9 UTC    = 86399.9 s    →  UT = 359.9996ᵘ  →  359:239.9
      
      Round trip:  2026-08-24T15:40:38.250Z  ↔  2026-08-24U235:038.25
    2. Greenwich, 2026-06-21 (\(\phi = 51.4778\), \(\lambda = 0.0\))

      UT_mid (Umi‑Time midnight)  =   0.0000ᵘ     θ_rotation = 0°
      EoT (at noon)              =  -1.8246 min   δ = 23.4381°
      UT_noon (physical)         = 180.4561ᵘ  → 180:109  (12:01:49 UTC)
      UT_solar mid (physical)    =   0.4561ᵘ  → 000:109
      H_0 (sunrise)              = 124.7520°
      UT_sunrise                 =  55.6853ᵘ  → 055:164  (03:42:44 UTC)   θ =  55.6853°
      UT_sunset                  = 305.2256ᵘ  → 305:054  (20:20:54 UTC)   θ = 305.2256°
    3. New York, 2026-03-20 (\(\phi = 40.7128\), \(\lambda = -74.0060\))

      UT_mid (Umi‑Time midnight)  =  74.0060ᵘ     θ_rotation = -74.006°
      EoT (at noon)              =  -7.3706 min   δ = 0.0400°
      UT_noon (physical)         = 255.8486ᵘ  → 255:204  (17:03:23 UTC)   θ = 181.8426°
      UT_sunrise                 = 164.8201ᵘ  → 164:197  (10:59:16 UTC)   θ =  90.8141°
      UT_sunset                  = 347.0494ᵘ  → 347:012  (23:08:11 UTC)   θ = 273.0434°
    4. Tokyo, 2026-12-21 (\(\phi = 35.6895\), \(\lambda = 139.6917\))

      UT_mid (Umi‑Time midnight)  = 220.3083ᵘ     θ_rotation = 139.6917°
      EoT (at noon)              =   2.1158 min   δ = -23.4356°
      UT_noon (physical)         =  39.7793ᵘ  → 039:187  (02:39:07 UTC)   θ = 179.4710°
      UT_sunrise                 = 326.8491ᵘ  → 326:204  (21:47:23 UTC, 2026-12-20)   θ = 106.5408°
      UT_sunset                  = 112.8345ᵘ  → 112:200  (07:31:20 UTC)   θ = 252.5262°

      Date interpretation: for this observer the sunrise instant is written 2026-12-21U326:204+140. With \(\lambda_s = +140\) and \(u = 326 \geq 360 - 140\), the UTC date resolves to 2026-12-20, matching the UTC instant above. Without a suffix the same instant is written 2026-12-20U326:204.

    5. Tromsø (\(\phi = 69.6496\), \(\lambda = 18.9553\))

      UT_mid (Umi‑Time midnight)  = 341.0447ᵘ     θ_rotation = 18.9553°
      
      2026-06-21:  arccos° argument < -1  →  Sun above h_0 all day (no sunrise/sunset)
                   UT_noon (physical) = 161.4980ᵘ  → 161:120  (10:45:59 UTC)
      
      2026-12-21:  arccos° argument > +1  →  Sun below h_0 all day (no sunrise/sunset)
                   UT_noon (physical) = 160.5573ᵘ  → 160:134  (10:42:13 UTC)
  12. Licensing

    This specification is published under the CC-BY-4.0 License. The license applies to the text of the specification itself and does not impose any licensing requirements on software, hardware, or documentation that implements Umi‑Time.

    Implementations may use any license—open‑source or proprietary—provided they accurately implement the normative requirements of Umi‑Time and do not present Umi‑Time as a different or incompatible time presentation standard. The CC-BY-4.0 License governing this specification does not extend to, or restrict, independent implementations.

    Derivative works, extensions, and alternative presentations of the specification are permitted under the terms of the CC-BY-4.0 License, so long as references to Umi‑Time remain truthful and consistent with the standard defined here.

  13. Summary

    Umi‑Time is a UTC‑based representation standard that presents UTC as a universal, location‑independent timestamp for global coordination. It expresses the UTC day as a continuous 360‑umi cycle mapped exactly from UTC, ensuring that umi values advance at a constant rate everywhere on Earth and that every moment has a single shared value. This provides humanity with a common daily reference that remains stable across all longitudes.

    While the Umi‑Time coordinate is universal, local interpretation is determined by the observer's longitude. This longitude‑derived context establishes the relationship between the universal Umi‑Time value and the observer's local day without altering the underlying umi progression.

    Solar context—including sunrise, sunset, twilight phases, and physical solar noon—is computed independently from the Umi‑Time coordinate. These solar events provide additional information about the observer's solar environment without affecting the universal time scale or its longitude‑based local interpretation.

    This separation of concerns allows Umi‑Time to be both globally uniform and locally meaningful: a single universal time representation enriched by longitude‑derived local interpretation and optional solar context. This specification defines the umi and umi‑second fields, the permitted textual formats, the optional local‑context suffixes, and the rules for parsing, validation, computation, and presentation, establishing a coherent foundation for software, science, communication, and human coordination at planetary scale.

Documentation
Developer
Project