Changes between Version 30 and Version 31 of BluePrint/CAPBroker


Ignore:
Timestamp:
04/07/14 02:50:47 (11 years ago)
Author:
Nuwan Waidyanatha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • BluePrint/CAPBroker

    v30 v31  
    22[[TOC]]
    33
    4 == Current Status ==
     4== Current Status == 
    55
    6 '''Available features:''' manage templates, manage messages [[BR]]
     6'''Available features:'''
     7* built on the Emergency Data Exchange Language (EDXL) Common Alerting Protocol (CAP) version 1.2 '''[1]'''
     8* manage templates, manage messages [[BR]]
    79
    810'''Missing features:'''
    … …  
    1113* common operating picture
    1214* subscription management
    13 * receive CAP feeds
     15* receive CAP feeds '''[2]'''
    1416* integrate with Google Alerthub
    1517* enable multi language "info" segments
    … …  
    1719
    1820UserGuidelines/Alerts
    19 
    2021== Introduction ==
    2122[http://en.wikipedia.org/wiki/Common_Alerting_Protocol Common Alerting Protocol] defines a data format for sharing alerts (and re-relaying) over various media channels. This project aims to implement core CAP features into Eden and provide usable UI elements for managing CAP alerts.The module will facilitate the publishing and relaying of alerts and warning as well as offer subscribers means to receive warnings and alerts of their choice. Moreover, the module will provide a common operating picture of the published alerts for improving situational-awareness (e.g. [http://gdacs.org/alerts/ GDACS common operating picture with message filtering]). The tools are mainly for National Disaster Management Organizations for managing [http://lirneasia.net/2012/05/masas-iscram-2012/ Multi-agency Situational-awareness] with capabilities for all-hazard all-media warning/alerting.[[BR]]