OMA Generic Open Terminal API Framework (GotAPI) Overview

The Generic Open Terminal API Framework (GotAPI) specification defines a variety of API exposure patterns for use in development of OMA enablers, and the functions required by API servers that support those exposure patterns. APIs designed per these patterns are intended to be “web-based” (i.e. accessed via the use of web technologies) and exposed to apps running in the following contexts:

• Web Browser apps, i.e. web apps running in a window of a web browser
• Web Runtime apps, i.e. web apps running outside a browser, e.g. under a Widget Engine or other “chromeless” runtime for execution of web content as standalone apps
• Hybrid Native/Web apps, i.e. apps that run web content through native APIs for that purpose
• Native Apps that directly use native platform APIs enabling use of the web-related protocols described in this document. Though not leveraging a full web execution environment, such apps can use the same network-based APIs as web apps.

The web-based methods defined by GotAPI are intended to offer a flexible set of options for OMA enablers to expose their services to apps via web-based APIs. Such APIs are primarily intended to be exposed to apps running in the device hosting the OMA enabler client, but in principle could also be exposed to apps in other devices that are networked with the OMA enabler client host device.

The exposure of OMA enabler-based services via such web-based APIs is intended to broaden the reach of OMA enabler deployments, by making it possible for web apps to access them, without explicit UA support of APIs specifically designed per the requirements of OMA enablers.