RE: [emergency-cap] Proposal on versioning the CAP Terms committee note

[<elysajones@yahoo.com>]

Sounds like a good proposal for the Committee Note. Elysa

 

From: Scott M. Robertson <Scott.M.Robertson@kp.org>
Sent: Saturday, August 8, 2020 9:39 PM
To: elysajones@yahoo.com
Cc: emergency-cap@lists.oasis-open.org; Chet Ensign <chet.ensign@oasis-open.org>
Subject: Re: [emergency-cap] Proposal on versioning the CAP Terms committee note

 

Yes, any new version, even minor version number, will require review and ballot. My proposal is to use minor version numbers to indicate term list updates (and non substantive edits) and major versions to indicate significant changes to the document. And to have those minor updates to go on a schedule, something like yearly (if there have been term updates). 

Scott M Robertson PharmD, RPh, FHL7, GISP, CISSP

Kaiser Permanente 

Technology Risk Office | Health IT Strategy & Policy

On Aug 8, 2020, at 8:24 AM, "elysajones@yahoo.com" <elysajones@yahoo.com> wrote:

ï

Caution: This email came from outside Kaiser Permanente. Do not open attachments or click on links if you do not recognize the sender.

---

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: emergency-cap@lists.oasis-open.org <emergency-cap@lists.oasis-open.org> On Behalf Of Scott M. Robertson
Sent: Friday, August 7, 2020 12:54 PM
To: emergency-cap@lists.oasis-open.org
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.

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.