Member Resources
A collection of resources useful to members of projects working at OASIS.
Higher Logic Workspace Transition FAQ: Use this link for answers on the most common ‘how to’ questions about our new TC workspace.
OASIS support request forms: Use these forms to assign procedural support tasks to the appropriate OASIS staff. To see the current work queue, click here.
For Committee Chairs
- General procedural notes: Documenting best-practices or checklists for working within the OASIS rules and policies.
- Motion/ballot language templates: Some motions at OASIS have specific required elements. Use the wording from these templates to capture the right information and put together your motions quickly. Note there is a sheet for TCs and a sheet for OPs.
- Standards workflow Gantt chart: This document provides a picture of the process specifications follow on the route to OASIS Standard.
- OASIS Committee Operations Process: Defining common rules that apply to any committee operating at OASIS.
- Open Project Rules: Rules governing the work done in OASIS Open Projects.
- Technical Committee (TC) Process: Rules governing the work done in OASIS Technical Committees.
- Open Repository Guidelines and Procedures: Rules governing open source projects hosted by OASIS Technical Committees.
- Liaison Policy: Rules governing formal liaison relationships between OASIS, TCs, or OPs and other organizations
For Editors
Editor’s Manual: The role of an editor is to create documents that reflect the consensus of the project team and capture the intent of the group clearly and unambiguously. These documents will show you both the operational tasks involved in editing and some of the organizational skills as well.
- Part 1: Role of the Editor: What commitments are you making if you volunteer to be an editor? What skills does it take?
- Part 2: Editorial Process: What are the step-by-step processes that work products follow from draft to final standard?
- Part 3: Work Product Structure: How are specifications structured and named at OASIS? What is the crucial metadata?
- Part 4: Work Product Preparation: How do you actually craft the work product? What steps do you need to take to move it forward?
Supporting resources: The documents below are additional resources that can help editors prepare their work.
- Request a starter document/template: Use this form to request a template for starting a new work product.
- DocBook template & style sheets: Stylesheets, authoring instructions, and the methodology for creating and publishing OASIS Committee Specifications and Committee Notes using DocBook XML
- DITA Stylesheets: Supporting development and maintenance of the style sheets and other resources that are used to build OASIS-styled publications from DITA source
Additional useful documentation: The documents below provide additional information on developing specifications at OASIS.
- Checklist for Verifying the Editorial Quality of OASIS Specifications: Use this checklist to look for typical problems found in specification documents.
- Document Submission Checklist: Check whether everything is in place for your specification to be submitted to OASIS for processing.
- Keyword Guidelines for OASIS Specifications and Standards: Learn how to use the keywords defined in RFC 2119 or in the ISO/IEC Directives.
- Guidelines to Writing Conformance Clauses: Conformance clauses that define what a conforming implementation must adhere to are a requirement in OASIS specifications. Learn how to write clauses that clearly capture the intent of your work.
- Conformance, Interoperability and Portability Testing: Proposed Procedures and Practices: Read one approach to handling testing for OASIS specifications. Also see the Proposed Testability Guidelines.
For Maintainers
- Maintainers Guidelines and Agreements: Describes issues of importance to maintainers of OASIS open source work.