2a. Identification of similar or applicable work that is being done in other OASIS TCs
or by other organizations, why there is a need for another effort in this area and how this
proposed TC will be different, and what level of liaison will be pursued with these other
organizations. Prior ODF work on test documents. http://develop.opendocumentfellowship.com/testsuite/ a comprehensive set of sample documents for ODF. Consists of .odt files and a view of the output (two Vendors only). This work has now finished, according to Lotzi Bölöni, PhD. Assistant Professor School of EECS, University of Central Florida OASIS Test Assertions Guidelines (TAG) TC http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=tag Related work on specification of Test Assertions. From Sun. http://blogs.sun.com/GullFOSS/entry/openoffice_org_odf_validation_service a web page where you can check whether an ODF file meets some basic conformance or validation requirements defined by the ODF specification. This service is in particular useful for developers that want to test their implementations, but it may also be used to check if a particular file is a valid ODF file. |
|
Home > ODF IIC Technical Committee Charter >
Similar or Applicable Work |
That might fit more in question (2)(a): "Identification of similar or applicable work that is being done in other OASIS TCs or by other organizations, why there is a need for another effort in this area and how this proposed TC will be different, and what level of liaison will be pursued with these other organizations."
In particular, if we find an issue that we want to discuss with the ODF TC, we do not need to write it up into a TC deliverable, get that document approved, etc. We would likely just have a liaison with the ODF TC (a person who is a member of both TC's) and say "Hey, can you bring this issue up at the next ODF TC call and report back to us next week?".
So I think the ODF TC is more than an audience -- we would want closer level of coordination via a liaison.