This chapter specifies purpose, functional requirements, and metadata for the four types of Process in M-Instance

1  App

2 Device

3 Service

4 User

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
AppID The ID of the App.
InRightsID The ID of the User’s Rights to Act on the App.
OutRightsID The ID of the Rights a User may acquire to act on the App.
DescrMdata Any description of the App.

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 is connected may request that the Device be subject to certification.
Metadata
DeviceID The ID of the Device.
InRightsID The ID of the Device’s Rights.
OutRightsID The ID of the Rights a User may acquire to act on the Device.
DescrMdata Any description of Device.

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. The Manager of the M-Instance may request certification of a hosted Service..
Metadata
ServiceID The ID of the Service.
InRightsID The ID of the User’s Rights to Act granted to the Service.
OutRightsID The ID of the Rights a User may acquire to Act on the Service.
DescrMdata Any description of the Rights.

1.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
UserID ID of User.
InRightsID ID of Rights held by User.
AccountIDs IDs of the Accounts where the User can operate.
WalletIDs IDs of Wallets User has Rights on.
PersonalDataID ID of Personal Data.
DescrMdata Any description of the User.