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

On Fri, Jun 13, 2008 at 9:36 AM, Dave Pawson <dave.pawson@gmail.com> wrote:
2008/6/13 Luc Bollen <luc.bol@gmail.com>:
> On Fri, Jun 13, 2008 at 3:35 AM, Sam Johnston <samj@samj.net> wrote:
>> I have identified two (possibly complementary) approaches:
>> (1) A (single or multi-page) document (or documents) available online
>> (2) An online engine for testing documents submitted via eg web form, email
>> [...]
>> I'm not sure which of these two approaches is most interesting/useful in
>> the context of an acid test, or if both are required, but perhaps it is
>> better to specify the requirements such a test must meet without specifying
>> the implementation. In any case an online test engine would be interesting
>> eg for verifying profile conformance.
> Sam, I'm convinced both approaches are needed.  An "ODF tool" can be either
> a consumer (e.g. a viewer), a producer (e.g. a tool producing an ODF
> document from a database) or both (e.g. a text editor).
> - a document available on-line will be of no use to test an ODF producer
> - an online verificator engine will be of no use to test an ODF consumer.


Let's make a guess. Somewhere between 5-60% of the tests will require
manual intervention.
Who will host the site, maintain the service. No, not Oasis.
Would you use it if you had to pay for it?
Who would use it? Vendors ( <6?)
Large corporations... Possibly.
.gov organisations? Possibly.
I don't think it's financially viable in this format.


- Approach 1 (Acid Test) have no recurrent costs: once the Acid Test document is ready, it can be hosted on OASIS servers like any other report.
- Approach 2 (Validator) has recurrent costs, but we can collaborate with groups already offering such a service, like the OpenDocument Fellowship (http://opendocumentfellowship.com/validator)

Manual interventions:
I don't think any manual interventions will be required for both these tests (unlike using a large test suite made up of hundreds of atomic tests)

- Acid Test: anybody willing to use an ODF consumer tool (an editor, a viewer...) could be interested to validate it using the Acid Test (it just take a few seconds to run)
- Validator: anybody developing an ODF producer could be interested to validate the generated ODF files, as well as anybody will to use such a tool.  Again, it will take only a few seconds to submit a produced file to the validator service and get the report.

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