<-Scope Go to ToC References ->
Capitalised Terms used in MMM-ARC and MMM-TEC have the meaning defined in Table 1. Non-capitalised terms letter have the meaning commonly defined for the context in which they are used or represent an entity in the real world. For instance,
- Table 1 defines Object, Scene, and User but does not define object, scene, and human.
- Object indicates an Item but object indicates an entity in the Universe commonly classified as object.
A dash “-” preceding a Term in Table 1 means the following:
- If the font is normal, the Term in the table without a dash and preceding the first one with a dash should be placed before that Term. The notation is used to concentrate in one place all the Terms that are composed of, e.g., the word Decentralised followed by one of the words Application, Autonomous Organisation, Finance, System, and User Identifier, or definitions belonging to the same class, e.g., Action and Items.
- If the font is italic, the Term in the table without a dash and preceding the first one with a dash should be placed after that Term. The notation is used to concentrate in one place all the Terms that are composed of, e.g., the word Interface preceded by one of the words Brain-Computer, Haptic, Speech, and Visual.
All MPAI-defined Terms are available online.
Table 1 – Terms and Definitions
| Terms | Definitions |
| Account | An Item that uniquely references a Registered human. |
| Action | A function performed by a Process. |
| – Authenticate | The Action of a User requesting an Authentication Service to: 1. Confirm that an Item or Process is what it claims to be with an Authentication Item request. 2. Grant Rights to Authentication Item response based on Model Rights. |
| – Author | The Action of a User requesting an Author Service to: 1. Produce an Item based on provided Items, Data, Qualifiers. 2. Grant Rights to the Authored Item based on Model Rights. |
| – Change | The Action of a User requesting a Rights Service to: 1. Modify the Rights of a Process or an Item based on Model Rights. 2. Grant the requesting User the Rights to further Change the Rights. |
| – Convert | The Action of a Process requesting a Conversion Service to: 1. Change the Data of an Item according to a given Qualifier 2. Grant Rights to the Converted Item based on Model Rights |
| – Discover | The Action of a User requesting a Discovery Service to 1. Provide Item IDs or Process IDs relevant to the Discovery Item request. 2. Grant Rights to the Discovery Item response based on Model Rights. |
| – Execute | The Action of a Process requesting an Execution Service to: 1. Execute a Program. 2. Grant Rights to the produced Items based on Model Rights. |
| – Hide | The Action of a Process requesting an Identification Service to: 1. Make the ID of an Item unavailable to all Processes, but the requesting Process. 2. Grant Rights to the Hidden Item based on Model Rights. |
| – Identify | Action of a Process requesting an Identification Service to: 1. Produce an Item from Data, Qualifier, and Model Rights provided by the requesting Process. 2. Grant Rights to the Item based on Model Rights. |
| – Inform | The Action of a User requesting an Information Service to: 1. Provide information about an Item or Process as contained in the Information Item request. 2. Grant Rights to Information Item response based on Model Rights. |
| – Interpret | The Action of a User requesting an Interpretation Service to: 1. Provide information about an Item or Process as contained in the Interpretation Item request. 2. Grant Rights to Interpretation Item response based on Model Rights. |
| – MM-Add | The Action of a User requesting a Location Service to: 1. Place an Item at an M-Location with a Spatial Attitude. 2. Grant Rights based on Model Rights to the MM-Added Item. Only the User who has MM-Added the Item shall be able to perceive it. Other Users shall be able to perceive it only if the Item is MM-Enabled |
| – MM-Anim | The Action of a User requesting that a Location Service: 1. Animate an MM-Added or MM-Embedded Item with a Stream or Command Item. 2. Grant Rights based on Model Rights to the MM-Animated Item. |
| – MM-Disable | The Action of a User requesting a Location Service to: 1. Stop making perceptible an MM-Embedded Item to all Users but the requesting User. 2. Preserve any change than may have been effected on the MM-Disabled Item. 3. Grant Rights to the MM-Disabled Item based on Model Rights. |
| – MM-Embed | The Action of a User requesting a Location Service to 1. Place an Item at an M-Location with a Spatial Attitude. 2. Make the Item perceptible. 3. Grant Rights to the MM-Embedded Item based on Model Rights. |
| – MM-Enable | The Action of a User requesting a Location Service to: 1. Add or Change the Spatial Attitude of an MM-Added Item at an M-Location: 2. Resize the Item by Rx, Ry, Rz along the Item’s axes. 3. Make the Item perceptible. 4. Grant Rights to the MM-Enabled Item based on Model Rights. |
| – MM-Move | The Action of a User requesting a Location Service to: 1. Move an MM-Added/MM-Embedded Item at an M-Location to another MM-Location. 2. Preserve any change that may have been effected on the Item in previous MM-Add, MM-Embed, or MM-Enable Actions. 3. Preserve the (un)perceptibility status of the Item. 4. Grant Rights to the MM-Moved Item based on Model Rights |
| – MM-PropertyChange | The Action of a User requesting a Location Service to modify the characteristics of an Item: 1. Resize the Item by Rx, Ry, Rz along the Item’s axes. 2. Display a specific Personal Status (if a Persona). 3. Grant Rights to the MM-Morphed Item based on Model Rights. |
| – MM-Send | The Action of a Process requesting a Communication Service: 1. To send a Message to other Processes. 2. To grant Rights to the receiving Process on the content of the Message. |
| – Modify | The Action of a User requesting an Identification Service to 1. Produce a new Item starting from an existing Item using new Data, Qualifier, and Model Rights to the new Item. 2. Grant Rights to the Modified Item based on Model Rights. |
| – MU-Actuate | The Action of a User requesting an ExIm Service to: 1. Render an Item at a U-Location as Media with a Spatial Attitude 2. Also render the Scene of the M-Location including the Item, if the M-Location field is present. 3. Grant Rights to the U-Location based on Model Rights. MM-Added Items preserve their (un)perceptibility attributes. |
| – MU-Send | The Action of a Process requesting an ExIm Service to: 1. Send a Message to Processes in the Universe. 2. Grant Rights to Data and Qualifier based on Model Rights. |
| – Post | The Action of a User requesting that a Marketplace Service: 1. Include an Asset to its repository. 2. Grant Rights based on Model Rights if a Transaction based on Model Transaction is performed. |
| – Register | The Action of a human requesting that a Registration Service: 1. Open an Account based on the human’s Personal Data. 2. Potentially pays for the Account. 3. Grant their Users Rights to perform Actions in the M-Instance. |
| – Resolve | The Action of: 1. A Process requesting that a Resolution Service set up a session between/among two/more than two Processes in two/more than two M-Instances. 2. A Process or Resolution Service responding to a session request. |
| – Transact | The Action of a User1 (“sender”) requesting that a Transaction Service: 1. Assign Rights on an Asset to User2 (“receiver”). 2. Cause: 2.1. Wallet1 of User1 to be increased by Value1. 2.2. Wallet2 of User2 to be decreased by Value2. 2.3. Wallet3 of the Service enabling/facilitating the Transaction to be increased by Value3 (optionally). |
| – UM-Capture | The Action of a Process holding Rights to a U-Location to request an ExIm Service to: 1. Capture Data and Qualifier with a Spatial Attitude from Media at U-Location. 2. Grant Rights to the Process to Identify the Data and Qualifier as Item. |
| – UM-Send | The Action of a Process requesting an ExIm Service to: 1. Be allowed to receive a Message from a Service in the Universe. 2. Grant Rights to Act on the content of the Message. |
| – Validate | The Action of a Process requesting a Validation Service to confirm that a Process hold claimed Rights. |
| Actuator | A component of a Device able to MU-Render an Item to or MU-Send Items to a U-Environment. |
| Capabilities | A Data Type containing the list of Actions and related data that can be performed on an Item, and that an M-Instance, M-Environment, or a Process can perform. |
| Certification | The attestation that a Process or Item has specified characteristics. |
| Command | A Item used to effect instantaneous changes to an Item or to an R-Item via an MM-Anim or MU-Anim Process Action (see Stream). |
| Conversion | The process of Modifying the Data of an Item according to provided Data and Qualifier. |
| Decentralised | |
| – Application | (dApp) A Process that runs on a decentralised computing system. |
| – Autonomous Organisation | (DAO) An organisation without centralised leadership, where the main governing rules are typically encoded by means of a Smart Contract. |
| – Finance | (DeFi) A financial technology based on a secure infrastructure of distributed ledgers like those used by crypto currencies. |
| – System | A set of dApps enabling a group of Users to make decisions without a centralised entity. |
| Device | Equipment enabling:
– A U-Environment to interact with an M-Instance and/or |
| Duty | A moral or legal obligation to act or behave. |
| Ecosystem | The ensemble of entities and rules ensuring that Metaverse Instances operate in the interest of Metaverse Stakeholders. |
| Entitlement | The state of a Process having certain Rights in an M-Instance. |
| Governance | The action or manner of directing and controlling actors of the Metaverse Ecosystem. |
| Information and Communication Technologies | (ICT) Technologies that enable the processing and distribution of information via the network. |
| Interface | A communication pathway enabling a human to interact with M-Instance: |
| – Brain-Computer | (BCI) by sensing and processing the electrical activity of the brain. |
| – Haptic | through bodily movements and sensations. |
| – Speech | using spoken language. |
| – Visual | through bodily movements and visual messages. |
| Item | A Data Type representing a perceptible or abstract object in an M-Instance referenced by a unique Identifier and describing its capabilities, qualifier(s), metadata, Processes that hold Rights on the Item, and links it to an M-Environment if relevant. |
| – Account | An Item that 1. Uniquely references a human registered with an M-Instance. 2. Includes the IDs of the human’s Personal Profile, Processes, and their Internal Rights. |
| – Activity Data | An Item recording the IPP Protocols executed by a Process. |
| – Any Item | An enumerated Data Type defining the complete set of Actions that may occur in the MPAI MMM V2.2 ecosystem. It provides a controlled Action vocabulary used across Marketplace processes, MMM AIM workflows, and User initiated procedures. |
| – Asset | An Item or a Process intended for Transactions. It includes Identifier, Capabilities, Provenance and economic metadata. |
| – Authentication | An Item generated by 1. A Process requesting a Service to confirm that an Item is what it claims to be. 2. A Service containing the response to the request |
| – Basic Certificate | An Item attesting the suitability of a Process for specific MMM-TEC V2.0 usages. Other types of Certificates are possible and are listed in the Certificate Qualifier. |
| – Basic Discovery | An Item used by a Process to request that a Service discover Items or Processes. Other types of Discover Items are possible and are listed in the Discovery Qualifier. |
| – Basic Interpretation | An Item used by a Process to request that a Service provide information on or interpretation of Items or Processes. Other types of Interpret Services are possible and are listed in the Interpretation Qualifier. |
| – Basic M-Location | An Item representing a region of an M-Instance with Space-Time attributes that is not exposed as further subdivided as a Location. |
| – Basic Object | An Item representing: – Data of a specific media type perceptible by a specific device and/or a human. – Descriptive Data regarding Sub-Types, Formats and Attributes of the Data (optionally). |
| – Basic Scene Descriptors | An Item representing the Objects of a Basic Scene and their arrangement in the Scene. |
| – Basic Scene Geometry | An Item representing the spatial arrangement of the Objects in a Basic Scene. |
| – Basic U-Location | An Item representing a region of the Universe with Space-Time attributes that is not (exposed as) further subdivided. |
| – Capabilities | A Data Type containing the list of Actions and related data that can be performed on an Item, and that an M-Instance, M-Environment, or a Process can perform. |
| – Category | Metadata specifying characteristics of an Item or a Process. |
| – Certificate | An Item Process attesting the suitability of a Process for specific usages that is not a Basic Certificate. |
| – Cognitive State | An Item representing the Personal Status Factor representing the internal state of an Entity such as “surprised” or “interested”. |
| – Contract Object | An Item representing terms and conditions or a Program that is executed according to certain terms when conditions are met. The terms and conditions are represented by:
|
| – Currency Object | An Item representing the unit of measure of an Amount of a Value in terms of:
|
| – Discovery Object |
|
| – Emotion | An Item representing the Personal Status Factor representing the internal state of an Entity such as that resulting from its interaction with the Context, such as “Angry”, “Sad”, “Determined”. |
| – Event | A Process Action or a logical combination of Process Actions performed at an expression of Time. |
| – Event Descriptors | An Item representing the series of Scene Descriptors from start and end time. |
| – Fault Behaviour Report | An Item issued by any Process to the relevant Service to report suspected faulty, fraudulent, deceptive, or otherwise non‑compliant behaviour observed within the M‑Instance. |
| – Fault Detection Report | An Item issued by a Service of an M‑Instance to the corresponding Service of another M‑Instance to notify suspected non‑compliant behaviour by a Process belonging to that other M‑Instance in the M-Instance of the reporting Service. |
| – Financial Error Report | An Item used by a Process to report a suspected error in a previously executed Transaction. |
| – Identifier | A Data Type that uniquely references one Process or one Item in an M-Instance. |
| – Interpretation Object |
|
| – IPP Message | An Item that a Source Process sends to a Destination Process requesting the performance of a Process Action. |
| – Licence | An Item that describes the Rights to an Item or a Process in an M-Instance that Licensor and Licensee hold during a Time as facilitated by a Service Provider. |
| – M-Capabilities | An Item representing the capabilities of an M-Instance or M-Environment. |
| – M-Environment | An Identified administrative subset of an M-Instance. |
| – M-Instance | A Virtual Space created according to the MMM-TEC Technical Specification of the MPAI-Metaverse Model. |
| – Market Classes | Define a controlled vocabulary used to categorise Assets, Rights, Services, and experiences shared. These classes allow implementers and markets to express, in a standardised way, the kind of economic entity that is being described. |
| – Marketplace Policy IDs | Identifiers of the policy applied to listing, transaction, or operation of an Asset (Item or Service). Identifiers begin with the prefix MPOL- and may be drawn from an authoritative enumeration or – until the enumeration is finalised – may conform to an approved pattern. |
| – Message | An Item that a Source Process MM-Sends to a Communication Service, or UM-Sends to an Import Process, or MU-Sends to an Export Process requesting it to deliver it to a Destination Process. A Message may contain: Item, Data, Data and Qualifier, Data and Metadata. |
| – M-Instance | An Item representing the Virtual Space created according to the MMM-TEC Technical Specification of the MPAI-Metaverse Model. |
| – M-Location | An Item representing a region of an M-Instance with Space-Time attributes that is (exposed as) further subdivided. |
| – Object | An Item including a collection of Basic Objects possibly of different Media Types. An Object may have a hierarchical structure where Objects contain Basic Objects and Objects. |
| – Orientation | An Item representing an Object’s orientation, orientation velocity, and orientation acceleration. |
| – P-Capabilities | An Items containing the list of Processes and Actions that it can perform. |
| – Penalty | The set of Actions and Process Actions that a Process is prohibited from performing as a result of the Process’s non-compliance. |
| – Personal Data | An Item containing a human’s Personal Profile and Activity Data of their Users. |
| – Personal Profile | An Item containing information about a human submitted when Registering with an M-Instance. |
| – Personal Status | An Item representing the information internal to an Entity that characterises their behaviour. |
| – Point of View | An Item representing the Position and Orientation of an Object in a Virtual Environment excluding velocity and acceleration. |
| – Position | An Item representing an Object’s position, velocity, and acceleration. |
| – Process | A Program executed in an M‑Instance – as an App, Device, Service, or User – that performs MPAI‑specified Actions on Items/Processes, subject to its Rights and the M-Instance’s Rules. |
| – Process Action | An Item that specifies the Action that a Process may perform based on its Rights and the M-Instance Rules. |
| – Program Object |
|
| – Provenance | A Data Type containing an ordered list of Events representing lifecycle-relevant information about an Asset. Each Event in the Provenance corresponds to an operation that has affected the Asset or one of its successive representations. |
| – Resolution | An Item containing an M-InstanceA’s ProcessA Request to Resolution ServiceA to set up a session involving different M-Instances’ Processes and the Responses of the Resolution Services and destination Processes. |
| – R-Item | A perceptible object in the Universe or the Analogue Twin in the Universe of an Item in the Metaverse |
| – Rights | A Data Type that expresses a set of normative statements (Rights) governing the Actions a Process Must, May, or May Not perform on Items or Processes within an M‑Instance or M‑Environment. |
| – Rules | An Item including a Process type, a deontic verb – Permission, Prohibition, or Obligation, and a Process Action. |
| – Scene Descriptors | An Item including the Objects of a Scene, the Sub-Scenes, and their arrangement in the Scene. |
| – Scene Geometry | An Item representing the arrangement of the Objects of a Scene that may include Objects and Sub-Scenes in a hierarchical fashion. |
| – Service Pricing Model | A Data Type defining the rules, parameters, and conditions under which a service is offered, billed, chosen, settled, and accessed. |
| – Simple Certificate | A simple form of Certificate attesting that the Actions of a Process conform with the MMM-TEC Technical Specification. |
| – Simple Contract | An MPAI-specified Contract providing basic functionalities for seller (Sender), buyer (Receiver), and Service Provider that facilitates Simple Contract definition and execution. |
| – Social Attitude | An Item representing Personal Status Factor representing the internal state of an Entity related to the way it intends to position itself vis-à-vis the Context, e.g., “Respectful”, “Confrontational”, “Soothing”. |
| – Space-Time | An Item representing the Spatial Attitude and Time information. |
| – Spatial Attitude | An Item representing the Position and Orientation of an Object, and their velocities and accelerations. |
| – Summary | An Item representing a text-based abridged outline of the utterance(s) of one or more Entities represented by their User ID and including Space-Time, Text, and Personal Statuses. |
| – Time | An Item representing the start time and end time of a duration. |
| – Transaction | A data type representing the transfer of digital assets, rights, or values among participants in an MPAI‑MMM ecosystem. A Transaction records the identifiers of the involved parties, the assets or processes being transacted, the values exchanged, and the metadata required for traceability, validation, and auditing. |
| – U-Environment | An Item representing an Identified subset of the Universe. |
| – U-Location | An Item representing a region of the Universe with Space-Time attributes. |
| – Universe-Metaverse Map | An Item representing a list of U-Locations and corresponding M-Locations and/or Items with their Spatial Attitudes. |
| – Validation | An Item sent by a Process to a Service requesting it to validate a claim that another Process makes about its Rights and the response of the Service. |
| – Value | An Item combining an Amount and a Currency. |
| – Wallet | A container of Values. |
| Layer | |
| – Enabling Service | The set of Services such as payment, security, identity, privacy, etc. that enable operation of an M-Instance. |
| – Experience | The set of functions, such as Devices, that generate Experiences. |
| – Infrastructure | The set of functions such as network, transport, storage, and (cloud, edge) processing that enable an M-Instance to operate. |
| – Platform | The set of Services, such as content creation, content discovery, and content access functions that enable an M-Instance to operate. |
| Level | A type of Right, currently Internal (granted at Registration Time), Acquired (by Process Activity), Granted (by another Process). |
| Metaverse | |
| – Interoperability | The ability of an M-Instance to exchange and make use of the data of a user device or another M-Instance as intended by a user device or M-Instance. |
| – Industry | The collection of players that support the design, development, deployment, operation, and content and service provisioning to Metaverse Instances. |
| – Instance | (M-Instance) An implementation providing all or a subset of the Metaverse Functionalities. |
| – Manager | The entity overseeing the operation of an M-Instance. |
| – Operation Model | The components and sequence of steps involved in the operation of an M-Instance. |
| – Operator | The entity overseeing the operation of an M-Environment. |
| – Partner | A User participating in activities of a Metaverse Operator (i.e., a business customer of an Operator) |
| – Profile | A recognised subset of the Functionalities (Functionality Profile) or Technologies (Technology Profile) specified by the Common Metaverse Specifications. |
| – Level | A subdivision of a Profile that indicates the degree of completeness of the user experience provided by that Level. |
| – Registration | The provisioning by a human of a subset of Personal Data to an M-Instance/Environment to obtain an Account. |
| – Sensor | A Device able to UM-Capture a scene and other environment information as Data. |
| – Specification | The collection of standards specifying the Technologies and Technology Profiles enabling Metaverse Interoperability. |
| – Stakeholder | An entity performing a function aimed at achieving a goal in an M-Instance. |
| – State | The set of values and stored data of an M-Instance at a given time. |
| – Tool | A Technology or group of Technologies enabling an M-Instance to provide a Functionality. |
| – Technology | A structured application of scientific and/or technical methods that supports a Functionality. |
| Oracle | A Service providing U-Environment information to a Blockchain. |
| Persona | A Model representing a human. |
| Privacy | The Rights of a User to keep their Personal Profile secret. |
| Process | |
| – App | An application-specific Program executed on a Device. |
| – Device | A Process able to: 1. UM-Capture Data from a U-Location 2. UM-Send Data and Metadata to a User. and/or 1. MM-Send an Entity from an M-Location to the Device. 2. MU-Render an Entity at a U-Location. |
| – Functionality | The attribute of a Process that is able to perform particular Action(s). |
| – Service | A Process that can be called to provide specific Functionalities. |
| – User | A Process representing a human. |
| Render | The action of creating an R-Item. |
| Sense of | |
| – Agency | The subjective awareness of being able to decide, execute, and control one’s own actions in an M-Environment. |
| – Embodiment | The engagement of senses to form a complete M-Instance Experience. |
| – Presence | The feeling of being in an M-Instance with other Digital Humans for real. |
| Smart Contract | A Program stored on a Blockchain that runs when activated by an external entity, e.g., a User or another Smart Contract. |
| Stream | A Item used to effect continuous changes to an Item or to an R-Item via an MM-Anim or MU-Anim Process Action (see Command). |
| Token | |
| – Fungible | A representation of an Asset that is interchangeable with other Assets of the same type. |
| – Non-Fungible | (NFT) A unique digital identifier of an Asset that: – Cannot be copied (i.e., a copy is known to be a copy), substituted, or subdivided. – Is recorded in a digital ledger. – Is used to certify Object authenticity and ownership. |
| Trust-less system | A system allowing a User to make reliable Transactions without trusting or knowing the parties the User makes Transactions with. |
| Twin | |
| – Analogue | The replica of an Item to the Universe as an R-Item. |
| – Digital | The replica of an object or scene to the Metaverse as an Item. |
| Universe | The physical world. |
| – Metaverse Map | An Item providing a list of U-Locations and corresponding M-Locations and/or Items with their Spatial Attitudes in an M-Instance. |
| Use Case | An example of how an application domain can be supported by an M-Instance/Environment. |
| User Keys | The pair of public and private keys where the public key is used to encrypt, and the private key is used to both encrypt and decrypt Data. |
| User Identifier | |
| – Decentralised | An Identifier that enables the verifiable association with a User without requiring a centralised registry. |
| – Self-Sovereign | A Decentralised Identifier derived from the User’s Public Key owned and managed directly by the User based on the knowledge of their own Private Key, e.g., stored in the Crypto Wallet enabled by the Blockchain underpinning the Metaverse Instance. |
| Value Metadata IDs | Define the set of identifiers that may be used to tag metadata values associated with transactional or functional attributes in MMM-TEC frameworks. When the authoritative enumeration is considered complete, the pattern fallback will be removed. |
| Wallet | A container of Assets, Licences, Rights, Transactions, Values, and Cryptographic Keys. |
| – Crypto | Software or hardware holding the Public and Private Keys of a User to enable them to make Transactions by accessing their Account on a Blockchain. |
<-Scope Go to ToC References ->