emergency-cap — archive

Proposal on versioning the CAP Terms committee note

From: Chet Ensign <[email protected]>
To: [email protected]
Date: Sat, 08 Aug 2020 18:08:00 -0000

Hi Elysa, Scott, Rex - Your version numbering isn't what triggers a public review. When to do a public review is up to the TC keeping in mind that you have to do public review(s) before you can vote to approve a CSD as a Committee Specification. In other words, if you do v1.0, 1.1, 1.x ... but you just leave those as local copies of your working draft, that is no problem. Let's say you publish v1.5 and the TC feels that this is mature and ready for approval. It then will need to go through public review before you can request the Special Majority Vote to approve the CS. If you don't make that threshold until v2.0, that's fine too. You would eventually end up with CAP Events Terms v2.0 Committee Specification 01. Does that explain it clearly? /chet On Sat, Aug 8, 2020 at 11:24 AM < [email protected] > wrote: Scott, I may be wrong but I think if we roll a version number it has to go through public review. Rex may know for sure of TC Admin can advise. I think after we publish, we will track changes in the revision history with working drafts until we are ready for a PR and new version. I ve copied Chet on this for his insight. Thanks, Elysa From: [email protected] < [email protected] > On Behalf Of Scott M. Robertson Sent: Friday, August 7, 2020 12:54 PM To: [email protected] Subject: [emergency-cap] Proposal on versioning the CAP Terms committee note Unless OASIS policy doesn t allow this Regarding versioning of the CAP Terms committee not for updates to the CAP Event Terms List: what if we use minor numbers (to the right of the decimal point) for List (and editorial) updates, and major revision numbers for document content changes? Initial publication v1.0 First List update v1.1 List update and some editorial fixes v1.2 V1.3 v1.n Substantive content update v2.0 Just a thought Scott M Robertson PharmD, RPh, FHL7, GISP, CISSP Principal Technology Consultant Kaiser Permanente Technology Risk Office Health IT Strategy & Policy 310-200-0231 tro.kp.org ---------- kp.org/thrive NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, you are prohibited from sharing, copying, or otherwise using or disclosing its contents. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and permanently delete this e-mail and any attachments without reading, forwarding or saving them. Thank you. -- /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