Once it if âfully qualifiedâ, nothing wrong with OPENC2-CAP
Or an actuator could be declared to be an Axtuator
CAXP
From: Dave Lemire <dave.lemire@g2-inc.com>
Sent: Wednesday, April 17, 2019 2:21 PM
To: Considine, Toby <Toby.Considine@unc.edu>
Cc: Chet Ensign <chet.ensign@oasis-open.org>; OASIS OpenC2 List <openc2@lists.oasis-open.org>
Subject: Re: [openc2] openc2-cap repository proposal
I played with some names, starting from
Custom Actuator Profiles
-
CuAP (Joe's suggestion)
-
CAPro (sounds too much like Bass Pro)
-
CActP (makes me think of cactus)
-
CustomAPs (highly readable)
Most of our open repo names are on the longer side anyway (e.g., lycan-python) and I don't see much benefit to emphasizing concise here, so I like the last one best: openc2-customaps. If having
it run together is confusing it could be openc2-custom-aps.
+1
CAP is a very well socialized acronym, and I fear distributing an OPenC2 CAP message inside a CAP alert encoded in EDXLâto respond to a Physical Emergency caused by a CyberAttack
From:
openc2@lists.oasis-open.org <openc2@lists.oasis-open.org>
On Behalf Of Chet Ensign
Sent: Wednesday, April 17, 2019 12:56 PM
To: Dave Lemire <dave.lemire@g2-inc.com>
Cc: OASIS OpenC2 List <openc2@lists.oasis-open.org>
Subject: Re: [openc2] openc2-cap repository proposal
Hey Dave, I just saw this. One thing that occurs to me is the potential for confusion around the name.
CAP is an OASIS Standard - Common Alerting Protocol (https://www.oasis-open.org/standards#capv1.2). The
CAP standard is widely deployed in emergency communication systems around the globe for all manner of disaster: tsunamis, earthquakes, hurricanes, tornados. floods. For people outside our community, seeing CAP already comes with a lot of meaning to it. (And
in case anybody thinks that the differences are obvious, I just spent 20 minutes yesterday explaining why a potential legal markup project had nothing to do with CAP's sibling EDXL (Emergency Data Exchange Language).
I would like to avoid muddying the meaning of CAP if possible by using a different acronym. Maybe cucp or cacp or capro? I'm sure you all can find a far more elegant solution than
that!
For convenience, here's a copy of the proposal to create an open repo for Custom Actuator Profiles (openc2-cap). As Joe Brule stated
at this morning's TC meeting session, the window to register objections is open until 10:00pm EDT tonight.
David P. Lemire, CISSP
HII Mission Driven Innovative Solutions (HII-MDIS, formerly G2, Inc.)
Technical Solutions (A Division of Huntington Ingalls Industries)
OpenC2 Technical Committee Secretary
OpenC2 Implementation Considerations SC Co-chair
Contractor support to NSA
Email: dave.lemire@g2-inc.com
Work (301)
575-5190
| Mobile
(240)
938-9350
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
--
Chief Technical Community Steward
OASIS: Advancing open standards for the information society
http://www.oasis-open.org
Primary: +1 973-996-2298
Mobile: +1 201-341-1393
|