> For the complete documentation index, see [llms.txt](https://mims.oascities.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mims.oascities.org/mims-specification-v9.0/citiverse/mim9-citiverse/specifications-and-standards.md). # Specifications & Standards ### Reference standards and specifications Most scene and delivery standards that MIM9 needs are either new or still being finalised in 2026, so each entry carries its status. Status for entries marked "not re-checked" is from general knowledge and must be verified before publication. | Standard | Body | Used for | Status (September 2026) | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------- | ------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | | [OpenUSD Core Specification 1.0](https://www.linuxfoundation.org/press/alliance-for-openusd-announces-core-specification-1.0-the-universal-language-for-building-3d-worlds) | AOUSD | Authoring and composition (M1, M3) | Ratified December 2025; covers USDA, USDC and USDZ; Core 1.1 planned for 2026 ([80.lv](https://80.lv/articles/aousd-released-openusd-core-specification)) | | [OpenUSD Gaussian splat schema](https://www.linuxfoundation.org/press/aousd_prmarch2026) | AOUSD / OpenUSD | Reality capture (M1) | In OpenUSD v26.03 as UsdVolParticleField3DGaussianSplat | | [glTF 2.1](https://www.khronos.org/blog/introducing-gltf-2.1-with-complex-scenes) | Khronos | Delivery of composed scenes (M1, M2, M4) | Core features confirmed June 2026; specification being finalised in the open | | glTF 2.0 / ISO/IEC 12113:2022 | Khronos, ISO/IEC JTC 1 | Asset delivery (M1) | International Standard (not re-checked) | | [KHR\_gaussian\_splatting](https://www.khronos.org/news/press/gltf-gaussian-splatting-press-release) | Khronos | Reality capture (M1) | Release candidate February 2026; ratification targeted Q2 2026, to confirm | | [3D Tiles 1.1](https://docs.ogc.org/cs/22-025r4/22-025r4.html) | OGC | Geospatial streaming (M1, M5) | OGC Community Standard, approved December 2022 | | [3D Tiles 2.0](https://github.com/CesiumGS/cesium/issues/13528) | OGC | Geospatial streaming on glTF 2.1 (M1, M5) | In development; schemas not yet final | | CityGML 3.0, CityJSON 2.0 | OGC | City models (M1, see MIM7) | Adopted (not re-checked) | | IFC 4.3 (ISO 16739-1:2024), BCF | buildingSMART, ISO | BIM content and issues (M1, M3) | Adopted (not re-checked) | | MPEG-I Scene Description (ISO/IEC 23090-14) | ISO/IEC JTC 1/SC 29 | Immersive media scene description on glTF (M1) | Published; referenced by 3GPP ([5G-MAG](https://www.5g-mag.com/tech/xr/)) | | OGC GeoPose 1.0 | OGC | Pose of users and objects (M3) | Adopted (not re-checked) | | [IEEE 2874-2025](https://spatialwebfoundation.org/swf/the-spatial-web-standards/) | IEEE SA | Spatial web identifiers, modelling and transactions (M3, C6) | Approved May 2025 | | OpenXR 1.x, WebXR | Khronos, W3C | XR device access (M4) | OpenXR ratified; WebXR a W3C draft (not re-checked) | | WebRTC | W3C, IETF | Pixel streaming, split rendering (M5) | Recommendation / RFCs (not re-checked) | | [3GPP TS 26.565](https://www.etsi.org/deliver/etsi_ts/126500_126599/126565/18.02.00_60/ts_126565v180200p.pdf) | 3GPP (ETSI TS 126 565) | Split rendering (M5) | Rel-18, v18.2.0 (January 2025) | | [3GPP TS 26.567](https://www.3gpp.org/technologies/sr-ims) | 3GPP | Split rendering over IMS (M5) | Rel-19 | | [IETF Media over QUIC Transport](https://datatracker.ietf.org/group/moq/) | IETF | Scalable real-time distribution (M5) | Internet-Draft (draft-20, August 2026); IESG submission milestone December 2026 | | NGSI-LD, OGC SensorThings, OGC API Features and Processes | ETSI, OGC | Data binding (M2) | See MIM0, MIM7 and MIM8 | | EN 301 549, WCAG 2.2 | ETSI/CEN/CENELEC, W3C | Accessibility (R4.6) | Adopted (not re-checked) | **Related standardisation activity.** [ITU-T Study Group 20](https://www.itu.int/metaverse/) works on IoT, digital twins and smart cities, and the ITU Joint Coordination Activity on Metaverse Standardization (JCA-MV) coordinates metaverse work. The [ITU Focus Group on metaverse](https://www.itu.int/en/ITU-T/focusgroups/mv/Pages/default.aspx) produced the CitiVerse definition that MIM9 should align with. ISO/IEC JTC 1/CG 2 coordinates metaverse and citiverse strategy, and a joint working group of JTC 1 and IEC SyC Smart Cities works on a Local Digital Twin reference architecture ([ITU 2nd Citiverse Assembly](https://www.itu.int/metaverse/virtual-worlds/2nd-citiverse-assembly/)). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://mims.oascities.org/mims-specification-v9.0/citiverse/mim9-citiverse/specifications-and-standards.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.