Skip to content

Reading Guide

Universal Manifest — OMA3 Handout Collection

Section titled “Universal Manifest — OMA3 Handout Collection”

Prepared for: Alfred Tom and OMA3 members Date: 2026-03-12 Context: “Architectural overview (data structures, file formats, etc.) to figure out how to fit UM into IWPS.”


This is a set of nine short documents that explain Universal Manifest from the ground up. Each document covers one topic. You can read them in order for the full picture, or jump to any single document and understand it on its own.

The documents are written for standards body reviewers who want to understand UM’s architecture — what the data structures look like, how they fit together, and where UM complements IWPS.

#TitleWhat It CoversPages
01The ProblemWhy portable state is needed1
02The EnvelopeWhat a Universal Manifest is (minimal JSON-LD document)2
03Facets and PointersModular data compartments and lightweight references2
04ConsentDefault-deny privacy that travels with the data2
05SignaturesCryptographic tamper detection (v0.2)2
06The ResolverHow manifests are found (myum.net)2
07IWPS + UMThe complete portaling stack — the key document for OMA33
08Beyond MetaverseThe full application space (15 categories, 163 use cases)3
09What’s NextCurrent status, deferred items, collaboration opportunities2

Read 01 (the problem) and 07 (IWPS integration). These two documents frame the relationship between UM and IWPS.

Read 01 through 07 in order. This gives you the complete technical architecture before the integration discussion.

Each handout references the relevant specification and explainer documents. The full specification lives at:

TermDefinition
UMUniversal Manifest — the specification and portable document format
UMIDUniversal Manifest Identifier — a UUID-based URN for global identification
FacetA named, modular data compartment inside a manifest
PointerA URI referencing external authoritative data
TTLTime-to-live via issuedAt / expiresAt timestamps
IWPSInter-World Portaling Standard (OMA3)
JCSJSON Canonicalization Scheme (RFC 8785)