Re: New Rules & WS-Calendar

Yes, under the newly approved changes, the TC can move to start the ballot to approve WS-Calendar SOAP-based Services Version 1.0 with non-material changes. I thought I had a few days to write up how this will work in practice but apparently the window was even smaller than I thought. But that's good - just proves this change was needed.

Here is how to proceed:

1. The usual practice - prepare the working draft to be approved, load it to Kavi, note the link, etc. - with this one added step: prepare a record of the change(s) and include it in the zip file with the draft. The easiest way to do this may be to simply create a diff between the updated working draft and the last CSPRD. Alternatively, if it is just a single sentence, you can create a change log text file with a title like "ws-calendar-soap-wd10-changelog.zip" and in it state that on line number so and so the following sentence was added "xxx yyy zzz." The key thing here is that there be a record that anyone can look at, compare back to the working draft, and confirm for themselves that the change is non-material.

2. Approve as usual with the addition of text indicating that the TC affirms that the changes since the last public review are non-material. Let's go with language like:

"MOTION: Move to direct the Chair to request that the TC Administrator start a Committee Specification Ballot for the TC work product WS-Calendar SOAP-based Services Version 1.0 as linked to and described at <kavi file link> including the non-material changes made to the work product since the last public review documented in <filename>.

The Chairs are further directed to affirm that the changes are non-material and to perform any necessary actions as required by the OASIS TC Process and TC administrator to complete that action, per Section 3.3 of the OASIS TC Process."

3. Enter the CS ballot ticket for me at https://www.oasis-open.org/resources/tc-admin-requests/committee-specification-ballot-request . In the Notes box at the bottom, just note that non-material changes are included so I watch out for that.

4. I will then start the approval ballot. The ballot will also be announced to members@ mailing list with the change record attached. Should anyone come back and say "hey, that change isn't non-material" then you will have to go back and do the public review. Assuming no one does - and frankly, from what I've seen this past year, it is unlikely that anyone is going to object to simple doc fixes - once the ballot closes, we'll go forward from there.

So a little bit of additional text to save a public review.

I will close the PR ticket since it obviously wont' be needed. Let me know if you have any questions. This will be a good thing to show that on day 1 this saved a TC an unnecessary public review.

Make the motion to approve the draft as a Committee Specification *with non-material changes.*

On Tue, Jul 31, 2012 at 4:38 PM, Toby Considine <Toby.Considine@gmail.com> wrote:

The sole change to SOAP was a single sentence that is meaningless in SOAP but that was part of REST.

Under the new rules, can we ballot sending the updated CSD for SOAP directly to Committee Specification? If we wait until tomorrow?

(Note to TC members, as of August 1, trivial editorial changes do not necessarily require another public review)

Thanks

tc

"You can cut all the flowers but you cannot keep spring from coming."
-Pablo Neruda.

Toby Considine
TC9, Inc
TC Chair: oBIX & WS-Calendar
TC Editor: EMIX, EnergyInterop
U.S. National Inst. of Standards and Tech. Smart Grid Architecture Committee

Email: Toby.Considine@gmail.com
Phone: (919)619-2104
http://www.tcnine.com/
blog: www.NewDaedalus.com

--

/chet
----------------
Chet Ensign
Director of Standards Development and TC Administration
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn: http://linkd.in/OASISopen
Twitter: http://twitter.com/OASISopen
Facebook: http://facebook.com/oasis.open

ws-calendar message