OASIS TC Formation 1. Name of Technical Committee The name of the committee shall be the Emergency XML (EM-XML) Technical Committee (TC). The Technical Committee may constitute subcommittees or other groupings as necessary and appropriate to carrying out the Technical Committee's purpose. 2. Statement of Purpose In a world where a risk is present in everything we do, from breathing air and 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 management and emergency preparedness and response, the EM-XML Technical Committee has been formed. The purpose of the Technical Committee 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: o Unified incident identification o Emergency GIS data accessibility and usage o Notifications methods and messages o Situational reporting o Source tasking o Asset and resources management o Monitoring and data acquisition systems o Staff, personnel and organizational management 3. Deliverables and Schedule o 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. o Q2 2003: Delivery of first draft of the first XML-based standard from the group. o Q3 2003: Design compliance test suite and scenarios to assist implementers of the EM-XML standards. o Q3 2003: Publish best practices to be used by implementers of the EM-XML standards. o Q4 2003: Delivery of first official OASIS standard. 4. Language All business will be conducted in English. 5. Meeting Schedule o The first meeting will be a teleconference held by phone on February 6th, 2003. o Teleconferences at one-week intervals following formation of the EM-XML TC until further notice. o 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 o Allen Wyke (awyke@blue292.com), Blue292, Inc. o Rick Carlton (rcarlton@eteam.com), E Team, Inc. o Joyce Kern (joyce.kern@sungard.com), SunGard Planning Solutions o Gary Ham (hamg@battelle.org), DMI-S o Karl Kotalik (karl.kotalik@nc4.us), NC4 o Dave Robinson (robinson1d@netscape.net), Wells Fargo N.A. o Jay Clark (jclark@shipanalytics.com), Ship Analytics 7. TC Chairs o Chair: Allen Wyke, Blue292 o Vice Chair: Rick Carlton, E Team, Inc. 8. Phone Meeting Sponsors o E Team, Inc. 9. Face-to-Face Meeting Sponsors o E Team, Inc. o Blue292, Inc.