MSI-NUM-1.0
Universal Encoding

A standard is only real when systems can exchange it. MSI-NUM defines the notation for coordinates, time, motion, height, epochs, drift vectors, orientation, and metadata — consistent everywhere.

Why Encoding Is a Standard

Different teams can agree on physics but still fail to interoperate if formats differ. MSI-NUM is the glue: it defines how MSI is written, stored, exchanged, and labeled — so machines and humans always agree.

Most system failures don’t come from physics — they come from ambiguity. Different formats, missing epochs, silent assumptions. MSI-NUM eliminates interpretation; it defines how other MSI standards are encoded and exchanged.

Lon/Lat: λᴹˢᴵ, φᴹˢᴵ (decimal degrees) Elevation: Hᴹ, Dᴹ (metres) Velocity: v = (vₙ, vₑ) mm/yr Time: MT (MSI-TIME-1.0), MSI-CAL dates

Purpose

MSI-NUM establishes a consistent framework for numerical representation across standards, software systems, records, and scientific models. It separates numerical meaning from formatting, localization, or implementation-specific assumptions.

Core Principles

Scope

MSI-NUM applies to identifiers, counts, measurements, indices, and ordered references used throughout MSI standards. It does not mandate a single numeric base or encoding, but defines rules for equivalence and interoperability.

Applications

Relationship to Other Standards

MSI-NUM underpins all quantitative MSI standards, including MSI-TIME, MSI-CAL, MSI-ZERO, MSI-TRF, and MSI-DRIFT. It ensures numerical consistency across coordinate systems, epochs, and reference frames.

Canonical Examples

The examples below are illustrative placeholders — the page is for look-and-feel.

MSI-NUM Example Encoding Longitude / Latitude: λᴹˢᴵ +10.5532° φᴹˢᴵ +48.1231° Frame + Epoch: MSI-TRF-2030, epoch T₀ = 2030-01-01 00:00:00 MT₀ Drift vector: v = (vₙ, vₑ) = (+12.1, −4.7) mm/yr Time: 2041-PR-12 14:32:08 MT (MSI-CAL-1.0)
MSI-NUM VALIDATOR TOOL
Paste payload → check required fields + compliance mark

Compliance Validation

This mini-app will validate a payload (JSON/CSV/text) and confirm whether required MSI metadata is present (frame, epoch, model versions).