W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2005

CAP protocol standardizes emergency communications

From: Mark D. Urban <docurban@nc.rr.com>
Date: Wed, 30 Nov 2005 20:50:02 -0500
To: <w3c-wai-ig@w3.org>
Cc: "'WebAIM Discussion List'" <webaim-forum@list.webaim.org>
Message-ID: <!&!AAAAAAAAAAAYAAAAAAAAAM/kxUwX/nZDqbm/cHtcKuvCgAAAEAAAALEwZMlAG51JsG1OSMK2ue4BAAAAAA==@nc.rr.com>
For those of you in the field of emergency communications, this is a big
deal - and potentially with enormous impacts on persons with disabilities.
One could forsee specialized devices that would receive these standardized
messages and provide them to persons with disabilities in whatever format
they need (maybe over the INCITS V2 standards??)
 
Imagine how something like this might have helped in Hurricane Katrina or
the Indian Ocean Tsunami?
 
 
Regards,
 
-Mark D. Urban 
 
919-395-8513 (cell)
Chair, North Carolina Governor's Advocacy Council for Persons with
Disabilities
Keep up with the latest in worldwide accessibility at
(http://www.icdri.org/)
 
 
Members Approve Common Alerting Protocol (CAP) v1.1 as OASIS Standard
> 
> Boston, MA, USA; 30 November 2005 -- OASIS, the international e- 
> business standards consortium, today announced that its members have 
> approved the Common Alerting Protocol (CAP) version 1.1 as an OASIS 
> Standard, a status that signifies the highest level of ratification. 
> Developed through an open process by the OASIS Emergency Management 
> Technical Committee, CAP provides a simple, general-purpose format for 
> exchanging all-hazard emergency alerts and public warnings over any 
> network.
> 
> "CAP allows a consistent warning message to be disseminated 
> simultaneously over many different systems, increasing warning 
> effectiveness while simplifying the notification task," said Elysa 
> Jones of Warning Systems, Inc., chair of the OASIS Emergency 
> Management Technical Committee. "Since the approval of CAP v1.0 in 
> 2004, the standard has been deployed by a wide variety of government 
> agencies and companies within the emergency management community. CAP 
> v1.1 incorporates many lessons learned in the production 
> implementation of the standard."
> 
> Jones cited several high-profile CAP implementations, including the 
> United States National Oceanic and Atmospheric Administration
> (NOAA) and the United States Geological Survey (USGS).
> 
> "CAP is an integral part of relaying civil emergency messages on the 
> NOAA Weather Radio All Hazards and other NWS dissemination systems," 
> said Mark Paese, Director, Operations Division for NOAA's National 
> Weather Service. "Its success is an excellent example of how the 
> emergency management community and the government can work together to 
> increase the effectiveness of emergency alerting."
> 
> "The United States Geological Survey is pleased to be providing 
> information about earthquakes and volcano and landslide advisories in 
> CAP format," said David Oppenheimer, a seismologist with the USGS 
> Earthquake Hazards Program. "The advantage of CAP is that it allows 
> the USGS to instantaneously distribute our earthquake information to a 
> wide audience of emergency responders in an approved message format." 
> The USGS automatically distributes CAP messages about earthquakes 
> within minutes after their occurrence as well as advisories via the 
> Disaster Management Interoperability Services (DMIS) and as an RSS 
> feed from the USGS website.
> 
> CAP v1.1 enhancements include flexible geographic targeting using 
> latitude/longitude shapes and other geospatial representations in 
> three dimensions; multilingual and multi-audience messaging; phased 
> and delayed effective times and expirations; enhanced message update 
> and cancellation features; template support for framing complete and 
> effective warning messages; compatibility with digital encryption and 
> signature; and a facility for digital images and audio.
> 
> Chip Hines, Program Manager for the Disaster Management eGov 
> Initiative Office of the Chief Information Officer Emergency 
> Preparedness and Response/FEMA Department of Homeland Security, noted, 
> "Not only does the publication of the CAP OASIS Standard signify an 
> increase in capability to send alerts, it also shows that the process 
> works--that the emergency community is ready, willing, and able to 
> bring standards into their operations. CAP has grown into a standard 
> that is being adopted worldwide, helping the seamless transition of a 
> host of alerts across platforms and systems. The end result is a world 
> better prepared for any emergency."
> 
> "The CAP OASIS Standard is being used in many exciting ways, some that 
> weren't envisioned in the initial stages of its development.
> It offers tremendous benefits for local public safety environments as 
> well as in global and regional efforts, such as tsunami warnings," 
> said Patrick Gannon, president and CEO of OASIS. "With this work and 
> their continuing efforts, members of the OASIS Emergency Management 
> Technical Committee are responding well to today's critical need for 
> enhanced response. There is little doubt that the use of CAP offers 
> the potential to save lives."
> 
> The OASIS Emergency Management Technical Committee remains open to new 
> participation and particularly seeks input from those in the 
> international community  to advance CAP in alignment with other 
> specifications in its Emergency Data Exchange Language (EDXL) suite. 
> All interested parties are encouraged to exchange information on 
> implementing CAP via the cap-dev mailing list 
> ( <http://www.oasis-open.org/mlmanage/>
http://www.oasis-open.org/mlmanage/
). As with all Consortium 
 <http://www.oasis-open.org/mlmanage/> > projects, archives of the OASIS
Emergency Management Committee's work 
 <http://www.oasis-open.org/mlmanage/> > are accessible to both members and
non-members, and OASIS hosts an 
 <http://www.oasis-open.org/mlmanage/> > open mail list for public comment
on the standard.
 <http://www.oasis-open.org/mlmanage/> > 
 <http://www.oasis-open.org/mlmanage/> > 
 <http://www.oasis-open.org/mlmanage/> > About OASIS:
 <http://www.oasis-open.org/mlmanage/> > 
 <http://www.oasis-open.org/mlmanage/> > OASIS (Organization for the
Advancement of Structured Information
 <http://www.oasis-open.org/mlmanage/> > Standards) is a not-for-profit,
international consortium that drives 
 <http://www.oasis-open.org/mlmanage/> > the development, convergence, and
adoption of e-business standards. 
 <http://www.oasis-open.org/mlmanage/> > Members themselves set the OASIS
technical agenda, using a 
 <http://www.oasis-open.org/mlmanage/> > lightweight, open process expressly
designed to promote industry 
 <http://www.oasis-open.org/mlmanage/> > consensus and unite disparate
efforts. The consortium produces open 
 <http://www.oasis-open.org/mlmanage/> > standards for Web services,
security, e-business, and standardization 
 <http://www.oasis-open.org/mlmanage/> > efforts in the public sector and
for application- specific markets. 
 <http://www.oasis-open.org/mlmanage/> > Founded in 1993, OASIS has more
than 5,000 participants representing 
 <http://www.oasis-open.org/mlmanage/> > over 600 organizations and
individual members in 100 countries. 
 <http://www.oasis-open.org/mlmanage/> > Approved OASIS Standards include
AVDL, CAP, DITA, DocBook, DSML, ebXML 
 <http://www.oasis-open.org/mlmanage/> > CPPA, ebXML Messaging, ebXML
Registry, OpenDocument, SAML, SPML, UBL, 
 <http://www.oasis-open.org/mlmanage/> > UDDI, WSDM, WS- Reliability, WSRP,
WS-Security, XACML, XCBF, and XML 
 <http://www.oasis-open.org/mlmanage/> > Catalogs.
 <http://www.oasis-open.org/mlmanage/> > http://www.oasis-open.org
 <http://www.oasis-open.org/> > 
 <http://www.oasis-open.org/> > 
 <http://www.oasis-open.org/> > Additional information:
 <http://www.oasis-open.org/> > 
 <http://www.oasis-open.org/> > OASIS Emergency Management Technical
Committee http://www.oasis- 
 <http://www.oasis/> > open.org/committees/emergency
 <http://www.oasis/> > 
 <http://www.oasis/> > FAQ
 <http://www.oasis/> >
http://www.oasis-open.org/committees/emergency/faq.php
 <http://www.oasis-open.org/committees/emergency/faq.php> > 
 <http://www.oasis-open.org/committees/emergency/faq.php>  
Received on Thursday, 1 December 2005 01:50:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:23 GMT