Common Alerting Protocol: Difference between revisions

Revision as of 17:06, 6 April 2023

Revision as of 04:20, 24 July 2023

Line 1:

{{shortShort description|XML-based markup language}}

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, such as [[Google Public Alerts]] and [[Cell Broadcast]]. CAP increases warning effectiveness and simplifies the task of activating a warning for responsible officials.

Line 18:

The US [[National Science and Technology Council]] (NSTC) November 2000 report on "Effective Disaster Warnings" recommended that "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."<ref>{{cite web |url=http://www.sdr.gov/NDIS_rev_Oct27.pdf |title=Archived copy |access-date=2006-05-03 |url-status=dead |archive-url=https://web.archive.org/web/20060513144112/http://www.sdr.gov/NDIS_rev_Oct27.pdf |archive-date=2006-05-13 }}</ref>

In 2001, an international independent group of over 120 emergency managers that was convened online by California emergency telecommunications expert Art Botterell 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 Partnership for Public Warning and a number of international warning system vendors.<ref>http{{Cite web|url=https://www.ppw.us {{webarchive/|urlarchiveurl=https://web.archive.org/web/20020928072102/http://www.ppw.us/ |dateurl-status=2002dead|title=ppw.us -09 Domain Name For Sale|archive-date=28 September 2002|website=Dan.com}}</ref> 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&nbsp;1.0 specification was approved by [[OASIS (organization)|OASIS]] in April 2004. Based on experience with CAP&nbsp;1.0, the OASIS Emergency Management Technical Committee adopted an updated CAP&nbsp;1.1 specification in October 2005.<ref>{{cite web |url=http://www.oasis-open.org/committees/emergency |url-status=dead |archive-url=https://web.archive.org/web/20030207195408/http://www.oasis-open.org/committees/emergency/ |archive-date=2003-02-07 |title=OASIS - Committees - OASIS Emergency Management TC}}</ref><ref>[http://www.oasis-open.org/committees/download.php/14759/emergency-CAPv1.1.pdf {{BareCommon URLAlerting PDF|date=JanuaryProtocol, 2022}}v. 1.1] oasis-open.org</ref> At a meeting in Geneva in October 2006 the CAP&nbsp;1.1 specification was taken under consideration by the [[International Telecommunication Union]]'s [[ITU-T|Standardization Sector]] for adoption as an ITU-T recommendation. CAP was subsequently adopted as Recommendation X.1303.<ref>{{cite web |title=X.1303 : Common alerting protocol (CAP 1.1) |url=https://www.itu.int/rec/T-REC-X.1303/en |publisher=International Telecommunication Union |access-date=2019-04-30}}</ref>

CAP specification version 1.2 has been available since July 2010 at the OASIS website.<ref>[http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2-os.pdf {{BareCommon URLAlerting PDF|date=JanuaryProtocol 2022}}Version 1.2] oasis-open.org</ref>

==Implementation==