Lists Home |
Date Index |
A new OASIS technical committee is being formed. The OASIS Emergency
Management Technical Committee (EM TC) has been proposed by the
following members of OASIS: Allen Wyke, Blue292, Inc.; Rick Carlton,
ETeam, Inc.; Joyce Kern, SunGard Planning Solutions; Gary Ham, DMI-S;
Karl Kotalik, NC4; Dave Robinson, Wells Fargo N.A.; and Jay Clark, Ship
The proposal for a new TC meets the requirements of the OASIS TC Process
(see http://oasis-open.org/committees/process.shtml), and is appended to
this message. The proposal, which includes a statement of purpose, list
of deliverables, and proposed schedule, will constitute the TC's
charter. The TC Process allows these items to be clarified (revised) by
the TC members; such clarifications (revisions), as well as submissions
of technology for consideration by the TC and the beginning of technical
discussions, may occur no sooner than the TC's first meeting.
To become a member of this new TC you must 1) be an employee of an OASIS
member organization or an Individual member of OASIS; 2) notify the TC
chair, Allen Wyke (email@example.com) of your intent to participate at
least 15 days prior to the first meeting; and 3) attend the first
meeting on 11 February. You should also subscribe to the TC's mail list.
Note that membership in OASIS TCs is by individual, and not by
organization. You must be eligible for participation at the time you
time you notify the chair.
The private mail list firstname.lastname@example.org is for committee
discussions. TC members as well as any other interested OASIS members
should subscribe to the list by going to the mail list web page at
http://lists.oasis-open.org/ob/adm.pl, or by sending a message to
email@example.com with the word "subscribe" as the
body of the message. (Note that subscribing to the mail list does not
make you a member of the TC; to become a member you must contact the TC
chair and attend the first meeting as described in the preceeding
A public comment list will be available for the public to make comment
on the work of this TC; a message may be sent to the TC via the address
The archives of both of these mail lists are visible to the public at
Further information about this topic may be found on the Cover Pages at
http://xml.coverpages.org/emergencyManagement.html "XML and Emergency
Karl F. Best
Vice President, OASIS
+1 978.667.5115 x206
1. Name of Technical Committee
The name of the committee shall be the Emergency Management Technical
The TC may constitute subcommittees or other groupings as necessary and
appropriate to carrying out the TC's purpose.
2. Statement of Purpose
In a world where a risk is present in everything we do, from breathing
air to responding to natural and man-made disasters, there is an
enormous need to remove any barriers that prevent or hinder data,
communication, and technology interoperability. Many of the barriers are
inherit side effects of bringing together diverse people, cultures,
geographical locations, and systems, but today's technology can and
should be used to help bridge gaps and overcome these obstacles.
Specifically, applications can be empowered to support open structured
information standards, which can then provide mechanisms to leverage
disparate data, any services, and functional assets.
In order to advance the fields of incident preparedness and response in
addition to emergency management, the Emergency Management TC has been
formed. The purpose of the TC is to design, develop, and release XML
Schema-based standards that begin to solve these real-world problems.
These standards will not only provide a framework for data exchange, but
also for functionality and service accessibility, all with the common
goal of seamless application and data interoperability.
The core scope of this activity shall include, but is not limited to:
- Unified incident identification
- Emergency GIS data accessibility and usage
- Notifications methods and messages
- Situational reporting
- Source tasking
- Asset and resources management
- Monitoring and data acquisition systems
- Staff, personnel and organizational management
3. Deliverables and Schedule
- Q1 2003: Research to find any related XML-based DTDs and XSD schemas
that should be considered or included in our efforts. This will be done
in collaboration with OASIS and/or other relevant national standards
bodies and authorities. Blue292, Inc. intends to contribute a
notification specification and form data collection specification to the
new TC at its first meeting for consideration as the basis of work.
- Q2 2003: Delivery of first draft of the first XML-based standard from
- Q3 2003: Design compliance test suite and scenarios to assist
implementers of the Emergency Management standards.
- Q3 2003: Publish best practices to be used by implementers of the
Emergency Management standards.
- Q4 2003: Committee approval of first specification to be submitted for
consideration as OASIS standard.
All business will be conducted in English.
5. Meeting Schedule
- The first meeting will be a teleconference held by phone on February
- Teleconferences at one-week intervals following formation of the
Emergency Management TC until further notice.
- Face-to-face meetings, which will be one and a half to two days in
length, will be held quarterly at location to be determined by the TC.
6. Eligible Persons
- Allen Wyke (firstname.lastname@example.org), Blue292, Inc.
- Rick Carlton (email@example.com), E Team, Inc.
- Joyce Kern (firstname.lastname@example.org), SunGard Planning Solutions
- Gary Ham (email@example.com), DMI-S
- Karl Kotalik (firstname.lastname@example.org), NC4
- Dave Robinson (email@example.com), Wells Fargo N.A.
- Jay Clark (firstname.lastname@example.org), Ship Analytics
7. TC Chairs
- Chair: Allen Wyke, Blue292
- Vice Chair: Rick Carlton, E Team, Inc.
8. Phone Meeting Sponsors
- E Team, Inc.
9. Face-to-Face Meeting Sponsors
- E Team, Inc.
- Blue292, Inc.