This release includes some minor errata and editorials to the 1.1 Approved Release, released on the 9th of February 2010.
The interfaces workstream defines the Javascript APIs to 14 distinct device interfaces
| 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 security 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 |
|---|---|
| Conformance Definition | Introduces the scope and process by which BONDI conformance can be claimed |
| Compliance Matrix | Defines a detailed matrix of the capabilites against which BONDI compliant technology must make a claim |
| Test Coverage | A document that identifies how much of the BONDI funcionality is covered explicitly by objective, repeatable Javascript tests |
This release is an update to the 1.1 release and has an "Approved Releaseî status.
For any questions regarding this release or BONDI in general please contact Nick Allott OMTP BONDI CTO