3 Information about this submission. 2
4 Comments on/extensions to requirements (if any) 2
5 Detailed description of submission. 2
1 Abstract
This document is provided to help those who intend to submit a response to Call for Technologies: MPAI as a Service V1.0. Text in
- Blue (as in this sentence) provides guidance to Respondents and should not be included in a Response.
- Red (as in this sentence) is text that must be present. If the Response is in multiple files, each file shall include the statement marked as green. If a Response does not include the text marked as green, the submission will be rejected.
- Black (as in this sentence) is text that is suggested and that Respondents may use in a submission.
2 Introduction
This document is submitted by <organisation name> (if an MPAI Member) and/or by <organisation name>, a <company, university etc.> registered in <…> (if not an MPAI member) in response to the Call for Technologies: MPAI as a Service V1.0 [5] `published by Moving Picture, Audio and Data Coding by Artificial Intelligence (MPAI) on 2026/03/18.
In this document, the submitter proposes technologies that satisfy the said Call for Technologies V1.0 and Framework Licence: MPAI as Service V1.0 [6].
<Company and/or Member> explicitly agrees to the steps of the MPAI standards development process defined in Annex 1 to the MPAI Statutes (N2774) and [4], in particular <Company and/or Member> declares that <Company and/or Member> or its successors will make available the terms of the Licence related to its Essential IPR according to the Framework Licence: MPAI as a Service V1.0 [6], alone or jointly with other IPR holders after the approval of Technical Specification: MPAI as a Service V1.0 by the MPAI General Assembly and in no event after commercial implementations of the Technical Specification become available on the market.
< Company and/or Member> acknowledges the following points:
- MPAI is not obligated, by virtue of this Call for Technologies, to select a particular technology or to select any technology if those submitted are found inadequate.
- A representative of <Company and/or Member> shall present this submission at a meeting communicated by the MPAI Secretariat. If no <Company and/or Member> will attend the meeting and present their submission, this will be discarded.
- <Company and/or Member> shall make available a working implementation – including source code – for use in the development of Reference Software Specification and eventual publication by MPAI before the technology submitted is published in a Technical Specification.
- The software submitted may be written in programming languages that can be compiled or interpreted and in hardware description languages, upon acceptance by MPAI for further evaluation of their submission in whole or in part.
- <Company> shall immediately join MPAI upon acceptance by MPAI for further evaluation of this submission as a whole or in part.
- If <Company> does not join MPAI, this submission shall be discarded.
3 Information about this submission
This information corresponds to Annex 1 of N2880. It is included here for submitter’s convenience.
- Title of the proposal
- Organisation: company name, position, e-mail of contact person
- What are the main functionalities of your proposal?
- Does your proposal provide or describe a formal specification and APIs?
- Will you provide a demonstration to show how your proposal meets the evaluation criteria?
4 Comments on/extensions to requirements in Call for Technologies (if any)
| 1. | Y/N |
| 2. | Y/N |
| 3. | Y/N |
5 Detailed description of submission
5.1 Proposal section #1
5.2 Proposal section #2
….
6 Conclusions
7 References
- MPAI; The MPAI Statutes
- MPAI; The MPAI Standards
- MPAI; The MPAI Workplan
- MPAI; The MPAI Patent Policy
- MPAI; Call for Technologies: MPAI as a Service (MPAI-MAS) V1.0.
- MPAI; Framework Licence; MPAI as a Service (MPAI-MAS) V1.0.
