Portability is not a feature. It is a governance contract between format, carrier, and permission.
TL;DR — Measurement portability is not achieved by adding an export button. It requires three components to travel together: a semantically structured data format, a carrier that no single operator controls, and a permission model embedded in the record itself. Without all three, data that leaves one system cannot be trusted or reused in another.
Measurement portability is consistently misunderstood as a product convenience. In practice, it is an infrastructure property — one that most fashion systems do not possess. When a customer's fit data exists only inside a brand's CRM, it is not portable. It is captured.
The distinction matters because GDPR Article 20 establishes a legal right to data portability in machine-readable, interoperable format — yet fashion operators routinely satisfy this right with CSV exports that are technically compliant and practically useless. A file that requires manual re-entry, loses provenance, and carries no permission context is an export. It is not portability.
Definition
Measurement Portability
The legal right and technical capability to move fit data across operators — brands, ateliers, tailors — without re-entry, context loss, or dependence on the originating system. Genuine portability preserves the data's semantic structure, its chain of provenance, and the customer's revocable permissions at every transfer point.
A portable format is the prerequisite every other component depends on. Without it, the data that leaves one system is not interpretable in the next. In practice, most measurement exports today are flat files: chest 98, waist 82, inseam 78. These numbers carry no semantic context — no measurement method, no body landmark definition, no garment-type qualifier.
ISO 8559-1:2017 defines over 170 named body measurements, each with a standardised landmark definition. A chest measurement taken at the axilla level means something different from one taken at the fullest point of the chest. Without the ISO landmark reference embedded in the data, the receiving tailor or algorithm cannot know which was used. The number 98 is not information — it is a digit.
W3C JSON-LD 1.1 provides the mechanism to bind semantic meaning to measurement fields through linked-data vocabularies. When each measurement key maps to a dereferenceable URI identifying the measurement method, the body landmark, and the measurement standard, the data becomes self-describing. A brand in Milan and an atelier in Paris both read the same record without a translation layer.
Neutrality in a data carrier means that no single operator can unilaterally revoke access, alter the record, or condition portability on continued commercial engagement. When a carrier is controlled by the brand that captured the original measurements, it is not neutral — it is a retention mechanism with a portability label.
In practice, when measuring customers for bespoke garments, we have observed that operator-hosted portability fails at the moment of relationship end. A customer who leaves a brand loses access to their own measurements within 30 to 90 days in the majority of systems. The data was never theirs to carry; it was theirs to view on the operator's terms.
The W3C Verifiable Credentials model addresses this by separating the issuer — the operator who measured the customer — from the holder, who is the customer, and the verifier, who is any subsequent operator receiving the credential. The holder controls the credential. The issuer cannot revoke it by deleting an account. The verifier can check the issuer's cryptographic signature without calling back to the issuer's server.
GS1 Digital Link provides complementary infrastructure for product-side data, enabling garment data to travel alongside customer fit data through a common URI resolver. Together, these two standards outline what a neutral carrier layer looks like: a system where the customer holds the credential and any compliant operator can receive and verify it, without routing the exchange through the original data collector.
A carrier controlled by the measuring operator is not neutral infrastructure. It is a lock-in mechanism that delays churn while calling itself a service.
The most common portability failure mode is a permission model that lives beside the data rather than inside it. In this design, consent is recorded in the operator's database and the exported data carries none of it. When the data moves, the permissions stay behind.
Under GDPR Article 20, the right to portability applies to personal data — and body measurements are personal data by any reasonable interpretation. The European Data Protection Board has clarified that portability must enable data to be transmitted directly between controllers, in a format that preserves the data subject's rights. A bare CSV does not satisfy this. The permissions must be machine-readable, embedded, and enforceable by the receiving system.
When these four elements are embedded in the record — not stored separately in an operator's CRM — portability becomes durable. The customer carries an intelligible, permissioned, reusable record into every new relationship. The Shared Ledger model, as used in the Size Passport architecture, treats permission state as a first-class attribute of the fit record rather than a metadata footnote.
The EU Ecodesign for Sustainable Products Regulation 2024/1781 requires Digital Product Passports for textile and apparel categories from 2026. This creates a structural forcing function: brands that have not built interoperable data infrastructure will face compliance cost at a moment when regulators are already scrutinising fashion's sustainability claims.
Research published in ScienceDirect on digital product fitting demonstrates that when accurate body data and garment specification data meet reliably at the point of purchase decision, return rates drop substantially. The academic literature confirms what practice suggests: the infrastructure gap between body data and garment data is where fit failures originate. Portability is the bridge.
McKinsey's State of Fashion 2024 identifies personalisation at scale as the primary commercial opportunity in fashion's next cycle. But personalisation without portability is personalisation trapped inside a single brand. A customer who has been measured by one operator starts from zero with the next. The commercial case for cross-brand fit memory — built on genuinely portable data — is direct and measurable.
Fashion interoperability, as outlined in the infrastructure literature and in the Size Passport approach to the Shared Ledger, is not a feature vote. It is the decision to build a data layer whose value compounds across every operator who adopts it, rather than depleting with each relationship that ends.
Technical standards are necessary but not sufficient. The hardest portability problem is not the data format or the carrier protocol. It is the governance question: who decides what the neutral infrastructure layer is allowed to do, and what incentive structures prevent the largest operator in the ecosystem from capturing it?
In practice, every attempt to build shared infrastructure in a competitive industry faces the same structural risk: the operator with the most data has the most to gain from a system that looks neutral but quietly advantages incumbent data holders. ISO standards help at the field-definition layer. W3C standards help at the credential layer. Neither standard answers the governance question.
The answer has to be designed at the governance layer before the product layer. Rules about who may write to the shared record, under what conditions, with what audit trail, and with what recourse for the data subject must be fixed before commercial adoption begins. Once adoption creates lock-in, retroactive governance becomes negotiation theatre.
A trustworthy fit infrastructure cannot be designed brand-first and corrected later. Governance, data model, and permission posture have to be right before the product layer becomes commercially persuasive. The customer's trust is the asset — and it is easier to destroy than to rebuild.
GDPR Article 20 establishes the legal minimum: personal data must be exportable in a structured, commonly used, machine-readable format on request. Measurement portability goes further. It requires the data to be semantically interpretable, permission-annotated, and receivable by another system without re-entry or translation. GDPR sets the floor; genuine portability defines the ceiling.
Ad-hoc sharing solves individual cases but does not constitute infrastructure. An API controlled by the originating brand routes all exchanges through that brand's consent model, rate limits, and commercial terms. If the brand changes terms or closes, the data becomes inaccessible. Infrastructure-grade portability requires the data to be held by the customer and verifiable by any compliant recipient, independent of the original operator's availability.
A data export is a snapshot: a file produced at a moment in time, stripped of provenance, carrying no permissions, and legible only to a human or a system that already understands the encoding. A portable credential, in the W3C Verifiable Credentials sense, is a self-describing object: it identifies the issuer cryptographically, carries the subject's consent scope, specifies the data model, and can be verified by any compliant receiver without contacting the issuer. The credential travels with its own trust context.
Body measurements are biometric-adjacent personal data. Several EU member states classify 3D body scan data under enhanced protection categories. The principle of data minimisation under GDPR means operators should only collect the measurements required for their service. Portability infrastructure that transmits a full 170-field body model to a retailer needing only five jacket measurements is not merely inefficient — it may be non-compliant. Granular field-level consent, scoped per operator and per purpose, is a regulatory requirement as much as a design choice.
The Size Passport architecture, built on the Shared Ledger model, is designed around all three components: ISO-referenced measurement fields in a JSON-LD structure for semantic portability, a customer-held credential model using W3C Verifiable Credentials for neutral carriage, and embedded consent scopes with revocation paths for permission portability. The Shared Ledger acts as the neutral governance layer — owned by the customer, readable by permitted operators, and not controlled by any single brand.
Sources
Related concepts