https://www.oasis-open.org/policies-guidelines/tc-process
·
"Committee Note" is a Non-Standards
Track Work Product that has been approved by a Technical
Committee as specified
in Section
3.0.
·
"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.
"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.
"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 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.
"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.
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.
(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.
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.
So,
what this all means is that we are not required to hold a
Special
Majority Vote as I thought we were. A simple Full Majority
Vote, without the
need for electronic oversight, is allowable. So when we meet
on 9 July 2013, we
can vote it out of the SC and vote it on to the Em Adoption
TC where we can decide if we want a Special Majority Vote or
a simple full Majority Vote for approving Committee Note
Publication for both Notes the
following Tuesday, 9 July 2013 at the EM Adoption TC, though
I would prefer getting a nod
from the EM TC, too.