<-AI Modules     Go to ToC

1. Technical Specification 2. Conformance Testing 3. Performance Assessment

1. Technical Specifications

Table 1 provides the list of the Data Types specified by CAE-ASM V1.0 – Acoustic Profile (CAE-ACP), Audio Scene Reference (CAE-ASR) and User Command (CAE-UCM) – with links to the pages dedicated to them and to their JSON syntax. Each includes Definition, Functional Requirements, Syntax, Semantics, Conformance Testing, and Performance Assessment. A User Command carries the User Point of View (UserPoV) and the Objects to acquire (AcquiredObject). The Data Types that the AIMs of CAE-ASM V1.0 use and that CAE-ASM V1.0 does not specify are specified by MPAI-OSD V1.5 and MPAI-TFA V1.5, and are referenced in the pages of the Composite AIM and of its AIMs.

Table 1 – Data Types specified by CAE-ASM V1.0

Acronym Name JSON Acronym Name JSON
CAE-ACP Acoustic Profile File CAE-ASR Audio Scene Reference File
CAE-UCM User Command File

2 Conformance testing

The Conformance a Data instance conforms with CAE-ASM 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 CAE-ASM V1.0specified 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.

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.

<-AI Modules     Go to ToC