Common Alerting Protocol (CAP): Format and Purpose

common alerting protocol

Trying to work out how one warning reaches phones, radios and TVs alike? The common alerting protocol (CAP) is a standard message format that lets a single alert travel across many warning systems at once.

This page is part of a wider guide that explains how do emergency alerts work, from the first warning to the device in your hand.

Item Value
Full name Common Alerting Protocol (CAP)
Version covered here Version 1.2
Approved as an OASIS Standard 01 July 2010
Licensing basis Royalty-free
Added in this version Digital signature support

These figures come from the OASIS standard page and the OASIS press release of August 2010. They can change, so check the sources before you rely on them.

What the common alerting protocol does

The Common Alerting Protocol is, in the words of its OASIS specification, a simple but general format for exchanging all-hazard emergency alerts and public warnings over all kinds of networks. It describes how a warning message is written, not which siren, phone or broadcaster delivers it. Read the full text in the CAP specification.

The same specification points to three main benefits:

  • One consistent warning message can be disseminated simultaneously over many different warning systems, which increases effectiveness while simplifying the warning task.
  • Patterns in local warnings can be detected more easily, which might reveal an undetected hazard or hostile act.
  • The format acts as a template for effective warning messages, built on best practices from academic research and real-world experience.

In practical terms, a shared format means the content of a warning is written once and understood by many systems. Nobody has to translate between each vendor’s private method.

Where CAP came from and who maintains it

According to the introduction to Canada’s profile of CAP, the need for a public alerting protocol was identified in a report from the year 2000 by the US National Science and Technology Council, titled “Effective Disaster Warnings”. You can find that history in the Canadian profile documentation.

The standards consortium OASIS announced in August 2010 that version 1.2 had become an official OASIS Standard, which it described as the highest level of ratification. Its standards page lists the approval date as 01 July 2010. Both facts appear in the OASIS press release and the standard page.

The chair of the OASIS Emergency Management Technical Committee said in that announcement that CAP has been driven by practitioners, reviewed by vendors and adopted internationally. The same release says version 1.2 brought digital signature support, giving added security and authentication for next-generation alerting systems, and that CAP is offered on a royalty-free basis (OASIS press release).

CAP also sits inside a family. The release says the EDXL family of standards also includes the Distribution Element, Hospital Availability Exchange and Resource Message, and that the standard has been approved as an ITU-T standard (OASIS press release).

How one message reaches many channels

OASIS calls CAP an all-hazard, all-media format. In its words, the same message can provide notifications by radio, television, cell phones, email and other media, as set out in the August 2010 announcement.

The Canadian profile makes a related point: compliance is not tied to one alerting method, communications channel or group of stakeholders (Public Safety Canada). So CAP is best read as a shared language that sits upstream of delivery. For one delivery channel in detail, see the explainer on wireless emergency alerts.

Rows of gray equipment cabinets line a brightly lit corridor.

Why countries write their own profiles

A profile is accepted, in the Canadian documentation, as necessary to target the needs specific to a country or system using the base standard. It adds local rules without replacing CAP, and the same document states that valid CAP-CP is also valid CAP (Public Safety Canada).

The OASIS announcement says Canada and the U.S. have adopted profiles of CAP that define events, location codes and other parameters specific to their needs (OASIS press release). Location codes matter because a warning has to say where it applies, and the guide to location-based emergency alerts covers that side.

Two profiles are named in the same release:

  • The Canadian Profile (CAP-CP) supports automated translation of emergency messages, which the release calls critical for Canada’s bi-lingual society.
  • The U.S. Integrated Public Alert and Warning System Profile (IPAWS) defines codes in support of the Emergency Alert System.

The IPAWS profile itself describes IPAWS as a public alerting “system of systems” created by the U.S. Federal Emergency Management Agency (IPAWS profile).

Who supported CAP at approval

As of the OASIS announcement in August 2010, CAP was supported by the World Meteorological Organization, Environment Canada and the U.S. National Weather Service. The release adds that the U.S. Geological Survey uses CAP for earthquake and tsunami warnings (OASIS press release).

The sources used for this page do not cover later adoption. Check the OASIS pages and the relevant national authority for the present picture.

Reading CAP claims with care

Talk of “CAP-compliant” systems can hide differences. Before you rely on a claim, ask:

  • Which version of the standard is meant?
  • Is a national profile involved, and which one?
  • How old is the source, and has the standard or profile moved on?

CAP is a message format, not a warning authority. For what to do in a real emergency, follow your official local emergency authorities.

Frequently asked questions

Does CAP itself send alerts to phones?

Show answer

No. CAP describes the content of a warning, and separate warning systems and channels do the delivering.

Which version of CAP does this page describe?

Show answer

It covers version 1.2, the release named in the OASIS press release. Check the OASIS standard page for any later revision before relying on this summary.

Do implementers pay to use CAP?

Show answer

OASIS’s August 2010 release says it can be implemented without royalties (OASIS press release). Patent and licensing details sit in the notices of the specification, so read those before building anything.

What is the difference between CAP and a profile?

Show answer

CAP is the base format. A profile narrows it for local needs; the IPAWS profile, for instance, interprets the standard to meet the needs of that U.S. system (IPAWS profile).