Common Alerting Protocol: Difference between revisions

Revision as of 07:45, 9 September 2012

Revision as of 17:46, 30 October 2012

Line 2:

The '''Common Alerting Protocol''' (CAP) is an [[XML]]-based data format for exchanging [[Emergency population warning|public warnings]] and emergencies between [[alerting technologies]]. CAP allows a warning message to be consistently disseminated simultaneously over many warning systems to many applications. CAP increases warning effectiveness and simplifies the task of activating a warning for responsible officials.

Individuals can receive standardized alerts from many sources and configure their applications to process and respond to the alerts as desired. Alerts from the [[Department of Homeland Security]], the [[Department of the Interior]]'s [[United States Geological Survey]], and the [[Department of Homeland SecurityCommerce]],'s [[NOAANational Oceanic and Atmospheric Administration]] (NOAA), and Statestate and Locallocal government agencies can all be received in the same format, by the same application. That application can, for example, sound different alarms based on the information received.

By normalizing alert data across threats, jurisdictions, and warning systems, CAP also can be used to detect trends and patterns in warning activity, such as trends that might indicate an undetected hazard or hostile act. From a procedural perspective, CAP reinforces a research-based template for effective warning message content and structure.

Line 13:

*Template support for framing complete and effective warning messages;

*Digital encryption and signature capability;

*Facility for digital images, audio, and video.

==Background==

The [[National Science and Technology Council]] (NSTC) report on “Effective Disaster Warnings” [http://www.sdr.gov/NDIS_rev_Oct27.pdf PDF] (November, 2000) recommended that “a standard method should be developed to collect and relay instantaneously and automatically all types of hazard warnings and reports locally, regionally and nationally for input into a wide variety of dissemination systemssystems”.”

In 2001 an international, independent group of over 120 emergency managers began specifying and prototyping the Common Alerting Protocol data structure based on the recommendations of the NSTC report. The project was embraced by the non-profit [http://www.ppw.us Partnership for Public Warning] and a number of international warning system vendors. A series of field trials and long-term demonstration projects during 2002-03 led to the submission of a draft CAP specification to the OASIS standards process for formalization.

The CAP  1.0 specification was approved by [[OASIS (organization)|OASIS]] in April, 2004. Based on experience with CAP  1.0, the OASIS [http://www.oasis-open.org/committees/emergency Emergency Management Technical Committee] adopted an updated [http://www.oasis-open.org/committees/download.php/14759/emergency-CAPv1.1.pdf CAP  1.1 specification] in October 2005. At a meeting in Geneva in October, 2006 the CAP  1.1 specification was taken under consideration by the [[International Telecommunications Union]] for adoption as an ITU recommendation.

==Current Implementationsimplementations==

===United States===

According to a [http://www.incident.com/cookbook/index.php/CAP_Fact_Sheet CAP 1.0 Fact Sheet], CAP implementations have been demonstrated by agencies and companies including: [[United States Department of Homeland Security]]; [[National Weather Service]]; [[United States Geological Survey]]; [http://edis.oes.ca.gov California Office of Emergency Services]; Virginia Department of Transportation; GeoDecisions, Inc.; Blue292; Warning Systems, Inc.; Comlabs, Inc.; mobileFoundations; Ship Analytics; MyStateUSA; IEM, Inc.; Hormann America, Inc.; Oregon RAINS; Alerting Solutions, Inc. and others.

It is also mentioned by the [[Internet Society]] in its 2005 [http://www.isoc.org/challenge/ "Public Warning Network Challenge"].

DuringIn early 2005, the U.S.  Department of Homeland Security (DHS), in partnership with the [http://www.apts.org Association of Public Television Stations], demonstrated CAP-based "digital EAS" broadcasts over public television digital TV transmitters and satellite links in the [[Washington, D.C.]] area and nationwide.

CAP is the foundation technology for the planned "[http://www.fema.gov/emergency/ipaws/ Integrated Public Alert and Warning System]," an all-hazard, all-media national warning architecture being developed by DHS, the [[National Weather Service]] within NOAA, and the [[Federal Communications Commission]].

===Canada===

In Canada, a working group composed of public alerting practitioners and government agencies has developed a CAP Canadian Profile (CAP-CP) based on CAP but specialized to address the needs of Canadian public alerting stakeholders, such as bilingualism, geocoding for Canada, managed lists of locations and events, etc. The Canadian government has adopted CAP-CP for its National Public Alerting System (NPAS) project. The CAP-‑CP working group, along with stakeholders and projects such as the Canadian Association for [http://www.capan.ca Public Alerting and Notification (CAPAN)] and [http://sarnia-lambton.netalerts.ca/ Netalerts' Sarnia Lambton trial], are now working with and refining CAP-‑CP for national application in Canada.

CAP has been implemented for a small-scale, grassroots hazard information system in [[Sri Lanka]] following the [[2004 Indian Ocean Tsunami]]. This implementation was part of the [http://www.lirneasia.net/projects/current-projects/evaluating-last-mile-hazard-information-dissemination-hazinfo/ "HazInfo Project"] funded by Canada's International Development Research Centre.

===Worldwide===

In 2007, the [http://www.itu.int/ITU-T/ International Telecommunication Union, Telecommunication Standardization Sector] (ITU-T) adopted the Common Alerting Protocol as Recommendation [http://www.itu.int/rec/T-REC-X.1303-200709-I/en X.1303]. The recommendation annex contains an authoritative [[ASN.1]] module translation of the CAP XML schema that may be useful for some implementations. Rec. X.1303 is within the remit of ITU-‑T Study Group 17 (Security), Rapporteur Group on Cybersecurity (Q.4/17) [http://www.itu.int/ITU-T/studygroups/com17/index.asp] for purposes of further evolution of the standard.

==External links==