Re: [oiic-formation-discuss] Draft Interoperability and Conformance TC formation proposal (0.2)

["Peter Dolding" <oiaohm@gmail.com>]

On Fri, Jul 25, 2008 at 4:37 AM,  <robert_weir@us.ibm.com> wrote:
> The following activities are explicitly not within the Scope of the OIC TC:
>
> Acting as a rating or certifying authority or agency for conformance of ODF
> implementations;
> Authoring or distributing software that tests the conformance or
> interoperability of ODF implementations;
>
Ok what is the point of the TC then.  Distributing software that tests
the conformance or interoperablity is kinda a key requirement.

It removes the means to do "state of ODF conformance and
interoperability (March 1st, 2009);" with correctness.

How can you find out how conformance and interoperability is going if
you cannot send out tests.  Its going to be a complete yes sir it
works everywhere limited tested and all.  Acid Tests have there place
to make sure results found in controlled testing match real world.
Distributing software is kinda key to Acid Testing to make sure
results in reports are correct.   Worst case is if a application has
failed and failed in lab conditions and shows up in Acid Testing that
it works fine.  Cause was that you lab had a damaged copy of the
application.  Acid testing is a key part of the process.

Ok if you don't want to certify that is fine.  Tieing report writers
hands so they cannot do good tests is not fine.  Basically person
writing report by this cannot chase down reports of something not
working to standard that works in the lab by creating a acid test and
sending out and record it in the report that application has unknown
cause of variation from standard here proven by a acid test.

Please create workable limitations.  Authoring and distributing tests
has to be allowed at least under some conditions.

Thank you very much for making the TC another joke if that line goes
threw unaltered.

Peter Dolding