Next in thread →
Next in month →
Re: [soa-rm] Second Public Review`
Hi Duane, Thanks for the doccos. Will get back to you soon if there are any issues. Regards, Ram ----- Original Message ----- From: Duane Nickull To: Ram Kumar ; SOA-RM Cc: ; Matt MacKenzie Sent: Saturday, June 03, 2006 5:40 AM Subject: [soa-rm] Second Public Review` Ram: Please let this be the official notification that our TC has voted to move to a second Public review to allow comments on the sections of the Public Review Draft changed as a result of comments received during the first public review. We understand that the term is for 15 days and unless otherwise notified, the TC would like to commence this immediately. The drafts are here: PDF - http://www.oasis-open.org/apps/org/workgroup/soa-rm/download.php/18486/pr-2changes.pdf DOC - http://www.oasis-open.org/apps/org/workgroup/soa-rm/download.php/18487/wd-soa-rm-pr2.doc Zipped HTML - http://www.oasis-open.org/apps/org/workgroup/soa-rm/download.php/18488/soa-rm-pr2.html.zip The issues list showing all comments received during the first public review and their disposition is located here: http://www.oasis-open.org/apps/org/workgroup/soa-rm/download.php/18489/IssuesListComments-10.xls The minutes carrying the motion approved by full majority vote are located here: http://www.oasis-open.org/apps/org/workgroup/soa-rm/download.php/18484/SOA-RM%20Minutes-May-31-2006.doc Please let Frank, Matt and I know if you require anything further. Duane ******************************* Adobe Systems, Inc. - http://www.adobe.com Adobe Developer Program - http://developer.adobe.com/ Chair - OASIS SOA Reference Model Technical Committee Personal Blog - http://technoracle.blogspot.com/ ******************************* From: Ram Kumar [mailto:] Sent: Thursday, May 18, 2006 12:26 PM To: Duane Nickull; Michael Stiefel; Subject: Re: [soa-rm] Approval Process For Specification Hi Duane, To answer Michael's last/latest email asking specifically about the format to log comments, most TCs use a spreadsheet - that's the easiest. But some use word also. They list the date of the comment, who it was from, the general description, a link to the actual comment message, and then the disposition status. The Chair has to include a link to the comment log in their submission for OASIS Standard balloting and it will be included it in the submission announcement. If you need some sample of some comment log, let me know. Hope this helps. Thanks Regards, Ram ----- Original Message ----- From: "Duane Nickull" <> To: "Michael Stiefel" <>; <> Sent: Friday, May 19, 2006 3:29 AM Subject: RE: [soa-rm] Approval Process For Specification He just cut and pasted from the website which doesn't answer the specific questions we need. We require the details of what format the changes are noted in. I guess we can just submit the comment log unless notified otherwise. One thing we have to do is to re-approve it as a Committee Draft by majority vote. I will set up the vote for a period of 7 days via internet once the final draft has been delivered to the committee. Duane ******************************* Adobe Systems, Inc. - http://www.adobe.com Adobe Developer Program - http://developer.adobe.com/ Chair - OASIS SOA Reference Model Technical Committee Personal Blog - http://technoracle.blogspot.com/ ******************************* -----Original Message----- From: Michael Stiefel [mailto:] Sent: Wednesday, May 17, 2006 3:18 PM To: Subject: [soa-rm] Approval Process For Specification As per my assignment from today's meeting, here is the reply I got from Ram Kumar: The TC must track the comments received as well as the disposition of each comment. The TC may conduct any number of review cycles (i.e. approval to send a Committee Draft to Public Review, collecting comments, making edits to the specification, etc.). The first public review of a specification must take place for a minimum of 60 days, and any subsequent reviews must be held for a minimum of 15 days. Changes made to a specification 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 specification must be re-approved as a Committee Draft and then approved to go to public review by the TC. If Substantive Changes are made to the specification after the public review, whether as a result of public review comments or from Member input, then the TC must conduct another review cycle. The specification may not be considered for approval by the TC as a Committee Specification until it has undergone a review cycle during which it has received no comments that result in Substantive Changes to the specification. Approval of a Committee Specification After the public review of a Public Review Draft the TC may approve the specification as a Committee Specification. The approval of a Committee Specification shall require a Special Majority Vote (at least two thirds of the Voting Members vote "yes" and no more than one fourth of the Voting Members vote "no". These numbers are based on the total number of Voting Members, regardless of the number of Voting Members present in the meeting. Abstentions are not counted.) . The TC Chair shall notify the TC Administrator that the TC is ready to vote on the approval of the specification, and provide to the TC Administrator the location of the editable versions of the specification files. The TC Administrator shall set up and conduct the ballot to approve the Committee Specification.
Next in thread →
Next in month →