[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency-cap-profiles] CAP Profile SC - Statement ofPurpose_GT suggestions [SEC=UNCLASSIFIED]
|
UNCLASSIFIED I agree with Patti’s thread
here. In Australia, CAP is already in use with Government Agencies to
communicate all-hazard alerting messages to other agencies (ie they never
distribute CAP messages to the public), so the intent for the SC should be more
generically focused. I would also suggest inserting the
term “all-hazard” to replace “public” in order to be
more explicit that this SC is focused on producing Profiles for all hazards,
not just alerting for weather-related events. My suggested revision:
Subcommittee formed to review CAP requirements for all-hazard alerts and
warnings and to evaluate, refine and formalize technical specifications to
create a valid CAP Profile. Also, might there be a need to
replace ‘valid’ with ‘conformant’? Greg Trott CAP-AU PM From: Aymond, Patti [mailto:Patti.Aymond@iem.com]
I lean toward
removing the “public” restriction. I would expect this SC to work
on CAP profiles that include agency-to-agency or agency-to-staff alert and
warning. Of course, we could
leave the restriction in and revisit the charter if a non-public profile
arises. From: Elysa Jones [mailto:elysajones@yahoo.com] Friends, As discussed on the call yesterday, it has
been called to my attention by Chet Ensign that the statement of purpose for
this SC is quite restrictive and does not support international profiles.
We properly took on the CAP-AU work at the TC following the TC process and we
agreed that the work would be done in the CAP Profiles SC. Accepting the
work does fall within the charter of the TC. The TC by resolution can
change the statement of purpose (aka charter) for the SC. This decision
is not done within the SC but I would like for us to discuss here on the list
recommended wording to be presented to the TC for consideration. As we saw yesterday, the Charter appears
blank on the group home page. I have asked Chet about that. The
current statement of purpose according to our OASIS records provided by Chet is
as follows: "Subcommittee formed to review the DHS FEMA/IPAWS
"Common Alerting Protocol (CAP) v1.1 Profile Requirements" document
to refine and formalize technical specifications and create an "IPAWS
Common Alerting Protocol (CAP) Version 1.1 Profile", in order to support
CAP within the U.S. Emergency Alert System (EAS)." Obviously this is
quite restrictive and must be updated. Here is a suggested wording to
consider: Subcommittee formed
to review requirements for a CAP Profile for public alert and warning from
various entities and to evaluate, refine and formalize technical specifications
and to create a valid CAP Profile. I thought it would
be helpful to explicitly use the phrase “public alert and warning”
so as not to imply that we are making a decision for this SC to also consider,
say Sensor Profiles. Although that may certainly be the case, I would
rather make that decision explicitly. Please provide any
suggested wording for the statement of purpose for us to discuss on the list in
hopes that we can suggest something to the TC in our meeting on Tues. Regards, Elysa If you have received this transmission in error please notify us immediately by return e-mail and delete all copies. If this e-mail or any attachments have been sent to you in error, that error does not constitute waiver of any confidentiality, privilege or copyright in respect of information in the e-mail or attachments. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]