Sure. The steps to do that are explained here ->
https://www.oasis-open.org/resources/tcadmin/approving-a-committee-specification-or-note-draft-with-non-material-changes Here are the key steps: - Use cs01, your last approved publication, to produce a new working draft that incorporate the non-material changes. Keep a log of the changes that you make (a red-lined version of the spec works fine for that purpose). - Pass a motion to request that a Special Majority Vote be held to approve that working draft as a Committee Specification. The specific wording you can use should be in the instructions. - Then I hold the Special Majority Vote and, because it is being done with Non-Material Changes, alert the OASIS membership of the vote. So long as no one objects to the changes being deemed non-material - and no one ever has - once the ballot passes, I publish your CS02. Have a look at the instructions and let me know if you have questions on any of it. /chet On Thu, Dec 18, 2014 at 8:32 AM, Michael S. Tsirkin <
mst@redhat.com > wrote: OK, but it seems that if only non-material changes have been made since the last public review, then we don't need to do another public review? Formally speaking: If only Non-Material Changes are made to the draft after the public review, whether as a result of public review comments or from TC Member input, then the TC may proceed with the approval as a Committee Specification in accordance with Section 3.3 without conducting another public review cycle. Specifically, we would like to put up a draft for v1.0-cs02, with only non-material changes as compared to the latest draft v1.0-csprd01 that went through public review, then request a Special Majority Vote for the advancement of that draft as a Committee Specification. Informally speaking, we are talking about correcting some typos and making minor editorial changes. It seems a waste to do a public review just for that. Pls let us know. On Wed, Dec 10, 2014 at 07:11:54AM -0500, Chet Ensign wrote: > Hi Michael, > > Well, you can't really publish an errata yet. Virtio V1.0 is a Committee > Specification and errata can only be published for OASIS Standards. Rather, the > approach you need to take is to prepare a new working draft and treat it as a > new Committee Specification Draft. After public review, it is then approved by > the TC as Committee Specification 02. > > /chet > > > On Wed, Dec 10, 2014 at 1:20 AM, Michael S. Tsirkin <
mst@redhat.com > wrote: > > Hi Chet, > I started preparing errata for virtio 1.0. > > What's the proper format for latest version > and for citation format sections for errata > documents? > > Thanks, > > -- > MST > > > > > -- > > /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 > > Check your work using the Support Request Submission Checklist at http:// >
www.oasis-open.org/committees/download.php/47248/ > tc-admin-submission-checklist.html > > 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 -- /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 Check your work using the Support Request Submission Checklist at
http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 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