OASIS Emergency Management Adoption TC
Supporting widespread implementation of EDXL standards including CAP through education and market awareness
Table of Contents
- Technical Work Produced by the Committee
- Expository Work Produced by the Committee
- External Resources
- Mailing Lists and Comments
- Additional Information
- 100715: First run of EDXL-101 completed
Registered: 170+; attended: 104
- 100601: EM-TC seeks feedbacks from users of emergency response standards
The Emergency Management TC seeks input from users who have implemented the EDXL-Distribution Element (DE). Use cases, requirements for new elements, enhancement to existing elements, and other suggestions are welcome. This feedback will form the basis for discussion and consensus on possible changes and enhancements to EDXL-Distribution Element.The following link will take the reader to a letter from the chair with specific information about what information is being sought and how to submit comments via the normal OASIS comment method.
- 090514: three subcommittes have been formed (see below)
- 090501: Inaugural meeting
Participation in the OASIS Emergency Management Adoption Committee is open to all interested parties, including emergency management professionals, solution providers, government agencies, and consultants. Contact email@example.com for more information on joining the Committee.
Governments around the world are mandating the use of the Common Alerting Protocol (CAP) and Emergency Data Exchange Language (EDXL) standards. The OASIS Emergency Management Adoption Committee works to raise awareness and provide education on the best ways to implement CAP and the family of EDXL standards including the Distribution Element (DE), Hospital AVailability Exchange (HAVE), and Resource Management (RM).
The Committee provides a neutral ground where implementers and solution providers can connect, share experiences, and learn how best to deploy implementation programs. The group works closely with the OASIS Emergency Management Committee, where the CAP and EDXL specifications are advanced.
- Emergency Management Adoption Events & Demos Subcommittee: this SC shall work on organizing speakers and topics for events that the EM Adoption TC decides to support. They shall also be responsible for organizing scenarios and planning of OASIS Interop events
- Emergency Management Adoption Collateral & Documents Subcommittee: this SC shall be responsible for writing or editing whitepapers, primers, slide presentations, etc.
- Emergency Management Adoption Outreach & Education Subcommittee: this SC shall be responsible for identifying, building and maintaining relationships with external organizations. It shall also support communities of interest such as the meteorological community to promote the global adoption of the CAP OASIS Standard (and ITU-T X.1303) by weather and meteorological agencies world-wide
This Committee has not produced technical work yet.
- Overview of EDXL Emergency Standards Video
- OASIS EDXL Datasheet
- OASIS EDXL Product Directory
- July 15, 2010 original presentation:
This one-hour briefing on the EDXL suite of standards provides an overview of EDXL and explains how implementation can enhance interoperability and information sharing capabilities in the emergency management and response domains.
The presentation highlights the Common Alerting Protocol (CAP) and the Distribution Element (DE), and includes specific implementation examples.
The webinar also provides an overview of the NIMS Supporting Technology Evaluation Program which reviews EDXL products and publishes reports on the Responder Knowledge Base website.
- July 15, 2010 original presentation:
- WCDM 2010 Conference:
- June 8, 2010 Poster session - download poster
Although not produced by the OASIS Emergency Adoption Committee, the following information offers useful insights into its work:
- OASIS Emergency Interoperability Member Section
- OASIS EDXL Standards LinkedIn Group
- Cover Pages Report
Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.