Linked by Thom Holwerda on Tue 4th Sep 2007 21:40 UTC, submitted by archiesteel
Thread beginning with comment 268568
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
4? I've heard 3 elsewhere.
The dates are on Wikipedia.
"The first official ODF-TC meeting to discuss the standard was December 16, 2002".
"After responding to all written ballot comments, and a 30-day default ballot, the OpenDocument International Standard went to publication in ISO, officially published November 30, 2006."
That is four years from woa to go.
The other relevant date is this:
"OASIS submitted the ODF specification to ISO/IEC Joint Technical Committee 1 (JTC1) on November 16, 2005"
So that is 1 full year in the ISO process, following three full years of collaborative, consesnus development.







Member since:
2005-07-06
Well ODF spent 4 years at OASIS before being submitted. And then when it was submitted the limitations of the proposal were documented. A specification does not have to cover every eventuality. However what the specification does cover should be clear and allow for an implementation (in terms of compliance) to be created based on the specification alone. Writing a specification and saying that part X "should match this specific legacy app" is not only insufficient but sloppy.
Edited 2007-09-04 22:06