Technical Advisory Board (TAB)

 View Only

OASIS-tab@ConnectedCommunity.org

Contacts

Chair: Chet Ensign
chet.ensign@oasis-open.org

OASIS Staff Contact: Scott McGrath
scott.mcgrath@oasis-open.org

OASIS Staff Contact: James Bryce Clark
jamie.clark@oasis-open.org

OASIS Staff Contact: Paul Knight
paul.knight@oasis-open.org

Charter

Click link below to view.

Description

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.

Group Notes

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's proposed work plan for 2018/2019 is:


Strategic

  • Draft policy for handling security vulnerability reports and recommendations on infrastructure to support reporting and reporting

  • Suggest organization of OASIS resources to align with work-flow (e.g. 'Resources for editors')

  • Draft proposal for improving errata process

  • Draft proposal for maintaining and deprecating OASIS Standards after a TC is closed

  • Help promote Open Projects

  • Review/help proposers improve draft OP charters

  • Help identify features to make OPs attractive to developers


Tactical
  • Finish the Google master citation sheet 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)


Guidance / Best Practices

  • Open first half of TAB calls to OASIS members as 'open office hours'

  • Draft OASIS Chairs manual


Ongoing
  • Comments to TCs on 1st public reviews

  • Maintain W3C and IETF citation master lists





Recent TAB material for members:





tab-respec , a GitHub project supporting development and maintenance of extensions to the ReSpec application to enable it to produce OASIS-styled specifications.
Best Practices for Meeting Minutes

Request TAB Pre-review comments

IETF RFC Citation List for OASIS Editors: A list of current IETF RFCs in proper citation format for OASIS spec editors.

W3C Recommendation Citation List for OASIS Editors: A list of current W3C Recommendations in proper citation format for OASIS spec editors.

Checklist for Verifying the Editorial Quality of OASIS Specifications: For spec writers and TC members, this draft lists the questions TAB members use when performing a public review of a Committee Spec Draft.

Guidelines to Writing Conformance Clauses for OASIS Specifications : For spec writers and TC members, this current draft provides guidelines on how to write conformance statements for OASIS specifications.

OASIS Keyword Guidelines (v6.2): Your guide to using keywords in OASIS work products.

Conformance, Interoperability and Portability Testing: Procedures and Practices: Do implementations of your specification play well with other implementations? This document helps you avoid guessing the answer to that question.

Testability Guidelines: Are you ready to move up to the next level of standards writing? Testable standards? It's a big step but here is a little boost to get you started.



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

Public Resources

Announcements

Log in to see this information

Either the content you're seeking doesn't exist or it requires proper authentication before viewing.