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] Summary and Focus?

--- On Thu, 6/19/08, robert_weir@us.ibm.com <robert_weir@us.ibm.com> wrote:

> From: robert_weir@us.ibm.com <robert_weir@us.ibm.com>
> Subject: Re: [oiic-formation-discuss] Summary and Focus?
> To: oiic-formation-discuss@lists.oasis-open.org
> Date: Thursday, June 19, 2008, 5:11 PM
> Shawn <sgrover@open2space.com> wrote on 06/19/2008
> 10:29:09 PM:
> I don't think the TC will be testing anything, in terms
> of downloading 
> vendor software, executing tests of it, score and
> officially reporting the 
> results.  We're not proposing the creation of a testing
> lab or the 
> creation of a certifying lab.  But we are creating assets
> that could be 
> used by third party testing labs, or by implementors
> directly, to evaluate 
> their conformance to the ODF standard, and to evaluate
> interoperability 
> scenarios.
> What I am hearing in terms of deliverables include the
> following:
> 1) Researching the state of ODF interoperability today and
> issuing a 
> report, with recommendations.  Update this report
> periodically.
> 2) Researching the best practices in profiles, and issuing
> a "ODF Profiles 
> Requirements" document
> 3) Creating an "ODF Conformance Test
> Requirements" document that details 
> the exact items required to test conformance of an ODF
> document and of an 
> ODF application to the ODF standard.
> 4) Creating an ODF Interoperability Test Requirements
> document that 
> defines additional tests, including an Acid-like test and
> other 
> interoperability tests.
> 5) Create the actual ODF instance documents needed to meet
> the 
> requirements of the Interoperability Test Requirements
> above. 
> 6) Write profile of ODF to improve interoperability in
> specific areas. 
> I've heard ODF for archiving and ODF for web mentioned.
> 7) Write guidelines for ODF implementors on various topics,
> i.e., how to 
> use the internationalization features of ODF.
> 8) Write a report on best practices in creating
> interoperable documents 
> with ODF.
> 9) Unspecified deliverables on improving interoperability
> with other 
> markup languages, e.g., DITA, OOXML.

I presume that in writing this material we might work alongside others writing tests and such or no?

How hands off or on would the ODF spec be to a rewriting? Do you intend on coming up with these deliverable without touching the spec even if the ODF TC is not very cooperative?


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