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] My perspective. display perferct?

"Dave Pawson" <dave.pawson@gmail.com> wrote on 07/02/2008 01:34:17 AM:

> 2008/7/1  <robert_weir@us.ibm.com>:
> >> Thinking about it further, it also doesn't seem reasonable to
> >> require that something be a standard before the TC can consider it.
> >> To be of most value to vendors and to promote best interop, it seems
> >> obvious to me to work on standards which are not yet finalized.
> >> Surely the best point at which to raise interop concerns with a
> >> standard is before it's finalized/ratified?
> >>
> >
> > That would be ideal, I think.  OASIS encourages co-implementation during the
> > development of a standard.  In fact, a TC must point to successfuluses of a
> > draft before it can be eligible for vote as an OASIS Standard.  So although
> > it would be bad to release a conformance test before the corresponding ODF
> > standard is approved,
> Not bad. Impossible. Co-implementation? No.
> Please test this. I can't tell you what it is, but please test this.
> Nonsense

Surely, we already have co-implementation today on the ODF TC, and most every other TC in OASIS.  The standard does not go from 100% undefined to 100% defined overnight.  Some parts are finished before other parts, and TC's indicate this with the issue of Committee Drafts and Committee Specifications.  We would obviously write test cases for the parts that were already defined.

The odd thing is, you know all this.  You've participated in ODF TC's before.  So why are you saying that this is impossible?


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