[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: proposal for new TC rule regarding coordinating changes to the KMIPSpecification and KMIP Usage Guide
Hi – Several times it’s been hard to get information for the KMIP Usage Guide created, once a proposal for the KMIP Specification has been balloted and approved. So in order to ensure that we have all the information relevant to both the KMIP Specification and the KMIP Usage Guide at the time we vote to include new functionality in KMIP, TC members have suggested that the TC vote to require that any proposal for changes to the KMIP Specification must also, at the time of ballot, include any new material for the Usage Guide. I have confirmed with the OASIS folks that there is no problem with creating such a rule (see the thread below). Here’s a first cut at the language for such a rule: No motion for an addition, deletion or modification to the KMIP Specification shall be accepted unless any KMIP Usage Guide addition, deletion or modification required in support of the change to the KMIP Specification has been defined and included in the same or accompanying ballot. We’ll plan to discuss this in Thursday’s call. Please feel free to send comments either to me or to the reflector. Thanks! Bob -----Original Message----- Hi Bob, If the TC wants to adopt that as a standing rule, I see no conflict with any OASIS policy or rule. As Robin says, you have identified the applicable portions of the OASIS TC Process. Since it requires a Full Majority Vote (more than 50% of the total number of voting members in the TC), you'll want to make sure your meeting gets the required number of attendees - unless you choose to run it as an electronic ballot. Either way, you may want to draft the language of the motion and the proposed language of the standing rule and circulate them ahead of time to get any initial debate or wordsmithing out of the way. I have noticed that the EMIX TC has been doing that lately with much success. By the time they present the motion at the meeting, the vote is just the final formality. Best regards, /chet > ---------- Forwarded message ---------- > From: Robin Cover <robin@oasis-open.org> > Date: Fri, Jul 22, 2011 at 6:01 AM > Subject: Re: question on TC procedure > To: robert.griffin@rsa.com > Cc: hal.lockhart@oracle.com, hardjono@mit.edu, > Subhash.Sankuratripati@netapp.com, indra.fitzgerald@hp.com, > MBJ@zurich.ibm.com, rha@zurich.ibm.com, Robin Cover > <robin@oasis-open.org> > > > On Fri, Jul 22, 2011 at 4:39 AM, <robert.griffin@rsa.com> wrote: >> Hi Robin, Thomas, Hal – >> >> A question came up in the TC meeting yesterday that I’m hoping you can help >> with. > > ======================================================= > [how about a TC resolution/agreement to] >> require that any proposal for changes to the KMIP >> Specification must also, at the time of ballot, >> include any new material for the Usage Guide. > ======================================================= > > Bob, I'll forward the question to Chet Ensign, who is now Director of > Standards Development and TC Administration. > > In any case, I think you have correctly identified the two sections in > the TC Process most relevant to use of a standing rule: > > 2.9 TC Procedure > http://www.oasis-open.org/policies-guidelines/tc-process-2010-07-28#procedure-standingRules > > 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 published on the TC’s web page. > > 2.8 TC Visibility > http://www.oasis-open.org/policies-guidelines/tc-process-2010-07-28#visibility-webPages > > 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 > > Best wishes, > > - Robin > > Robin Cover > OASIS, Director of Information Services > Editor, Cover Pages and XML Daily Newslink > Email: robin@oasis-open.org > Staff bio: http://www.oasis-open.org/people/staff/robin-cover > Cover Pages: http://xml.coverpages.org/ > Newsletter: http://xml.coverpages.org/newsletterArchive.html > Tel: +1 972-296-1783 > >> >> Several times it’s been hard to get information for the KMIP Usage Guide >> created, once a proposal for the KMIP Specification has been balloted and >> approved. So in order to ensure that we have all the information relevant to >> both the KMIP Specification and the KMIP Usage Guide at the time we vote to >> include new functionality in KMIP, TC members have suggested that the TC >> vote to require that any proposal for changes to the KMIP Specification must >> also, at the time of ballot, include any new material for the Usage Guide. >> >> It’s not clear yet whether we want to do this. But if we do, is this a >> change to TC standing rules, as defined in section 2.9 of the TC process? Is >> there anything special we need to do, in that case? >> >> >> >> Thanks! >> >> >> >> Bob > > |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]