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

1    Definition

A Data Type digitally representing the surface and relevant features of a 3D object:

  • Sensed from the real world for use in a Virtual Space, or
  • Digitally generated, or
  • A mixture of the two.

It may be rendered  to be perceived as signals in the human-visible range (380 to 700 nm).

2     Functional Requirements

A 3D Model Object includes the Qualifier of the Data Type of which the 3D Model is an instance.

A 3D Model of a human is called Persona and may:

  1. Faithfully reproduce the visual appearance of the human.
  2. Have their visual appearance altered, compared to that of the human.
  3. Have an unrelated visual appearance.
  4. Display a presumptive Personal Status in speech, face, and gesture.
  5. Be driven by
    • The movements of the human.
    • A Process.

3     Syntax

https://schemas.mpai.community/PAF/V1.3/data/3DModel.json

4     Semantics

Label Size Description
Header N1 Bytes 3DModel Header
– Standard-3DModel 9 Bytes The characters “PAF-3MO-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.
3DModelID N5 Bytes Identifier of the 3DModel.
3DModelDataSpaceTime N6 Bytes Space-Time of 3DModel.
3DModelDataQualifier N7 Bytes Qualifier of 3DModel.
3DModelDataLength N8 Bytes Number of Bytes used by 3DModel.
3DModelDataURI N9 Bytes URI of Data of 3DModel.
DescrMetadata N10 Bytes Descriptive Metadata.

5     Conformance Testing

A Data instance Conforms with 3D Model Object (PAF-3MO) V1.3 if

  1. JSON Data validate against the 3D Model Object’s JSON Schema.
  2. All Data in the 3D Model 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