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

 


Help: OASIS Mailing Lists Help | MarkMail Help

oic message

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


Subject: Re: [oic] Suggestion of how to define tests for ODF 1.2 - part 1 -ODF Schema


On Tue, 2010-03-02 at 01:57 -0700, Svante Schubert wrote:
> On 03/02/10 00:09, Andreas J. Guelzow wrote:
> > On Mon, 2010-03-01 at 13:33 -0700, Svante Schubert wrote:
> > 
> >> The test execution is work that might be delegated to the ODFDOM working 
> >> group, I am chairing.
> > 
> > The ODFDOM seems to be a single implementation. Setting up tests as
> > suggested should therefore not delegated to a single implementor's
> > working group if interoperability is truly desired.
> > 
> 
> Only as ODFDOM is using the similar approach and therefore ODFDOM's API 
> is nearly identical, it is easy to use automated testing by descriptions.
> 
> For all other ODF implementations only the automation part falls apart, 
> but still they would have test descriptions with full ODF XML coverage, 
> divided into atomic functional units. This much more than anybody else 
> has to offer.
> 
> Why do you think these test description are not desired from an 
> interoperability standpoint, Andreas?

I do not think that test description are not desired, but I disagree
"test execution is work that might be delegated to" any _single_
implementor group.

If we want to delegate this we should simply say that we view it as the
responsibility of _every_ implementor group.

Andreas



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