|
Table of Contents
Announcements
02/09/2010:
The statements of use are in (MyStateUSA, WSI, EvoTec and IEM).
The CAP 1.2 Committee Specification is ready to move on to an OASIS Wide Standard Vote.
02/02 - 02/04/2010:
Interop Demo at TCIP Expo in Philadelphia. Press release
01/30 - 02/01/2010:
EM-TC Face-to-face meeting in Philadelphia for SC work: Msg&Notif. SC (SitRep) and IF SC (DE).
11/24/2009:
CAP 1.2 15-day public review completed. The TC is reviewing the comments received.
11/10/2009:
The TC has approved the "Welcome to the RIM" white paper for publication. Link to follow.
11/09/2009:
15-day review of EDXL-HAVE Errata completed - no comments reported.
11/02-04/2009:
InterOp demo at IAEM / EMEX in Orlando
10/20/2009:
FEMA recognizes our work for "CAP IPAWS Profile" with a letter of appreciation
10/14/2009:
15-day review of EDXL-RM Errata completed - no comments reported.
10/13/2009:
CAP v1.2 IPAWS Profile v1.0 - Ballot has closed. Approved as Committee Specification.
(pdf)
10/03/2009:
2009 Emergency InterOp Summit - Proceedings available
09/15/2009:
The EM TC and the EM Member Section have released the technical white paper Distribution Element (EDXL-DE) Basics.
Overview
The mission of the EM-TC is to create incident and emergency-related standards for data interoperability. The TC welcomes participation from members of the emergency management community, developers and implementers, and members of the public concerned with disaster management and response.
Current EM-TC standard efforts:
The Emergency Data Exchange Language (EDXL) is a broad initiative to create an integrated framework for a wide range of emergency data exchange standards to support operations, logistics, planning and finance:
- EDXL Common Alerting Protocol (EDXL-CAP)
- EDXL Distribution Element (EDXL-DE)
- EDXL Hospital AVailability Exchange (EDXL-HAVE)
- EDXL Resource Message (EDXL-RM)
- EDXL Reference Information Model (EDXL-RIM)
- EDXL Situation Reporting (EDXL-SitRep)
Members of the OASIS Emergency Management TC have voted to adopt the "RF on RAND" Intellectual Property Rights (IPR) mode for their work. As defined in the OASIS IPR Policy, "RF on RAND" operates in the same manner as RAND, however, it does not permit the patent holder to charge fees or royalties for the license (http://www.oasis-open.org/who/intellectualproperty.php).
For more information, see the TC Charter and FAQ
Subcommittees
- EM CAP Profiles SC
Subcommittee formed to review the DHS FEMA/IPAWS "Common Alerting Protocol (CAP) v1.1 Profile Requirements" document to refine and formalize technical specifications and create an "IPAWS Common Alerting Protocol (CAP) Version 1.1 Profile", in order to support CAP within the U.S. Emergency Alert System (EAS).
- EM GIS SC
Ensures the proper use and integration of these geographic standards into the development of Emergency Management interoperability standard.
- EM Infrastructure Framework SC
Produces a horizontal intellectual effort predicated on establishing a common set of EM infrastructure standards, regardless of originating industry and/or agency segment.
- EM Messages and Notification SC
Addresses procedures and formats for exchanging new and updated information related to functions including public safety, emergency response and homeland security.
- EM Reference Information Model SC
Conducts the work of creating the EDXL-RIM specification. The purpose of the EDXL-RIM specification is to provide a high-level, abstract, information model for the family of EDXL specifications.
- EM Adoption SC
The former EM Adoption SC has migrated to the OASIS Emergency Management Adoption TC
Technical Work Produced by the Committee
Expository Work Produced by the Committee
External Resources
Although not produced by the OASIS Emergency TC, the following information offers useful insights into its work.
Mailing Lists and Comments
emergency: the list used by TC members to conduct Committee work. TC membership required to post. TC members are automatically subscribed; the public may view archives.
emergency-comment: a public mail list for providing input to the OASIS emergency Technical Committee members. Subscribe or view archives.*
emergency-dev: an unmoderated, public mail list that provides an open forum for developers to exchange ideas and information on implementing the emergency OASIS Standard. Subscribe or view archives.*
*To minimize spam, you must subscribe to these lists before posting.
Additional Information
Meeting Schedule:
- TC Meetings: Regular TC conference call is held every other Tuesday at 12:00 P.M. EST/EDT
- Subcommittee Meetings: Please see appropriate subcommittee page for specifics.
In The News:
press coverage can be found under the press link in the above purple box.
|
