Draft Interoperability and Conformance TC formation proposal

[robert_weir@us.ibm.com]

Here is the draft.  I'll be sending
this to the discussion list as well, but I want to send a preview version
out to the adoption TC for discussion on tomorrow's TC call.

I'm not wed to any words here, so don't hesitate
to make bold changes.

-Rob

----------------------------------------

TC formation proposal.

1a. Name:  OASIS OpenDocument Format Interoperability and Conformance
Technical Committee (OIC TC)

[Note that it is not "Implementation,
Interoperability and Confomance" any more.  The general feeling
on the discussion list was that we had more than enough work just doing
Interoperability and Conformance and that implementation guides as well
would be too much work for this TC.]

1b. Statement of Purpose

The OpenDocument Format for Office Applications
(OpenDocument) OASIS Standard defines an XML schema for office applications
and its semantics. The schema is suitable for office documents, including
text documents, spreadsheets, charts and graphical documents like drawings
or presentations, but is not restricted to these kinds of documents. 

There are several commercial and open source
applications available based on the OpenDocument Format, with more currently
under development.  With the depth and breadth of the functionality
specified by ODF, conformance and interoperability are not trivially achieved
by implementors, but require attention to numerous details and diverse
requirements.   

It is the purpose of the OIC TC to provide
materials and host events that will help implementors create applications
which conform the ODF standard and which are able to interoperate. 

1c. Scope of Work

In accordance with the OIC TC's purpose, the scope of our work will include
the following activities:

1. To assess the state of conformance and interoperability among ODF implementors and periodically to issue an Implementation Report that notes areas of accomplishment as well as areas needing improvement.
2. To define a detailed conformity assessment specification which can be used to test an implementation's conformance to the ODF standard;
3. To define one or more interoperability assessment specifications which can be used to test interoperability between implementations, or among a group of implementations;
4. To define profiles which specify conformance and interoperability achievable by using a subset of the ODF standard, e.g., an ODF web profile, or an ODF/A profile for archiving.
5. To define profiles which specify the the interoperability achieved by combing ODF with with other standards, e.g., ODF + DITA, or ODF + ISO PDF;
6. To provide feedback, where necessary, to the ODF TC on changes to ODF that might improve interoperability;
7. To coordinate, in conjunction with the ODF Adoption TC, Interop Workshops and OASIS InterOp demos related to ODF;
8. To liaise on conformance and interoperability topics with other TC's and bodies whose work is leveraged in present or future ODF specifications.

1d. List of Deliverables

1. Co-Host an Interoperability Workshop, along with the ODF Adoption TC, at the OpenOffice.org Conference in Beijing (November, 2008)
2. Initial Implementation Report (May 1st, 2009)and semi-annually thereafter;
3. Report on the best practices on profiles and recommendations on possible ODF-related profiles (March 1st, 2009);
4. A conformity assessment specification, detailing how each requirement and recommendation in the ODF standard may be tested for conformance (May 1st, 2009);
5. An interoperability assessment specification, issued in several parts, according to functionality (several incremental deliverables, Q4 2008 through 2009)

1e. IPR Mode

This TC will operate under the "RF on Limited Terms" mode

1f. Audience

The anticipated audience includes:

1. Implementors -- Commercial and Open Source publishers of ODF native or compatible applications and tools.
2. Integrators -- Third-party developers and independent software vendors who interact with and/or integrate ODF.
3. Users -- End Users of ODF applications and tools, including both typical and 'power' users.
4. Procurers -- Those who purchase or define requirements for the purchase of ODF-related technology.
5. Regulators -- Officials who specify the use of document standards.
6. Testers -- Third-party testing and certification labs.g ODF

1g. Language of the TC

TC business will be conducted in English.


2. Informative information


2a. Similar work

We note the work of Lotzi Bölöni at the University
of Central Florida and his initial work in defining an ODF "test suite",
work now maintained by the Open Document Fellowship:

http://develop.opendocumentfellowship.com/testsuite/

We also note that the work of the OASIS Test
Assertions Guidelines (TAG) TC may be of use to us in defining test cases:

http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tag

Sun Microsystems has has also done some work related to ODF conformance
testing:

http://blogs.sun.com/GullFOSS/entry/openoffice_org_odf_validation_service

We note that the W3C has test suite work
efforts pertaining so several of the standards which ODF references, including
MathML and XForms.  We would expect to consult with them on any overlapping
topics.



2b. First meeting.

The initial meeting will be by telephone and will be hosted by IBM.  

[Date to be determined, likely late September/early
October, 2008 .  Must be no less than 30 days after TC is formed]

2c. Meeting schedule

We anticipate meeting, by teleconference,
every two weeks.

2d. Minium membership who support this proposal.

[We will need 5 OASIS members, from at least
3 member organizations]


2e. Convener
    Rob Weir [The convenor hosts the first first call, where
the Chair (or Chairs) will be elected, and is the main point of contact
until the TC is formed]

2f. Affiliation. None

2g. Contributions.
    Test specification for 1.1 Dave Pawson

2h  N/A

2i  None.