The whole story was published on InfoQ on 2008-09-07：http://www.infoq.com/news/2008/09/WebIDL
The W3C Web Applications Working Group recently published the working draft of Web IDL which was formerly known as the Language Bindings for DOM Specifications. The working draft defines a syntactic subset of OMG IDL version 3.0 for use by specifications that define interfaces. InfoQ spoke to the specification editor to learn more about the specification and its impact on the Web development community.The interface definition language defined by the working draft is called Web IDL which can be used to describe interfaces that are intended to be implemented in web browsers. Web IDL is an IDL variant with a number of features that allow the behavior of common script objects in the web platform to be specified more readily. A number of extensions are given to theIDL to support common functionality that previously must have been written in prose. In addition, precise language bindings for ECMAScript 3rd Edition and Java are given. The Introduction part of the document explains the reason for having such a specification:
Technical reports published by the W3C that include programming language interfaces have typically been described using the Object Management Group’s Interface Definition Language (IDL) [OMGIDL]. The IDL provides a means to describe these interfaces in a language independent manner. Usually, additional language binding appendices are included in such documents which detail how the interfaces described with theIDL correspond to constructs in the given language. However, the bindings in these specifications for the language most commonly used on the web, ECMAScript, are consistently specified with low enough precision as to result in interoperability issues. In addition, each specification must describe the same basic information, such as DOM interfaces described inIDL corresponding to properties on the ECMAScript global object, or the unsigned long IDL type mapping to the Number type in ECMAScript.
Web IDL is intended to specify in detail the language used by W3C specifications to define interfaces, and to provide precise conformance requirements for ECMAScript and Java bindings of such interfaces.
See InfoQ for the whole story.