Skip to main content

Schema

A reusable, record-less template of Properties embedded within an Object to represent a complex semantic shape.

type: data-model · status: draft · abstraction: instance

What it is​

A Schema is an embedded, reusable structure of properties. Unlike Objects, Schemas do not have their own Records or standalone data lifecycles. Instead, they define a consistent template of properties that can be used as a Value Type for a Property on any Object.

The data assigned to a Schema property is stored directly on the parent Record that uses it. Users can populate these values by hand, or by using a "lookup" to copy them from an existing catalogue record — for example, selecting "A4" to instantly fill in a standard set of dimensions. Once copied, the values live independently on the record.

While Schemas are primarily designed for embedding flat values, they can selectively include actual reference properties. This allows a reusable shape to contain a live pointer to another Object's record — such as keeping a direct link to a curated "Finish" within a larger schema block — when a genuine identity link is required.

By building standard Schemas into the canonical library — such as a "Dimension" schema containing width, height, and depth — IMOS enables tenants and modules to share dense semantic structures. For example, if a Material Object, a Box Object, and a Machining Centre Object all use the canonical Dimension schema, the platform's UI, workflows, and AI agents inherently understand how to compare their structural footprints without custom mapping logic.

Why it exists​

To prevent the fragmentation of complex but ubiquitous data structures. Without Schemas, every Object that requires physical dimensions or locations would define independent, differently named, and differently scoped primitive properties. This breaks interoperability.

By extracting recurring property sets into a structured Value Type, we give the platform and AI agents a common semantic foundation to compare multi-attribute concepts logically and automatically, while keeping the data safely bound to the owning Record.

Relationships​

Outgoing

  • is an instance of → Value Type (many-to-one)
  • is composed of → Property (one-to-many) — A Schema declares a structured set of Properties that make up its template.

Neighbourhood​

Stakeholder summaries​

  • Product — Allows product templates to be effortlessly repurposed across multiple object architectures, guaranteeing UI uniformity.
  • Investor — Promotes rapid development scalability by preventing duplicated development effort across disparate data objects.
  • Marketing — Easily drop standardised information structures, like addresses or standard dimensions, directly into any new form.
  • Engineering — Embedded, reusable property templates serialised onto the host record to standardise complex data shapes without table sprawl.