1.      Definition

Visual Data entering an AIW or AIM.

 2      Functional Requirements

Input Visual shall have a Format ID and an Attribute ID.

Input Visual is used in different application domains.

In the Connected Autonomous Vehicle domain, Input Visual is used to:

  1. Provide the location of visual objects.
  2. Incorporate outdoor Visual information into the Basic Environment Representation.

3      Syntax

https://schemas.mpai.community/OSD/V1.1/data/InputVisual.json

 4       Semantics

Label Size Description
Header N1 Bytes Input Visual Header
– Standard 9 Bytes The characters “CAE-IVI-V”
– Version N2 Bytes Major version – 1 or 2 characters
– Dot-separator 1 Byte The character “.”
– Subversion N3 Byte Minor version – 1 or 2 characters
MInstanceID N4 Bytes ID of the Metaverse Instance.
InputVisualID N5 Bytes ID of Input Visual.
InputOutputVisualData N6 Bytes Set of Input Visual Data
– InputVisualFormatID Ny Bytes ID of Visual Format
– InputVisualLength N8 Bytes The Length of Input Visual in Bytes
– InputVisualDataURI N9 Bytes The URI of Input Visual
InputVisual N10 Bytes Set of Attributes of Input Visual
– InputVisualAttributeID N11 Bytes The Attribute ID of Input Visual
– InputVisualAttributeFormatID N12 Bytes The Attribute Format ID of Input Visual
– InputVisualAttributeLength N13 Bytes The Length of Input Visual Attribute in Bytes
– InputVisualAttributeDataURI N14 Bytes URI of Input Visual Attribute
DescrMetadata N15 Bytes Descriptive Metadata

5         Data Formats

VisualFormats and VisualAttributes are required.

 6       To Respondents

Respondents are invited to propose Visual Formats and Visual Attributes.