Thank you for the guidance for the next steps.
Our TC meets on Monday next week. I will update the Committee Specification and create a summary of the change before the TC call. Then, I will present them to the TC. Once TC agrees to move forward, which I expect, I will make a request to carry out the Special Majority vote as you suggest.
Regards,
Tom
2022/02/01 1:55ãChet Ensign <chet.ensign@oasis-open.org>ãããã:Hi Tom,Thanks for sharing this comprehensive list with the TC. You are on the right track. If this is helpful, here are the next steps:- I will use this email to create a comment resolution log that we can load with the specification.- You can proceed with preparing a new working draft of the Committee Specification with the non-material changes made. Please also create a summary of the changes made. I think you could use the brief description of the 7 changes - that is the level of detail we need.- When that is done, package the new working draft, the change summary, and any other parts of the spec in a ZIP file and load it to the TC document repository. Then assign me the task of carrying out the Special majority vote using https://www.oasis-open.org/project-administration-support-requests/form-request-a-special-majority-vote-on-submitting-a-revised-specification-to-the-call-for-consent/- I will set up the vote and run it. After it passes, I will then take the steps to load the revised CS to the docs.oasis-open.org file server and the set up the Call for consent by the OASIS members.Again, you're doing a great job here. Thanks and don't hesitate to ask any questions./chetOn Mon, Jan 31, 2022 at 3:42 AM Tsutomu Kamimura <tomkamimura@icloud.com> wrote:PROMCODE TC members,The public review of PROMCODE specification CS02 was conducted from November 30, 2021 to January 29, 2022. Here is a summary. of commentsFirst, no external comments were received during the review period.TC members did one more review of the specification document and posted their comments to the TC mailing list. Here is a list of links to the posting.In addition to these comments, Andrew Berezovskyi pointed out the inconsistency of document stages between promcode-spec.html and promcode-shapes.ttl.All the comments received are of editorial nature and do not affect the specification including the basic model and resource definitions. Here are brief description of each.1. The comments are to update the editors' affiliation and e- mail address and adding acknowledge statements to Prof. Aoyama as well as to Nanzan University.2. The comment is to add Kobayashi-san of NEC to the list of TC members in Appendix B.3. Miss spells and typos in promcode-shapes.html4. Grammatical error and typos in Chapters 5 and 7 of promcode-spec.html5 Editorial comments on formatting and some wording in Chapter 4 of promcode-spec.html . Also a comment on reference to project management standard PMBOK. The current reference is to Edition 5 which is outdated and subsumed by the latest Edition 7. So, the reference needs to be updated.6. Editorial comments on miss spells and misplaced sentences in promcode-vocab.html7. Inconsistency of stages between promode-spec.html and promcode-shapes.ttl. Both should be CS02. The same for promcode-vocab.html and promcode-vocab.ttlââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââI will revise the committee specification documents to accommodate all the comments. We will decide next actions at our next TC meeting on February 7, 2022.T. Kamimura--
Chet Ensign
Chief Technical Community StewardOASIS Open
+1 201-341-1393
chet.ensign@oasis-open.org
www.oasis-open.org