MPAI-MMM Functional Requirements – Items

2.     An M-Instance may

2.1.  Add Functionalities not supported by MPAI-Metaverse Model – Architecture. In this case full Interoperability with other M-Instances may not be achieved.

2.2.  Enables the creation of M-Environments.

1.     Profile of the M-Instance.

2.     Data Formats supported by Items (needs a Taxonomy).

3.     Services supported (needs a Taxonomy).

An Identifier of an Item may have a hierarchical structure in case it is useful to Identify an Item based on the M-Instance, the M-Environment:

1.     M-InstanceID

2.     M-EnvironmentID

3.     ItemID.

1.       Shall express the permissions, obligations, and prohibitions with respect to Actions performed by a User on Items.

2.       May grant a User the Rights to:

2.1.      Make Transactions.

2.2.      Export Items to another Metaverse.

3.       May grant a visitor (non-Registered human) limited Rights.

1.     Shall be executable in the M-Instance.

2.     May be subject to certification before being admitted to 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.

An Account shall include:

1.     The ID of the Registered human.

2.     An M-Instance-specific subset of the Registered human’s Personal Data.

3.     The Rights held by each User in the M-Instance/M-Environment.

4.     The IDs of Devices, Apps, and Users, and Personae.

1.     The M-Instance ID.

2.     The duration the Activity Data refer to.

3.     The list of Interactions.

1.     First Name

2.     Last Name

3.     Address

4.     Nationality.

5.     Age.

1.     Rights and Obligations of the Account-holding human.

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.

1.     An Item, or

2.     Data and Metadata

2.       The characteristics of all Processes are:

2.1.      List of Actions that can be performed.

2.2.      List of Items supported with Data Formats.

2.3.      List of Data Types supported.

2.4.      The cost of performing an Action.

3.       Additionally, a Device has: Apps on board.

4.       Additionally, a User has: Human represented by User.

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.

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.

1.     The Entity or the ID of the Entity to be Authenticated.

2.     Information related to the rendering of AuthenticateOut (optional).

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.

1.     Made available to the User as Item, and

1.     Rendered to the User as a perceptible Object as specified in AuthenticateIn.

1.     A description of the Items to be Discovered or recommended.

2.     Information related to the rendering of DiscoverOut.

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.

1.     Shall be Identified by their IDs.

2.     May be:

2.1.  Accompanied by descriptions.

2.2.  Rendered to the User as a perceptible Object.

1.     A description of the Item about which information is requested.

2.     Information related to the rendering of InformOut.

1.     Item Metadata

2.     Any other information that a Service may provide on the Item.

Information on the rendering of InformOut may be provided by:

1.     Media types used for rendering.

2.     Spatial Attitude of InformOut rendered Object.

1.     Made available to the User as an Item, or

2.     Rendered to the User as a perceptible Object.

1.     The ID or the Item to be Interpreted.

2.     Information related to the rendering of InterpretOut.

Information on InterpretOut Rendering may be provided by:

1.     Media type used for rendering.

2.     Spatial Attitude of InterpretOut rendered Object.

1.     Described by the IDs of the Interpreted Item.

2.     Rendered to the User as a perceptible Object.

1.     May be:

1.1.  MM-Embedded at an M-Location.

1.2.  Posted to a Service (e.g., a marketplace).

2.     Shall:

2.1.  Preserve the Data Formats of the Item that has spawned it.

2.2.  Include the date it was Modified as Asset.

1.     The types of Items 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.

1.     On an Asset.

2.     Starting from the first Transaction and including the last.

3.     The Marketplace on which a Transaction may have been performed.

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.

1.     Start Time and End Time.

2.     M-LocationID.

3.     List of selected Entities of the M-Location.

1.     ID of User the Experience refers to.

2.     EventID

3.     Start Time and End Time of the Experience.

4.     List of Entities perceived and Interactions made by a User.

1.     The Request-Action issued by a User on an Entity at an M-Location and the corresponding Time.

2.     The Response-Action issued by the requested Process.

1.     U-LocationID and Metadata related to the U-LocationID.

2.     M-LocationID(s) and/or EntityIDs, and Metadata related to the M-LocationID(s) and/or EntityIDs corresponding to the U-LocationID.

1.     The type(s) of Media (Audio-Visual-Haptic) composing the Model.

2.     The type(s) of Animation the Model can accept.

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.2.6.     RADAR

2.2.7.     LiDAR

2.3.  Haptic Data representation.

3.     The type of Object, e.g.:

3.1.  An inanimate Object (e.g., a table).

3.2.  A Model (e.g., a Persona).

3.3.  An autonomous Object (e.g., a robot).

3.4.  An animal, possibly with high accuracy.

3.5.  A human, possibly with high accuracy.

4.     The Data Format used.

2.     The Scene may be MM-/UM-Animated.

3.     The Objects in the Scene may be MM-/UM-Animated.

1.     UM-Animate a Model.

2.     UM-Animate an Object.

3.     UM-Animate a Scene.

4.     Represent a Digitised Object (e.g., a Point Cloud) MM-Embedded at an M-Location.

1.     Shall define the space of the M-Instance or M-Environment that is included in the M-Location.

2.     May enable the creation of sub-spaces defining sub-M-Locations included in the M-Location (e.g., the rooms of an apartment).

1.     Shall define the space in the Universe that is included in the U-Location.

2.     May enable the definition of sub-spaces defining sub-U-Locations included in the U-Location.

The enforcement of Rights to a U-Location is not part of MPAI-MMM – Architecture.