Accessibility Evaluation of the OpenDocument v1.0 specification
The ODF Access Requirements report has been created by the Accessibility Subcommittee and has been approved by the OpenDocument TC.
Open Document Format v1.1 Accessibility Guidelines Version 1.0
The Open Document Format v1.1 Accessibility Guidelines Version 1.0 have been created by the Accessibility Subcommittee and after public review have been approved by the OpenDocument TC as a Committee Specification. They are available in OpenDocument, PDF and HTML formats.
OpenDocument Metadata Use Cases and Requirements Document
The Metadata Use Cases and Requirements document has been created by the Metadata Subcommittee and has been approved by the OpenDocument TC. It is available in
OpenDocument and
PDF formats.
Wiki for the OASIS OpenDocument TC member collaboration
External Resources
Although not produced by the OASIS OpenDocument TC, the following information offers useful insights into its work.
OpenDocument XML.org is a community-driven site hosted by OASIS that provides reliable background information on the standard. The site also serves as a community bulletin board and directory where readers post news, ideas, opinions, and recommendations. It incorporates wiki functionality to let users edit and add new pages to the site. The public is encouraged to contribute content.
Open Document Format for Office Applications (OpenDocument)
v1.0 an OASIS Standard
CoverPages, 23 May 2005
Members Approve OpenDocument as OASIS Standard
OASIS News, 23 May 2005
"OASIS
Members Collaborate to Advance Open XML Format for Office Applications:
Arbortext, Boeing, Corel, Drake Certivo, Sun Microsystems, and Others
Develop Open Office Standard at Global Consortium"
OASIS, 20 Nov 2002
Mailing Lists and Comments
office: the list used by TC members to conduct Committee work. TC membership
required
to post. TC members
are
automatically subscribed; the public may view archives.
office-comment: a public mail list for providing input to the OASIS office
Technical Committee members.
Send a comment or view archives.
opendocument-users: an unmoderated, public mail list that provides an open forum for
developers to exchange ideas and information on
implementing the office OASIS Standard. Subscribe or view
archives.*
*To minimize spam, you must subscribe to this list before posting.
Additional Information
Standing Rules
The TC has approved the following standing rule on 21 July 2008:
1. Any TC member may propose a substantive addition, deletion or change to the current working draft of the ODF specification by submitting a Proposal. This standing rule does not apply to editorial changes.
2. A TC member wishing to make a Proposal (the Proposer) should first announce their intention to make a Proposal on the ODF TC's mailing list. Detail is not needed at this point, but such notification is recommended in order to let other interested TC members know that someone is working in this area and to prevent duplication of effort.
3. The Proposer then must fill out the New Proposal Form on the ODF TC's wiki, with details of the Proposal.
4. When the Proposal is ready for broader discussion within the TC, the Proposer must post a link to it to the TC's mailing list to solicit feedback.
5. The Proposer controls the content of the Proposal and the pace at which the Proposal advances towards approval. As it is discussed on the mailing list, TC members may propose changes to the Proposal. However, only the Proposer, and those whom he or she designates, may edit the proposal.
6. When the Proposer wishes for the Proposal to be discussed in a TC meeting, he or she must notify the TC mailing list of this intent by the Wednesday prior to the Monday TC meeting in which he or she wishes to discuss the Proposal. If the agenda cannot accommodate this discussion during the next TC meeting, the Chair(s) should ensure that the discussion is scheduled for the next available TC meeting, with no new notification by the Proposer needed. A Proposal may be discussed in multiple TC meetings.
7. When the Proposer wishes to request a vote to accept his or her Proposal, he or she must notify the TC mailing list of this intent by the Wednesday prior to the Monday TC meeting in which he or she wishes to have the vote. If the agenda cannot accommodate this vote during the next TC meeting, the Chair(s) should ensure that the vote is scheduled for the next available TC meeting, with no new notification by the Proposer needed. No Proposal shall be voted on unless it formally meets the definition of "contribution" as defined by OASIS IPR Policy. No Proposal shall be voted on unless it has already been discussed in a previous TC meeting. Simple Majority Vote shall determine whether a Proposal is approved or not.
8. The TC Chairs shall be responsible for maintaining a record in the Proposal form, of when the proposal was initiated, at which TC meetings it was discussed, when a vote was requested, when the vote was held, and the outcome of the vote.
