MHonArc v2.5.0b2 -->
emergency message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: [emergency] Re: Interoperability of XML Schemas
Title: [emergency] Re: Interoperability of XML
Schemas
Deborah, Allen, Everyone,
DMIS implements a CAP API for beta testing:
http://www.cmi-services.org
CAP specifically overlaps ICS201, (Incident Command System form
201), but where that particular piece of work current resides within
DHS is something we don't know. However, during last week's TC
meeting, we discussed the recent release, March 1, 2004 of the DHS
National Incident Management System (152 pages)
http://www.dhs.gov/interweb/assetlibrary/NIMS-90-web.pdf
Specifically, I wrote a strawman .xsd schema based on the data
dictionary developed by David Hall before he left the TC. I uploaded
the file ICS-201-draft0.2.xsd for reference only to the
Resources folder of the EM TC Documents section.
A recent article in the Homeland Security Monitor newsletter of
Intellibridge.com
http://www.intellibridge.com
highlighted ICS (but not the 201 form which was derived from a
Fire Fighters Search and Rescue Incident Command System Form--I have
boldfaced the reference below):
Department of
Homeland Security (DHS) Secretary Tom Ridge announced on 1 March the
approval of the National Incident Management System (NIMS), "the
Nation's first standardized management plan that creates a unified
structure for Federal, state, and local lines of government for
incident response," a DHS statement said. Making the announcement
during an address to the annual meeting of the National Association of
Counties, Ridge said, "NIMS gives all of our Nation's [first]
responders the same framework for incident management and fully put
into practice the concept of, 'One mission, one team, one
fight.'" The new national emergency response plan boosts the
nation's capabilities by "identifying and integrating core
elements and best practices." Key components of the plan include:
Incident Command System (ICS), a unified command that establishes
fives functional areas for managing all major incidents-command,
operations, planning, logistics, and finance/administration-and
provides for coordinated efforts as well as joint decisions; NIMS
Integration Center (NIC) will provide strategic direction and
oversight of the NIMS and develop and facilitate national standards;
Joint Information System (JIS) will provide the public with timely and
accurate incident information and unified public messages, and will
employ Joint Information Centers that bring incident communicators
together during an incident. Ridge called NIMS a "common operating
picture from which we can all work," adding, "As we developed
NIMS, we made sure everyone had a seat at the table. We will call on
[local officials] late to execute the game plan," Nation Journal's
Technology Daily reported.
ANALYSIS: NIMS is
the latest step in the federal government's goal toward issuing a
National Response Plan (NRP), or all-hazards plans. In October 2003,
Secretary Ridge announced the approval of the Initial National
Response Plan (INRP), a roadmap for developing "a unified approach
to domestic incident management" in the U.S. It linked five
emergency response plans and established a coordinating structure for
emergency response personnel across all levels of government. NIMS,
with its standardized incident management processes, protocols and
procedures, will support the INRP until the final NRP, which is under
development, is completed. Unlike the INRP, which will be replaced,
NIMS "will continue to provide the Nation's doctrinal guidance for
incident management for acts of terrorism, natural disasters, and
other emergencies." Despite Ridge's announcement on NIMS, the
system is still not complete, according to Bob Stephen, a special
assistant to Ridge, National Journal's Technology Daily reported.
While he did not have a specific time for when the plan's guidelines
would be finalized, he said once that happened, state and local
government would have until 1 October to comply or risk DHS
withholding homeland security grants.
That's about as specific to CAP overlap of anything I personally
know about.
At 8:33 AM -0500 3/13/04, R. Allen Wyke wrote:
Hello Deborah, and thanx for the email. I
apologize for the delay in responding, but I have been out for the
past 2 weeks.
At this point, the TC has not identified any overlapping schemas,
however we are aware of several contextually related efforts - such as
ACN. Other than what we have listed in our Requirements document (you
can find on our website), we have not formalized a list of these
related efforts. That being said, I have cc:ed the EM TC list. We are
in the process of trying to provide additional information on CAP to
the outside world, and this is a perfect example of the kinds of
things we need.
Thanx again - Allen
On Feb 26, 2004, at 2:55 PM, Folger, Deborah H wrote:
TO: Allen Wyke
OASIS Emergency Management TC Chair
Allen,
I work for Boeing and we are doing some work in the area of
interoperability of XML Schemas, specifically we are experimenting
with auto generating transformation between XML Schemas.
We have been looking at the CAP Schema, and would like to find some
other schemas that overlap in domain with CAP, such as DOD or other
agencies that might need to communicate data with the CAP Schema.
Do you know of any such schemas or do you have any source we could
contact?
We'd appreciate any help you can give us.
Thanks,
Deborah Folger
*BOEING - Phantom Works
Mathematics and Computing Technology
Information Management and Collaborative Technologies
' 425-865-6669 * Deborah.H.Folger@Boeing.com
Telecommuting on Friday use :
' 425-746-7220 or ' 425-466-6031cell
To unsubscribe from this mailing list (and be removed from the roster
of the OASIS TC), go to
http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgroup.php.
Tel: 510-849-2309
Fax: By Request
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]