+1, except for your timescales? This TC is expected to start work in 90days
+ a few for setup?
Do you think 1.2 will be done then?
A few what? Days? Weeks? Months? What is the typical TC gestation period?
May 05 to Feb 07 from 1.0 to 1.1?
I can't see 1.2 being done in 3 months more unless you know something
I don't Sam?
According to Wikipedia:
- OpenDocument 1.0 (second edition)
is the published ISO/IEC 26300:2006 standard. It also has the status of
a Committee Specification in OASIS. It includes all the editorial
changes made to address JTC1 ballot comments, and as such it reflects
the approved ISO/IEC 26300:2006 standard, as published by ISO and IEC.
It is available in ODT, HTML and PDF formats.
- OpenDocument 1.1 was approved by OASIS on 19 October 2006. It includes additional features to address accessibility concerns.[7] The Open Document Format for Office Applications (OpenDocument) Specification v1.1 was approved as an OASIS Standard on 1 February 2007 following a call for vote issued on 16 January 2007.[8][9] The public announcement was made on 13 February 2007.[10]
- OpenDocument 1.2 is currently being written by the ODF TC. It will
include additional accessibility features, metadata enhancements,
spreadsheet formula specification based on the OpenFormula
work (ODF 1.0 did not specify spreadsheet formulae in detail, leaving
many aspects implementation-defined) as well as any errata submitted by
the public. Originally OpenDocument 1.2 was expected by October 2007
but now is expected to become an OASIS standard around September 2008
and a new ISO/SEC version by summer of 2009.[11]
Note: my question about ISO standards was answered by the document I referenced; oops!
> In any case I think there is too much riding on this particular decision to
> defer it to the TC (which may well /not/ enjoy the lack of bias that a
> public forum with many more participants will have).
Ditto. Which is why I'm backing 1.1 as 'out there', and hoping
2.2 will only improve things.
In any case the 1.2 spec (or something very, very close to it) will be available to the TC when it kicks off; even better if it's not formalised as there may be some opportunity to have input before it's set in stone (yet another reason to go for the most recent release - so the ODF TC and ODF IIC TC are 'in sync' and considering similar issues). Furthermore, by the time the TC produces useful output, 1.2 should be well on the road to international standard status (and in the very least have been ratified by OASIS).
Ideally all versions would be catered for and idenfitied in the TC output where possible (eg tests should include information on which version(s) they apply to). This may not be practical for all deliverables so perhaps a little bit of flexibility is called for.