<–Use Cases    Go to ToC      Conclusions–>

Table of Contents of Chapter 9 – Functionality Profiles

9.1    Profile elements

9.2    Profile structure

9.3    Baseline Functionality Profile

9.4    Finance Functionality Profile

9.5    Management Functionality Profile

9.6    High Functionality Profile

9.1        Profile elements

Table 1 lists the currently identified Actions, Items and Data Types. Actions in italic require more than one Action to be executed.

Table 28 – Metaverse Actions, Entities, and Data Types

Actions Items Data Types
Authenticate Account Address
Author Activity Data Amount
Change App Cognitive State
Discover Asset Coordinates
MU-Export Device Currency
Hide DiscoverIn Emotion
Identify DiscoverOut Personal Status
Inform Event Point
Interpret Experience Point of View
MM-Add Identifier Social Attitude
MM-Animate InformIn Spatial Attitude
MM-Capture InformOut Time
MM-Embed InterpretIn Orientation
MM-Enable InterpretOut Position
MM-Disable Interaction
MM-Send Ledger
MU-Render Map
MU-Actuate M-Environment
MM-Send Message
Post M-Instance
Read M-Location
Register Model
Track Object
Transact Persona
UM-Animate Personal Profile
UM-Capture Process
UM-Render Provenance
UM-Send Rights
Rules
Scene
Service
Social Graph
Stream
Transaction
U-Environment
U-Location
User
User Data
Value
Wallet

9.2        Profile structure

The structure of the Metaverse Functionality Profiles derived from the above includes hierarchical Profiles and independent Profiles. Profiles may have Levels. As depicted in Figure 3, the currently identified Profiles are Baseline, Management, Finance, and High. Details are provided in the next Sections. The currently identified Levels for Baseline, Management, and High Profiles are Audio only, Audio-Visual, and Audio-Visual-Haptic.

Figure 3 – the currently identified Functionality Profiles

The allocation of Actions and Items is made for The Baseline, Finance, and Management Profiles. The identified four Profiles serve well the needs conveyed by the identified Functionalities. As more of them will be added, the number of Profiles and potentially of Levels, is likely to increase.

9.3        Baseline Functionality Profile

The Baseline Functionality Profile enables a human equipped with a Device to allow their Users to perform the functions of Table 29. Basic forms of baseline lecture, meeting, and hang-out are supported but not Transactions and User management.

Table 29 – Actions and Items of the Baseline Functionality Profile

Functions Action Items
Call Service Call Service, Item
Read Items and Data Read Item
Create and Identify Item Identify Item, Identifier
Make Item inaccessible Hide Item
Author Entity Author Item
Place Entity at an M-Loc, no perception MM-Add Entity, M-Loc
Make MM-Added Entity perceptible MM-Enable Entity
Place an Entity at M-Loc, w/ perception MM-Embed Entity, M-Loc
Animate Model with an autonomous Process MM-Animate Model
Make available Object to a User MM-Capture Entity
Stop perception of Scene MM-Disable Entity, M-Loc
Render at U-Loc Entity at M-Loc MU-Render Entity, M-Loc, U-Loc
Make scene at U-Loc available to a Device UM-Capture U-Loc
Make Data of a Device available to a Process UM-Send Device, Process
Transfer Data between Processes MM-Send Message
Animate Model @M-Loc w/ Data from U-Loc UM-Animate Model, U-Loc
Place Entity @ M-Loc w/ Data from U-Loc UM-Render Entity, M-Loc, U-Loc
Send an Entity at an M-Loc to a Device MM-Send Entity, Device, M-Loc
Place & Animate Model at M-Loc, Render Track Model, Stream
Store Item MU-Export Item
App triggers perception of Entities Map

Note that this Use Case implies: M-Instance, User and that Entity implies Scene, Object, Model, Persona.

Table 30 lists the Actions, Entities, and Data Types of the Baseline Functionality Profile.

Table 30 – Actions, Entities, and Data Types of the Baseline Functionality Profile

Actions Author Call Identify Destroy
MU-Export MM-Add MM-Animate MM-Capture
MM-Embed MM-Disable MM-Enable MM-Send
MU-Render Read Track UM-Animate
UM-Capture UM-Render UM-Send
Items Identifier Map Message M-Instance
M-Location Model Object Process
Scene Service Stream U-Location
User
Data Types Address Coordinates Orientation Position
  Spatial Attitude

9.4        Finance Functionality Profile

The Financial Functionality Profile enables a User to Post Assets and make Transactions. As depicted in Figure 5, this Profile is independent of the Basic and Management Functionality Profiles. It contains a subset of the Actions, Items, and Data Types of the Baseline Profile and adds Financia-related Actions, Items, and Data Types. Currently, this Profile does not have Levels.

The Finance Functionality Profile enables a human equipped with a Device to enable their Users to perform the functions of Table 31. The Table does not include Actions and Item already introduced in the Baseline Profile.

Table 31 – Actions and Items of the Finance Functionality Profile

Functions Action Items
Register Register M-Environment, Account, Activity Data
Personal Profile, Rules, Social Graph
Submit Asset to marketplace Post Asset
Make a Transaction of an Asset Transact Asset, Ledger, Provenance, Rights,
Transactions, Value, Wallet
Discover Assets Discover Request-Discover, Response-Discover
Get information on Asset, User Inform Request-Inform, Response-Inform
Change User Rights Change

Table 32 lists the Actions, Entities, and Data Types of the Finance Functionality Profile.

Table 32 – Actions, Entities, and Data Types of the Finance Profile

Actions Change Discover Inform Post
Register Transact
Items Account Activity Data Asset Ledger
M-Environment Personal Profile Provenance Request-Discover
Request-Inform Response-Discover Response-Inform Rights
Rules Social Graph Transaction Value
Wallet
Data Types Amount Currency Time

9.5        Management Functionality Profile

The Management Functionality Profile supports all Actions, Items, and Data Types of the Baseline Profile and those enabling a controlled ecosystem where humans Register, Users are Authenticated, and advanced Services, such as Discover and Interpret, can be Called.

The Management Functionality Profile extends the capabilities of the Baseline Profile to perform the functions of Table 33. The Table does not include Actions and Item already introduced in the Baseline and Finance Functionality Profiles. As depicted in Figure 5 the Management Functionality Profile is a superset of the Baseline Profile.

Table 33 – Actions and Items of the Baseline Functionality Profile

Functions Action Items
Register with an M-Environment (Register) M-Environment
Check that an Entity is what it says it is Authenticate Request-Authenticate,

Response-Authenticate

Request interpretation of Item Interpret Request-Interpret,

Response-Interpret

Save the Experience of an Event (MU-Export) Interaction, Experience, Event

Table 34 lists the Actions, Entities, and Data Types of the Management Functionality Profile that are not already included in the Baseline and Finance Profile.

Table 34 – Actions, Entities, and Data Types of Management Profile

Actions Authenticate Interpret
Items Event Experience Interaction M-Environment
Request-Authenticate Response-Authenticate Request-Interpret Response-Interpret
Data Types Cognitive State Emotion Personal Status Social Attitude

9.6        High Functionality Profile

This Profile includes all other Profiles. The list of Actions, Entities, and Data Types required for this Profile is provided by Table 28.

<–Use Cases    Go to ToC      Conclusions–>