OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oiic-formation-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [oiic-formation-discuss] Which is definitive odf?

2008/6/16 Sam Johnston <samj@samj.net>:
>> >> - In that light, I believe this TC should always be working with the
>> >> most
>> >> recent "official" version of ODF.
>> >
>> > +1
>> +1, deferred perhaps until the new TC is formed (if it is).
>> I.e. the most recent official version at the time of the new TC formation?
>> Official being released by Oasis, not sanctified by OSI (I think
>> that's reasonable).
> Agreed for the clarification of 'official' but for me it's more important
> that the /output/ of the TC matches the currently available version; if 1.2
> arrives a day after the TC is formed it should still be considered/targeted.
> 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).

-1 Sam.
Lets say the TC works for 3...24 months, whatever.
During that time they need (IMHO) a stable standard from which to work.
Otherwise they are testing a moving target.

Agree with your logic but the above would be a nightmare.

To 'keep up to date' is the issue.
Suggest a request to the main TC to identify (change markup) all changes
to an existing document with each release such that this TC can
identify changes.

Another one would be to produce a version (xhtml) which had navigable
ID values to check tests against links to the standard.


Dave Pawson

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]