RE: Major Milestone - RM for SOA is now at Committee Specification Status

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

Ram:

Our editors should have the final documents in the vault this week so
you can set up the special vote for CS status.  I will ping you when
they have it ready.

Thanks

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: Ram Kumar [mailto:ram.kumar@oasis-open.org] 
Sent: Thursday, June 29, 2006 1:08 PM
To: Duane Nickull
Subject: Re: Major Milestone - RM for SOA is now at Committee
Specification Status

Hi Duane,

I jsut read the minutes of the meeting and looks like I misunderstood
your email. Your committee has voted to go to the next stage, which is
agree to move the public review draft as a committee specs. and not
to adopt as a committee spec. vote. Extract of your minutes:
"
The TC unanimously approved to attain OASIS Committee Specification
status 
for the SOA Reference Model Public Review Draft.



Some editorial changes are required to the specification document prior
to 
submitting it to OASIS for Special Majority Vote."



My apologies for my mis-understanding of your email.



Regards,



Ram

----- Original Message ----- 
From: "Ram Kumar" <ram.kumar@oasis-open.org>
To: "Duane Nickull" <dnickull@adobe.com>
Sent: Thursday, June 29, 2006 11:09 PM
Subject: Re: Major Milestone - RM for SOA is now at Committee
Specification 
Status


