OMTP is pleased to announce the ìBONDI 1.1 Candidate Releaseî, the second public release of the BONDI specifications.
The BONDI version 1.1 release is an update to version 1.0 targeted at including some minor additions relating to system event management and a suite of developer tools to assist in market adoption.
|Interface Requirements||Identifies the requirements for each of the APIs in scope for BONDI|
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.
|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.
|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 is an update to the 1.0 release and has an "Candidate Releaseî status.