JavaDoc - post-F2F update

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

JavaDoc - post-F2F update

Rotan Hanrahan

Based on resolutions taken during the F2F, I have made a further update to the Java and JavaDoc [1] for the DDR Simple API. While this is intended to capture the technical decisions, there may yet be some semantic nuances from the Rec-track document that need to be reflected in the Java and this will be done as soon as possible.
 
Java was chosen by the DDWG as a de-facto interface design language because of the availability of practical experience and supporting tools. However, at all times, the group kept in mind that the interface is to bind to several languages including Web Services, C#. Python, Perl etc. It was also the intention to derive an IDL version of the interface specification from the Java with a view to making the IDL normative. In practice, the group has found that the Java-based description of the interface is far more detailed and mature (and hopefully soon also stable). For this reason, the Java-based description will be the basis of the normative definition of the interface, and the Java source code shall serve as the binding of the interface definition to Java (versions 5 and 6).
 
The group intends to provide, by way of an informative addendum, an IDL definition derived from the Java-based (normative) definition. WSDL will also be made available, and other language bindings where possible. The purpose of the IDL and other language bindings is to demonstrate that the interface is indeed language neutral, even though it has used the Java language as a specification language.
 
The Simple API is not a full and complete solution to the need for access to contextual information in support of adaptation processes for the delivery of adaptive content/services to mobile Web-enabled devices. It is, however, an excellent first step. The group has attempted to balance the needs of new users, robustness in design, potential for evolution and flexibility in implementation. The emphasis has been on providing a timely solution, rather than on absolute perfection. I can assure you that considerable effort has been made to ensure that it is of high quality.
 
As its name suggests, the Simple API is the precursor to a more advanced API that will support access to delivery context information in support of the Web's general adaptation requirements. The work to create such a solution will continue beyond the lifetime of the DDWG. Meanwhile, the Simple API should serve the needs of the mobile Web developer community for whom it has been created.
 
Over the next few months, the final stages of this new technology will unfold. Your attention and feedback will be most welcome.
 
---Rotan, chair.
 
[1] http://www.w3.org/2005/MWI/DDWG/drafts/api/Overview.html