Skip to main content

Value Type

The primitive or semantic data type behind every Property.

type: data-model · status: published · abstraction: entity

What it is​

A Value Type defines how a Property's data is stored, validated, rendered and interpreted. Every Value Type is one of two kinds. Five are primitives, holding raw data with no added meaning: Text, Number, Boolean, Date and Timestamp. Twelve are semantic, carrying business meaning beyond the raw value: Address, File, Formula, Location, Measurement, Money, Relationship, Rich Text, Schema, Select, Status and Zoned Timestamp.

Semantic Value Types carry meaning the platform can act on. A Measurement identifies its unit and supports compatible conversion; Money carries its currency denomination and permits safe same-currency arithmetic. This meaning drives validation, interfaces, formulas, integrations and canonical data exchange.

Why it exists​

Without semantic typing, cross-tenant analytics and integrations are guesswork. Value Types are what let IMOS know that two tenants recording "500" and "0.5" are both describing half a tonne, and what let an integration map a field automatically instead of by hand.

Relationships​

Incoming

  • types ← Property — Every Property declares one Value Type.

Neighbourhood​

Stakeholder summaries​

  • Product — Each Value Type needs an input control, a display format and validation rules.
  • Investor — Semantic typing is the quiet moat: it turns messy customer data into a comparable, tradeable dataset.
  • Marketing — IMOS understands units, currencies and quantities — so your numbers always mean what you meant.
  • Engineering — Type registry driving storage encoding, validators, renderers, unit conversion and integration field mapping.