OMA Release Program
OMA releases three types of Specifications. The Requirements Definitions indicating areas where a specification may be beneficial, the Enabler and Reference Releases and the Test Specifications and Validation plans that are all made public can be accessed from these pages.
Requirements Definitions The OMA Requirement Documents (RDs) are normative documents that identify use cases from which market requirements are distilled and which may be implemented in subsequent OMA Enabler Releases. RDs are part of the Enabler Releases for which they specify requirements. The table below lists the OMA RDs which currently are not included in Enabler Releases.
Enabler and Reference Releases
OMA is committed to deliver Releases with proven interoperability that fulfils the needs of the marketplace. In doing so, OMA has instituted a clear working process to develop open technical specifications that when combined, produce an Release with which differentiable and interoperable services can be created. The working process is a continuous program designed to deliver two key milestones for each Release. The OMA Release Program consists of the two phases:
- Phase 1 (Candidate Release) - An approved set of open technical specifications and/or other technical material, either:
forming an Enabler Release that can be implemented in products and solutions and which can be tested for interoperability, or
forming a Reference Release that serves an alternative purpose, e.g. as a set of rules and guidelines for developing other Releases.
- Phase 2 (Approved Release)- The Release has undergone a period of public comment (minimum 30days) and in addition (for Enabler Releases) completed the applicable interoperability validation.
Test Specification and Validation Plan Documents
OMA Enabler Test Specification Documents (ETS)
The Enabler Test Specifications (ETS) define the test cases for Enabler Releases, including the methodology to test, expected inputs andoutputs, responses and behaviour for each specified test.
OMA Enabler Validation Plan Documents (EVP)
The Enabler Validation Plan (EVP) documents provide a clear plan by which OMA will validate an Enabler. This includes not only activities relatedto TestFests but other validation activities that may be needed in lieuof or in addition to TestFests for all or part of the technicalelements of the enabler. The contents of an EVP will include the needed objectives laid out in the process document regarding enablervalidation (see section 13.1.4 Candidate Validation and Final ApprovalPhase), and alternative validation activities as described in section13.1.4.3 (Stage 15.1 Alternative Validation Activities).
The EVP provides supplementary test planning information, in addition tothe ETS, that helps implementers understand the scope and quantity oftesting necessary to complete the implementation of an OMA Enabler. Implementers should refer to both the EVP and the specified version ofthe ETS detailed within the EVP to ensure correct implementation of the Enabler.