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] Acid Tests (was: Re: [oiic-formation-discuss] Interoperability versus Conformity)

2008/6/12 Luc Bollen <luc.bol@gmail.com>:
> On Thu, Jun 12, 2008 at 2:49 PM, Dave Pawson <dave.pawson@gmail.com> wrote:
>> > However, it is not well suited to validate the Output part of the
>> > application ("Does the application produce valid ODF files?").
>> If you add, when written to disk as an ODF 'package' it helps?
>> I can check zip format
>> I can unzip it.
>> Check content
>> Parse XML
>> Validate XML
>> run other logic tests on XML
>> But again you need some sort of profile.
> I don't think what Dave describes here can still be called an Acid Test (too
> many steps, need for a parser...).

No one has defined what an acid test is AFAIK?

 Probably the closest to an "Output Acid
> Test" would be:
> - open the standard Acid Test file
> - save it
> - open the saved Acid Test file with a reference application known to be
> "correct".

I think the chair of this group tried to slip that one past us.
No such thing as a reference implementation. Not even conformant.

> In any case, I would recommend to clearly indicates in the TC charter that
> there are 2 aspects to be validated when we talk about interoperability:
> - the ability to correctly handle valid ODF files
> - the ability to produce valid ODF files.

Which reflects Pauls definition of application interoperability I think.
Even harder than document interop Luc!


Dave Pawson

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