> Hi Duane,
>
> What I understand from your email is that your committee
> has voted to adopt the draft spec. as a committee spec. and
> now  you want to prepare to take it to the next step, i.e. OASIS
standard.
>
> But as per the TC process, a TC can't vote on its own for Committee 
> Specification
> status but that a request must be made to the TC Administrator to run
the 
> ballot.
> You'll need to submit a link to the minutes where a motion was made
and 
> carried to
> request such a ballot, as well as links to the 3 required versions of
the 
> spec: editable source, PDF and
> HTML.
>
> Regards,
>
> Ram
>
> ----- Original Message ----- 
> From: "Duane Nickull" <dnickull@adobe.com>
> To: "SOA-RM" <soa-rm@lists.oasis-open.org>
> Cc: "Ram Kumar" <ram.kumar@oasis-open.org>; "Carol Geyer" 
> <carol.geyer@oasis-open.org>; "Jamie Clark"
<jamie.clark@oasis-open.org>
> Sent: Thursday, June 29, 2006 7:45 AM
> Subject: Major Milestone - RM for SOA is now at Committee
Specification 
> Status
>
>
> All:
>
> This is an important email for the TC.  Please take the time to read
> through it.  There are several items and questions for individuals on
> this TC within this email.
>
> Thank you in advance - Duane
>
> This morning we dealt with 4 comments received during the second and
> final public review of the Committee Draft.  Although 3 of the 4
> comments did not require a formal answer (they were on parts of the
> draft other than the scope of the comments), we decided to answer them
> all with equal weight.  The answers have not required any changes on
the
> existing draft.
>
> Editors:
>
> Please update the current Committee Public Review Draft 2.0 to reflect
> this status.
>
> - adjust the date
> - adjust the status
> - remove the red text illustrating the changes from CD PR 1 - 1.0
> - take a final read to see if there are any other objects that require
> modification (name spellings etc.)
>
> At this point, the vote has been passed by a duly made motion and the
> re-submitted draft will be scrutinized before our next regular
> conference call in 2 weeks and adopted.
>
> We have one further milestone to go if we want to become an official
> OASIS Standard.  This requires a special process described on the
OASIS
> rules and procedures page:
>
> http://www.oasis-open.org/committees/process.php#3.4
>
> In short:
> *****************************************************
>    Simultaneously with the approval of a Committee Specification or at
> a later date, a TC may resolve by Special Majority Vote to submit the
> Committee Specification to the membership of OASIS for consideration
as
> an OASIS Standard. Upon resolution of the TC to submit the
> specification, its Chair shall submit the following items to the TC
> Administrator:
>
>       1. Links to the approved Committee Specification in the TC's
> document repository, and any appropriate supplemental documentation
for
> the specification, both of which must be written using the OASIS
> templates. The specification may not have been changed between its
> approval as a Committee Specification and its submission to OASIS for
> consideration as an OASIS Standard, except for the changes on the
title
> page and running footer noting the approval status and date.
>       (Will be done by editors)
>
>       2. The editable version of all files that are part of the
> Committee Specification;
>       (Editors)
>       3. Certification by the TC that all schema and XML instances
> included in the specification, whether by inclusion or reference,
> including fragments of such, are well formed, and that all expressions
> are valid;
>       (Not relevant to us)
>       4.A clear English-language summary of the specification;
>       (Request for volunteer to write)
>
>       5. A statement regarding the relationship of this specification
> to similar work of other OASIS TCs or other standards developing
> organizations;
>       (To be taken from Spec??? Need volunteer)
>       6. Certification by at least three OASIS member organizations
> that they are successfully using the specification;
>       (Please post to the general list)
>       7. The beginning and ending dates of the public review(s), a
> pointer to the announcement of the public review(s), and a pointer to
an
> account of each of the comments/issues raised during the public review
> period(s), along with its resolution;
>        (all of this is on Kavi - Ram: please tell us if we need to do
> more)
>       8. An account of and results of the voting to approve the
> specification as a Committee Specification, including the date of the
> ballot and a pointer to the ballot;
>        (this was done during todays' meeting so the minutes can be
used
> for this)
>       9. An account of or pointer to votes and comments received in
any
> earlier attempts to standardize substantially the same specification,
> together with the originating TC's response to each comment;
>        (This is in Kavi - Ram - do we need to do more)
>      10. A pointer to the publicly visible comments archive for the
> originating TC;
>        (This pointer is already part of our public facing website)
>      11. A pointer to any minority reports submitted by one or more
> Members who did not vote in favor of approving the Committee
> Specification, which report may include statements regarding why the
> member voted against the specification or that the member believes
that
> Substantive Changes were made which have not gone through public
review;
> or certification by the Chair that no minority reports exist.
>        ( I hereby certify that no minority reports exist)
>
>    The above submission must be made by the 15th of any month to the
TC
> Administrator, who shall have until the end of the month to complete
> administrative processing and checking for completeness and
correctness
> of the submission. If the submission is incomplete it shall be
rejected
> but may be resubmitted at a later time.
>
>    No part of the submission may be changed after being submitted to
> the TC Administrator. The TC that originated the specification may
> resolve by Special Majority Vote to withdraw the proposed
specification
> at any point after it is submitted to the TC Administrator for
> administrative processing and before the start of the voting period.
>
>    Errata or Corrigenda to a Committee Specification are not permitted
> after its submission; if changes are required the Committee
> Specification must be withdrawn by the TC, edited, re-approved as a
> Committee Specification, then resubmitted.
>
>    The TC Administrator shall submit the proposal to the OASIS
> membership by the first day of the following month. The first 15 days
of
> that month shall be used by the membership to familiarize themselves
> with the submission. Voting shall start on the 16th of the month. The
> voting representatives of those organizational members of OASIS who
were
> members at the beginning of the familiarization period are eligible to
> vote, and must submit their ballots by the end of the month.
>
>    In votes upon proposed OASIS Standards, each OASIS organizational
> member shall be entitled to cast one vote. Votes shall be cast via the
> publicly archived electronic voting facility supplied by OASIS.
Ballots
> shall be publicly visible during voting and may be changed up until
the
> end of the voting period. The results of a vote on a proposed standard
> shall be provided to the membership and to the TC no later than seven
> days following the close of the voting period.
>
>    If at the end of the voting period at least 15 percent of the
voting
> membership has voted to approve the proposed standard, and if no votes
> have been cast to disapprove the proposed standard, it shall become an
> OASIS Standard immediately following the end of the voting period.
> However, if negative votes amounting to less than 15 percent of the
> voting membership have been cast, the TC shall be notified of the
> negative votes, after which the TC shall have 30 days to take one of
the
> following actions by Resolution of a Special Majority Vote: (a)
request
> the TC Administrator to approve the specification as submitted despite
> the negative votes; (b) withdraw the submission entirely; or (c)
submit
> an amended specification, in which case the amended submission shall
be
> considered as if it were a new submission, except that information
> regarding previous votes and any disposition of comments received in
> previous votes shall accompany the amended submission.
>
>    If at the end of the voting period less than 15 percent of the
> voting membership has voted to approve the proposed standard, or if at
> the end of the voting period 15 percent or more of the voting
membership
> has voted to disapprove the proposed standard, or if the originating
TC
> upon notification of negative votes takes no formal action within the
30
> days allocated for consideration of the results, then the
specification
> shall not become an OASIS Standard. This shall not prevent a later
> version of the same specification from being submitted again as
> specified in this section.
>
>    No changes may be made to the specification after approval as an
> OASIS Standard except for the changes on the title page and running
> footer noting the approval status and date.
>
>
>
>
> *******************************
> 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/
> *******************************
>
>
>
>