Common Alerting Protocol: Difference between revisions

Revision as of 05:39, 10 November 2005

Revision as of 05:55, 10 November 2005

Line 1:

The '''Common Alerting Protocol''' (CAP) is an [[XML]]-based data format for exchanging emergency [[AMBER Alert|alerts]] and [[Emergency population warning|public warnings]] among different alerting technologies. CAP allows a consistent warning message to be disseminated simultaneously over many different warning systems, in order to increase warning effectiveness and simplifyingsimplify the warning activation task for responsible officials.

By normalizing alert data across threats, jurisdictions and warning systems, CAP also facilitatescan be used in the detection of trends and patterns in local warning activity, such as might indicate an undetected hazard or hostile act. AndFrom a procedural perspective, CAP reinforces a research-based template for effective warning messagesmessage based on best practices identified in academic researchcontent and real-world experiencestructure.

The CAP data structure is backward-compatible with existing alert formats including the [[Specific Area Message Encoding]] (SAME) used in [[NOAA Weather Radio|Weatheradio]] and the broadcast [[Emergency Alert System]], while adding capabilities including:

* Flexible geographic targeting using latitude/longitude “boxes” and other geospatial representations in three dimensions;

Line 15:

== Background ==

The [[National Science and Technology Council]] (NSTC) report on “Effective Disaster Warnings” ([[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 systems.”

In 2001 an independent group of emergency managers began specifying a 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 in April, 2004. The [http://www.oasis-open.org Organization for the Advancement of Structured Information Standards] (OASIS)] is a not-for-profit, international consortium that drives the development, convergence and adoption of e-business standards. Members themselves set the OASIS technical agenda, using a lightweight, open process expressly designed to promote industry consensus and unite disparate efforts. OASIS produces worldwide standards for security, web services, conformance, business transactions, supply chain, public sector, and interoperability within and between marketplaces.

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.

Line 25:

== Current Implementations ==

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]]; California Office of Emergency Services; Virginia Department of Transportation; GeoDecisions, Inc.; E Team; Blue292; Warning Systems, Inc.; Comlabs, Inc.; mobileFoundations; Ship Analytics; MyStateUSA; IEM, Inc.; Hormann America, Inc.; Oregon RAINS.

During early 2005 the U.S. Department of Homeland Security (DHS), in partnership with the Association of Public Television Stations, demonstrated "digital EAS" broadcasts over public television digital TV transmitters and satellite links in the Washington, D.C. area and nationwide.