<– Metaverse Operation Model Go to ToC Functional Requirements of Items–>
7.1 App
Purpose | An application-specific Program executed on a Device. | ||||||||||
Functional Requirements | The Manager of the M-Instance in which an App will be deployed may request that the Device be subject to certification. | ||||||||||
Metadata |
|
7.2 Device
Purpose | 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. |
||||||||||
Functional Requirements | To connect and interoperate with an M-Instance, a Device needs to
1. Exchange Capabilities with the M-Instance. 2. Use the same Item Data Formats or rely on a Conversion Service. The Manager of the M-Instance to which a Device connect may request that the Device be subject to certification. |
||||||||||
Metadata |
|
7.3 Service
Purpose | A Process that can be called to provide specific Functionalities. | ||||||||||
Functional Requirements | A Service may be:
1. One of the Services natively supported by an M-Instance. 2. Hosted by the M-Instance but provided by a third party. A hosted Service may be subject to certification by the Manager of the M-Instance or an entity delegated by them. |
||||||||||
Metadata |
|
7.4 User
Purpose | A Process representing a human. | ||||||||||||
Functional Requirements | 1. A User may perform the following functions:
1.1. The interface of the human with the M-Instance. 1.2. Render the User as a Persona: 1.2.1. UM-Animated by a Stream. 1.2.2. MM-Animated by an autonomous agent. 2. Animation results from an MM-/UM-Animate Action and enabled by a Program run by the User. 3. The Animation Program may be provided: 3.1. By the human. 3.2. By the M-Instance. The Manager of the M-Instance where a User running a proprietary Program is deployed may request that the Program be subject to certification. |
||||||||||||
Metadata |
|
<– Metaverse Operation Model Go to ToC Functional Requirements of Items–>