OASIS Open Command and Control (OpenC2) TC

To the TC Admins:   This is my first Errata, so I apologize in advance for any missteps. The OpenC2 Language Specification Subcommittee is proposing that WD15 ( https://www.oasis-open.org/apps/org/workgroup/openc2/download.php/66144/openc2-oc2ls-wd15.zip ) be approved as an errata. The package includes a MD file including the proposed change, a PDF with line numbers produced from that PDF, a PDF file showing the changes, and an HTML file produced from the MD. After consulting with the Subcommitee, and following direction of the Co-Chairs of the TC and all Sub-Committees meeting en banc, we wish to initiate the voting process. To that end: 1) We wish to adopt WD15 as a CSD. Please initiate a vote to adopt as a Committee Specification Draft with a goal of production OpenC2 Language Specification v1.0 Errata 1. 2) Please Initiate a Full Majority Vote that the proposed corrections do not constitute a Material Change. 3) The vote further directs that as soon as practicable following that vote, that WD15 be released for public review of the errata as per the TC process. If Errata extend the artifact naming, this will be CSPRD04. If Errata have a different naming process, please name it as required and adjust the vote accordingly. It is the intent of the TC to move forward as rapidly as possible to final vote on the Errata. Please let me know if there is a step I have missed or of we can further consolidate the process. If there is a form for submitting such a request, please let me know quickly and I will fill it out.   Thanks   Toby Considine Co-Chair, OpenC2 Language Subcommittee 

Hi Toby, I started doing this long reply with the steps needed and then realized that we are talking about a Committee Specification, not an OASIS Standard. Errata can only be done on OASIS Standards. You don't need them for CS because you can simply approve a new, updated CSPRD followed by a CS vote. So all you need to do is request the public review for WD15 using https://www.oasis-open.org/resources/tc-admin-requests/15-day-committee-specification-draft-public-review-request and we'll get it prepped and out the door. It should be a quick turnaround. Let me know if you have any questions - /chet On Fri, Nov 8, 2019 at 8:06 AM Considine, Toby < Toby.Considine@unc.edu > wrote: To the TC Admins: This is my first Errata, so I apologize in advance for any missteps. The OpenC2 Language Specification Subcommittee is proposing that WD15 ( https://www.oasis-open.org/apps/org/workgroup/openc2/download.php/66144/openc2-oc2ls-wd15.zip ) be approved as an errata. The package includes a MD file including the proposed change, a PDF with line numbers produced from that PDF, a PDF file showing the changes, and an HTML file produced from the MD. After consulting with the Subcommitee, and following direction of the Co-Chairs of the TC and all Sub-Committees meeting en banc, we wish to initiate the voting process. To that end: 1) We wish to adopt WD15 as a CSD. Please initiate a vote to adopt as a Committee Specification Draft with a goal of production OpenC2 Language Specification v1.0 Errata 1. 2) Please Initiate a Full Majority Vote that the proposed corrections do not constitute a Material Change. 3) The vote further directs that as soon as practicable following that vote, that WD15 be released for public review of the errata as per the TC process. If Errata extend the artifact naming, this will be CSPRD04. If Errata have a different naming process, please name it as required and adjust the vote accordingly. It is the intent of the TC to move forward as rapidly as possible to final vote on the Errata. Please let me know if there is a step I have missed or of we can further consolidate the process. If there is a form for submitting such a request, please let me know quickly and I will fill it out. Thanks Toby Considine Co-Chair, OpenC2 Language Subcommittee -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

Well, I feel sheepish: read the errata process description but never caught the "OASIS Standard" part of the introduction. My bad. To be clear: Do we need a TC vote to approve the CSPRD before the 15-day review? And, assuming approval, no comments, how do we version the corrected product? Toby's described "CS 01 of Language Spec v1.0" -- is that the right phrasing? Dave David Lemire, CISSP Systems Engineer HII Mission Driven Innovative Solutions (HII-MDIS) formerly G2, Inc. Technical Solutions Division 302 Sentinel Drive Annapolis Junction, MD 20701 Email: dave.lemire@g2-inc.com Work: 301-575-5190 Mobile: 240-938-9350 On Fri, Nov 8, 2019 at 9:43 AM Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi Toby, I started doing this long reply with the steps needed and then realized that we are talking about a Committee Specification, not an OASIS Standard. Errata can only be done on OASIS Standards. You don't need them for CS because you can simply approve a new, updated CSPRD followed by a CS vote. So all you need to do is request the public review for WD15 using https://www.oasis-open.org/resources/tc-admin-requests/15-day-committee-specification-draft-public-review-request and we'll get it prepped and out the door. It should be a quick turnaround. Let me know if you have any questions - /chet On Fri, Nov 8, 2019 at 8:06 AM Considine, Toby < Toby.Considine@unc.edu > wrote: To the TC Admins: This is my first Errata, so I apologize in advance for any missteps. The OpenC2 Language Specification Subcommittee is proposing that WD15 ( https://www.oasis-open.org/apps/org/workgroup/openc2/download.php/66144/openc2-oc2ls-wd15.zip ) be approved as an errata. The package includes a MD file including the proposed change, a PDF with line numbers produced from that PDF, a PDF file showing the changes, and an HTML file produced from the MD. After consulting with the Subcommitee, and following direction of the Co-Chairs of the TC and all Sub-Committees meeting en banc, we wish to initiate the voting process. To that end: 1) We wish to adopt WD15 as a CSD. Please initiate a vote to adopt as a Committee Specification Draft with a goal of production OpenC2 Language Specification v1.0 Errata 1. 2) Please Initiate a Full Majority Vote that the proposed corrections do not constitute a Material Change. 3) The vote further directs that as soon as practicable following that vote, that WD15 be released for public review of the errata as per the TC process. If Errata extend the artifact naming, this will be CSPRD04. If Errata have a different naming process, please name it as required and adjust the vote accordingly. It is the intent of the TC to move forward as rapidly as possible to final vote on the Errata. Please let me know if there is a step I have missed or of we can further consolidate the process. If there is a form for submitting such a request, please let me know quickly and I will fill it out. Thanks Toby Considine Co-Chair, OpenC2 Language Subcommittee -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

Hi Dave - Hey, no problem. This has come up before. Actually, I think this has an easier solution. I just ran over the delta PDF. The number of changes is small. I am fine with the TC using that delta PDF as the change log and requesting a Special Majority Vote to approve a working draft with non-material changes as a Committee Specification. I suggest you get approval of a motion like this: I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve OpenC2 Language Specification v1.0 WD15 contained in ( https://www.oasis-open.org/apps/org/workgroup/openc2/download.php/66144/openc2-oc2ls-wd15.zip ) 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 openc2-oc2ls-cs01-wd15-delta.pdf in the ZIP file, 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 run the Special Majority Vote and you then will have OpenC2 Language Specification v1.0 Committee Specification 02. In other words, no public review required. Does that work? /chet On Fri, Nov 8, 2019 at 10:00 AM Dave Lemire < dave.lemire@g2-inc.com > wrote: Well, I feel sheepish: read the errata process description but never caught the "OASIS Standard" part of the introduction. My bad. To be clear: Do we need a TC vote to approve the CSPRD before the 15-day review? And, assuming approval, no comments, how do we version the corrected product? Toby's described "CS 01 of Language Spec v1.0" -- is that the right phrasing? Dave David Lemire, CISSP Systems Engineer HII Mission Driven Innovative Solutions (HII-MDIS) formerly G2, Inc. Technical Solutions Division 302 Sentinel Drive Annapolis Junction, MD 20701 Email: dave.lemire@g2-inc.com Work: 301-575-5190 Mobile: 240-938-9350 On Fri, Nov 8, 2019 at 9:43 AM Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi Toby, I started doing this long reply with the steps needed and then realized that we are talking about a Committee Specification, not an OASIS Standard. Errata can only be done on OASIS Standards. You don't need them for CS because you can simply approve a new, updated CSPRD followed by a CS vote. So all you need to do is request the public review for WD15 using https://www.oasis-open.org/resources/tc-admin-requests/15-day-committee-specification-draft-public-review-request and we'll get it prepped and out the door. It should be a quick turnaround. Let me know if you have any questions - /chet On Fri, Nov 8, 2019 at 8:06 AM Considine, Toby < Toby.Considine@unc.edu > wrote: To the TC Admins: This is my first Errata, so I apologize in advance for any missteps. The OpenC2 Language Specification Subcommittee is proposing that WD15 ( https://www.oasis-open.org/apps/org/workgroup/openc2/download.php/66144/openc2-oc2ls-wd15.zip ) be approved as an errata. The package includes a MD file including the proposed change, a PDF with line numbers produced from that PDF, a PDF file showing the changes, and an HTML file produced from the MD. After consulting with the Subcommitee, and following direction of the Co-Chairs of the TC and all Sub-Committees meeting en banc, we wish to initiate the voting process. To that end: 1) We wish to adopt WD15 as a CSD. Please initiate a vote to adopt as a Committee Specification Draft with a goal of production OpenC2 Language Specification v1.0 Errata 1. 2) Please Initiate a Full Majority Vote that the proposed corrections do not constitute a Material Change. 3) The vote further directs that as soon as practicable following that vote, that WD15 be released for public review of the errata as per the TC process. If Errata extend the artifact naming, this will be CSPRD04. If Errata have a different naming process, please name it as required and adjust the vote accordingly. It is the intent of the TC to move forward as rapidly as possible to final vote on the Errata. Please let me know if there is a step I have missed or of we can further consolidate the process. If there is a form for submitting such a request, please let me know quickly and I will fill it out. Thanks Toby Considine Co-Chair, OpenC2 Language Subcommittee -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393

I'm quite sure that if we can approve this document w/o a public review that will make many people happy. We've got a TC meeting on the 20th, so we should be able to approve that resolution then and move to the Special Majority Vote. Dave David Lemire, CISSP Systems Engineer HII Mission Driven Innovative Solutions (HII-MDIS) formerly G2, Inc. Technical Solutions Division 302 Sentinel Drive Annapolis Junction, MD 20701 Email: dave.lemire@g2-inc.com Work: 301-575-5190 Mobile: 240-938-9350 On Fri, Nov 8, 2019 at 10:31 AM Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi Dave - Hey, no problem. This has come up before. Actually, I think this has an easier solution. I just ran over the delta PDF. The number of changes is small. I am fine with the TC using that delta PDF as the change log and requesting a Special Majority Vote to approve a working draft with non-material changes as a Committee Specification. I suggest you get approval of a motion like this: I move to approve the Chair requesting that TC Administration hold a Special Majority Vote to approve OpenC2 Language Specification v1.0 WD15 contained in ( https://www.oasis-open.org/apps/org/workgroup/openc2/download.php/66144/openc2-oc2ls-wd15.zip ) 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 openc2-oc2ls-cs01-wd15-delta.pdf in the ZIP file, 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 run the Special Majority Vote and you then will have OpenC2 Language Specification v1.0 Committee Specification 02. In other words, no public review required. Does that work? /chet On Fri, Nov 8, 2019 at 10:00 AM Dave Lemire < dave.lemire@g2-inc.com > wrote: Well, I feel sheepish: read the errata process description but never caught the "OASIS Standard" part of the introduction. My bad. To be clear: Do we need a TC vote to approve the CSPRD before the 15-day review? And, assuming approval, no comments, how do we version the corrected product? Toby's described "CS 01 of Language Spec v1.0" -- is that the right phrasing? Dave David Lemire, CISSP Systems Engineer HII Mission Driven Innovative Solutions (HII-MDIS) formerly G2, Inc. Technical Solutions Division 302 Sentinel Drive Annapolis Junction, MD 20701 Email: dave.lemire@g2-inc.com Work: 301-575-5190 Mobile: 240-938-9350 On Fri, Nov 8, 2019 at 9:43 AM Chet Ensign < chet.ensign@oasis-open.org > wrote: Hi Toby, I started doing this long reply with the steps needed and then realized that we are talking about a Committee Specification, not an OASIS Standard. Errata can only be done on OASIS Standards. You don't need them for CS because you can simply approve a new, updated CSPRD followed by a CS vote. So all you need to do is request the public review for WD15 using https://www.oasis-open.org/resources/tc-admin-requests/15-day-committee-specification-draft-public-review-request and we'll get it prepped and out the door. It should be a quick turnaround. Let me know if you have any questions - /chet On Fri, Nov 8, 2019 at 8:06 AM Considine, Toby < Toby.Considine@unc.edu > wrote: To the TC Admins: This is my first Errata, so I apologize in advance for any missteps. The OpenC2 Language Specification Subcommittee is proposing that WD15 ( https://www.oasis-open.org/apps/org/workgroup/openc2/download.php/66144/openc2-oc2ls-wd15.zip ) be approved as an errata. The package includes a MD file including the proposed change, a PDF with line numbers produced from that PDF, a PDF file showing the changes, and an HTML file produced from the MD. After consulting with the Subcommitee, and following direction of the Co-Chairs of the TC and all Sub-Committees meeting en banc, we wish to initiate the voting process. To that end: 1) We wish to adopt WD15 as a CSD. Please initiate a vote to adopt as a Committee Specification Draft with a goal of production OpenC2 Language Specification v1.0 Errata 1. 2) Please Initiate a Full Majority Vote that the proposed corrections do not constitute a Material Change. 3) The vote further directs that as soon as practicable following that vote, that WD15 be released for public review of the errata as per the TC process. If Errata extend the artifact naming, this will be CSPRD04. If Errata have a different naming process, please name it as required and adjust the vote accordingly. It is the intent of the TC to move forward as rapidly as possible to final vote on the Errata. Please let me know if there is a step I have missed or of we can further consolidate the process. If there is a form for submitting such a request, please let me know quickly and I will fill it out. Thanks Toby Considine Co-Chair, OpenC2 Language Subcommittee -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393 -- /chet ---------------- Chet Ensign Chief Technical Community Steward OASIS: Advancing open source & open standards for the information society http://www.oasis-open.org Mobile: +1 201-341-1393