<-Operation Model Go to ToC Actions->
An instance of a Program running in a Device or in the computing platform underpinning an M-Instance. Process is specified by:
- The Functions it performs
- Its Process Capabilities.
- Metadata having the general form:
| ProcessID | The ID of the Process. |
| InRights | The list of Process Actions the Process can perform. |
| OutRights | The list of Process Actions that another Process can request the Process to perform. |
| WalletID | The ID of the Wallet related to the Process. |
| DescrMdata | Any human-readable description of the Process. |
Metadata are extensible.
The Manager of the M-Instance running a Process may request that the Process be certified.
There are four types of Process.
| 1 App | 2 Device | 3 Service | 4 User |
1 App
| Functions | An instance of 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. |
2 Device
| Functions | A Device can:
1. UM-Capture Data from a U-Location |
| Functional Requirements | To connect and interoperate with an M-Instance, a Device needs to expose its Process Capabilities to the M-Instance. |
3 Service
| Purpose | A Process that provides 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. |
1.4 User
| Purpose | A Process representing a Registered human. |
| Functional Requirements | 1. A User may perform the following functions: 1.1. Act as the interface of the human with the M-Instance. 1.2. Render the User as a Persona UM-Animated by a Stream or 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 by the human or by the M-Instance. |
