[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [odf-adoption] Draft Interoperability and Conformance TC formationproposal
Hi Rob, please find my feedback inline: robert_weir@us.ibm.com wrote: > > 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; I think I do know hat is meant by #2 and #3, and also where the difference is between the two. However, conformance is defined by the ODF specification and therefore can be tested out of the box. In contrast to this, interoperability is a broad term that cannot be tested without first defining what is meant by interoperability. I was therefore confused by the very similar language of the two items. I'm not sure, but maybe we should add a sentence to #3 that says that a method to measure our judge the interoperability between implementations needs to be developed. Alternatively, we may think of replacing the "test" in #3 with some other term to emphasize that it is a different kind of test than #2. > 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 "the the" should read "the". > 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; I think we should use the official name of the ODF TC here just to avoid ambiguities. Maybe we should also add an "OASIS" in front of all OASIS TC's to which we are referring. > 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) I'm not sure if we can mention a workshop as a deliverable in the charter, nor whether it is reasonable to mention one particular event there. The TC process defines "deliverables" as follows: # "OASIS Draft Deliverable" means any of the following: Working Drafts, Committee Drafts and Public Review Drafts. # "OASIS Final Deliverable" means any of the following: Committee Specifications, OASIS Standards and Approved Errata. > 2. Initial Implementation Report (May 1st, 2009)and semi-annually > thereafter; Shouldn't we add a later date here? It seems to me that an implementation requires that deliverables #4 and #5 are available. Due date for #4 is May, due date for #5 is Q4 2008 through 2009. Best regards Michael -- Michael Brauer, Technical Architect Software Engineering StarOffice/OpenOffice.org Sun Microsystems GmbH Nagelsweg 55 D-20097 Hamburg, Germany michael.brauer@sun.com http://sun.com/staroffice +49 40 23646 500 http://blogs.sun.com/GullFOSS Sitz der Gesellschaft: Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht Muenchen: HRB 161028 Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels, Dr. Roland Boemer Vorsitzender des Aufsichtsrates: Martin Haering
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]