Technical Specification: MPAI Metaverse Model (MPAI-MMM) – Architecture specifies:

  1. Terms and Definitions
  2. Operation Model
  3. Functional Requirements of Processes, Actions, Items, and Data Types
  4. Scripting Language
  5. Functional Profiles

enabling Interoperability of two or more metaverse instances (M-Instances) if they:

  1. Rely on the Operation Model, and
  2. Use the same Profile Architecture, and
    • Either the same technologies, or
    • Independent technologies while accessing Conversion Services that losslessly transform Data of an M-InstanceA to Data of an M-InstanceB.

Note: Full Interoperability may not be achieved if the M-Instances implement different Profiles.

The contents of this Technical Specification: MPAI Metaverse Model (MPAI-MMM) – Architecture is:

1. Scope Normative
2. Terms and Definitions Normative
3. Metaverse Functionalities Informative
4. Metaverse Operation Model Normative
5. Functional Requirements of:
5.1. Processes, i.e., Programs executing in an M-Instance Normative
5.2. Actions, i.e., Functionalities provided by Processes Normative
5.3. Items, i.e., Data and Metadata supported by an M-Instance Normative
5.4. Data Types, i.e., Data used in Actions and Items Normative
6. MPAI-MMM Scripting Language Normative
7. Use Cases Informative
8. Functional Profiles Normative

This Technical Specification has been developed by the MMM group of the Requirements Standing Committee. MPAI may decide to publish extensions or new versions of this Technical Specification, or other Technical Specifications of the MPAI-MMM series.