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] Feedback to the ODF TC

robert_weir@us.ibm.com wrote:
> Would you want this as a formal report, where the proposed TC reviews the 
> ODF standard and comes up with a list of such ambiguous clauses, much as 
> the Accessibility TC reviewed ODF 1.0 and wrote up recommendations?
> Or are you suggesting that these instances would be naturally found in the 
> process of creating our test requirements document, and as we search for 
> testable provisions in the ODF standard, such ambiguous statements would 
> be reported, individually, to the ODF TC?

I think it's a bit of both, really. We probably don't need to hunt down
the ODF spec for such ambiguous clauses because we'll encounter them
during all the other work. IMHO we should create a formal report of all
the issues found, so the ODF TC has something to work on, but we should
also report them informally as we find them. Just so the ODF TC doesn't
get hit with a list of 100+ issues they never heared of when our work is
completed. So, when they get our final report, there won't be much in it
that they don't already know about informally and we don't have to wait
too long for the ODF TC to complete it's work on it.

Also, if the OIIC TC works on a published spec (like 1.1 instead of 1.2
-- IIRC it hasn't been decided yet) then we should also look if the
issue still exists in the current ODF draft so the ODF TC can fix it
before it's released.

Sander Marechal

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