EAS-CAP Industry Group Working Documents

Download Document:

Comments:

Abstract: The ECIG Implementation Guide (version 1.0) has been compiled in light of the draft OASIS CAP v1.2 specification and the IPAWS CAP-EAS Profile v1.0, as well as the results of a public comment period on the prior draft Implementation Guide.  The guide is intended to further reduce areas of uncertainty in how an alert will be presented to the public via CAP-EAS, so that originators and distributors of alerts can deliver the intended message to the public, regardless of the vendors or platforms involved. This ECIG Implementation Guide has not been written to benefit any specific vendor or type of equipment. The goal is general interoperability at a data and messaging level.  The guide has been written to facilitate the success of any CAP-to-EAS system, including existing and planned state, local, territorial and tribal systems; the proposed IPAWS system, and National Weather Service system. To that end, in addition to addressing general CAP-to-EAS implementation issues, this guide also directly addresses constraints and requirements of the IPAWS program.

Please file any comments via the ECIG Public Discussion List

Subscribe to the ECIG-Public List

Abstract: A consensus among EAS equipment manufacturers and warning practitioners regarding a single recommended pattern for compatible encoding—the draft “EAS-CAP Implementation Guide”—is documented along with a number of related recommendations.  The draft ECIG Implementation Guide has been compiled in light of the draft OASIS CAP v1.2 specification and the IPAWS CAP-EAS Profile v1.0

Abstract: Public warnings intended for transmission over the Emergency Alert System (EAS) can be encoded in Common Alerting Protocol (CAP) messages in various ways. A consensus among EAS equipment manufacturers and warning practitioners regarding a single recommended pattern for compatible encoding—the “EAS-CAP Profile”—is documented along with a number of related recommendations.

Comment period closed.