Stub Manifests
This site includes “near-real” stub manifests to make Universal Manifest concrete for adopters.
These stubs intentionally include extra fields that are not yet standardized in the v0.1 context/schema (v0.1 allows unknown fields). Treat them as shape + intent fixtures, not final ontology.
Where to see them
Section titled “Where to see them”Stub fixtures (v0.1)
Section titled “Stub fixtures (v0.1)”Each link below opens a raw JSON-LD fixture (useful for copy/paste, diffing, and quick inspection).
- Venue edge (venue identity + policy + edge endpoints)
- Display device (device registration + trust metadata)
- Creator public capsule (safe public projection for screens)
- Social profile (future profile projection surface)
- Display envelope (implementation-specific fixture for signage runtime)
- OMATrust proof-based service attestation
- OMATrust trusted-attester service attestation
- OMATrust lifecycle-edge (revoked or superseded) attestation
What to look for (how these help adopters)
Section titled “What to look for (how these help adopters)”Even if you ignore every optional field, you can still gain value from:
subject(stable identity reference)- TTL (
issuedAt/expiresAt) shardsas a composition mechanismpointersas “canonical lives elsewhere” references
These stubs are designed to make it easier to implement:
- projections for different surfaces (public display vs web profile)
- local-first consumption (cache while in use, log by
@id) - forward compatibility (unknown field tolerance)