OMTP is pleased to announce the ìBONDI 1.0 Approved Releaseî, the first major public release of the BONDI specifications.
In February 2009, OMTP released its candidate release of BONDI which heralded significant interest from across the internet and mobile industry communities. Subsequent to this release, OMTP received significant external input which together with the major efforts of the OMTP membership has allowed the necessary changes to be made to create an Approved Release.
This new release comprises a set of documents that define use cases, requirements and interfaces. Together, these will help the industry as a whole rapidly converge on interoperable widgets and web applications, which can be granted access to sensitive native device capability. The release provides sufficient information for a potential implementer to create a runtime which will be interoperable with BONDI applications.
This BONDI 1.0 Approved Release compliments and builds upon the work of the W3C Widgets 1.0: Packaging and Configuration. The intent is to converge BONDI with the final stable release of this work. The current referenced specifications are in-progress (last call working draft). An updated version is imminent within W3C and the BONDI specifications will be updated to reflect this when it is available.
The interfaces workstream defines the Javascript interfaces to 14 distinct device capabilities
| Document | Description |
|---|---|
| Interface Requirements | Identifies the requirements for each of the APIs in scope for BONDI |
| Javascript APIs | The formal specification of the APIs, error codes and security implications of each of the APIs in BONDI |
| Javascript API Design Patterns | Establishes common patterns and conventions, to ensure consistency of BONDI compliant APIs |
The Architecture and Security work stream defines the architectural components to deliver API extensibility and the security framework required to protect an end user from the risks associated with the opening up of sensitive APIs. It includes the precise definition of a flexible security mechanism. The exposure of these interfaces is essential to enable great services. However, a security framework is essential to protect the user from the abuse of these interfaces by malicious web applications or widgets.
| Document | Description |
|---|---|
| Architecture and Security | Primary specification document for the architecture and secuity workstream |
| Architecture and Security Appendices | Appendices to complement the above document |
| Application Lifecycle and Events | Defines requirements of application lifecycle |
| XML definition of Security Policy (RelaxNG) | The precise syntactic definition of the XML security policy |
| XML definition of Digital Signatures (RelaxNG) | File on which the security policy definition is dependent |
The Compliance work stream defines what it means for a runtime to be BONDI compliant, both in terms of the compliance process and the distinct components against which compliance has to be made.
| Document | Description |
|---|---|
| Compliance Definition | Introduces the scope and process by which BONDI compliance can be claimed |
| Compliance Matrix | Defines a detailed matrix of the capabilites against which BONDI compliant technology must make a claim |
This release has an "Approved Releaseî status. This means it has been approved by the BONDI Steering Committee, and has previously been through a formal Candidate Release and public consultation phase in which externally raised change requests have been addressed.
The next planned release of BONDI will be version 1.1, targeted to include some minor additions relating to system event management and a suite of developer tools to assist in market adoption.