Summary

  • A public-review comment at OASIS must be acknowledged, tracked and given a disposition, but it is not a personal veto or the final organization-wide approval of a standard.
  • A Technical Committee's Special Majority, the evidence of Statements of Use and the Organizational Members' Call for Consent answer different questions. A versioned lifecycle receipt should keep their boundaries visible.

One document can cross three different authority gates

The tempting shorthand is simple: a draft was reviewed, the committee voted, therefore OASIS approved it. The current process is more useful—and more demanding—than that shorthand permits.

The first gate is internal to the Technical Committee. A Committee Specification Draft can enter public review only after a Full Majority of eligible Voting Members approves that move. The first review must last at least 30 days; later reviews of the same work product must last at least 15. The length tells a reader that outsiders and non-voting participants had a defined channel to inspect the text. It does not tell the reader that they acquired a ballot.

The second gate is also technical, but it is not identical to opening a review. The committee must acknowledge comments, track them and post their dispositions after review. If a response produces a Material change, another review is required before approval as a Committee Specification. Only after a successful review and comment resolution can the committee approve a Committee Specification by Special Majority.

That Committee Specification is the highest approval the TC can give on its own authority. It is an important fact, not an inferior near-miss. But it is still not the same fact as an OASIS Standard. A reader who calls it the final organization-wide decision has skipped a constituency.

The third gate begins only if the committee chooses to seek the OASIS Standard stage. It needs a Special Majority to submit the approved Committee Specification as a candidate, plus three Statements of Use that refer to that specification, including at least one from an Organizational Member. The candidate then goes through a public review of at least 60 days. After that review and its handling, the TC Administrator runs a Call for Consent for at least 14 days among eligible OASIS Organizational Members.

This is not a complicated way of saying the same people vote twice. It is a chain of different questions: did the TC put a defined text into review; did it deal with review input sufficiently to make a technical decision; is there stated use evidence; and do eligible Organizational Members raise enough valid objections to stop organizational approval?

A comment has a required record, not an automatic command

Public review is easy to diminish because a commenter cannot simply press a button and reject the text. It is equally easy to inflate because the comment channel is public. Both readings erase the process actually described.

The present rule gives a comment a process consequence. The TC must acknowledge receipt, track the comment and publish its disposition. The committee must assess whether changes resulting from review are Material. A Material change sends the work product through another review cycle before a Committee Specification vote. That is a real constraint: a committee cannot quietly adopt a materially altered text while using the earlier review as if it covered the new text.

The rule does not say that every comment commands the committee's preferred technical answer. It does not turn raw comment count into a popularity contest. A technical body can disagree with a comment while recording why. The public record should therefore preserve the original comment, the version it addressed, the disposition, the change if any and the materiality assessment. “Resolved” without those links is too thin for someone arriving later to tell whether the term means accepted, rejected, deferred, merged with another issue or made obsolete by a new draft.

That distinction protects both sides. Commenters retain an attributable path to challenge an ambiguity or an implementation burden. Maintainers retain room to make a reasoned technical judgment instead of treating the inbox as a referendum. Later users can see which question was asked and what changed, without inventing unanimity.

The TC ballot has a denominator, and that denominator matters

The Committee Specification ballot is not a show of hands in a meeting. A Special Majority requires at least two-thirds of eligible Voting Members to vote yes and no more than one-quarter to vote no. Abstentions and non-votes do not count as yes or no, but eligible voters remain in the fixed denominator.

That design makes an attendance screenshot poor evidence. A packed call can still lack the votes required for a Special Majority. A small group of vocal authors can still fail to represent the eligible voter universe. Conversely, a passed Special Majority is evidence of a specific TC threshold; it is not evidence that every commenter, implementer or Organizational Member endorsed the text.

The receipt should freeze the eligible-voter count at ballot opening, the ballot type, opening and closing times, yes/no/abstention and non-vote counts, result, exact document version and any vote-resolution record. It need not publish a theory about why a person did not vote. It needs only to stop later narratives from changing the denominator after the outcome is known.

Statements of Use are evidence of use, not extra ballots

Before a Committee Specification can become a Candidate OASIS Standard, the process requires three Statements of Use referencing it; at least one must come from an Organizational Member. A statement is evidence about successful use or implementation under the defined process. It is not a fourth technical ballot, a universal interoperability guarantee or a proxy for market adoption.

This matters because implementation evidence and approval authority are different surfaces. The Statements of Use show that the candidate has crossed a use-evidence threshold. The TC's Special Majority authorizes submission. The later Call for Consent applies the organizational objection rule. A clear receipt keeps each field in its own column rather than letting “three users” become shorthand for “the membership approved.”

Consent is a defined organizational mechanism, not technical silence

The current OASIS model changed a historical habit of reading approval through percentage-based affirmative and negative ballots. Under the current Call for Consent, eligible Organizational Members are presumed to consent unless they file a valid objection through the voting facility. The call lasts at least 14 days. An objection must state a reason and/or proposed remedy. Fifteen or more valid objections reject the candidate; fewer than fifteen lead to the process's TC response or withdrawal path.

That is a meaningful organizational rule. It should not be caricatured as “nobody voted,” nor converted into a claim that silent organizations performed a technical review or agreed with every editorial choice. It establishes the thing its rule establishes: no threshold number of valid organizational objections stopped the candidate at that gate.

The difference is practical. A technical editor looking for a design rationale should read the comment log and TC decision record. An organization assessing approval status should read the consent notice, eligible-member universe, valid objections and final announcement. An implementer assessing deployed experience should read the Statements of Use and their scope. Each question has a different proof object.

Publish a lifecycle receipt rather than a prestige label

OASIS does not need a new authority to make these boundaries visible. It needs a compact receipt linked from every significant standards-track state change.

For public review, the receipt should name the exact document hash or immutable URI, stage, opening vote, review dates, comment channels, comments received, dispositions and materiality result. For Committee Specification approval, it should preserve the eligible TC-voter count, ballot threshold and result. For Candidate status, it should list the three Statements of Use, distinguish the Organizational Member statement, and identify the candidate's 60-day review period. For the final stage, it should state the eligible Organizational Member scope, Call for Consent dates, valid-objection count, any response path and the published status.

The point is restraint. The receipt must not say a public comment was a vote, a TC ballot was a corporate ratification, a Statement of Use was a technical endorsement by everyone, or a silent organization supplied engineering consensus. It should show exactly what each gate has proven and leave the rest unclaimed.

Sources

  1. OASIS Technical Committee Process
  2. OASIS TC Handbook: Public Review
  3. OASIS TC Handbook: Committee Specifications
  4. OASIS TC Handbook: Approving an OASIS Standard
  5. OASIS TC Handbook: Work Product Lifecycle
  6. Lu Heng, The Multi-Stakeholder Mirage