CAP Profile SC - Statement of Purpose

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

emergency-cap-profiles message