Contribution for "Proposed initial draft of "Architecture and Requirements for Web-based Signage Player - Emergency Information Profile"

Hello and Happy New Year ! 

 

1/ "Common Alerting Protocol"  (part of the EDXL - Emergency Data Exchange
Language and ITU X1303) seem a good choice for this subject, no ?

 

The most common standard for sharing alerts is the Common Alert Protocol
(CAP), which many agencies and countries have adopted.

The Common Alerting Protocol (CAP) is a digital format for exchanging
emergency alerts that allows a consistent alert message to be disseminated
simultaneously over many different communications systems. FEMA worked with
the Organization for the Advancement of Structured Information Standards
(OASIS) to develop a standardized international technical data profile that
defines a specific way of using the standard for the purposes of the
Integrated Public Alert and Warning System (IPAWS).

 

Benefits of CAP

As more systems are built or upgraded to CAP, a single alert can trigger a
wide variety of public warning systems, increasing the likelihood that
intended recipients receive the alert by one or more communication pathways.
CAP provides the capability to include rich content, such as photographs,
maps, streaming video and more as well as the ability to
geographically-target alerts to a defined warning area, limited only by the
capacity of the delivery system used. 

 

Guidance and Technical Documents

.
<http://www.fema.gov/redirect?url=http%3A%2F%2Fdocs.oasis-open.org%2Femergen
cy%2Fcap%2Fv1.2%2FCAP-v1.2-os.pdf> OASIS CAP 1.2 Standard

.
<http://www.fema.gov/redirect?url=http%3A%2F%2Fdocs.oasis-open.org%2Femergen
cy%2Fcap%2Fv1.2%2Fipaws-profile%2Fv1.0%2Fcap-v1.2-ipaws-profile-v1.0.pdf>
OASIS CAP v1.2 IPAWS Profile Version 1.0

.
<http://www.google.fr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=14&ved=0CEYQFjA
DOAo&url=http%3A%2F%2Fwww.eumetsat.int%2Fwebsite%2Fwcm%2Fidc%2Fidcplg%3FIdcS
ervice%3DGET_FILE%26dDocName%3DPDF_common_alerting_protocol%26RevisionSelect
ionMethod%3DLatestReleased%26Rendition%3DWeb&ei=Pi_JUvn2EPLK0AXZ2YHwDQ&usg=A
FQjCNHwg-CFsJKGhR40Z-xkqXW9WRURoQ&bvm=bv.58187178,d.d2k> CAP-EP: EUMETSAT's
profile on the Common Alerting Protocol (P

.  Common Alerting Protocol Profile Requirements (
<http://www.fema.gov/redirect?url=http%3A%2F%2Fpreview.fema.net%2Fpdf%2Femer
gency%2Fipaws%2Foasis.pdf> PDF 698KB,
<http://www.fema.gov/redirect?url=http%3A%2F%2Fpreview.fema.net%2Ftxt%2Femer
gency%2Fipaws%2Foasis.txt> TXT 79KB)

.
<http://www.google.fr/url?sa=t&rct=j&q=&esrc=s&source=web&cd=10&ved=0CH4QFjA
J&url=http%3A%2F%2Fwww.itu.int%2Fdms_pub%2Fitu-d%2Fopb%2Fstg%2FD-STG-SG02.22
-2010-PDF-E.pdf&ei=PivJUr7cK6ep0AX07oGoAQ&usg=AFQjCNFczjBUu-wOrLJYuPh6RUcXZI
FEAw&bvm=bv.58187178,d.d2k&cad=rja> Question 22/2 - Guidelines on the Common
Alerting Protocol ... - I

.  SIP http://tools.ietf.org/search/draft-rosen-sipping-cap-00

.  Air Quality feeds : http://feeds.enviroflash.info/ 

.  Google Alert Hub : http://alert-hub.appspot.com/ 

.  EDXL :
https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=emergency 

..

 

The IPAWS Open Platform for Emergency Networks (OPEN) is a set of securely
hosted Web services that enable the routing of standards-compliant emergency
messages between disparate third-party applications, systems, networks and
devices. Since the initial version of OPEN (DM-OPEN 1.0) had an established
capability to route Common Alerting Protocol (CAP) alerts between
organizations and to the public via the National Weather Service's (NWS)
All-Hazards Emergency Message Collection System (HazCollect), OPEN was
selected by FEMA to perform message aggregation for IPAWS.

 

2/ Classification of Severity Level for display:

 

NWEM Event Codes 
Event Code  Priority  Event (Product) Name 
AVW  1  Avalanche Warning 
CDW  1  Civil Danger Warning 
CEM  1  Civil Emergency Message 
EQW  1  Earthquake Warning 
EVI  1  Immediate Evacuation Warning 
FRW  1  Fire Warning 
HMW  1  Hazardous Materials Warning 
LEW  1  Law Enforcement Warning 
NUW  1  Nuclear Power Plant Warning 
RHW  1  Radiological Hazard Warning 
SPW  1  Shelter In Place Warning 
VOW  1  Volcano Warning 
AVA  2  Avalanche Watch 
CAE  2  Child Abduction Emergency 
LAE  2  Local Area Emergency 
TOE  2  911 Telephone Outage Emergency 
ADR  3  Administrative Message/Follow up Statement 
NIC  3  National Information Center 
DMO  Configurable  Practice/Demo Warning 
NPT  Configurable  National Periodic Test 
RMT  Configurable  Routine Monthly Test 
RWT  Configurable  Routine Weekly Test 
NMN  Not Currently Disseminated  Network Message Notification

 

 

http://docs.oasis-open.org/emergency/edxl-cap-logo/v1.0/cnd01/CAP-Logos/ 

http://docs.oasis-open.org/emergency/edxl-cap-logo/v1.0/cnd01/CAP-Logos/CAP-
Icon-L.png

 

 

3/  Reception of emergency information

"We are considering WebSocket or HTTP PUSH for this." Why not but have a
look at :

 

XEP-0127: Common Alerting Protocol (CAP) Over XMPP :
<http://xmpp.org/extensions/xep-0127.html>
http://xmpp.org/extensions/xep-0127.html 

PubSubHubbub:  ie http://alert-hub.appspot.com/ for
http://www.google.org/crisisresponse/ 

 

4/ Some remarks :

Beyond the outdoor, digital signage in the company (university, etc..) is
something to consider.
This leads us to think that in a company, the center of interest is local
and outside/public ; The company may indeed be alerted by an earthquake but
also a fire in the ground floor of its building.

Web based Signage Player must be considered at least two sources of
information (ie two CAP servers).

 

Sincerly,

 

Franck Dupin

 

Description : logo-innes

ZAC Atalante champeaux

5A rue Pierre Joseph Colin

35000 RENNES - FRANCE

Tel: +33 (0)2 23 20 01 62 / Fax: +33 (0)2 23 20 22 59 /
<http://www.innes.fr/> http://www.innes.fr