[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Uploaded a candidate draft for Committee Specification Draft
I have uploaded an updated draft to http://www.oasis-open.org/committees/download.php/41212/icom-spec-draft-01f.doc. This version is ready for the TC to vote for approval as a
Committee Specification Draft for public review. Thanks, Eric For your convenience, I have included excerpts from the
OASIS TC Process http://www.oasis-open.org/committees/process.php.
3.1 Approval of a Committee Draft The TC may at any stage
during development of a Work Product approve the Work Product as a Committee
Specification Draft or Committee Note Draft, as appropriate. Approval of
these drafts shall require a Full Majority Vote of the TC. The TC may
approve a Work Product, revise it, and re-approve it any number of times as a
Committee Specification Draft or Committee Note Draft. 3.2. Public Review of a Committee
Draft Before the TC can approve
a Committee Specification Draft as a Committee Specification, or a Committee
Note Draft as a Committee Note, 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 or Committee Note Public Review Draft, as appropriate. 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 or Committee Note Draft, as appropriate, and
then approved to go to public review by the TC. If any 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 must conduct another review
cycle. The draft may not be considered for approval by the TC as a Committee
Specification or Committee Note until it has undergone a review cycle during
which it has received no comments that result in any changes. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]