WebIDL Plans

Hi,
We are planning to move WebIDL forward to REC, here is the plan to achieve that:

1/ remove the v1/v2 distinction.
   The goal here is to remove entirely the now obsolete v1, and keep what is currently known as WebIDL v2 as the editor’s copy.
2/ Create a new document with "stable" features in the edcopy, where stable means the feature is implemented and useful for other specifications, and doesn't contain major bugs.
  A tentative list of what would be needed is as follow.
  * Everything from old v1 expect ArrayClass which is not used, nor implemented anywhere.
  * Add Promise<T>, Iterators, NewObject, Dictionary constructors, Buffer types (USVString and ByteString as well, depending on their      status)
3/ Publish and work on the test suite.
4/ Try to go to REC asap.
5/ reiterate the process with WebIDL level ’n’ (name subject to usual bikeshedding) when more things are implemented, or when ES-(new version) will be out.

This plan keeps the language definition and binding behaviors together, but strips out stuff that isn't stable, not widely implemented, or used in specifications. Also note that the goal is to generate the document from the edcopy, to eliminate as much as possible synchronisation issues, and reduce the load of the editor’s copy… editors.
Thanks,

-- 
Baroula que barouleras, au tiéu toujou t'entourneras.

        ~~Yves

Received on Friday, 10 April 2015 12:54:00 UTC