<-AI Modules Go to ToC

Table 1 lists the Data Types used by CAV-TEC. Each entry includes a link to the relevant specifications. Note that several Data Types are specified by other MPAI Technical Specifications than CAV-TEC: MPAI-CAE, MPAI-MMC, MPAI-OSD, MPAI-PAF, and MPAI-TFA. Data Types referenced by such Data Types are not listed here but are specified by the relevant Technical Specification.

Table 1 – Data Types referenced by CAV-TEC

Acronym Name JSON Acronym Name JSON
OSD-3DO 3D Model Object X OSD-OOR Orientation X
CAV-ALT Alert X OSD-PAT Path X
CAV-AMD AMS Data X OSD-PCE Perceptible Entity X
CAV-AHM AMS-HCI Message X CAV-PPR Personal Preferences X
CAV-AMM AMS-MAS Message X CAV-PPF Personal Profile X
OSD-ANN Annotation X MMC-EPS Personal Status X
OSD-AUO Audio Object X OSD-OPV Point of View X
OSD-MSD AV Scene Descriptors X PAF-PAV Portable Avatar X
CAV-BED Basic Environment Descriptors X OSD-OPS Position X
PAF-BDD Body Descriptors X OSD-RAO RADAR Object X
OSD-BBX Bounding Box X OSD-RSD RADAR Scene Descriptors X
CAV-BRC Brake Command X CAV-RDA Road Attributes X
CAV-BRR Brake Response X CAV-RSS Road Signs and Signals X
CAV-BRS Brake States X CAV-RDS Road State X
CAV-CID CAV Identifier X CAV-RTE Route X
CAV-CVS CAV State X OSD-SPT Space-Time X
OSD-COO Coordinates X OSD-OSA Spatial Attitude X
CAV-ERA Ego-Remote AMS Message X CAV-SPD Spatial Data X
CAV-ERH Ego-Remote HCI Message X OSD-SPO Speech Object X
PAF-FCD Face Descriptors X OSD-TXO Text Object X
CAV-FED Full Environment Descriptors X OSD-TIM Time X
CAV-GNO GNSS Object X CAV-TRR Traffic Rules X
OSD-IID Instance Identifier X CAV-TSO Traffic Sign Objects X
OSD-LIO LiDAR Object X OSD-TRJ Trajectory X
OSD-LSD LiDAR Scene Descriptors X OSD-USO Ultrasound Object X
OSD-LCO Location Object X OSD-USD Ultrasound Scene Descriptors X
MMC-MEA Meaning X OSD-VIO Visual Object X
CAV-MTC Motor Command X OSD-VSD Visual Scene Descriptors X
CAV-MTR Motor Response X CAV-WTD Weather Data X
CAV-MTS Motor States X CAV-WHC Wheel Command X
OSD-OMO Offline Map Object X CAV-WHR Wheel Response X
OSD- Offline Map Scene Descriptors X CAV-WHS Wheel States X

2 Conformance testing

The Conformance a Data instance conforms with AIH-HSP V1.0 is expressed by one of the two statements:

  1. “Data conforms with the relevant (Non-MPAI) standard” – for Data.
  2. “Data validates against the Data Type Schema” – for Data Object.

The latter statement implies that:

A Data instance Conforms with AIH-HSP V1.0 specified Data Type if:

  1. Its JSON Object validates against its JSON Schema.
  2. Any included JSON Object validates against its JSON Schema.
  3. All Data in the JSON Object:
    1. Have the specified Data Types.
    2. Conform with the Qualifiers signaled in their JSON Schemas. For example, if the data cldata to be UNICODE, it should conform with what the Text Qualifier (MPAI-TFA V1.4) defines as UNICODE.

Note that at this stage the AIH-HSP V1.0 does specifies Conformance Testing for Data Types.

3 Performance Assessment

Performance is an umbrella term used to describe a variety of attributes – some specific of the application domain served by a specific Data Type. Therefore, Performance Assessment Specifications provide methods and procedures to measure how well a Data instance represents an original Data entity. Performance of an Implementation includes methods and procedures for all or a subset of the following characteristics:

  1. Quality– for example, how well a Scene Descriptors instance represent a scene.
  2. Bias: – for example, how dependent on specific features of the training data is the inference represented by the Data instance.
  3. Legality– for example, whether the Data instance was produced in a jurisdiction at a time by an AIM that complies with the relevant a regulation, e.g., the European AI Act.
  4. Ethics – for example, the data instance complies to a target ethical standard.

Note that at this stage the AIH-HSP V1.0 specifies Performance Assessment only of some Data Types.

<-AI Modules Go to ToC