1      Definition

Rules is an Item representing the set of rules governing an M-Instance of M-Environment.

2      Functional Requirements

The Rules Item may include:

  1. M-Instance specificities:
    • Permission-based or permission-less access policy
    • Trusted or trust-less relationship between Users and M-Instance
    • Access policies to public/private spaces
    • Certification requirements for imported Processes and Data
    • Scope of Rights for each Account type
    • Rights to offer Services
    • Inter M-Instance activity policy
  2. Personal Data
    • Subsets of required Personal Data for each Account type.
    • Processes and Personae
    • Activity Data retention, processing and access policy
  3. Rights
    • Maximum number of
      • Processes per Account
      • Maximum number of Personae for each User
      • Maximum number of concurrent Users and Objects
    • Extent of Rights to import, store, retrieve, export Processes, Items, and Data
      • Import audio, speech, visual, and haptic models
      • Persistently store Items
      • Store, search, and retrieve Scenes and Events
      • Export Items
    • Communication
      • Authenticate Items and  Processes
      • Send public or private Speech, Audio, Visual, and Haptic Messages
      • Make Items inaccessible
    • Place Items with Spatial Attitudes at M-Locations
    • Connect with other M-Instances
  4. Develop Economic Activity
    • Acquire Rights
    • Grant Rights
    • Make or request a Process to make Actions
    • Create persistent (as opposed to ephemeral) Scenes at M-Locations.
    • Exclusive use M-Locations for a duration.
    • Perform or request another User to perform Actions on Items.
    • Develop an economic activity in an M-Environment.
    • Make an Asset out of an Item.
    • Make a Transaction on an Asset.
    • Make an agreement with another User, e.g., via a Contract.
  5. Service Access
    • Author an Item.
    • Obtain Conversion of an Item from a Format to another Format.
    • Change the Rights of a Process.
    • Discover Objects, Processes, Events, or Experiences.
    • Find the Transactions involving an Asset under specified conditions.
    • Obtain an interpretation of an Item
    • Obtain information about a Process or an Item.
    • Obtain a recommendation of Processes or Items.
    • Posts an Item that can be Transacted (Asset) to a marketplace.
    • Store Objects, Scenes, Events.
    • Retrieve Objects, Scenes, Events.
  6. Activity Regulation
    • A priori/a posteriori/mixed/random control
    • Sanctions applied to Users for lack of Actions in compliance with the Rules

3      Syntax

https://schemas.mpai.community/MMM4/V1.0/data/Rules.json

4      Semantics

Label Size Description
Header N1 Bytes Header of Rules Item.
– Standard 9 Bytes The characters “MMM-RUL-V”.
–  Version N2 Bytes Major version expressed as 1 or 2 characters.
– Dot-separator 1 Byte The character “.”
– Subversion N3 Byte Minor version expressed as 1 or 2 characters
MInstanceID N4 Bytes Identifier of M-Instance.
RulesID N5 Bytes The ID of the Rules
RulesDataQualifier N6 Bytes Qualifier of Rules.
RulesDataLength N7 Bytes Number of Bytes of Rules Data.
RulesDataURI N8 Bytes URI of Rules Data.
DescrMetadata N9 Bytes Descriptive Metadata.