Ratified extensions define context, scopes, UUIDs, and persist or remove operations. See implications for durable XR experiences.
Direct answer
The OpenXR 1.1.63 specification includes the ratified extensions XR_EXT_spatial_persistence and XR_EXT_spatial_persistence_operations. They allow you to create a persistence context, query compatible scopes, and persist or remove spatial entities by asynchronous operations based on XR_EXT_future. The standard improves logic portability, but does not guarantee that all runtimes offer the same scopes, capacity, or retention. Applications must enumerate support, version associated data, handle completion and failure, and offer fallback when persistence does not exist.
Persistence is no longer a proprietary detail
A common interface reduces specific code per runtime, although storage and sharing policies remain implementation dependent.
Asynchronous operation needs state
Requesting persistence does not mean completing it. The product must wait for the future, record results and avoid presenting premature success.
UUID identifies; does not explain
The identifier locates the entity, but content, version, owner, and permissions require a separate, migratable data model.
Removal is part of the life cycle
Experiences must allow expiration, replacement, and deletion. Orphan entities increase clutter, storage, and privacy risk.
Nexus Reading
Design persistence as a contract: scope, identity, duration, authorization, migration and fallback. Test restart, upgrade, loss of support, and complete removal.
FAQ
Are extensions ratified?
Yes. The official version 1.1.63 pages indicate ratified status.
Is the persistence call immediate?
No. Operations use the XR_EXT_future asynchronous pattern and require query and completion.
Does every OpenXR runtime need to support them?
No. Extensions should be enumerated and enabled only when available.
Essential guides to delve deeper into the decision
This editorial analysis was produced by Nexus from the official sources below, consulted on September 28, 2026. The text is original and interprets practical implications for companies.
- Khronos — XR_EXT_spatial_persistence_operations: ratified status, dependencies, and asynchronous operations of persisting and removing entities.
- Khronos — XR_EXT_spatial_persistence: contexts, scopes, UUIDs, state, and discovery of persisted entities.
Date reported by main source: OpenXR 1.1.63 consulted on September 28, 2026; ratified standard analysis.