RE: [soa-rm] Approval Process For Specification

["Duane Nickull" <dnickull@adobe.com>]

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:development@reliablesoftware.com] 
Sent: Wednesday, May 17, 2006 3:18 PM
To: soa-rm@lists.oasis-open.org
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.