Just talked to Paul and thought this through a bit more. He is going to go ahead and fix the CS01. What is published now is not what the TC voted to approve so it is up to us to remedy that. Paul will get right on that.On Fri, Mar 2, 2018 at 10:12 AM, Chet Ensign <chet.ensign@oasis-open.org> wrote:Hi David,I'm copying Paul to make sure we properly untangle this.Looking at the ballot to approve the CS (https://www.oasis-open.org/apps/org/workgroup/coel/ballot. ), I see that it approved [1] URI for the specification https://www.oasis-open.org/comphp?id=3175 mittees/download.php/62533/COE " for the CS. Paul, it looks like David is correct: I see in the notes that you used the CSPRD02 to create the CS.L-v1.0-wd03.docx So it looks like this is indeed our mistake and we'll need to fix it.If the TC is going to approve a new working draft with new non-material changes, we'll treat that as CS02.David, do you want us to go ahead and correct the current CS01 using the proper source file? Or do you just want us to leave it as is and process the new one?Also, where do you all publish the minutes of the TC meetings? I went looking for the minutes of the previous meeting and I can't find any sign of minutes in either your email archive or your document repository.To avoid this kind of confusion in the next one, please use motion language like this in the meeting and in the minutes:]I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve <Working Draft title, version number and working draft number> contained in <URL for the revised draft in Kavi> as a Committee Specification. I further move that the TC affirm that changes have been made since the last public review, that the changes made are documented in <URL for the summary of changes> and that the TC judges these changes to be Non-Material in accordance with the definition in the OASIS TC Process (http://www.oasis-open.org/policies-guidelines/tc-process# ).dNonmaterialChange I don't know how I did this with this last approval but with this motion in your minutes, there is no chance that we will publish the wrong files. The URL to the working draft in the motion is then the file that we pick up and publish. Also, it is how I connect the dots after the fact for anyone who wants to know how we got that approved and published work.Thanks,/chet--On Fri, Mar 2, 2018 at 9:35 AM, dave.snelling@uk.fujitsu.com <dave.snelling@uk.fujitsu.com> wrote:Chet,
I’m sorry about this, but we are going to need to run some of the gauntlet again.
As a result of the missing lines in tables, we took a closer look and it seems that Paul used the PR version for creating the CS version rather than the updated WD version with non-substantive changed in it. So he needs to run the process again.
However, NOT YET!
Our closer look has revealed a few more non-substantive changes required. So we will affect those next week and request another ballot from you about this time next week. Sorry about this, we don’t want to make extra work, but we also want it as right as it can be.
Dr. David Snelling
Fujitsu Distinguished Engineer
Program Director Artificial Intelligence
CTO Office EMEIAFujitsu
Mob: +44 (0) 7590-293439
Email: Dave.Snelling@UK.Fujitsu.com
Web: uk.fujitsu.com
Fujitsu is proud to partner with Action for Children
P Please consider the environment - do you really need to print this email?
Unless otherwise stated, this email has been sent from Fujitsu Services Limited (registered in England No 96056); Fujitsu EMEA PLC (registered in England No 2216100) both with registered offices at: 22 Baker Street, London W1U 3BW; PFU (EMEA) Limited, (registered in England No 1578652) and Fujitsu Laboratories of Europe Limited (registered in England No. 4153469) both with registered offices at: Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE.
This email is only for the use of its intended recipient. Its contents are subject to a duty of confidence and may be privileged. Fujitsu does not guarantee that this email has not been intercepted and amended or that it is virus-free.
/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--
/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
OASIS - Advancing open standards for the information society - Document Process Analyst