This week's TC meeting voted to adopt the proposed standing rules from the new OASIS Document Life Cycle Best Practices and the TC's page at OASIS has been updated accordingly (added as SRs 7-9). The TC's previous and new standing rules can be viewed there.
For work product editors, the adoption of SR-7 has implications for how CSDs are numbered as discussed where the standing rule is described in the best practices document and illustrated in appendix B.2. Essentially, things are vastly simplified and after the TC's initial Full Majority Vote to approve CSD01 for a specific work product version, an editor can declare subsequent CSDs by uploading a document package to the TC's document store with the CSD number in the package name <document name> - <version> - CSD##. OASIS publication of a CSD still requires submission of a Publish A Draft Work request (the TC Secretary can assist if needed).
------------------------------
David Lemire, CISSP
HII / National Security Agency
OpenC2 TC Secretary
david.p.lemire@hii.com------------------------------