Technical Committee (TC) Process (24 April 2014)
Table of Contents
This version of the OASIS TC Process was approved by the OASIS Board of Directors on 24 April 2014 and became effective 01 May 2014. The change was announced to OASIS members on 12 May 2014 in https://lists.oasis-open.org/archives/members/201405/msg00017.html.
1. Definitions 2. Technical Committees 2.1 TC Discussion Lists 2.2 TC Formation 2.3 First Meeting of a TC 2.4 TC Membership and Participation 2.5 Termination of TC Membership 2.6 Leaves of Absence 2.7 TC Chairs 2.8 TC Visibility 2.9 TC Procedure 2.10 TC Meetings 2.11 TC Charter Clarification 2.12 TC Rechartering 2.13 TC Voting 2.14 TC Subcommittees 2.15 Closing a TC 2.16 Maintenance Activity of OASIS Standards Final Deliverables 2.17 Intellectual Property Rights Procedures 2.18 Work Product Quality 2.19 Designated Cross-Reference Changes 2.20 Commercial Terms and Conditions 3. Approval Process 3.1 Approval of a Committee Draft 3.2 Public Review of a Committee Draft 3.3 Approval of a Committee Specification 3.4 Approval of an OASIS Standard 3.5 Approved Errata 4. Board of Directors Involvement in the TC Process 4.1 OASIS TC Administrator 4.2 Appeals 5. Application to Existing TCs
- “Administrative Document” is a document which is used by a TC only in support of internal operations such as minutes, agenda, liaison statements, issue lists, bug lists, etc. and which are not an OASIS Deliverable. An Administrative Document must not use a Work Product template. Inter-group communications to request review, respond to review comments, or to respond to questions or requests for clarifications are considered to be Administrative Documents.
- “Approved Errata” shall have the meaning defined in Section 3.5.
- “Candidate OASIS Standard” is a document that has been submitted for approval as an OASIS Standard as specified in Section 3.4.
- “Charter” is the organizational document for a TC comprised of the items included in the proposal to form that TC, as defined in Section 2.2, and may be modified as described in Section 2.11.
- “Committee Note” is a Non-Standards Track Work Product that has been approved by a Technical Committee as specified in Section 3.3.
- “Committee Note Draft” is a Non-Standards Track Work Product approved by a Technical Committee as specified in Section 3.1.
- “Committee Note Public Review Draft” is a Committee Note Draft that has been approved by the TC to go to public review as specified in Section 3.2 of this Process.
- “Committee Specification” is a Standards Track Work Product that has been approved by a Technical Committee as specified in Section 3.3.
- “Committee Specification Draft” is a Standards Track Work Product approved by a Technical Committee as specified in Section 3.1.
- “Committee Specification Public Review Draft” is a Committee Specification Draft that has been approved by the TC to go to public review as specified in Section 3.2 of this Process.
- “Convener” is an Eligible Person who serves in the role of organizing the first meeting of the TC, as defined in Section 2.3.
- “Eligible Person” means one of a class of individuals that includes (a) OASIS Individual Members, (b) employees or designees of OASIS Organizational Members, and (c) such other persons as may be designated by the OASIS Board of Directors.
- “Errata” means a set of changes or proposed changes to an OASIS Standard that are not Substantive Changes.
- “Full Majority Vote” is a TC vote in which more than 50% (more than half) of the Voting Members vote “yes”, regardless of the number of Voting Members present in the meeting. Abstentions are not counted. For example, in a TC in which there are 20 Voting Members, at least 11 Voting Members must vote “yes” for a motion to pass.
- “IPR” means intellectual property rights.
- “Leave of Absence” shall have the meaning defined in Section 2.6.
- “Meeting” is a meeting of the TC that is properly called and scheduled in advance as described in Section 2.10.
- “Member“, with respect to a TC, means an Eligible Person who is allowed to subscribe to the TC email list, participate in list discussions, attend and participate in TC meetings, and make Contributions to the TC. The process for becoming a Member of a TC is defined in Section 2.4.
- “Minimum Membership” means five Voting Members of a TC (or, in the case of a TC about to be formed, five Eligible Persons), at least two of which represent OASIS Organizational Members.
- “Non-Material Change” is any change to the content of a Work Product that does not add or remove any feature of the Work Product and that: (a) constitutes only error corrections, editorial changes, or formatting changes; or (b) is a pro forma change to content required by TC Administration.
- “Non-Standards Track Work Product” is a Work Product produced and approved by a TC in accordance with the TC Process which may be progressed to Committee Note as described in Section 3. Non-Standards Track Work Products are intended to be informative and explanatory in nature. They are not subject to the patent licensing and non-assertion obligations requirements of the OASIS IPR Policy.
- “Normative Portion” shall have the meaning defined for such term by the OASIS IPR Policy.
- “Normative Reference” means a reference in a Standards Track Work Product to an external document or resource with which the implementer must comply, in order to comply with a Normative Portion of the Work Product.
- “OASIS Deliverable” means any of the following: Committee Specification Drafts, Committee Specification Public Review Drafts, Committee Specifications, Candidate OASIS Standards, OASIS Standards, Approved Errata, Committee Note Drafts, Committee Note Public Review Drafts, and Committee Notes.
- “OASIS Individual Member” means an OASIS Member who is classified as such in their executed Membership Agreement.
- “OASIS Member” means a person, organization or entity who is a voting or non-voting member of the corporation, as defined by the OASIS Bylaws.
- “OASIS Non-Standards Draft Deliverable” means any of the following: Committee Note Drafts and Committee Note Public Review Drafts.
- “OASIS Non-Standards Final Deliverable” means any of the following: Committee Notes.
- “OASIS Organizational Member” means an OASIS Member who is classified as such in their executed Membership Agreement.
- “OASIS Standards Draft Deliverable” means any of the following: Committee Specification Drafts and Committee Specification Public Review Drafts.
- “OASIS Standards Final Deliverable” means any of the following: Committee Specifications, Candidate OASIS Standards, OASIS Standards and Approved Errata.
- “OASIS Standard” is a Candidate OASIS Standard that has been approved by the OASIS Membership as specified in Section 3.4.
- “OASIS TC Administrator” means the person or persons representing OASIS in administrative matters relating to TCs. All official communications must be sent to firstname.lastname@example.org.
- “Observer” is an Eligible Person who is subscribed to the TC email list, and may attend TC meetings, but is not allowed to participate in TC email list discussions, participate or speak in TC meetings, or make Contributions to the TC. The process for becoming an Observer is defined in Section 2.4.
- “Persistent Non-Voting Member” is a TC Member who has declared their non-voting status in that TC. The process for becoming a Persistent Non-Voting Member of a TC is defined in Section 2.4.
- “Primary Representative“, for any OASIS Organizational Member, means the person or persons designated by that Member to serve as the consortium’s principal contact for administrative issues.
- “Public” and “publicly” mean all persons, organizations and entities, whether or not OASIS Members.
- “Quorum” is the number of Voting Members of a TC that must be present in a meeting so that Resolutions and decisions may be made. The Quorum for OASIS TC meetings is a simple majority (more than half) of Voting Members.
- “Quorate Meeting” is a TC meeting at which a Quorum is present.
- “Resolution” means a decision reached by a TC by vote. Resolutions require a Simple Majority Vote to pass, unless a Full Majority Vote or Special Majority Vote is required under this Process.
- “Simple Majority Vote” is a vote in which the number of “yes” votes cast is greater than the number of “no” votes cast. Abstentions are not counted. For example, in a Quorate Meeting in which 20 Voting Members are present, if 7 vote “yes” and 4 vote “no”, the motion passes.
- “Special Majority Vote” is a TC vote in which at least 2/3 (two thirds) of the Voting Members vote “yes” and no more than 1/4 (one fourth) of the Voting Members vote “no”. These numbers are based on the total number of Voting Members, regardless of the number of Voting Members present in the meeting. Abstentions are not counted. For example, in a TC in which there are 30 Voting Members, at least 20 Voting Members must vote “yes” for a motion to pass; but if 8 or more vote “no” then the motion fails. All Special Majority Votes must be conducted via electronic ballot by the OASIS TC Administrator.
- “Standards Track Work Product” is a Work Product produced and approved by a TC in accordance with the TC Process which may be promoted to Committee Specification or OASIS Standard as described in Section 3.
- “Statement of Use“, with respect to a Committee Specification, is a written statement that a party has successfully used or implemented that specification in accordance with all or some of its conformance clauses specified in Section 2.18, identifying those clauses that apply, and stating whether its use included the interoperation of multiple independent implementations. The Statement of Use must be made to a specific version of the Committee Specification and must include the Specification’s approval date. The party may be an OASIS Member or a non-member. In case of a non-member, the Statement of Use must be submitted on the TC comment-list. A TC may require a Statement of Use to include hyperlinks to documents, files or demonstration transcripts that enable TC members to evaluate the implementation or usage. A Statement of Use submitted to the TC must be approved by TC resolution as an acceptable Statement of Use with respect to the Committee Specification. A party can only issue one Statement of Use for a given specification. When issued by an OASIS Organizational Member, a Statement of Use must be endorsed by the Organizational Member’s Primary Representative.
- “Subcommittee” (or “SC”) is a group of Members of a TC producing recommendations for consideration by the parent TC.
- “Substantive Change” is a change to an OASIS Standard that would require a compliant application or implementation to be modified or rewritten in order to remain compliant.
- “Technical Committee” (or “TC”) means a group comprised of at least the Minimum Membership formed and conducted according to the provisions of this OASIS TC Process.
- “Voting Member” is a Member of a TC who has voting rights in the TC. The process for gaining voting rights is defined in Section 2.4.
- “Work Product” is a document which is either a Standards Track Work Product or a Non-Standards Track Work Product.
- “Work Product Approval Motion” is any motion to initiate a Work Product Ballot.
- “Work Product Ballot” is any TC ballot for the:
- approval of a Committee Specification Draft or Committee Note Draft,
- start of a Public Review,
- approval of a Committee Specification, or a Committee Note,
- submission of a Committee Specification as a Candidate OASIS Standard.
- “Working Draft” is a preliminary version of a Work Product produced by one or more TC Members that has not yet been voted on by the TC and approved as a Committee Specification Draft or a Committee Note. Some examples are initial contributions and revisions made by editors or other TC Members.
The use of the term “day” or “days” in this TC Process refers to calendar days.
No later than 15 days following the submission, the OASIS TC Administrator shall provide these materials to the OASIS Membership with a Call For Participation in a discussion list whose purpose is to propose the TC described in the application.
Discussion on the list is restricted to evaluating the interest in proposing a new OASIS TC, and defining the proposal for one or more new OASIS TCs. The list of subscribers to the discussion list shall be available to all subscribers. The discussion list shall automatically close 90 days after the Call For Participation is issued.
Any group of at least Minimum Membership shall be authorized to begin a TC by submitting to the OASIS TC Administrator, with a copy to those listed in 2(d) and 2(e) below, the following items, written in English and provided in electronic form as plain text. No information other than these items may be included in the proposal. All items must be provided in any subsequent revision of the proposal, and must be submitted in the same manner as the original submission. Any documents referenced in the proposal shall be publicly available.
(1)(a) The name of the TC, such name not to have been previously used for an OASIS TC and not to include any trademarks or service marks not owned by OASIS. The proposed TC name is subject to TC Administrator approval and may not include any misleading or inappropriate names. The proposed name must specify any acronyms or abbreviations of the name that shall be used to refer to the TC.
(1)(c) The scope of the work of the TC, which must be germane to the mission of OASIS, and which includes a definition of what is and what is not the work of the TC, and how it can be determined when the work of the TC has been completed. The scope may reference a specific contribution of existing work as a starting point, but other contributions may be made by TC Members on or after the first meeting of the TC. Such other contributions shall be considered by the TC Members on an equal basis to improve the original starting point contribution.
(2)(a) Identification of similar or applicable work that is being done in other OASIS TCs or by other organizations, why there is a need for another effort in this area and how this proposed TC will be different, and what level of liaison will be pursued with these other organizations.
(2)(b) The date, time, and location of the first meeting, whether it will be held in person or by telephone, and who will sponsor this first meeting. The first meeting of a TC shall occur no less than 30 days after the announcement of its formation in the case of a meeting held exclusively by telephone or other electronic means, and no less than 45 days after the announcement of its formation in the case of a meeting held face-to-face (whether or not a telephone bridge is also available).
(2)(c) The projected ongoing meeting schedule for the year following the formation of the TC, or until the projected date of the final deliverable, whichever comes first, and who will be expected to sponsor these meetings.
(2)(e) For each OASIS Organizational Member listed in (2)(d), the name, electronic mail address, membership affiliation, and statement of support for the proposed Charter from the Primary Representative.
No later than 5 days following the submission, the OASIS TC Administrator shall either return the submission to its originators, with an explanation indicating its failure to meet the requirements set forth in this section, or shall post notice of the submission to an announced mailing list (or equivalent method) visible to the submission proposers and the OASIS Membership, for comment.
The notice will announce that comments will be received until the 14th day after the notice, and will announce a date within 4 days of that 14th day for a conference call, among the Convener, the OASIS TC Administrator, and those proposers who wish to attend. Other OASIS Members who wish to attend may observe.
The proposer group may amend their submission at any time until the 28th day after the submission (except that changes to the roster of proposers may occur at any time until the final posting). By the 28th day the proposer group must post a pointer to an account of each of the comments / issues raised during that review, along with its resolution.
No later than the 30th day after the submission, if those pointers have been posted, and the last version of the submission from the proposer group meets the requirements of these rules, the OASIS TC Administrator must post them to the OASIS Membership with a Call For Participation and an announcement of a first meeting. Otherwise, the Convener may obtain a single 10-day extension for posting a compliant proposal with the OASIS TC Administrator.
Eligible Persons intending to participate in the first meeting must use the OASIS collaborative tools to register as a TC Member, and to specify whether they intend to gain voting rights, no later than 7 days prior to a meeting. No later than 7 days prior to the meeting, the OASIS TC Administrator will post a notice to the prospective Members on the TC’s general email list inviting indications of candidacy for TC Chair to be posted to that list.
If the Eligible Person is an employee or designee of an OASIS Organizational Member, the Primary Representative of that organization must confirm to the Convener and to the TC Administrator that the person may become a Member of the TC.
Every Eligible Person who has so registered and been confirmed shall be a Member of the TC beginning with the first meeting. Every Eligible Person who has so registered, requested voting rights, been confirmed, and is present at the first meeting of a TC shall be a Voting Member of the TC beginning with the first meeting.
The first meeting of a TC must occur at the place and time and in the manner described in the announcement. Any initial meeting whose time or location is changed and any initial telephone or other electronic meeting that fails to grant access to every Eligible Person previously registering to attend shall be subject to appeal as provided in Section 4.2.
2.4.1 Observer: An Eligible Person may become an Observer of a TC by registering as an Observer using the electronic collaboration tools provided by OASIS. If the Eligible Person is an employee or designee of an OASIS Organizational Member, the Primary Representative of that organization must be notified that the person has requested to become an Observer. The Observer is not a TC Member so has no attendance or participation requirements to maintain this status, other than to remain an Eligible Person.
2.4.2 Member: Any time after the first meeting, an Eligible Person shall become a Member of an existing TC by registering as a Member using the electronic collaboration tools provided by OASIS. If the Eligible Person is an employee or designee of an OASIS Organizational Member, the Primary Representative of that organization must confirm to the Chair and to the TC Administrator that the person may become a Member of the TC. Upon receipt by the Chair of confirmation by the Primary Representative the Member may begin participating, but shall not have voting rights. A Member shall become eligible to vote in the TC when the requirements below are met.
2.4.3 Persistent Non-Voting Member: A Member or Voting Member may, at any time after joining a Technical Committee, send e-mail to both the Chair and the TC mailing list informing them of their change in membership status, effective as of the date of notice, or other specified future date. A Persistent Non-Voting Member retains participation rights but is not eligible to vote and does not count towards Quorum. A Persistent Non-Voting Member who wishes to gain voting rights must send e-mail to both the Chair and the TC mailing list informing them of their intent to become a Voting Member and must follow the rules in section 2.4.4(c) as if they had lost their voting rights due to non-attendance.
(a) After the first Meeting of a TC, a Member shall gain voting rights at the close of the second consecutive Meeting attended by the Member or, if less than two Meetings are called within 60 days after the person becomes a Member, at the close of that 60th day. OASIS Individual Members and the representatives of OASIS Organizational Members are equally eligible to serve as Voting Members of a TC.
(b) A Voting Member must be active in a TC to maintain voting rights. In TCs that hold Meetings, a Voting Member who is absent from two consecutive Meetings (as recorded in the minutes) loses his or her voting rights at the end of the second Meeting missed. If a TC has adopted a standing rule to conduct business only by electronic ballot, without Meetings, then a Voting Member who fails to cast a ballot in two consecutive Work Product Ballots loses his or her voting rights at the close of the second ballot missed.
(c) A TC Member who has lost his or her voting rights shall regain them for a TC that holds Meetings by attending two consecutive Meetings (as recorded in the minutes), thus regaining voting rights after the end of the second Meeting attended or, if less than two Meetings are called within 60 days after the loss of such rights, at the close of that 60th day. A Member of a TC that does not hold Meetings may regain voting rights by making a request to the chair(s) to regain them, effective at the close of the 60th day after the request.
Except as provided in Section 2.6, membership in an OASIS TC shall be terminated under the following conditions:
(2) Persons who lose Eligible Person status for reasons including, but not limited to, change of employment shall have up to 15 days of TC membership as an OASIS Individual Member in which to request a Leave of Absence or re-establish eligibility. A Member shall lose TC membership on the 16th day after losing Eligible Person status or at the end of a Leave of Absence requested as specified in Section 2.6 if Eligible Person status has not been re-established.
Every Voting Member of an OASIS TC shall be entitled to at least one Leave of Absence during any one twelve month period. During a Leave of Absence, a Voting Member shall be exempt from the participation criteria specified in Section 2.4. A first Leave of Absence during any one twelve month period shall be obtained automatically by sending an email to both the Chair and the TC mailing list. The Chair must notify the TC of all Leaves of Absence by reporting them in the minutes of the TC’s next meeting.
A Voting Member who has already been granted a Leave of Absence during any twelve month period may apply for a maximum of one additional Leave of Absence during the same twelve month period, but a second Leave of Absence during any twelve month period shall be granted only upon formal Resolution of the TC.
A Voting Member of a TC who has been granted a Leave of Absence shall not have voting rights in the TC and all of its Subcommittees for the duration of the Leave; voting rights shall resume immediately upon the person returning from Leave.
The length of a Leave of Absence shall be specified in advance by the Voting Member requesting it and shall not exceed 45 days. A Leave of Absence shall begin no earlier than seven days after the date upon which the request was delivered to the Chair of the TC and shall end on the date specified, or at the beginning of the first TC meeting or Subcommittee meeting attended after the Leave begins, or upon transmittal of the first mail ballot returned after the Leave begins, whichever comes first. Time allocated for a Leave of Absence but not used due to early resumption of participation cannot be carried over into another Leave.
Each TC must have a Chair. Only Members and Voting Members of the TC are eligible to be Chair or co-Chair. The TC Chair is initially elected at the first meeting. The Chair is elected by Full Majority Vote of the TC. If the TC does not have a Chair then all TC activities, with the exception of the selection of a new Chair, are suspended; if the TC does not have a Chair for 120 days, the TC Administrator must close the TC.
The responsibilities of Chair of a TC may be discharged by no more than two co-Chairs. In the event that the Chair position is so shared each co-Chair is equally responsible for the Chair duties and responsibilities. Throughout this TC Process, whenever a notification to the TC Chair is required this must be made to both co-Chairs.
A TC Chair may be removed by action of the Board of Directors or by a Special Majority Vote of the TC. In the event that a TC has co-Chairs each may be removed individually or both may be removed by a single action.
A vacancy in chairing a TC shall be deemed to exist when (i) the Chair or one or both co-Chairs has been removed, (ii) the Chair or one or both co-Chairs has resigned the position, or (iii) the Chair or one or both co-Chairs ceases to be a Member of the TC. Vacancies in chairing a TC shall be filled by election from the TC Members; the TC may elect at any time by vote to elect a co-Chair, if only one Chair is seated, or to leave a second seat vacant. Any TC chair or co-chair election shall be by Full Majority Vote of the TC, with each winning candidate having received a full majority vote regardless of the number of candidates.
The same provisions regarding Leaves of Absence shall apply to the Chair or co-Chair of a TC as to the other TC Members, and additionally the Chair must notify both the OASIS TC Administrator and the TC at least 30 days prior to any non-emergency Leave of Absence.
The official copies of all resources of the TC and its associated Subcommittees, including web pages, documents, email lists and any other records of discussions, must be located only on facilities designated by OASIS. TCs and SCs may not conduct official business or technical discussions, store documents, or host web pages on servers or systems not designated by OASIS. All web pages, documents, ballot results and email archives of all TCs and SCs shall be publicly visible.
Mail Lists: Each TC shall be provided upon formation with a general discussion email list and a means to collect public comments. Subscription to the general email list shall be required for Members, Voting Members, Persistent Non-Voting Members and Observers of the TC.
The minutes of each TC meeting and a record of all decisions shall be posted to that TC’s general email list. All official communications and discussions of the TC must take place on the email list. All TC email lists shall be archived for the duration of the corporation, and all TC email archives shall be publicly visible.
The purpose of the TC’s public comment facility is to receive comments from the public and is not for public discussion. Comments shall be publicly archived, and shall be forwarded to one or more Members of the TC including the TC Chair. TCs shall not be required to respond to comments. Comments to the TC made by Members of the TC must be made via the TC general email list, and comments made by non-TC members, including from the public, must be made via the TC’s comment facility. Comments shall not be accepted via any other means.
Web Pages: The OASIS TC Administrator shall provide the TC with a publicly accessible web page. The TC must keep the following information current on the TC web page: the TC name and Charter; standing rules and other adopted procedures; meeting schedule; anticipated deliverables and delivery dates; list of TC Members; the name and email address of the TC Chair or co-Chairs as well as other positions such as secretary, editor, etc. that may exist; list of Subcommittees, their deliverables, and members; links to a repository of the draft and completed TC documents with identification of the latest versions of the TC’s Work Products; and a link to the IPR declarations for that TC.
Announcements: The OASIS TC Administrator shall create a publicly archived list for announcements from the OASIS TC Administrator regarding TCs. Any Eligible Person shall be able to subscribe to this list. Every important change in TC status shall be posted to the announcement list; such changes shall include but not be limited to the following: TC formation; TC Charter revision; start of Public Review; approval of Committee Specifications and Committee Notes; submission of a Committee Specification as a Candidate OASIS Standard; approval or rejection of a proposed OASIS Standard; and closure of a TC.
The operation of TCs shall be governed by Robert’s Rules of Order Newly Revised, insofar as such rules are not inconsistent with or in conflict with this TC Process, the OASIS IPR Policy, the OASIS Bylaws, other Board-approved policies, or with provisions of law. The duration of a TC shall be considered a single session. Formal actions of TCs shall be governed by the same rules regardless of the language in which the work is taking place.
Standing rules may be adopted, amended, or rescinded by Full Majority Vote of the TC. The TC may not adopt standing rules or other Resolutions related to IPR, quorum requirements, membership, voting, participation, or that otherwise conflict with or supersede any OASIS Board-approved policy. Standing rules, and any amendments to them, must be communicated to the TC Administrator, who may rescind them if they are in conflict with OASIS policy, and, in order to be enforceable, must be posted on the TC’s web page.
TC meetings must be properly called and scheduled in advance using the OASIS collaborative tools. Meetings scheduled or conducted in such a manner as to exclude the participation of any Member is subject to appeal. Meetings may be conducted face-to-face or via telephone conference or other electronic media that allow participation of all Members of the TC. In order to enable the openness of TC proceedings, meetings should be scheduled and conducted so as to permit the presence of as many TC Observers as is logistically feasible. Meeting minutes must be recorded and posted to the TC’s general email list and referenced on the TC web page.
Without a Quorum present discussions may take place but no business may be conducted; those present may act as a “Committee of the Whole” as defined in Robert’s Rules of Order Newly Revised, and make a report to the entire TC. Attendance must be recorded in the meeting minutes. Meetings without Quorum shall still count towards attendance for purposes of Members gaining, maintaining, or losing voting rights.
A TC may clarify its Charter only for the purpose of removing ambiguity or for narrowing the scope of the topic defined by the Charter. The TC may not broaden or otherwise change its scope of the topic of work. The list of deliverables may be expanded only if the new deliverables are within the scope of the topic.
Approval for clarification shall require a Special Majority Vote of the TC. The clarification of the Charter may occur no earlier than the first meeting of the TC. The TC Chair shall notify the TC Administrator that a motion has been made to clarify the Charter, and the TC Administrator shall set up and conduct the ballot.
The TC Administrator may prevent the proposed clarification from coming to vote if it is not in conformance with OASIS policies. The TC Administrator must within 15 days either open the ballot or reply to the TC with the reason why the change cannot be voted upon. The clarified Charter shall not take effect until approved and announced by the TC Administrator. The TC Administrator shall publicize approved changes as specified in Section 2.8 and any revisable publicly visible description (e.g., web page) promulgated by the TC shall be updated to reflect such changes.
In order to expand the scope of a TC, it must be rechartered. The TC shall retain the same name, all email lists and archives, web pages, etc. Contributions made to the TC under the prior charter must be recontributed to be used under the revised charter.
Rechartering shall not change the TC name nor the IPR Mode of the TC. If a different name or IPR Mode is desired then a new TC (with a unique name) must be formed and the normal rules for creating a new TC apply (see section 2.2).
A proposal to recharter the TC must be made by Resolution and submitted to the TC Administrator. The proposal shall follow the rules for a proposal to form a new TC as specified in section 2.2 excluding items 2(d) and 2(e).
The TC Administrator shall reply to the proposers within 15 days, and if the proposal is complete shall schedule a ballot. Approval for rechartering shall require a Special Majority Vote of the TC being rechartered.
Once the ballot has been approved, the following steps shall be taken:
- Within five days of approval, the TC Administrator shall announce the rechartering to the OASIS Membership with a Call for Participation (including instructions for how and when to join the the newly rechartered TC) and an announcement of the first meeting in the same manner as for a new TC.
- The TC may continue work until seven days before the first meeting under the new charter. Seven days before the first meeting, all work of the TC shall stop and the TC Administrator shall send an email to the TC mailing list describing the procedure for re-joining the TC and remove all Members and TC officers from the TC roster.
- OASIS members wishing to (re)join the TC shall follow the normal procedures for joining a new TC. In the event that a member is not able to join in the seven day period before the first meeting, because of lack of online access, the member’s primary representative may ask the TC Administrator to add the member to the TC.
The same rules and procedures regarding the First Meeting of a TC specified under section 2.3 also apply for the first meeting of the rechartered TC, except as superseded in this section.
TC votes require a Simple Majority Vote to pass, except as noted elsewhere in this Process. All TC ballots requiring a Special Majority Vote for approval must be conducted by the TC Administrator; the TC Chair shall notify the TC Administrator that a motion has been made which requires a Special Majority Vote, and the TC Administrator shall set up and conduct the ballot.
Eligibility: A Member of a TC must have voting rights to make or second a motion, and must have voting rights at the time a ballot is opened in order to vote on that ballot. Every Voting Member of a TC has a single vote. Organizations do not vote in TCs. Proxies shall not be allowed in TC voting.
Electronic Voting: TCs may conduct electronic ballots, either by using the TC’s general mail list or the publicly archived electronic voting functionality provided by OASIS. The minimum period allowed for electronic voting shall be seven days; the TC may specify a longer voting period for a particular electronic ballot. Any Work Product Ballot conducted as an electronic ballot must permit each voter to choose “yes”, “no” or “abstain.” Eligible voters may change their vote up until the end of the voting period.
The TC may by Resolution create a Subcommittee (SC). The Resolution must be minuted, and must include the name, statement of purpose, list of deliverables, and name of the Chair of the SC. All of these items must fall within the Charter of the TC and conform to OASIS policy.
The deliverables of the SC are made only to the TC. Members of the SC must first be Members of the TC. Observers of a TC may be Observers of a SC, but may not become SC members without first becoming a Member of the TC. An SC member may resign from the SC and remain a Member of the TC.
The TC Administrator must close a TC that has completed the deliverables listed in its Charter if the TC does not add new deliverables or that fails to elect a Chair for the period provided in Section 2.7.
The TC Administrator may close a TC that fails to conduct at least one Quorate Meeting or conduct any Work Product Ballots during any six month period; whose membership falls below the Minimum Membership; which has not completed its deliverables within the schedule listed in its Charter; or which has failed to show progress towards achieving its purpose as defined by its Charter.
(3) Maintenance Activity on an OASIS Standards Final Deliverable may be done by a TC other than the TC that originated the deliverable, if: (a) the name of the OASIS Standards Final Deliverable to be maintained is listed as a deliverable in its Charter, and (b) if the originating TC is not closed, it has consented to the Maintenance Activity by a Special Majority Vote.
The TC shall operate in accordance with the OASIS Intellectual Property Rights (IPR) Policy.
Notices of Disclosed Claims, as defined in and required by the OASIS IPR Policy, shall be made by sending an email message to the TC Administrator, who shall post the disclosure on the TC’s web page and notify the TC via the TC general email list. The TC shall make no formal decision with regard to the applicability or validity of an IPR disclosure.
Contributions, as defined in the OASIS IPR Policy, shall be made by sending to the TC’s general email list either the contribution, or a notice that the contribution has been delivered to the TC’s document repository; a URL or other reference to the document is not sufficient. Written contributions must be converted to electronic format and delivered to the TC’s general email list or document repository. The TC is not required to acknowledge or use any Contribution.
(1) General. All documents and other files produced by the TC, including Work Products at any level of approval, must use the OASIS file naming scheme, and must include the OASIS copyright notice. All document files must be written using the OASIS document authoring templates, which shall be maintained and made available by the TC Administrator. The name of any Work Product may not include any trademarks or service marks not owned by OASIS.
(2) Acknowledgements. Any Work Product that is approved by the TC at any level must include a list of people who participated in the development of the Work Product. This list shall be initially compiled by the Chair, and any Member of the TC may add or remove their names from the list by request.
(4) File Formats. Editable formats of all versions of TC documents must be delivered to the TC’s document repository. Working Drafts may be in any format (i.e. produced by any application). All approved versions of OASIS Deliverables must be delivered to the TC’s document repository in the (1) editable source, (2) HTML or XHTML, and (3) PDF formats; and the TC must explicitly designate one of those delivered formats as the authoritative document. Any links referenced by the TC shall be to the HTML, XHTML and/or PDF formats stored using repositories and domain names owned by OASIS and as approved by the TC Administrator.
(5) Multi-Part Work Products. A Work Product may be composed of any number of files of different types, though any such multi-part Work Product must have a single Work Product name and version number. Irrespective of the number and status of the constituent parts, the Work Product as a whole must be approved by a single Work Product Ballot.
(6) Allowed changes. Any change made to a Work Product requires a new version or revision number, except for changes made to (a) the approval status, (b) the date, (c) the URIs of the Work Product as appropriate, (d) the running header/footer, (e) updates to the file names of all Work Product files and any references between them, (f) any approved Designated Cross-Reference Changes, or (g) when a Committee Specification is approved as an OASIS Standard, and prior to its publication, any references to a Committee Specification may be updated if the referenced Committee Specification has subsequently been approved and published as an OASIS Standard. All of 6(a-g) must be made after the approval of the Work Product as a Committee Specification Draft, Committee Note, Committee Specification, Candidate OASIS Standard, or OASIS Standard and before its official publication by TC Administration.
(7) Computer Language Definitions. All normative computer language definitions that are part of the Work Product, such as XML instances, schemas and Java(TM) code, including fragments of such, must be well formed and valid.
- All normative computer language definitions must be provided in separate plain text files;
- Each text file must be referenced from the Work Product; and
- Where any definition in these separate files disagrees with the definition found in the specification, the definition in the separate file prevails.
- All computer language definitions should be provided in separate plain text files; and
- Each text file should be referenced from the Work Product.
A specification that is approved by the TC at the Committee Specification Public Review Draft, Committee Specification or OASIS Standard level must include a separate section, listing a set of numbered conformance clauses, to which any implementation of the specification must adhere in order to claim conformance to the specification (or any optional portion thereof).
Every Work Product must clearly indicate on the cover page whether it is a Standards Track Work Product or Non-Standards Track Work Product. The cover page of a Non-Standards Track Work Product must clearly and conspicuously state that the patent provisions of the IPR Policy do not apply to that Non-Standards Track Work Product.
Documents which use formats that support headers and footers should indicate on every page whether the document is a Standards Track Work Product or Non-Standards Track Work Product. In these cases, every Non-Standards Track Work Product must also have a brief statement on every page that the patent provisions of the IPR Policy do not apply.
A TC wishing to update the Normative References or non-Normative References in the Normative References or Non-Normative References section in one of its OASIS Work Products to reflect the outcome of a pending status change in another OASIS Work Product may do so, by adopting a “Designated Cross-Reference Change” as part of its Work Product Approval Motion, which must include: (a) a list designating each of the other OASIS Work Products (including version number) that are referenced by that Work Product and whose cross-references should conditionally be updated; (b) a reference to this Section 2.19; and (c) an acknowledgement that approval and publication of the Work Product may be delayed by the Designated Cross-Reference Changes.
Designated Cross-Reference Changes may only be made on Work Product Approval Motions for Committee Specification Drafts, Public Review Drafts, Committee Specifications, and Candidate OASIS Standards. Designated Cross-Reference Changes may only be made for Work Products with the following pending status changes:
- Working Drafts to be approved as Committee Specification Drafts and/or
- Committee Specification Drafts to be approved as Public Review Drafts and/or
- Committee Specification Drafts or Public Review Drafts being approved as Committee Specifications and/or
- Committee Specifications being approved as Candidate OASIS Standards and/or
- Candidate OASIS Standards being approved as OASIS Standards.
Designated Cross-Reference Changes may not be made to any OASIS Work Product changing its version or revision number nor to any non-OASIS standard or publication.
The text of a proposed Designated Cross-Reference Change to a Work Product shall only include for each cross-referenced Work Product:
- the current name, version and revision number;
- the current URI;
- the expected approval status; and
- the expected approval date of the cross-referenced Work Product.
The effectiveness of a proposed Designated Cross-Reference Change in a Work Product is conditioned on the resolution of the expected approval action for each cross-referenced Work Product. Therefore, if a Work Product Approval Motion includes proposed Designated Cross-Reference Changes, the effectiveness of the subject Work Product’s approval will be delayed until the resolution of all other cross-referenced Work Product approval actions. The TC Administrator will withhold announcement and certification of the Work Product itself until all such cross-referenced resolutions are complete.
If the Work Product Approval Motion (which includes Designated Cross-Reference Changes) passes, then, when the last cross-referenced approval is resolved, the final approved version will be published with all of its conditional descriptions of the cross-referenced Work Products updated to reflect their correct status at that time.
Provisions involving business relations between buyer and seller such as guarantees, warranties, and other commercial terms and conditions shall not be included in an OASIS Standard. The appearance that a standard endorses any particular products, services or companies must be avoided. Therefore, it generally is not acceptable to include manufacturer lists, service provider lists, or similar material in the text of a standard or in an annex (or the equivalent). Where a sole source exists for essential equipment, materials or services necessary to comply with or to determine compliance with the standard, it is permissible to supply the name and address of the source in a footnote or informative annex as long as the words “or the equivalent” are added to the reference. In connection with standards that relate to the determination of whether products or services conform to one or more standards, the process or criteria for determining conformity can be standardized as long as the description of the process or criteria is limited to technical and engineering concerns and does not include what would otherwise be a commercial term.
- Committee Specification Draft,
- Committee Specification Public Review Draft,
- Committee Specification,
- Candidate OASIS Standard,
- OASIS Standard,
- Approved Errata.
Non-Standards Track Work Products may directly be approved as Committee Notes by the Technical Committees via a Full Majority vote.
Public reviews are optional for Committee Notes. If a TC wishes to conduct public reviews before approving a Committee Note, the same procedures for approving a Committee Specification (as outlined in section 3.1, section 3.2 and section 3.3) and a similar terminology used for the intermediate drafts of the Committee Specifications (i.e. Committee Note Draft and Committee Note Public Review Draft) must be followed.
Note that a Committee Note is never progressed as an OASIS standard.
After approving a Committee Note, a Technical Committee may notify the TC Administrator for publishing the Committee Note to the OASIS Library and announcing its publication to the OASIS membership.
The TC may at any stage during development of a Work Product approve a Working Draft as a Committee Specification Draft. Approval of these drafts shall require a Full Majority Vote of the TC. The TC may approve a Working Draft, revise it, and re-approve it any number of times as a Committee Specification Draft
Before the TC can approve a Committee Specification Draft as a Committee Specification, the TC must conduct a public review of the work. The decision by the TC to submit the draft for public review requires a Full Majority Vote, and must be accompanied by a recommendation from the TC of external stakeholders who should be notified of the review. The draft approved to go to review shall be called a Committee Specification Public Review Draft. The public review must be announced by the TC Administrator to the OASIS Membership list and optionally on other public mail lists; the TC Administrator shall at the same time issue a call for IPR disclosure for Committee Specification Public Review Drafts.
Comments from non-TC Members must be collected via the TC’s archived public comment facility; comments made through any other means (unless made by a TC Member via the TC email list) shall not be accepted. The TC must acknowledge the receipt of each comment, track the comments received, and post to its primary e-mail list its disposition of each comment at the end of the review period.
No changes may be made to the public review draft during a review. If the TC decides by Full Majority Vote that changes are required, the draft shall be withdrawn from review after the Chair informs the TC Administrator, and then subsequently resubmitted by the TC for a new Public Review cycle of the same type, either initial or subsequent.
The TC may conduct any number of review cycles (e.g. approval to send a Committee Specification Draft to public review, collecting comments, making edits to the Committee Specification Draft, etc.). The initial public review of a public review draft must take place for a minimum of 30 days, and any subsequent reviews must be held for a minimum of 15 days. Changes made to a committee draft after a review must be clearly identified in any subsequent review, and the subsequent review shall be limited in scope to changes made in the previous review. Before starting another review cycle the revisions must be re-approved as a Committee Specification Draft and then approved to go to public review by the TC.
If any changes that are not Non-Material are made to the draft after the public review, whether as a result of public review comments or from TC Member input, then the TC must conduct another review cycle. The draft may not be considered for approval by the TC as a Committee Specification until it has undergone a review cycle during which it has received no comments that result in any changes that are not Non-Material.
If only Non-Material Changes are made to the draft after the public review, whether as a result of public review comments or from TC Member input, then the TC may proceed with the approval as a Committee Specification in accordance with Section 3.3 without conducting another public review cycle.
After the public review, the TC may approve the Committee Specification Draft as a Committee Specification If any comments have been received during the most recent Public Review period, that vote may not commence any earlier than 7 days after the last day of that Public Review. The approval of a Committee Specification shall require a Special Majority Vote. The TC Chair shall notify the TC Administrator that the TC has resolved to request a Special Majority Vote for the advancement of the draft as a Committee Specification and provide to the TC Administrator the URI for the meeting minutes which record the TC’s resolution, including the location of the editable versions of the files and any other ballot details (for example, Designated Cross-Reference Change motions). The TC Administrator shall set up and conduct the ballot to approve the Committee Specification
If Non-Material Changes have been made to the draft since its last public review then the TC must provide an acceptable summary that is clear and comprehensible of the changes made since the last public review and a statement that the changes are all Non-Material to TC Administration. TC Administration shall announce the opening of the ballot to approve the draft to the OASIS Membership and optionally on other public mail lists along with the summary of changes and the TC’s statement. If any Eligible Person objects that the changes are not Non-Material before the ballot closes, TC Administration shall halt the ballot and require the TC to submit the draft for another public review cycle. If such objection is made after the ballot has closed, TC Administration shall reject it and the results of the ballot shall stand.
Approval of an OASIS Standard is a multi-step process:
- Submission of a Candidate OASIS Standard to the TC Administrator,
- Completion of a public review lasting a minimum of 60 days, and
- A membership-wide ballot.
- A potential single, second membership-wide ballot to address negative comments.
After the approval of a Committee Specification, and after three Statements of Use referencing the Committee Specification have been presented to the TC, a TC may resolve by Special Majority Vote to submit the Committee Specification as a Candidate OASIS Standard. At least one of the Statements of Use must come from an OASIS Organizational Member. The TC may decide to withdraw the submission, by Special Majority Vote, at any time until the final approval. Upon Resolution of the TC to submit the specification, its Chair shall submit the following items to the TC Administrator:
(a) Links to the Candidate OASIS Standard in the TC’s document repository, and any appropriate supplemental documentation, all of which must be written using the OASIS templates in effect at the time of the Committee Specification approval vote. The specification must not have been changed between its approval as a Committee Specification and its submission to OASIS for consideration as an OASIS Standard, except for the changes allowed in Section 2.18(6).
(c) Certification by the TC that all schema and XML instances included in the specification, whether by inclusion or reference, including fragments of such, are well formed, and that all expressions are valid;
(g) The beginning and ending dates of the public review(s), a pointer to the announcement of the public review(s), and a pointer to an account of each of the comments/issues raised during the public review period(s), along with its resolution;
The TC Administrator shall complete administrative processing and checking for completeness and correctness of the submission within 15 days. If the submission is incomplete it shall be rejected but may be resubmitted at a later time.
No part of the submission may be changed or altered in any way after being submitted to the TC Administrator, including by Errata or corrigenda. Errata, corrigenda or other changes to an OASIS Standard are not permitted after its submission for OASIS Standard approval, except that changes which address comments associated with negative votes on an OASIS Standard may be allowed as described in section 3.4.4 below.
A public review of the Candidate OASIS Standard shall be announced by the TC Administrator to the OASIS Membership list and optionally on other public mail lists.
Comments from non-TC Members must be collected via the TC’s archived public comment facility; comments made through any other means (unless made by a TC Member via the TC email list) shall not be accepted. The TC must acknowledge the receipt of each comment, track the comments received, and post to its primary e-mail list the disposition of each comment at the end of the review period.
No changes may be made to the Candidate OASIS Standard during a review. If the TC decides by Full Majority Vote that changes are needed, then the specification must be withdrawn from review after the Chair informs the TC Administrator.
Upon completion of the public review, the Chair must notify the TC Administrator of the results.
- If no comments were received, the TC Administrator must start the ballot for OASIS Standard approval within 7 days of notification.
- If comments were received, but no changes are to be made to the Candidate OASIS Standard, the Chair will request that the TC Administrator start a Special Majority Ballot for the TC to approve continuing with the OASIS Standard ballot. The TC Administrator will begin said ballot within 7 days of receipt. Upon successful completion of that ballot, the TC Administrator will, within 7 days, begin the ballot for OASIS Standard approval.
- If comments were received and only Non-Material Changes are to be made to the Candidate OASIS Standard, the editor(s) will prepare a revised Candidate OASIS Standard. Changes may only be made to address the comments. The TC must provide an acceptable summary that is clear and comprehensible of the changes made and a statement that the TC judges the changes to be Non-Material to TC Administration and request a Special Majority Vote to proceed with the membership vote. TC Administration shall hold the Special Majority Vote and announce it to the OASIS membership and optionally on other public mail lists along with the summary of changes and the TC’s statement. If the Special Majority Vote passes, the TC Administrator must start the ballot for OASIS Standard approval within 7 days of notification.
- If comments were received and Substantive Changes are to be made to the Candidate OASIS Standard, the editors(s) will prepare a revised specification to be approved as a Committee Specification Draft by the TC and proceed with a subsequent Public Review as noted in Section 3.2. Before resubmission the specification must be approved as a Committee Specification.
In votes upon Candidate OASIS Standards, each OASIS Organizational Member at the time the ballot is issued shall be entitled to cast one vote. Votes shall be cast via the publicly archived electronic voting facility supplied by OASIS. A ballot announcement will be sent to each member entitled to vote and shall specify the ballot closing date and time. Ballots shall be publicly visible during voting. Eligible voters may change their vote up until the end of the 14-day voting period. The results of a vote on a proposed standard shall be provided to the membership and to the TC no later than seven days following the close of the voting period.
If at the end of the voting period:
- if at least 15 percent of the voting OASIS Membership has voted to approve the proposed standard, and if no votes have been cast to disapprove the proposed standard, it shall become an OASIS Standard immediately following the end of the voting period; or
- if negative votes have been cast amounting to 25 percent or more of the votes cast, or if less than 15 percent of the voting OASIS Membership has cast positive votes to approve the proposed standard, the ballot is deemed to have failed and the submission fails; or
- if negative votes are cast amounting to less than 25 percent of the votes that have been cast, the TC shall be notified of the negative votes, after which the TC shall have 30 days to take one of the following actions by Resolution of a Special Majority Vote: (a) request the TC Administrator to approve the specification as submitted despite the negative votes; (b) withdraw the submission entirely; or (c) provide a submission amended to address negative votes as noted in section 3.4.4 below. If the originating TC upon notification of negative votes takes no formal action within the 30 days allocated for consideration of the results, then the specification shall not become an OASIS Standard.
Failure of a ballot for any reason shall not prevent a later version of the same specification from being submitted again as specified in this section 3.4.
An amended submission of a Candidate OASIS Standard may only be made once. There is no public review associated with this amended submission.
The TC shall have 30 days in which to approve the amended submission by Special Majority Vote and submit the amended Candidate OASIS Standard as specified in 3.4.1 above. The amended submission must be accompanied by an explanatory report listing all changes (and their rationale) made to the submission since the previous Candidate OASIS Submission vote, and additionally include a resolution report showing the disposition of all comments received during that first vote.
At the end of the Candidate OASIS Standard vote on the amended submission:
- if at least 15 percent of the voting OASIS Membership has voted to approve the proposed standard, and if no votes have been cast to disapprove the proposed standard, it shall become an OASIS Standard immediately following the end of the voting period; or
- if negative votes have been cast amounting to 25 percent or more of the votes cast, or if less than 15 percent of the voting OASIS Membership has cast positive votes to approve the proposed standard, the ballot is deemed to have failed and the submission fails; or
- if the amended submission receives negative votes amounting to less than 25 percent of the votes that have been cast, the TC shall be notified of the negative votes, after which the TC shall have 30 days to request, by Special Majority Vote, that the TC Administrator approve the specification as submitted despite the negative votes. If the TC, upon notification of negative votes, takes no formal action in this period to request approval, then the specification shall not become an OASIS Standard.
Failure of this subsequent ballot for any reason shall not prevent a later version of the same specification from being submitted again as specified in this section 3.4.
A TC may approve a set of Errata to an OASIS Standard which it developed as “Approved Errata” by:
(a) Adopting the set of proposed corrections as a Committee Specification Draft, in the form of a list of changes, and optionally accompanied by a copy of the original OASIS Standard text marked to incorporate the proposed changes.
(b) Confirming by Full Majority Vote that the proposed corrections do not constitute a Substantive Change.
(c) Submitting the proposed corrections for a 15-day public review, and completing that review, pursuant to Section 3.2.
(d) After the public review, confirming the proposed corrections as Approved Errata by a Full Majority Vote.
Once approved, the Approved Errata shall be made available with the OASIS Standard it corrects, in any publication of that OASIS Standard. Disposition of Approved Errata must be identified in the subsequent Committee Specification Public Review Draft of the corrected OASIS Standard.
A TC may not adopt Approved Errata to an OASIS Standard more than once in any six-month period.
The “OASIS TC Administrator,” as defined in Section 1 of this TC Process, shall act as the Technical Committee Liaison to the Board for the purpose of keeping the Board apprised of activities related to the TC Process. The specific duties of the TC Liaison shall be specified by the Board in consultation with the TC Administrator but shall, at a minimum, provide for the submission to the Board of a notice when a proposal has been received for the creation of a new TC and when a TC submits a Committee Specification as a Candidate OASIS Standard. Such notice shall be delivered via email to the Board immediately upon the receipt of the submission by the TC Administrator. The TC Administrator shall also send a copy of proposals for the creation of new TCs to the Technical Advisory Board (TAB) for their comment.
Notwithstanding anything to the contrary contained in this TC Process, upon majority vote of the members of the Board at a meeting thereof duly called and constituted, the creation of a new TC may be prevented, or a proposed OASIS Standard may be withheld from voting by OASIS Membership; the proposal or the submission shall be returned to the proposers or the sponsoring TC for additional consideration, with an explanation of the reasons for such action.
The Board of Directors may amend this TC Process at any time and from time to time at its sole discretion.
Any Eligible Person who believes that
- an action taken or not taken by or with respect to TCs, or
- an action taken or not taken by the TC Administrator,
is in violation of the procedures set forth in this TC Process or OASIS policies specified by the OASIS Board of Directors, may appeal such action or inaction.
Appellants shall file a complaint within 30 days of the action being appealed or at any time with respect to an inaction. The complaint shall state the nature of the objection(s), including any direct and material adverse effects upon the appellants; the section(s) of this TC Process or OASIS policies at issue; the actions or inactions at issue; and the specific remedial action(s) that would satisfy the appellants’ concerns. Previous efforts to resolve the objection(s) and the outcome of each shall be noted.
In the case of an appeal to the TC Administrator: within 15 days of receipt of the complaint, the TC Administrator shall provide a copy of the complaint to the TC; and within 30 days of such receipt, shall render a decision, with a copy to the TC.
In the case of an appeal to the OASIS Board of Directors: such appeal, in order to be valid, shall be sent to the board comment list (email@example.com) and the relevant TC(s). The Board shall hold a hearing (with the appellants invited) within 45 days of receipt of the appeal. The Board shall render its decision within 30 days. The decision of the Board shall be final.
The OASIS Board of Directors has the authority to effect such remedial action as may be necessary to remedy a complaint brought under this TC Process.
This TC Process applies to previously established TCs upon its adoption.
Dates Approved: Thu, 2014-04-24 Effective: Thu, 2014-05-01