OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [soa-rm] Second Public Review`

Hi Duane,
Thanks for the doccos. Will get back to you soon if there are any issues.
----- Original Message -----
Sent: Saturday, June 03, 2006 5:40 AM
Subject: [soa-rm] Second Public Review`



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:



The minutes carrying the motion approved by full majority vote are located here:



Please let Frank, Matt and I know if you require anything further.




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:ram.kumar@oasis-open.org]
Sent: Thursday, May 18, 2006 12:26 PM
To: Duane Nickull; Michael Stiefel; soa-rm@lists.oasis-open.org
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.








----- Original Message -----

From: "Duane Nickull" <dnickull@adobe.com>

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.


Adobe Systems, Inc. -
Adobe Developer Program - http://developer.adobe.com/
Chair - OASIS SOA Reference Model Technical Committee
Personal Blog -

-----Original Message-----
From: Michael Stiefel [mailto:development@reliablesoftware.com]
Sent: Wednesday, May 17, 2006 3:18 PM
Subject: [soa-rm] Approval Process For Specification

As per my assignment from today's meeting, here is the reply I got from

The TC must track the comments received as well as the disposition of
comment. The TC may conduct any number of review cycles (i.e. approval
send a Committee Draft to Public Review, collecting comments, making
to the specification, etc.). The first public review of a specification
must take place for a minimum of 60 days, and any subsequent reviews
be held for a minimum of 15 days. Changes made to a specification after
review must be clearly identified in any subsequent review, and the
subsequent review shall be limited in scope to changes made in the
review. Before starting another review cycle the specification must be
re-approved as a Committee Draft and then approved to go to public
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
then the TC must conduct another review cycle. The specification may not
considered for approval by the TC as a Committee Specification until it
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
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
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.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]