The Fit LibrarySharing & Access

Shared Fit Language: the fashion interoperability framework

Shared language for fit records

A shared language that lets brands, ateliers, and platforms understand and contribute fit-related records without losing meaning.

What it means Why it matters Related readings Trust & foundations FAQ

Read in Italian Back to The Fit Library

Definition

Fashion Interoperability is the shared schema and permission model within Size Passport that lets fit records move between brands, ateliers and platforms without losing semantic meaning or requiring re-entry. It is not integration. Integration connects two named systems through a bridge somebody built on purpose; interoperability means any two conforming systems can exchange records without ever having been introduced, the way two mail servers exchange messages. That distinction is what decides whether a solution scales past the handful of partners willing to build bridges.

For the person

It means your data remains understandable when it crosses from one tailor, brand or service to another. You never see the schema, and that is the point: the experience of interoperability working is that nobody asks you to be measured again, and nobody asks you what a number in your own record meant. The experience of it failing is a fitting session you have already had, repeated.

For the ecosystem

A shared fit language creates platform leverage because each new operator strengthens the network instead of fragmenting it. That is the opposite of how fashion technology usually works, where every additional vendor adds another incompatible silo. The governance position matters as much as the technology: a schema controlled by one brand is a competitive weapon and will be refused by everyone else, which is why the carrier has to sit outside the competitive layer to be adoptable at all.

Why it matters

Why this page matters in the wider system.

Most fashion systems stay isolated, and the isolation is not accidental: every brand's data model was built to serve that brand, and nobody was paid to make it legible to a competitor. The result is that a measurement taken at one house is meaningless at the next, not because it is wrong but because nothing tells the receiving system what the field names refer to, what units are in play, or what reference posture was assumed. A shared fit language creates the rules that let one trusted record stay understandable across houses, ateliers and services — and without those rules, portability produces files that travel but cannot be read.

Defines shared semantic meaning for body, garment and fit records, so “chest circumference” means the same measurement on both sides of an exchange.

Fixes the unstated variables that silently break exchanges: units, reference posture, and whether a dimension is a body or a finished-garment measurement.

Standardises permissions and contribution boundaries across operators, so receiving a record does not imply a right to keep or resell it.

Aligns with existing standards rather than inventing a parallel vocabulary — ISO 8559-1 for measurement terminology, W3C JSON-LD for serialisation, GS1 Digital Link as the product-side precedent.

Makes AI retrieval more accurate because terms stay stable across surfaces, which is why the concept pages themselves are written as a controlled vocabulary.

This idea becomes clearer through the others around it.

Depends onFit & Measurements

Measurement Portability

Data portability for fit

A shared language is only useful if the data can move across systems.

SupportsSharing & Access

Trusted Record System

Trusted system for shared fit records

The ledger gives interoperability an operator-neutral substrate.

DefinesFit Across Brands

Garment Data Layer

Finished garment context

Garment records become interoperable only when their meaning is standardized.

Questions answered clearly

Direct answers for people, search, and AI systems.

Does interoperability mean every brand must use the same software?

No. It means different systems can exchange and interpret the same fit concepts without losing meaning. Each operator keeps its own software, its own fit blocks and its own construction logic. What they agree on is the vocabulary at the boundary — the same way two companies can agree on invoice formats without merging their accounting departments.

Why talk about interoperability so explicitly?

Because AI agents, partners and investors need to understand that this is infrastructure rather than a standalone app, and infrastructure has to be named to be adopted. There is also a practical reason: a controlled vocabulary published openly is what lets a retrieval system quote the definition correctly rather than paraphrasing it into something slightly wrong.

What is the difference between fashion interoperability and a universal size chart?

A universal size chart assumes one static mapping between body dimensions and garment sizes, and the industry has failed to agree on one for over a century. Interoperability is a schema and permission model: it lets operators keep their own construction logic while exchanging a shared, semantically precise fit record. The measurement is the stable thing; the size label is just a name each brand applies to it.

Which standards underpin fashion interoperability in Size Passport?

GS1 Digital Link for product-linked data structures, W3C JSON-LD for structured semantic records, ISO 8559-1 for the body measurement vocabulary, and GDPR Article 20 for the portability entitlement that gives the permission model its legal foundation. None of them is fashion-specific in the way a universal size standard would be, which is precisely why they are adoptable.

What breaks first when two systems are not interoperable?

Units and reference posture, long before anything more exotic. A chest measurement taken over a shirt and one taken on the body differ by a centimetre or more; a measurement taken with arms raised differs again. Neither system usually records which convention it used, so the receiving side applies its own and the error is invisible until the garment arrives.

Is interoperability compatible with a brand keeping its fit block private?

Yes, and that compatibility is deliberate. The schema governs the body record and the finished-garment measurements, not the pattern that connects them. A house can publish that its size 50 jacket measures 104 cm at the chest without revealing how it drafts the armhole. The trade secret stays a trade secret; what becomes legible is the outcome a customer needs in order to choose.