A premium concept layer for fit infrastructure.
This is the semantic operating system behind Size Passport: a public architecture of concepts, relationships, and standards context that makes the platform legible to customers, partners, investors, AI systems, and retrieval engines.
Identity
Body Passport
Body identity layer
Size Passport
Portable fit record
Portability
Measurement Portability
Data portability for fit
Cross-Brand Sizing
Brand-neutral fit translation
Infrastructure
Fashion Interoperability
Shared fashion data language
Garment Data Layer
Finished garment context
Shared Ledger
Neutral permissioned substrate
Intelligence + Luxury
Fit Intelligence
Interpretable fit knowledge
Fit Memory
Longitudinal fit continuity
Digital Tailoring
Tailoring informed by persistent data
Personalized Luxury Infrastructure
Trust layer for premium service
AI-readable abstract
Body-linked identity, permissioned portability, and operator-neutral ledger logic create the semantic core of the platform.
Core entities
11
Defined terms with reusable metadata and FAQ structure
Relationships
33
Explicit semantic links between infrastructure concepts
Languages
EN / IT
Concept surfaces published in English and Italian
Schema posture
JSON-LD
DefinedTermSet, DefinedTerm, FAQ, breadcrumbs, and WebPage
Concept clusters
The ontology is grouped by how the system behaves, not by marketing topic.
Identity Systems
Terms that explain what the customer-owned record is and how it should be recognized.
SP-ID-001
3 linksBody Passport
Body identity layer
A customer-owned identity layer for body measurements, fit history, and body-linked garment knowledge.
SP-ID-002
3 linksSize Passport
Portable fit record
The customer-facing product expression of a body passport: a portable record for measurements, garment history, and fit permissions.
Portability Layer
Terms that describe how fit data moves across operators without brand lock-in.
SP-PT-001
3 linksMeasurement Portability
Data portability for fit
The ability for body and fit data to move with the customer across brands, ateliers, and platforms.
SP-PT-002
3 linksCross-Brand Sizing
Brand-neutral fit translation
The interpretation layer that helps fit data remain useful across brands with different blocks, grading, and construction logic.
Intelligence Layer
Terms that turn measurements and garment history into reusable fit understanding.
SP-IN-001
3 linksFit Intelligence
Interpretable fit knowledge
The layer that converts measurements, history, and garment outcomes into reusable fit understanding.
SP-IN-002
3 linksFit Memory
Longitudinal fit continuity
The preserved record of how measurements, garments, and preferences evolve over time.
Infrastructure Layer
Terms that define the machine-readable substrate beneath the product experience.
SP-IF-001
3 linksFashion Interoperability
Shared fashion data language
The ability for brands, ateliers, and platforms to read and contribute fit-related data through shared semantic contracts.
SP-IF-002
3 linksGarment Data Layer
Finished garment context
The structured record of finished garment measurements, construction outcomes, and post-fitting observations linked to the person.
SP-IF-003
3 linksShared Ledger
Neutral permissioned substrate
The operator-neutral system of record that coordinates customer-owned fit data, permissions, and contributions across multiple brands.
Luxury Experience Layer
Terms that connect neutral data infrastructure with premium service and personalization.
SP-LX-001
3 linksDigital Tailoring
Tailoring informed by persistent data
A model of tailoring where measurements, garment outcomes, and preferences persist across sessions and operators.
SP-LX-002
3 linksPersonalized Luxury Infrastructure
Trust layer for premium service
The idea that premium fashion service becomes more valuable when personalization is built on persistent, customer-owned fit infrastructure.
Relationship pathways
The experience should feel navigable because the ontology is navigable.
Semantic FAQ
Questions the concept layer should answer directly.
Why create concept pages instead of a normal glossary?
Because the platform is not selling isolated terms. It is defining a new infrastructure model. Each page therefore explains the term, its relationships, and its operational role inside the system.
How does this help AI retrieval systems?
The concept layer creates stable entities, consistent definitions, cross-links, FAQ answers, and structured data. That makes the platform easier for large language models and semantic search engines to classify and summarize.
Why include Italian alongside English?
English is the retrieval and investor language. Italian anchors the platform in its real operating context and improves semantic consistency for local partners, ateliers, and press.