[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: TC formation proposal.
Below, and attached as text file.
Proposal, for discussion. I don't know what deliverable to add for the
acid tests. Suggestions please.
TIA DaveP
In conformance with
http://www.oasis-open.org/committees/process-2008-02-05.php#formation
TC formation proposal.
1a. Name
OASIS ODF Interoperability and Conformance (IIC) TC
1b. Statement of Purpose
The ODF community has recognised interoperability and interpretation
of the ODF specification as an issue. This TC is chartered to address
interoperability of ODF implementations.
1c. Scope of Work
The TC produces conformance and interoperability specification for the
ODF specification. The TC will not produce such software. Work will
focus on the most recent Oasis ODF standard, reviewing later releases
as appropriate.
This work will deliver on the following:
* A test specification for ODF
* An interoperability specification for ODF
Other related work in this area is recognised.
1d. List of Deliverables
1.* Produce a report on the current state of ODF implementation
interoperability; strengths, weaknesses and recommendations for
future improvement.
2.* Research best practices on profiles and produce a report on ODF
Profiles.
3.* Produce an "ODF Conformance Test Requirements" document detailing
how each atomic item in the standard is to be tested for conformance
of an ODF document and of an ODF application to the ODF standard.
4.* A definition of a normalized/canonical ODF instance used to support
a comparison tool.
5.* To consider and provide, if applicable, relative priorities to tests
or groups of tests?
6.* The TC shall deliver a definition of c18N above and beyond w3c c18N,
to include such as style variations and any other relevant
considerations for the purposes of supporting interop testing.
7.* To consider and provide, if applicable, relative priorities to tests
or groups of tests, one test or test group with another
8.* To define how test documents are to be collected for use in testing.
9.* A means of identifying extensions to ODF and adding an warning
comment to the test output"
10.* The specification of an FAQ, if appropriate, targeted at
interoperability and conformance issues
11.* A specification of interoperability addressing XML code level
interoperation.
1e. IPR Mode
This TC will operate under the 'RF on Limited Terms' mode as described
at http://www.oasis-open.org/who/intellectualproperty.php
1f.Audience
Audience Description
Implementors Commercial and Open Source distributors of ODF native or
compatible applications and tools.
Integrators Third-party developers and independent software vendors
who interact with and/or integrate ODF.
Users End Users of ODF applications and tools, including both typical
and 'power' users.
Procurers Procurers and purchasers of ODF-related technology.
Regulators Officials who specify the use of document standards.
Testers Third-party testing and certification labs.
Implementors Individuals and organisations implementing ODF
1g. Language of the TC
All business of the TC will be conducted in English.
2. Informative information
2a. Similar work
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.
2b. First meeting.
(tbc) October 2008 - telcon and email
2c. Meeting schedule
Email, monthly telcon unless changed by the TC
2d. Minium membership who support this proposal.
Dave Pawson
....
2e. Convener
TBA
2f. Affiliation. None
2g. Contributions.
Test specification for 1.1 Dave Pawson
2h FAQ is seen as a deliverable
2i Working Title.
ODF Interoperability and Conformance specification.
2008-07-21T09:32:15Z. Original version posted to oiic list. Dave Pawson.
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
In conformance with http://www.oasis-open.org/committees/process-2008-02-05.php#formation
TC formation proposal.
1a. Name
OASIS ODF Interoperability and Conformance (IIC) TC
1b. Statement of Purpose
The ODF community has recognised interoperability and interpretation
of the ODF specification as an issue. This TC is chartered to address
interoperability of ODF implementations.
1c. Scope of Work
The TC produces conformance and interoperability specification for the
ODF specification. The TC will not produce such software. Work will
focus on the most recent Oasis ODF standard, reviewing later releases
as appropriate.
This work will deliver on the following:
* A test specification for ODF
* An interoperability specification for ODF
Other related work in this area is recognised.
1d. List of Deliverables
1.* Produce a report on the current state of ODF implementation
interoperability; strengths, weaknesses and recommendations for
future improvement.
2.* Research best practices on profiles and produce a report on ODF
Profiles.
3.* Produce an "ODF Conformance Test Requirements" document detailing
how each atomic item in the standard is to be tested for conformance
of an ODF document and of an ODF application to the ODF standard.
4.* A definition of a normalized/canonical ODF instance used to support
a comparison tool.
5.* To consider and provide, if applicable, relative priorities to tests
or groups of tests?
6.* The TC shall deliver a definition of c18N above and beyond w3c c18N,
to include such as style variations and any other relevant
considerations for the purposes of supporting interop testing.
7.* To consider and provide, if applicable, relative priorities to tests
or groups of tests, one test or test group with another
8.* To define how test documents are to be collected for use in testing.
9.* A means of identifying extensions to ODF and adding an warning
comment to the test output"
10.* The specification of an FAQ, if appropriate, targeted at
interoperability and conformance issues
11.* A specification of interoperability addressing XML code level
interoperation.
1e. IPR Mode
This TC will operate under the 'RF on Limited Terms' mode as described
at http://www.oasis-open.org/who/intellectualproperty.php
1f.Audience
Audience Description
Implementors Commercial and Open Source distributors of ODF native or
compatible applications and tools.
Integrators Third-party developers and independent software vendors
who interact with and/or integrate ODF.
Users End Users of ODF applications and tools, including both typical
and 'power' users.
Procurers Procurers and purchasers of ODF-related technology.
Regulators Officials who specify the use of document standards.
Testers Third-party testing and certification labs.
Implementors Individuals and organisations implementing ODF
1g. Language of the TC
All business of the TC will be conducted in English.
2. Informative information
2a. Similar work
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.
2b. First meeting.
(tbc) October 2008 - telcon and email
2c. Meeting schedule
Email, monthly telcon unless changed by the TC
2d. Minium membership who support this proposal.
Dave Pawson
....
2e. Convener
TBA
2f. Affiliation. None
2g. Contributions.
Test specification for 1.1 Dave Pawson
2h FAQ is seen as a deliverable
2i Working Title.
ODF Interoperability and Conformance specification.
2008-07-21T09:32:15Z. Original version posted to oiic list. Dave Pawson.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]