This release outlines some of the work in progress APIs in scope for the BONDI 1.5 release
This public draft contains links to API elements only. It features none of the Compliance or Architecture and Security enhancements planned for the 1.5 release. The API listing given here is a partial listing; more APIs may well be added before 1.5 release is finalised.
The purpose of this release is to publically communicate part of the 1.5 scope, to stimulate public feedback on 1.5 details, and to stimulate input on further APIs for inclusion. Although we encourage companies (whether OMTP members or not) to collaborate on the ongoing BONDI reference implementation, in order to refine the specification, we stongly advise companies not to base commercial implementations on these specifications until they reach final Approved Release status.
If you wish to input into the process (by making change requests) or to input into the open source code base it is imperative that you as an individual, or on behalf of the comany you work for, sign up to the OMTP BONDI non member conditions. This is necessary because it is the clear intent to keep the BONDI platform defintion, unencumbered by IPR
There are currently 7 interfaces in scope of the BONDI 1.5 public working draft.
| Interface | Description |
|---|---|
| APDU API | This module allows the communication between web application and a smart card by using the Application Protocol Data Units (APDUs). An APDU is a short message represented by bytes. APDU messages are either commands or responses. APDU protocol is defined by ISO 7816-4 and is described in the Java Card Development Kit documentation at http://java.sun.com/products/javacard/. |
| Bluetooth API | This API provides access to the bluetooth functionality. This set of interfaces provides a framework for short range device and service discovery of other bluetooth devices. Once a service has been discovered it is then possible to connect to this service and exchange data. |
| Crypto API | The crypto API provides cryptographic functions like hashing, signature verification, encrypting and decrypting to allow exchanging data between a server and a BONDI client securely (encrypting/decrypting), protecting data integrity (one-way hashing) and verifying the authentity of data (digital signatures). |
| DLNA API | This API enables discovery of the DLNA devices in the local network, control of the devices. It shall/could be coupled with the Media Player API for local playback. |
| Server Push API | This API provides functionality of OMA Push delivery to Web Applications running in the widget context, which includes; registration/deregistration of web applications with the Push enabler and delivery of Push content to the registered application(s). |
| Sensor API | Sensor API Sensors are classified by type. Sensor type names are defined Strings, and creation new type names must be centrally defined (by the owner of this API definition). |
| Telephony API | This API provides access to core telephony functions, boht incoming and outgoing calls. |
For any questions regarding this release or BONDI in general please contact Nick Allott OMTP BONDI CTO