<– Functional Requirements of Processes Go to ToC Functional Requirements of Actions–>
General Items | Finance-related Items |
Human and User-related Items | Perception-related Items |
Items for Process Interaction | Space-related Items |
Items for Service access |
8.1 General Items
1.1.1 M-Instance
Purpose | An implementation of MPAI-Metaverse Model – Architecture. | ||||||||
Functional Requirements | An M-Instance may:
1. Implement a subset of MPAI-Metaverse Model – Architecture (i.e., a Functional Profile). 2. Add Functionalities not supported by MPAI-Metaverse Model – Architecture. In this case full Interoperability with another M-Instance may not be achieve 3. Enable the creation of M-Environments. |
||||||||
Metadata |
|
8.1.2 M-Capabilities
Purpose | An Item expressing the ability of an M-Instance to perform an Action on an Item. | ||||||||
Functional Requirements | An M-Instance/M-Environment may show its Capabilities, including Profile and the Data Formats used by the Items. | ||||||||
Metadata |
|
8.1.3 M-Environment
Purpose | An Identified administrative subset of an M-Instance. | ||||||||
Functional Requirements | An M-Environment may allow the definition, Identification, and access to M-Locations. | ||||||||
Metadata |
|
8.1.4 Identifier
Purpose | An Item that uniquely references an Item in an M-Instance. |
Functional Requirements | An Item can have more than one Identifier.
An Identifier of an Item may have a hierarchical structure: 1. M-InstanceID 2. M-EnvironmentID 3. M-LocationID 4. ItemID. An Identifier of an Item shall have a hierarchical structure: 1. M-InstanceID 2. M-EnvironmentID 3. M-Location 4. ProcessID 5. ItemID. |
Metadata | No Metadata |
8.1.5 Rules
Purpose | An Item expressing the terms and conditions under which a human deploys a User in an M-Instance or M-Environment. | ||||||||||
Functional Requirements | The Rules
1. Shall express the permissions, obligations, and prohibitions with respect to Actions performed by a User on Items. 2. May grant a User the ability to 2.1. Make Transactions. 2.2. Export Items to another Metaverse. |
||||||||||
Metadata |
|
8.1.6 Rights
Purpose | An Item expressing:
1. The ability of a Process to perform Actions on an Item during a Time and at an M-Location. 2. The possibility that an Item be subjected to an Action by a Process during a Time at an M-Location. |
||||||||
Functional Requirements | Rules may waive the need for certain Processes to hold certain Rights to perform certain Actions at certain Times. | ||||||||
Metadata |
|
8.1.7 Program
Purpose | Data that can be executed. | ||||||||||
Functional Requirements | The code:
1. Shall be executable in the M-Instance. 2. May be subject to certification before being admitted to the M-Instance. |
||||||||||
Metadata |
|
8.1.8 Contract
Purpose | A Program and its Metadata stored on a Device. It is activated by an external entity, e.g., a User, or another activated Contract. | ||||||||||
Functional Requirements | The Data of a Contract shall be in a form that allows its execution in the M-Instance.
A Contract may be subject to a certification carried out by or on behalf of the M-Instance Manager before it can be imported into an M-Instance. |
||||||||||
Metadata |
|
8.2 Human and User-related Items
8.2.1 Account
Purpose | An Item that uniquely references a human who has Registered. | ||||||||||
Functional Requirements | A User may have more than one Account with one or more M-Instances or M-Environments.
An Account shall include: 1. The ID of the Registered human. 2. An M-Instance-specific subset of the Registered human’s User Data. 3. The Rights held by each Users in the M-Instance/M-Environment. 4. The IDs of Devices, Apps, and Users, and Personae. |
||||||||||
Metadata |
|
8.2.2 Activity Data
Purpose | An Item containing the record of all the Actions made by a User. | ||||||||||||
Functional Requirements | Activity Data shall include:
1. The M-Instance ID. 2. The duration the Activity Data refer to. 3. The list of Interactions. |
||||||||||||
Metadata |
|
8.2.3 Personal Profile
Purpose | An Item containing the Data about the human represented by a User. | ||||||||||
Functional Requirements | The Personal Profile may include:
1. First Name 2. Last Name 3. Address 4. Nationality. 5. Age. |
||||||||||
Metadata |
|
8.2.4 Social Graph
Purpose | A representation of a User’s network of connections with Items and Processes. | ||||||||||
Functional Requirements | The Social Graph should represent the Times of Interactions with:
1. Items and Users at M-Locations. 2. Devices. 3. Services. |
||||||||||
Metadata |
|
8.2.5 User Data
Purpose | An Item containing Activity Data, Personae, Social Graph, and User Profile of a User. | ||||||||||||||||
Functional Requirements | User Data include the following Data:
1. Rights and Obligations held by the human with their Account. 2. The Personal Profile of the human. 3. The Personae that the Users of the human may assume. 4. The Activity Data of the Users of the human. 5. The Social Graphs of the Users of the human. |
||||||||||||||||
Metadata |
|
8.3 Items for Process Interaction
8.3.1 Message
Purpose | An Item a Source Process MM-Sends to a Destination Process. | ||||
Functional Requirements | A Message may contain:
1. An Item, or 2. Data and Metadata |
||||
Metadata |
|
8.3.2 P-Capabilities
Purpose | An Items containing a description of the characteristics of a Process. | ||||
Functional Requirements | 1. Provision of the P-Capabilities Item is optional.
2. The characteristics are: 2.1. Device: 2.1.1. Apps on board. 2.2. User: 2.2.1. Human the User represents. 2.3. All Processes 2.3.1. List of Actions that can be performed. 2.3.2. List of Items supported with Data Formats. 2.3.3. List of Data Types supported. 2.3.4. The cost of performing an Action. |
||||
Metadata |
|
8.3.3 Request-Action
Purpose | An Item containing the request to a Process to perform Action as defined in this document. | ||||
Functional Requirements | A Request-Action shall include:
1. Time the Request-Action was issued. 2. The Source ProcessID. 3. The Destination ProcessID. 4. The Action requested. 5. The ItemIDs relevant to the Action. 6. The Locations of the Items. 7. The Locations of the output Items produced by the Request-Action. 8. The requested Rights on the output Items. |
||||
Metadata |
|
8.3.4 Response-Action
Purpose | An Item containing the response of a Process to a Request-Action as defined in this document. | ||||
Functional Requirements | The Response-Item shall include:
1. Time the Response-Action was issued. 2. The Source ProcessID (Source refers to the Process that issued the request). 3. The Destination ProcessID. 4. The output Items produced by the Request-Action. 5. Error messages. |
||||
Metadata |
|
8.4 Items for Service access
8.4.1 AuthenticateIn
Purpose | An Item containing:
1. The Entity or the ID of the Entity to be Authenticated. 2. Information related to the rendering of AuthenticateOut (optional). |
||||||||||
Functional Requirements | The Entity to be Authenticated can be:
1. Speech produced by a User. 2. The visual appearance of a User. 3. … Information on the rendering of InterpretOut may be provided by: 1. Media type (text, speech, image, etc.) used for rendering. 2. Spatial Attitude of the Object rendering AuthenticateOut. |
||||||||||
Metadata |
|
8.4.2 AuthenticateOut
Purpose | An Item containing the result of the Service Acting on the Request-Authenticate Item and information about its rendering. | ||||||||||
Functional Requirements | AuthenticateOut shall be:
1. Made available to the User as Item, and 1. Rendered to the User as a perceptible Object as specified in AuthenticateIn. |
||||||||||
Metadata |
|
8.4.3 DiscoverIn
Purpose | An Item containing:
1. A description of the Items to be Discovered or recommended. 2. Information related to the rendering of DiscoverOut. |
||||||||||
Functional Requirements | Items candidate for Discovery may be described by:
1. Verbal/text description 2. Similar Items 3. Belonging to specific M-Instances/M-Environments/M-Locations 4. Belonging to specific sections of Activity Data. Information on DiscoverOut Rendering may be provided by: 1. Media type used for rendering. 2. Spatial Attitude of the Object rendering DiscoverOut. |
||||||||||
Metadata |
|
8.4.4 DiscoverOut
Purpose | An Item containing the description of the Items Discovered and information related to its rendering. | ||||||||||
Functional Requirements | Discovered Items shall be:
1. Described by the IDs of the Items Discovered. 2. Rendered to the User as a perceptible Object. |
||||||||||
Metadata |
|
8.4.5 InformIn
Purpose | An Item containing:
1. A description of the Item about which information is requested. 2. Information related to the rendering of InformOut. |
||||||||||
Functional Requirements | InformIn may refer to:
1. Item Metadata 2. Any other information that a Service may have on the Item. Information on rendering of InformOut may be provided by: 1. Media type used for rendering. 2. Spatial Attitude of InformOut rendered Object. |
||||||||||
Metadata |
|
8.4.6 InformOut
Purpose | An Item containing the description of the Item object of an InformIn. | ||||||||||
Functional Requirements | InformOut shall be:
1. Made available to the User as an Item, or 2. Rendered to the User as a perceptible Object. |
||||||||||
Metadata |
|
8.4.7 InterpretIn
Purpose | An Item containing:
1. The ID or the Item to be Interpreted. 2. Information related to the rendering of InterpretOut. |
||||||||||
Functional Requirements | Items candidate for Discovery may be described by: Item or ItemID.
Information on InterpretOut Rendering may be provided by: 1. Media type used for rendering. 2. Spatial Attitude of InterpretOut rendered Object. |
||||||||||
Metadata |
|
8.4.8 InterpretOut
Purpose | An Item containing the description of the Item object of an InterpretIn Item. | ||||||||||
Functional Requirements | Interpreted Items shall be:
1. Described by the IDs of the Interpreted Item. 2. Rendered to the User as a perceptible Object. |
||||||||||
Metadata |
|
8.5 Finance-related Items
8.5.1 Asset
Purpose | An Item that may be the object of a Transaction. | ||||||||||||
Functional Requirements | An Asset may be:
1. MM-Embedded at an M-Location. 2. Posted to a Service (e.g., a marketplace). An Asset shall: 1. Preserve the Data Formats of the Item that has spawned it. 2. Include the date it was created. |
||||||||||||
Metadata |
|
8.5.2 Ledger
Purpose | An Item containing a list of Transactions involving Assets. | ||||||||||
Functional Requirements | The list of entries of a Ledger is based on:
1. The types of Item included in the Ledger. 2. The Items at an M-Location. 3. The Users to which a Ledger refers. 4. The duration in time to which a Ledger refers. 5. The Items in a DiscoverOut Item. |
||||||||||
Metadata |
|
8.5.3 Provenance
Purpose | The Ledger associated and included in the metadata of a specific Asset. | ||||||||||||
Functional Requirements | The Provenance Item shall include the list of all Transactions executed:
1. On an Asset. 2. Starting from the first Transaction and including the last. 3. The Marketplace on which a Transaction was performed. |
||||||||||||
Metadata |
|
8.5.4 Transaction
Purpose | Item representing the changed state of the Wallets and the Rights of a seller User and a buyer User on an Asset and optionally of the Service facilitating/enabling the Transaction | ||||||||||||||||||||||
Functional Requirements | The Transaction shall represent:
1. The Time the Transaction is performed. 2. The Value moving into the Wallet of User 1 (seller). 3. The Value moved from the Wallet of User2 (buyer). 4. The Value moved into the Wallet of User 3 (service) – optional. 5. The Time the Value has moved to the seller Wallet. 6. The Time the Value has moved from the buyer Wallet. 7. The Rights to Act on the Asset owned by User1 after Time. 8. The Rights to Act on the Asset owned by User2 after Time. |
||||||||||||||||||||||
Metadata |
|
8.5.5 Value
Purpose | An Amount and the Currency with which the Amount is expressed. | ||||||
Functional Requirements | Value shall have a representation that enables the expression of the Amount and the Currency used to represent the Amount. | ||||||
Metadata |
|
8.5.6 Wallet
Purpose | A container of Values. | ||||||||
Functional Requirements | A Wallet shall enable the representation of the Amounts in each Currency. | ||||||||
Metadata |
|
8.6 Perception-related Items
8.6.1 Event
Purpose | An Entity that includes selected Entities at an M-Location and their Animations during a period. | ||||||||||||
Functional Requirements | An Event shall include:
1. Start Time and End Time. 2. M-LocationID. 3. List of selected Entities and their Animations. |
||||||||||||
Metadata |
|
8.6.2 Experience
Purpose | An Entity comprising User-selected Entities of an Event and the User Interactions with the Entities of the Event. | ||||||||||||
Functional Requirements | An Experience shall include:
1. ID of User who 2. The ID of the User who has selected Entities and performed Interactions. 3. Start Time and End Time 4. EventID 5. List of selected Entities, their Animations, and User Interactions. |
||||||||||||
Metadata |
|
8.6.3 Interaction
Purpose | An Item containing the Request-Action issued by a User on an Entity at an M-Location and the corresponding Time. | ||||||||||||
Functional Requirements | Interaction shall include the Request-Action Item. | ||||||||||||
Metadata |
|
8.6.4 Map
Purpose | An Item whose structure establishes a correspondence between U-Locations with M-Locations. | ||||||||||
Functional Requirements | A Map shall include a list containing for each U-LocationID the M-Location(s) corresponding with the U-Location:
1.1. The U-LocationID and the corresponding M-LocationID(s). 1.2. Metadata related to the U-LocationID. 1.3. Metadata related to the M-LocationID. |
||||||||||
Metadata |
|
8.6.5 Model
Purpose | An Object representing an object in the Universe whose features are ready to be MM-Animated or UM-Animated. | ||||||||||||||
Functional Requirements | A Model shall include:
1. The type(s) of Media (Audio-Visual-Haptic) composing the Model. 2. The type of Model, e.g.: 2.1. An inanimate Object (e.g., a table) 2.2. An autonomous Object (e.g., a robot) 2.3. An animal, possibly with high accuracy. 2.4. A human, possibly with high accuracy. |
||||||||||||||
Metadata |
|
8.6.6 Object
Purpose | An Item with at least one Audio, Visual and Haptics perceptibility attribute. | ||||||||||||||
Functional Requirements | An Object shall include:
1. The type(s) of Media (Audio-Visual-Haptic) composing the Model. 2. The Data representation 2.1. Audio Data representation, e.g.: 2.1.1. Mono (e.g., speech) 2.1.2. Stereo 2.1.3. Multichannel 2.1.4. Microphone array 2.1.5. Spatial Audio 2.2. Visual Data representation, e.g.: 2.2.1. Still 2.2.2. Mono 2.2.3. Camera array 2.2.4. Light field 2.2.5. Holography 2.3. Haptic Data representation. 3. The type of Object, e.g.: 3.1. An inanimate Object (e.g., a table) 3.2. An autonomous Object (e.g., a robot) 3.3. An animal, possibly with high accuracy 3.4. A human, possibly with high accuracy 4. The Data Format used. |
||||||||||||||
Metadata |
|
8.6.7 Scene
Purpose | A possibly hierarchical Composition of Objects having Spatial Attitudes. | ||||||||||||||
Functional Requirements | 1. It should be possible to MM-Embed a Scene at a specified M-Location.
2. The Objects in the Scene may: 2.1. Have a Spatial Attitude. 2.2. Be MM/UM-Animated. |
||||||||||||||
Metadata |
|
8.6.8 Stream
Purpose | An Item made by a continuous flow of Data. | ||||||||||
Functional Requirements | Streams may be scalable in space and time.
Streams may be used to: 1. Animate a Model. 2. Represent a Digitised Object in an M-Instance. |
||||||||||
Metadata |
|
8.6.9 Summary
Purpose | An Item containing Text and Personal Status labels. | ||||||||||
Functional Requirements | A Summary is an abridged outline of the utterance(s) of one or more Users possibly including their Personal Statuses. | ||||||||||
Metadata |
|
8.7 Space-related Items
8.7.1 M-Location
Purpose | An Identified delimited space of an M-Environment. | ||||||||||
Functional Requirements | An M-Location:
1. Shall define the space of the M-Instance belonging to the M-Location. 2. May enable the creation of sub-spaces defining sub-M-Locations |
||||||||||
Metadata |
|
8.7.2 U-Location
Purpose | An identifiable delimited portion of the Universe. | ||||||||||
Functional Requirements | A U-Location shall:
1. Shall define the space in the Universe belonging to the U-Location. 2. May enable the definition of sub-spaces defining sub-U-Locations comprised in the U-Location. The enforcement of Rights to a U-Location is not part of this document. |
||||||||||
Metadata |
|
<– Functional Requirements of Processes Go to ToC Functional Requirements of Actions–>