Common Alerting Protocol: Difference between revisions

Content deleted Content added
Undid revision 699243492 by Rogue897 (talk)
m clean up Category:CS1 errors: invisible characters + AWB general fixes using AWB
Line 1:
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.
 
Standardized alerts can be received 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 [[United States Department of Commerce]]'s [[National Oceanic and Atmospheric Administration]] (NOAA), and state and local 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.
Line 24:
 
==Implementations==
 
===United States===
According to a CAP 1.0 Fact Sheet,<ref>http://www.incident.com/cookbook/index.php/CAP_Fact_Sheet</ref> 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;<ref>{{cite web|url=http://edis.oes.ca.gov|title=Emergency Digital Information Service (EDIS)|work=ca.gov}}</ref> Virginia Department of Transportation; NDS, Ltd.; GeoDecisions, Inc.; Blue292; Warning Systems, Inc.; Comlabs, Inc.; mobileFoundations; Ship Analytics; AlertSense (formerly MyStateUSA); IEM, Inc.; Hormann America, Inc.; Oregon RAINS; Alerting Solutions, Inc. and others.
Line 29 ⟶ 30:
It is also mentioned by the [[Internet Society]] in its 2005 "Public Warning Network Challenge".<ref>{{cite web|url=http://www.isoc.org/challenge/|title=The Internet Rises to the Challenge of Public Warning|work=isoc.org}}</ref>
 
In early 2005, the U.S.&nbsp;Department of Homeland Security (DHS), in partnership with the Association of Public Television Stations,<ref>{{cite web|url=http://www.apts.org|title=Association of Public Television Stations|work=apts.org}}</ref> 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 "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]].<ref>http://www.fema.gov/emergency/ipaws/</ref>
 
===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&#8209;CPCAP‑CP working group, along with stakeholders and projects such as the Canadian Public Safety Operations Organization (CanOps) and Netalerts' Sarnia Lambton trial, are now working with and refining CAP&#8209;CPCAP‑CP for national application in Canada.{{cncitation needed|date=June 2015}}
 
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 "HazInfo Project", funded by Canada's International Development Research Centre.<ref>{{cite web|url=http://www.lirneasia.net/projects/current-projects/evaluating-last-mile-hazard-information-dissemination-hazinfo/|title=Evaluating Last-Mile Hazard Information Dissemination (HazInfo)|work=lirneasia.net}}</ref>
Line 41 ⟶ 42:
 
===Australia===
The Australian Government Standard for Common Alerting Protocol (CAP-AU-STD, 2012) was developed by a CAP-AU-STD stakeholder group comprising federal agencies Emergency Management Australia, the Bureau of Meteorology, GeoScience Australia, Department of Agriculture, Fisheries and Forestry and the Department of Health, as well as a number of State Government authorities and emergency services agencies. The project was co-ordinated by the Australian Government Attorney-General's Department (Australian Emergency Management).<ref>{{cite web|url=http://www.em.gov.au|title=Pages - Australian Emergency Management|work=em.gov.au}}</ref><ref>{{cite web|url=https://www.govshare.gov.au/item-details/?rid=57|title=Common Alerting Protocol – Australia (CAP-AU-STD) - GovShare|work=govshare.gov.au}}</ref>
- Australian Emergency Management|work=em.gov.au}}</ref> <ref>{{cite web|url=https://www.govshare.gov.au/item-details/?rid=57|title=Common Alerting Protocol – Australia (CAP-AU-STD) - GovShare|work=govshare.gov.au}}</ref>
 
===Worldwide===
In 2007, the International Telecommunication Union, Telecommunication Standardization Sector (ITU-T) adopted the Common Alerting Protocol as Recommendation X.1303.<ref>{{cite web|url=http://www.itu.int/ITU-T/|title=ITU Telecommunication Standardization Sector|work=ITU}}</ref><ref>{{cite web|url=http://www.itu.int/rec/T-REC-X.1303-200709-I/en|title=X.1303&nbsp;:&nbsp;Common alerting protocol (CAP 1.1)|author=tsbmail|work=itu.int}}</ref> 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&#8209;TITU‑T Study Group 17 (Security), Rapporteur Group on Cybersecurity (Q.4/17) for purposes of further evolution of the standard.<ref>{{cite web|url=http://www.itu.int/ITU-T/studygroups/com17/index.asp|title=ITU-T Study Group 17 (Study Period 2013-2016)|work=itu.int}}</ref>
 
== References ==