OpenDocument - Requirements SC

Join SC     SC Page     Send a comment to this SC

Statement of purpose
As the ODF TC completes its work on ODF 1.2, it is desirable to instantiate a parallel effort to gather requirements and define a vision for the next major revision of the standard.

It is the purpose of the ODF-Next Requirements Subcommittee to gather
requirements, to categorize these requirements by theme, to prioritize
these requirements, and to submit a report to the ODF TC on a recommended set of work items for the next major version of ODF, which will have the working name of "ODF-Next".

Scope of work

In accordance with the above Purpose, the ODF-Next Requirements SC would undertake the following activities:

To collect requirements for ODF-Next from TC members, from the OASIS ODF Adoption TC, from implementors, from users, from the public, and from other stakeholders;

To ensure that all requirements collected have been formally submitted as contributions to the ODF TC, either as TC member contributions or via the Feedback License;

To categorize these comments according theme;

To prioritize the themes and the requirements within the themes;

To produce and submit to the ODF TC a report on a recommended set of work items for ODF-Next


An ODF-Next Requirements Proposal document (target May 1st, 2009)

Manner and schedule of work
The work of the subcommittee will be primarily through conference calls and a mail list set up by OASIS for subcommittee work, or other IT tools provided by OASIS for TC work. Access by the public will be through an openly available mail list archive.

Conference calls may be scheduled on a regular basis as agreed by the subcommittee after its formation. The intent is to have this be a low-intensity background activity that sets a pace of work that will not
distract from ongoing ODF 1.2 work, and which will allow all interested TC members to participate.

Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.