| Version 7 (modified by , 9 years ago) ( diff ) |
|---|
How to Implement the CAP Broker
Table of Contents
Overview
- Alerts -- The qualifiers of the alert message. Includes alert identifier, sender, message type, scope (audience), references to other cap alerts and other fields.
- Alert information -- An alert can contain more than one information element, the primary purpose of this is to annotate the alert message in multiple languages. An information part of the alert contains fields that are pertinent to the actual subject and characters of the alert. Fields include: language, category of the alert, a short description of the event, expected response type, priority, urgency, severity, certainty, target audience, auxiliary codes and parameters as metadata to the event, time of effectiveness, onset and expiry, name of the sender, headline of the event, a url, contact information etc.
- Resource -- One or more files attached to the information (could be things like a map of the affected area, documents containing instructions etc.)
- Area -- Each alert information item may contain one or more area fields which describe the affected geographical area and optionally provide data to place it on a map.
- Alert information -- An alert can contain more than one information element, the primary purpose of this is to annotate the alert message in multiple languages. An information part of the alert contains fields that are pertinent to the actual subject and characters of the alert. Fields include: language, category of the alert, a short description of the event, expected response type, priority, urgency, severity, certainty, target audience, auxiliary codes and parameters as metadata to the event, time of effectiveness, onset and expiry, name of the sender, headline of the event, a url, contact information etc.
Work Flows
Create a CAP Message Template
An alert template is a pre-populated CAP message that is created to sp
Note:
See TracWiki
for help on using the wiki.
