4.3 Functional Requirements – Items

1.      An M-Instance-specific subset of the Registered human’s User Data.

2.      The Rights held by the human’s Users.

3.      The duration of the Rights.

4.      The duration of validity of the Account.

1.      The M-Instance ID.

2.      The duration the Activity Data refer to.

3.      The list of Interactions.

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

2.      Information related to the rendering of AuthenticateOut.

1.      Speech produced by a User.

2.      The visual appearance of a User

Information on the Rendering of InterpretOut may be provided by:

1.      Media type used for rendering.

2.      Spatial Attitude of InterpretOut rendered Object.

1.      Made available to the User as Item, or

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

The Data of a Contract shall be in a form that allows its execution in the M-Instance.

1.      A description of the Items to be Discovered.

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 DiscoverOut rendered Object.

1.      Described by the IDs of the Items Discovered.

2.      Rendered to the User as a perceptible Object.

1.      Start Time and End Time.

2.      M-LocationID.

3.      List of selected Entities, their Animations, and Interactions.

1.      Start Time and End Time

2.      EventID

3.      List of selected Entities, their Animations, and User Interactions.

An Identifier of an Item may have a hierarchical structure:

1.      M-InstanceID

2.      M-EnvironmentID

3.      M-LocationID

4.      ItemID.

An Identifier of an Item may have a hierarchical structure:

1.      M-InstanceID

2.      M-EnvironmentID

3.      ProcessID

4.      ItemID.

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 have on the Item.

Information on rendering of InformOut may be provided by:

1.      Media type 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.      The types of Item 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.      The M-Location it refers to.

2.      A list containing for each U-LocationID having one correspondence with an Entity at the M-Location:

2.1.   The IDs of the M-Location corresponding to the U-LocationID.

2.2.   Metadata related to the U-LocationID.

2.3.   Metadata related to the M-LocationID.

1.      An Item, or

2.      Data and Metadata

1.      Define the space of the M-Instance belonging to the M-Location.

2.      Enable the creation of sub-spaces defining sub-M-Locations

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

2.      The type of Model

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

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

2.3.   An animal, possibly with high accuracy

2.4.   A human, possibly with high accuracy

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

2.      The Data representation

2.1.   Audio Data representation

2.4.3.     Mono (e.g., speech)

2.1.2.     Stereo

2.1.3.     Multichannel

2.1.4.     Microphone array

2.1.5.     Spatial Audio

2.2.   Image Data representation

2.3.   Visual Data representation

2.3.1.     Mono

2.3.2.     Camera array

2.3.3.     Light field

2.3.4.     Holography

2.4.   Haptic Data representation

3.      The type of Object

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

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

3.3.   An animal, possibly with high accuracy

3.4.   A human, possibly with high accuracy

1.      First Name

2.      Last Name

3.      Address

4.      Country

5.      Age

6.      Biometric data

7.      …

1.      Shall be executable in the M-Instance.

2.      May be subject to certification before being admitted to the M-Instance.

1.      On an Asset.

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

3.      The Marketplace on which a Transaction was performed.

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 Location of the Items.

7.      The Location 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 ability of a User to perform Actions on Items for which it has Rights.

2.      The inability of a User to perform Actions on Items for which it has no Rights.

3.      The duty of a User to perform Actions on Items.

4.      The ability of a User to make Transactions.

1.      MM-Embed a Scene at a specified M-Location.

2.      Represent Objects:

2.1.   With their Spatial Attitude.

2.2.   Animated by a stream or an autonomous agent.

1.      The types and the connections with Items and their M-Locations.

2.      The types and the connections with Devices (frequency of use, etc.).

3.      The types and the connections with Services (frequency of use, etc.).

4.      The types and the connections with Users, groups of Users in terms of:

4.1.   Time

4.2.   M-Locations.

4.3.   Declared purpose.

Streams may be used for:

1.      Animating a Model.

2.      Represent a Digitised Object in an M-Instance.

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 Values were moved.

6.      The Rights to Act owned by User1 after Time.

7.      The Rights to Act owned by User2 after Time.

1.      Define the space in the Universe belonging to the U-Location.

2.      Enable the definition of sub-spaces (sub-U-Locations) comprised in the U-Location.

The enforcement of Rights to a U-Location is not part of this document.

1.      Rights held by the 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.

User Data should have a representation that allow extraction and sharing of a User Data subset.

1.      The Amounts in each Currency.

2.      The Transactions performed.