On Mon, Jun 16, 2008 at 12:44 PM, Sam Johnston <> wrote:
> Conversely a 1.2 release on the eve of the deliverables being delivered
> should not invalidate them. Perhaps something like:
>
> The TC will target /at least/ the most recent official OASIS release of ODF
> (1.1 at the time of writing).
Proposed alternative:
The TC will target the ISO/IEC:26300 version of ODF as its highest
priority, with support for later versions deferred until a new version
of ODF that requires read/write support for earlier versions still
responsive to market requirements is adopted as an international
standard.
I point out that ODF v. 1.1 has never been submitted to JTC 1 as draft
international standard. It is therefore not responsive to requirements
of the government market and is still not a stable standard, being
subject to change by JTC 1 as part of the even more unstable ODF v.
1.2.
Best regards,
Paul E. Merrell, J.D. (Marbux)
--
Universal Interoperability Council
<http:www.universal-interop-council.org>