[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Updated Timeline for progression toward XLIFF 2.0 OASIS Standard
|
Thanks Chet. Quite useful. And if memory serves, when we passed XLIFF 1.2, Mary gave us a list of the 323 along with their contact information (so we could kiss babies and twist arms
to get people to remember to vote). Is that still part of the workflow? Or is there a url for the 323? Thanks, Bryan From: Chet Ensign [mailto:chet.ensign@oasis-open.org]
Bryan, you have the basics right. The TC will need to pass a motion requesting that I hold a Special Majority Vote of the TC to approve sending the CS to the membership for consideration as a Candidate OASIS Standard. After that vote passes,
I prepare the COS and it goes out for 60 day public review. As of today, there are 323 active organizational members, so you will need 49 affirmative votes to pass. /chet On Mon, Sep 16, 2013 at 8:01 PM, Schnabel, Bryan S <bryan.s.schnabel@tektronix.com> wrote: Kevin (and Chet, a follow on question for you at the end), Good question. Here’s how it works (I’m summarizing 3.4.3 Initial Balloting for OASIS Standard approval from
https://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard ). After we submit there is another long public review. At the end a 14-day voting period begins. If at least 15% of the voting OASIS Membership votes to
approve, and we get no votes that disapprove, XLIFF 2.0 is a standard. If we less than 15% vote the ballot fails. If we get negative votes and they amount to 25% or more of all votes cast, the ballot fails. If at least 15% vote, and we get negative votes,
but they amount to less than 25% of all votes cast, we can request that the TC Admin approves the standard (which presumably he would); or withdraw the submission; or amend the submission to address the negative votes. Last time we got only approving votes, but just eked out enough votes to hit the 15%. So that’s the technical answer. Chet, please feel free to elaborate if I missed anything. But I suspect what you really want to know is what are the (rough) numbers. Chet, could you please help us with this? What is the total number of OASIS Organizational Members at the moment? With this we can extrapolate the percentages. Thanks, Bryan From: Kevin O'Donnell [mailto:kevinod@microsoft.com]
Bryan, do you the details of what’s required in the final OASIS specification approval ballot? Do we need a certain number of votes or a majority of
votes? From:
xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org]
On Behalf Of Schnabel, Bryan S Fixed some copy-paste errors – outcome is the same. From:
xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org]
On Behalf Of Schnabel, Bryan S Hello, As promised, I recalculated our timeline based on the timing of our PR2 (assuming PR2 is launched by OASIS by 16 Sep). If I simply update the previous timeline (https://lists.oasis-open.org/archives/xliff/201306/msg00042.html
) with the new dates, as fate would have it, we'd have (in my opinion) the absolutely most perfectly bad time imaginable for the ballot for OASIS Specification dates: 23 Dec – 06 Jan.
The unfortunate timing is nearly poetic in its misfortune: 1. Reconciled each PR1 comment: [03 Sep] 2. Statements of Use [identify by 16 Oct] A. Must have a statement of use for each core feature B. Should have a statement of use for each module feature B. Test Suite (1 application vs. ecosystem of tools) i. Reference Implementation (one implementation that touches each feature): nice to have; not must have [identify by 16 Oct; roll out by 04 Dec] ii. Ecosystem of tools [identify list by 16 Oct; roll out by 20 Nov] 3. Re-approved Committee Draft (that reflects resolved comments,
https://www.oasis-open.org/policies-guidelines/tc-process#committeeDraft ) [03 Sep] 4. Second Public Review, 15-day [17 Sep – 30 Sep] 5. Approve Committee Specification (https://www.oasis-open.org/policies-guidelines/tc-process#committeeSpec
) [16 Oct] 6. Approve OASIS Standard (https://www.oasis-open.org/policies-guidelines/tc-process#OASISstandard
) [16 Oct – 06 Jan] A. Submit Candidate Specification [16 Oct] B. Public Review of Candidate Specification (60 days) [23 Oct – 20 Dec] C. Ballot for OASIS Specification approval [23 Dec – 06 Jan]
So I think we need to adjust the date on step 5. It will either need to move in, or move back. Let's discuss at the next meeting. Thanks, Bryan
-- Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]