OASIS Emergency Management Technical Committee

Date:      Fri, 10 Jan 2003 09:04:27 -0500
From:      Karl Best <karl.best@oasis-open.org>
To:        members@lists.oasis-open.org, tc-announce@lists.oasis-open.org
Subject:   OASIS TC Call for Participation: Emergency Management TC

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 Analytics.

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 (awyke@blue292.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 emergency@lists.oasis-open.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 emergency-request@lists.oasis-open.org 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 paragraph.)

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 emergency-comment@lists.oasis-open.org.

The archives of both of these mail lists are visible to the public at http://lists.oasis-open.org/archives/

Further information about this topic may be found on the Cover Pages at http://xml.coverpages.org/emergencyManagement.html "XML and Emergency Management".

-Karl


Karl F. Best
Vice President, OASIS
+1 978.667.5115 x206
karl.best@oasis-open.org
http://www.oasis-open.org

Emergency Management Technical Committee Proposed Charter

Name of Technical Committee

The name of the committee shall be the Emergency Management Technical Committee (TC).

The TC may constitute subcommittees or other groupings as necessary and appropriate to carrying out the TC's purpose.

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

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 the group.
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.

Language

All business will be conducted in English.

Meeting Schedule

The first meeting will be a teleconference held by phone on February 11th, 2003.

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.

Eligible Persons

Allen Wyke (awyke@blue292.com), Blue292, Inc.
Rick Carlton (rcarlton@eteam.com), E Team, Inc.
Joyce Kern (joyce.kern@sungard.com), SunGard Planning Solutions
Gary Ham (hamg@battelle.org), DMI-S
Karl Kotalik (karl.kotalik@nc4.us), NC4
Dave Robinson (robinson1d@netscape.net), Wells Fargo N.A.
Jay Clark (jclark@shipanalytics.com), Ship Analytics

TC Chairs

Chair: Allen Wyke, Blue292
Vice Chair: Rick Carlton, E Team, Inc.

Phone Meeting Sponsors

E Team, Inc.

Face-to-Face Meeting Sponsors

E Team, Inc.
Blue292, Inc.

Prepared by Robin Cover for The XML Cover Pages archive. General references in "OASIS Emergency Management TC."

SEARCH Advanced Search ABOUT Site Map CP RSS Channel Contact Us Sponsoring CP About Our Sponsors NEWS Cover Stories Articles & Papers Press Releases CORE STANDARDS XML SGML Schemas XSL/XSLT/XPath XLink XML Query CSS SVG TECHNOLOGY REPORTS XML Applications General Apps Government Apps Academic Apps EVENTS LIBRARY Introductions FAQs Bibliography Technology and Society Semantics Tech Topics Software Related Standards Historic	OASIS Emergency Management Technical Committee Date: Fri, 10 Jan 2003 09:04:27 -0500 From: Karl Best <karl.best@oasis-open.org> To: members@lists.oasis-open.org, tc-announce@lists.oasis-open.org Subject: OASIS TC Call for Participation: Emergency Management TC 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 Analytics. 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 (awyke@blue292.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 emergency@lists.oasis-open.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 emergency-request@lists.oasis-open.org 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 paragraph.) 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 emergency-comment@lists.oasis-open.org. The archives of both of these mail lists are visible to the public at http://lists.oasis-open.org/archives/ Further information about this topic may be found on the Cover Pages at http://xml.coverpages.org/emergencyManagement.html "XML and Emergency Management". -Karl Karl F. Best Vice President, OASIS +1 978.667.5115 x206 karl.best@oasis-open.org http://www.oasis-open.org Emergency Management Technical Committee Proposed Charter Name of Technical Committee The name of the committee shall be the Emergency Management Technical Committee (TC). The TC may constitute subcommittees or other groupings as necessary and appropriate to carrying out the TC's purpose. 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 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 the group. 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. Language All business will be conducted in English. Meeting Schedule The first meeting will be a teleconference held by phone on February 11th, 2003. 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. Eligible Persons Allen Wyke (awyke@blue292.com), Blue292, Inc. Rick Carlton (rcarlton@eteam.com), E Team, Inc. Joyce Kern (joyce.kern@sungard.com), SunGard Planning Solutions Gary Ham (hamg@battelle.org), DMI-S Karl Kotalik (karl.kotalik@nc4.us), NC4 Dave Robinson (robinson1d@netscape.net), Wells Fargo N.A. Jay Clark (jclark@shipanalytics.com), Ship Analytics TC Chairs Chair: Allen Wyke, Blue292 Vice Chair: Rick Carlton, E Team, Inc. Phone Meeting Sponsors E Team, Inc. Face-to-Face Meeting Sponsors E Team, Inc. Blue292, Inc. Prepared by Robin Cover for The XML Cover Pages archive. General references in "OASIS Emergency Management TC."