Technical Advisory Board (TAB)

Join TC     TC Page     Send a comment to this TC

The purpose of the OASIS Technical Advisory Board (TAB) is to advise the OASIS Board of Directors, Staff, and Membership on matters related to the technical agenda of OASIS. The TAB focuses on improving the standards development process, improving the quality of OASIS Standards through the production of guidelines and educational materials, and advising on improvements to community and collaboration processes and technologies.



Feedback and Questions


The TAB welcomes questions and feedback from OASIS members as well as others interested in OASIS and its work. To send a question or comment to the members of the TAB, email tab-askthetab@lists.oasis-open.org. Email to the list does not require subscription or OASIS membership.

Chet Ensign, chet.ensign@oasis-open.org, Chair
Jacques Durand, jdurand@us.fujitsu.com, Secretary
Stefan Hagen, stefan@hagen.link, Secretary
Patrick Durusau, patrick@durusau.net, Secretary

Technical Advisory Board (TAB) - An OASIS Resource

The OASIS TAB assists the OASIS Board and staff by producing guidelines and best practice documents for use by specification editors and TC members, commenting on all first-time public reviews, and responding to requests for recommendations on improvements and new features.

2017/2018 TAB Work Plan

The TAB work plan for 2017/2018 is now approved.

Strategic
  • Support staff in the development of the new OASIS IT tools and interfaces (E.g. testing; 'as a chair’ perspective)
  • Support staff with the self-cert undertaking in the CTI and LegalDocML TCs
Tactical
  • Develop master citation list to track OASIS work product progress and act as a master citation list for OASIS Standards and Committee Specifications (similar to W3C and IETF lists)
  • Find opportunities to automate tasks to help members / staff increase productivity (e.g. generating the text of announcements, ballots, templates)
  • Take steps to support TCs and editors get started on a good footing (e.g. presentations to TCs during their first meetings; offer office-hour-type meetings with editors)
Guidance / Best Practices
  • Complete the OASIS Editor's manual
  • Draft OASIS Chairs manual
  • Draft advice to TCs on how to use collaborative editing tools
  • Review / reorganize TAB homepage and TAB documents
Ongoing
  • Comments to TCs on 1st public reviews
  • Maintain W3C and IETF citation master lists

Recent TAB material for members:

More guidance materials from the TAB can be found at the TAB Wiki under "Best Practices and Guidelines."

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.