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

1      Definition

A Data Type composed of

  1. Content represented by characters from a character set (Text Data).
  2. Text Qualifier.
  3. Text Space-Time information.

2      Functional Requirements

A Text Object includes:

  1. The ID of a Virtual Space (M-Instance) where it is or it will be located.
  2. The ID of the Text Object.
  3. The Text Object Space-Time information.
  4. The Text Data Qualifier.
  5. The Text Data as:
    1. A string, or
    2. A Text Payload represented as
      1. Length in Bytes of the Text Data.
      2. URI of the Text Data.

3      Syntax

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

4      Semantics

Label Size Description
Header N1 Bytes Text Object Data Header
– Standard-Visual Object 9 Bytes The characters “MMC-TXO-V”
– Version N2 Bytes Major version – 1 or 2 characters
– Dot-separator 1 Byte The character “.”
– Subversion N3 Bytes Minor version – 1 or 2 characters
MInstanceID N4 Bytes Identifier of M-Instance.
TextObjectID N5 Bytes Identifier of the Text Object.
TextObjectSpace-Time N6 Nytes Space-Time info of Text Object.
TextDataQualifier N7 Bytes Text Data Qualifier
TextDataPayload N8 Bytes Data of Text Object.
– Text as string, or N9 Bytes Text represented by a string.
– TextDataPayload N10 Bytes The Payload of the Text Object
  – TextObjectLength N11 Bytes Number of Bytes in Text Payload
  – TextObjectDataURI N12 Bytes URI of Data of Text Payload
DescrMetadata N13 Bytes Descriptive Metadata

5     Conformance Testing

A Data instance Conforms with MPAI-MMC V2.3 Text Object (MMC-TXO) if:

  1. The Data validates against the Text Object’s JSON Schema.
  2. All Data in the Text Object ’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