This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Common Alerting Protocol | |
|---|---|
| Name | Common Alerting Protocol |
| Abbreviation | CAP |
| Developed by | OASIS |
| Initial release | 2004 |
| Latest release | 1.2 |
Common Alerting Protocol The Common Alerting Protocol is a standardized XML-based data format designed to enable interoperability among National Weather Service, Federal Emergency Management Agency, European Union, United Nations, and World Health Organization alerting systems across diverse International Telecommunication Union, Internet Engineering Task Force, Organisation for the Advancement of Structured Information Standards, and European Telecommunications Standards Institute infrastructures. It provides a structured framework to describe hazard tsunami, earthquake, flood, hurricane, and pandemic events so that recipients such as Red Cross, UNICEF, World Bank, Interpol, and NATO components can automate dissemination through channels including SMS, radio broadcasting, television broadcasting, social media, and satellite communication.
CAP defines a machine-readable message envelope enabling conversion between legacy formats used by National Oceanic and Atmospheric Administration, Japan Meteorological Agency, Met Office (United Kingdom), Météo-France, Deutscher Wetterdienst, Environment Canada, and multicast/peer-to-peer systems operated by Microsoft, Google, Apple, Amazon (company), and Facebook. The protocol supports metadata fields for sender identity, geospatial polygons for affected areas used by ESRI, OpenStreetMap, and GIScience Research Group, urgency and severity vocabularies aligned with terminologies adopted by World Meteorological Organization, International Federation of Red Cross and Red Crescent Societies, and Centers for Disease Control and Prevention. CAP's design aims to facilitate end-to-end workflows connecting alert originators like National Guard, Civil Protection (France), Bundesamt für Bevölkerungsschutz und Katastrophenhilfe, and Protezione Civile to aggregators such as Reuters, Associated Press, Bloomberg L.P., and Agence France-Presse.
The CAP specification originated from collaborative initiatives between OASIS, World Meteorological Organization, International Telecommunication Union, United Nations Office for the Coordination of Humanitarian Affairs, and national agencies including NOAA, Met Office (United Kingdom), and Japan Meteorological Agency during early-2000s interoperability efforts prompted by events like the 2004 Indian Ocean earthquake and tsunami and the 2005 Hurricane Katrina response. Subsequent revisions involved standards bodies such as IETF working groups and regional stakeholders including European Commission, ASEAN Coordinating Centre for Humanitarian Assistance on Disaster Management, and Pacific Islands Forum, producing formal releases and errata culminating in versions maintained by OASIS technical committees and endorsed by organizations like ITU-T and ISO affiliates.
CAP messages are XML documents composed of core elements—identifier, sender, sent, status, msgType, scope—plus nested elements for event, urgency, severity, certainty, audience, and resources. The schema leverages namespaces and extensibility mechanisms compatible with XML Schema, Simple Object Access Protocol, Representational State Transfer, and Hypertext Transfer Protocol profiles used by vendors like IBM, Oracle Corporation, Red Hat, and Sun Microsystems. Geospatial targeting employs coordinate pairs, polygons, and circular areas interoperable with Geographic Information System, GeoJSON, and Keyhole Markup Language produced by Google Earth, Esri ArcGIS, and QGIS. Multimedia attachments and links reference MIME types and distribution endpoints compliant with IANA registries and content delivery networks operated by Akamai Technologies.
CAP is used for early warning systems for tsunami, volcanic eruption, earthquake, wildfire, chemical spill, and radiological incidents by agencies like Japan Meteorological Agency, NOAA National Weather Service, Instituto Nacional de Meteorología e Hidrología (Venezuela), Servicio Nacional de Meteorología e Hidrología del Perú, and municipal systems in New York City, Tokyo, London, Sydney, and São Paulo. Private-sector adopters include AT&T, Vodafone, Verizon Communications, and T-Mobile US for Wireless Emergency Alerts, while humanitarian NGOs like Médecins Sans Frontières and International Committee of the Red Cross integrate CAP into coordination platforms such as ReliefWeb and Humanitarian Exchange Language-based toolchains.
Adoption has been promoted through policy instruments and pilot programs by European Commission, United States Department of Homeland Security, Australian Department of Home Affairs, Canadian Radio-television and Telecommunications Commission, and regional bodies including ASEAN. Governance and maintenance responsibilities rest with OASIS technical committees in consultation with stakeholders such as ITU, WMO, national meteorological services, and telecom regulators, with implementation guidelines produced by institutions including World Bank disaster risk management units and academic centers like Massachusetts Institute of Technology, University of Oxford, and National University of Singapore.
CAP interoperates with protocols and standards including Emergency Alert System, Wireless Emergency Alerts, Common Alerting Protocol Profile for Public Safety, Open Geospatial Consortium standards, CAP v1.2 profiles, SIP, XMPP, and web APIs deployed by Google Public Alerts and Apple Emergency Alerts. Integration requires mappings between CAP elements and legacy formats used in EAS broadcasts, NOAA Weather Radio, and regional pagers provided by companies like Motorola Solutions and Ericsson. International harmonization efforts coordinate taxonomies and code lists across WMO, ITU, ISO, and regional emergency frameworks.
Critics note CAP's reliance on XML increases message size and parsing complexity for constrained devices compared to compact binary alternatives favored by 3GPP and LoRa Alliance, while interoperability challenges persist due to divergent vocabularies among agencies like NOAA, Japan Meteorological Agency, and European Centre for Medium-Range Weather Forecasts. Other limitations include inconsistent geospatial resolution across implementations seen in deployments by FEMA and regional civil protection agencies, privacy concerns raised by telecom operators and civil liberties groups such as Electronic Frontier Foundation, and governance bottlenecks within OASIS and multilateral institutions that complicate rapid schema evolution during emergent crises.
Category:Emergency communication