1     Definition 2     Functional Requirements 3     Syntax
4     Semantics 5    Conformance Testing 6     Performance Assessment

1      Definition

A Data Type representing a text-based abridged outline of the utterance(s) of one or more Entities represented as User ID,  Space-Time, Text, and Personal Statuses.

2      Functional Requirements

Summary includes:

  1. Virtual Space where Summary was generated  (M-Instance).
  2. Space-Time information in the Virtual Instance.
  3. Content for each speaking Entity:
    1. Text
    2. Space-Time information of the Entity the Text refers to.
    3. Personal Status of the Entity the Text refers to.

3      Syntax

https://schemas.mpai.community/MMC/V2.3/data/Summary.json

4      Semantics

Label Size Description
Header N1 Bytes Summary Header
– Standard-Item 9 Bytes The characters “MMC-SUM-V”
– Version N2 Byte Major version – 1 or 2 Bytes
– Dot-separator 1 Byte The character “.”
– Subversion N3 Bytes Minor version – 1 or 2 Bytes
MInstanceID N4 Bytes Identifier of M-Instance.
SummaryID N5 Bytes Identifier of the Summary.
SummarySpaceTime N6 Bytes Space-Time of Summary.
SummaryData[] N7 Bytes Data of Summary
– ReportedEntityID N8 Bytes ID of the Entity Reported in Summary
– ReportedEntityPersonalStatus N9 Bytes Personal Status of Entity Reported in Summary
– ReportedEntitySpaceTime N10 Bytes Time-Space info of Entity Reported in Summary
 – ReportedEntityTextObject N11 Bytes Text Object of Entity Reported in Summary
SummaryData N12 Bytes Summary Data.
– SummaryDataLength N13 Bytes Number of Bytes in Summary Data
– SummaryDataURI N14 Bytes URI of Data of Summary Data
DescrMetadata N15 Bytes Descriptive Metadata

5     Conformance Testing

A Data instance Conforms with MPAI-MMC V2.3 Summary (MMC-SUM) if:

  1. The Data validates against the Summary’s JSON Schema.
  2. All Data in the  Summary’s JSON Schema
    1. Have the specified type
    2. Validate against their JSON Schemas
    3. Conform with their Data Qualifiers if present.

6     Performance Assessment