Calls for Technologies

MPAI issues Calls for Technologies (CfT)when the development of a standard has reached the stage that requires technologies of its development. This page contains information related to such CfTs.


MPAI-MMCMPAI-CAE –  MPAI-AIF

MPAI-MMC

MPAI-5 has issued a Call for Technologies for the Multimodal Communication (MPAI-MMC) standard with associated Use Cases and Functional Requirements.

MPAI-CAE

MPAI-5 has issued a Call for Technologies for the Context-based Audio Enhancement (MPAI-CAE) standard with associated Use Cases and Functional Requirements.

MPAI will hold a videoconference presentation of the MPAI-MMC and MPAI-CAE Call for Technologies on 2021/03/10T15:00 UTC.

See the powerpoint slides of the first MPAI-CAE and MPAI-MMC presentation made on 2021/02/24T15:00UTC.

See the video recording of the presentation.


MPAI-MMCMPAI-CAE –  MPAI-AIF

MPAI-AIF

(the call is closed)

On 2020/12/16 the 3rd MPAI General Assembly (MPAI-3) has approved the publication of the MPAI-AIF Call for Technologies (MPAI document N100), Use Cases and Functional Requirements (MPAI document N74) and Framework Licence (MPAI document N101).

On 2021/01/20 the 4th MPAI General Assembly (MPAI-4) has approved the publication of Assessment of MPAI-AIF Submissions (MPAI document N137).

The MPAI Development Committee in charge of developing the MPAI-AIF standard (AIF-DC) has discussed several aspects of the submission assessment and came to some conclusion that are posted on this public web page for those non-members who plan on responding to the MPAI-AIF Call for Technologies.

  1. AIF Model
    Due to the broad scope of MPAI-AIF it may be challenging to pinpoint a single  basic AIF model (i.e. event based, callback based, etc..) that can satisfy all the requirements.
    Respondents are encouraged to specify the assumptions that relate to the environment(s) selected and to motivate their choice in detail.
  2. API
    1. The API definition is assumed to be general and as much as possible language independent so that its translation in specific programming languages (both for HW and SW specifications) is as simple and straightforward as possible.
    2. The API will include API components specific to the framework (i.e. instantiations of AIMs, their control, etc. ..) as well as API calls specific to the use case(s) that may be used as example of the framework. Only the AIF framework-specific API that address the requirements will be considered in the evaluation.
  3. Improvements to the AIF can be considered in the submission, that do not denaturate its basic structure.
  4. A consensus panel will be elected that will review and finalize the evaluations of the reviewers