Respondents are invited to propose Data Formats and Attributes of Data Types (Item) as described below.
1 General
| Items | Formats and Attributes | Requests to Respondents |
| Contract | MPAI expects that MMM Contracts, whether they are expressed by a contract expression language or executed a programming language, may also be developed by independent entities and carry a Contract-specific Contract FormatID. Reference to the future Data Types, Formats, and Attributes will be used as the basis for a Register of Contract Data Formats. | MPAI requests:
1. Comments on the Functional Requirements and JSON Syntax and Semantics of Contract. 2. Comments on the role of future Data Types, Formats, and Attributes as support for a Register of Contract Data Formats. 3. Suggestions of how such a Register should be operated. 4. Proposals for an initial list of Contract Formats and Attributes. |
| E-Capabilities | E-Capabilities require Item Format IDs which are handled Item by Item and Basic Data Format ID. | MPAI requests comments on the Functional Requirements and JSON Syntax and Semantics of E-Capabilities. |
| Identifier | No new Data Formats required. | MPAI request comments on:
1. Functional Requirements #2 (an Identifier of an Item may have a hierarchical structure )and #3 (An Identifier may signal the type of Process or Item it identifies). 2. JSON Syntax and Semantics of Identifier |
| M-Capabilities | M-Capabilities requires Item Format IDs which are handled Item by Item. | MPAI request comments on
1. Functional Requirements 2. JSON Syntax and Semantics. |
| No new Data Formats required. | MPAI request comments on:
1. Functional Requirements. 2. The JSON Syntax and Semantics. |
|
| Program | MPAI expects that different entities may develop and wish to import different Programs into an M-Instance. An M-Instance may require that a Program be certified before being imported. | MPAI requests:
1. Comments on a. Functional Requirements. b. JSON Syntax and Semantics. c. Program certification. 2. Proposals for an initial list of Program Formats and Attributes. |
| Rights | No new Data Formats required. | MPAI request comments on
1. Functional Requirements 2. JSON Syntax and Semantics. |
| MPAI assumes that different M-Instances will use different Rules. | MPAI requests:
1. Comments on: 1.1. Functional Requirements. 1.2. JSON Syntax and Semantics. 2. Proposals for Rules Formats and Attributes. |
2 Human and User
| Items | Data Formats | Requests to Respondents |
| Account | No new Data Formats required. | MPAI request comments on the Functional Requirements of Accounts. |
| Activity Data | No new Data Formats required. | MPAI request comments on the Functional Requirements of Activity Data. |
| Personal Profile | No Data Formats involved, save for Text for which MPAI has selected ISO/IEC 10646. | MPAI request comments on the Functional Requirements.
|
| Personal Data | No new Data Formats required. | MPAI request comments on the Functional Requirements |
3 Process Interaction
| Items | Data Formats | Requests to Respondents |
| Message | Message requires Data Formats. | MPAI request proposals for an initial set of Message Data Formats and Attributes. |
| P-Capabilities | No new Data Formats required. | MPAI request comments on Functional Requirements. |
| Process Action | No new Data Formats required. | MPAI request comments on Functional Requirements. |
| Request-Action | No new Data Formats required. | MPAI request comments on Functional Requirements. |
| Response-Action | No new Data Formats required. | MPAI request comments on
1. Functional Requirements of Response-Action. 2. Error messages |
4 Service Access
| Items | Data Formats | Requests to Respondents |
| Discover | MPAI assumes that different Discover Services will use different Discover Formats. | MPAI requests:
1. Comments on Functional Requirements. 2. Proposals for an initial list of Discover Formats. |
| Inform | MPAI assumes that different Inform Services will use different Inform Formats. | MPAI requests:
1. Comments on Functional Requirements. 2. Proposals for an initial list of Inform Formats. |
| Interpret | MPAI assumes that different Interpret Services will use different Ininterpret Formats. | MPAI requests:
1. Comments on Functional Requirements. 2. Proposals for an initial list of Interpret Formats. |
5 Finance
| Items | Data Formats | Requests to Respondents |
| Asset | No new Data Formats required. | MPAI request comments on Functional Requirements. |
| Provenance | No new Data Formats required. | MPAI request comments on Functional Requirements. |
| Transaction | No new Data Formats required. | MPAI request comments on Functional Requirements. |
| Value | No new Data Formats required. | MPAI request comments on Functional Requirements. |
6 Perception
| Items | Data Formats | Requests to Respondents |
| Audio Object | Audio Object Data Formats are important Service differentiators. Many formats are expected to be used. | MPAI requests:
1. Comments on Functional Requirements. 2. An initial list of Audio Data Formats to appear in the future Data Types, Formats, and Attributes. |
| Visual Objects | Visual Object Data Formats are important Service differentiators. Many formats are expected to be used. | MPAI requests:
1. Comments on Functional Requirements. 2. An initial list of Visual Data Formats to appear in the future Data Types, Formats, and Attributes. |
| Audio-Visual Basic Scene Descriptors | No new Data Formats required.
|
MPAI requests comments on Functional Requirements of Audio-Visual Basic Scene Descriptors. |
| Audio-Visual Scene Descriptors | No new Data Formats required.
|
MPAI requests comments on Functional Requirements of Audio-Visual Basic Scene Descriptors. |
| Universe to Metaverse Map | No new Data Formats required. | MPAI requests comments on Functional Requirements of Universe to Metaverse Map.
|
| Model | No new Data Formats required beyond those needed for Visual Object. | MPAI requests comments on Functional Requirements of Model. |
| Stream | There are already and there will likely be more Stream Formats. | MPAI requests
1. Comments on Functional Requirements of Model. 2. Proposals of Formats for inclusion in the future Data Types, Formats, and Attributes |
| Summary | There are already rich data formats. Summary requires extensions. | MPAI requests
1. Comments on Functional Requirements of Summary. 2. Proposals of Formats for inclusion in the future Data Types, Formats, and Attributes |
7 Space
| Items | Data Formats | Requests to Respondents |
| Spatial Attitude | Object Types, Media Types, and Coordinate Types are required. | Respondents are requested to comment on Functional Requirements and Object Type ID, Media Type ID, and Coordinate Type ID. |
| Point of View | Object Types, Media Types, and Coordinate Types are required. | Respondents are requested to comment on Functional Requirements and Object Type ID, Media Type ID, and Coordinate Type ID. |
| U-Environment | Formats for identifying U-Environments are required.
|
MPAI requests
1. Comments on Functional Requirements of Summary. 2. Proposals of Formats for inclusion in the future Data Types, Formats, and Attributes |
| Basic M-Location | Formats for identifying M-Locations are required.
|
MPAI requests
1. Comments on Functional Requirements of M-Locations. 2. Proposals of M-Location Formats for inclusion in the future Data Types, Formats, and Attributes |
| M-Location | Formats for identifying M-Locations are required.
|
MPAI requests
1. Comments on Functional Requirements of M-Locations. 2. Proposals of M-Location Formats for inclusion in the future Data Types, Formats, and Attributes |
| Basic U-Locations | Formats for identifying U-Locations are required.
|
MPAI requests
1. Comments on Functional Requirements of U-Location. 2. Proposals of U-Location Formats for inclusion in the future Data Types, Formats, and Attributes |
| U-Location | Formats for identifying U-Locations are required. | MPAI requests
1. Comments on Functional Requirements of U-Location. 2. Proposals of U-Location Formats for inclusion in the future Data Types, Formats, and Attributes |
