OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Fwd: Messages for Standardization - EDXL Standard Format for Resource Messaging

Dear EM-TC Members,

Attached are a letter and draft standards from the EIC for the EDXL resource standards development effort.  As before with the EDXL Distribution Element, we will need to review this package and determine if this work falls under the existing charter of the TC.  If it does, we will then decide whether to adopt this task.  As we have discussed over the past month, our TC structure needs to be reviewed to ensure that we can move through the process most efficiently for this new work, consider the sensor effort and support the comment period for the DE. 

Please review this submittal and be prepared to discuss the following during our 9/6 regular TC call:
1.  Does this work fall under the existing charter?
2.  Do we agree to take this on as a work product?
3.  How shall we structure our work to most efficiently address this effort?
4.  Is there any additional information or support we need from the EIC and the DHS/DM program

Feel free to start discussion on this list prior to the meeting.

Regards,
Elysa Jones, Chair
OASIS EM-TC
Engineering Program Manager
Warning Systems, Inc.
256-880-8702 x102
256-694-8702


X-Symantec-TimeoutProtection: 0
Delivered-To: ejones@warningsystems.com
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:mime-version:content-type;
        b=rdymE0VFLLFsAE4mXdYZAnXZKl+hSEIPnXa+5DtJF5r5IxYwPavewUmD+TrttefPqbkAZR7ZoIMmrSDaBzeqDM7FOVqCO1Fsj9ItaLE4TvqQhahy4tr1lPNIvl3OaYIwyvCdLykb5CDaW0lIZg7S4/7mwnwFHnbcJe/MczB2zg4=
Date: Mon, 29 Aug 2005 09:58:19 -0700
From: Matt Walton <mwalton3@gmail.com>
To: Elysa Jones <ejones@warningsystems.com>
Subject: Messages for Standardization - EDXL Standard Format for Resource Messaging
Cc: "Hines, Chip" <chip.hines@dhs.gov>, David Aylward <daylward@comcare.org>,
        "Kalin, Bill" <Bill.Kalin@associates.dhs.gov>,
        jsridgley@longbranchsystems.com, Art Brodsky <artbrodsky@yahoo.com>,
        "Baker, Ashley" <ashley.baker@associates.dhs.gov>,
        tgrapes@evolutiontechinc.com,
        "Tincher, Lee" <Lee.Tincher@associates.dhs.gov>
X-Virus-Scanned: ClamAV 0.83/1045/Sun Aug 28 12:03:55 2005 on magneto.pns.networktel.net
X-Virus-Status: Clean
X-NAS-Bayes: #0: 0; #1: 1
X-NAS-Classification: 0
X-NAS-MessageID: 46184
X-NAS-Validation: {4FFF9F5B-0862-47C2-858F-59F6F684AC80}

August 28, 2005

 

Ms. Elysa Jones, Chair

OASIS Emergency Management Technical Committee

c/o Warning Systems, Inc.

6767 Old Madison Pike, Suite 110

Huntsville, Alabama 35806

 

SUBJECT:  Messages for Standardization - EDXL Standard Format for Resource Messaging


Dear Elysa:

 

On behalf of the Emergency Interoperability Consortium (EIC), and with the concurrence of the Department of Homeland Security's Disaster Management e-Gov Initiative and the Standards Working Group it has sponsored, I would like to submit the attached documents for standards review and formalization by the Emergency Management Technical Committee (EM-TC) under the OASIS process.  

 

This proposal provides an initial set of fourteen resource messages for standardization.  The attached documents provide requirements and message definition across the scope of Emergency Data Exchange Language (EDXL) Resource Messages listed below:  

 
  1. "Request Resource"
  2. "Response to Request Resource"
  3. "Order Resource"
  4. "Dispatch Resource"
  5. "Request for Resource Information (RFI)"
  6. "Response to Request for Resource Information (RFI)"
  7. "Unsolicited Resource Offer"
  8. "Release Resource"
  9. "Request to Return Resource"
  10. "Response to Request Return Resource
  11. "Request Resource Quote"
  12. "Response to Request Resource Quote"
  13. "Request for Resource Status"
  14. "Resource Request Status"

 

Included with this proposal is a list of messages recently submitted by Jon Skeels representing the USDA Forest Service and the ROSS system.   Jon and his colleagues were very involved with and supportive of this process.  Although it is believed that most of this list is represented in the core documentation, this document is submitted for additional consideration by the EM-TC, and may result in definition of additional resource messages.

 

Taken together, these messages provide a foundation for integrated EDXL Resource communication to permit rapid and efficient data sharing among data systems used for incident and event management by all emergency response professions.  

 

This proposal was developed by the Disaster Management-sponsored EDXL Standards Working Group, a broad community of incident management practitioners representing almost every emergency response profession.   All such professions were invited to participate throughout the development of these proposed messages.  The practitioners made resource messaging a priority to begin with, and then drove the requirements process throughout.   The practitioners have been advised by a diverse group of federal agency representatives, and industry and technical experts (including several EIC members), and supported by a team from the DHS Disaster Management program.   This process has consumed six months and a large number of meetings and conference calls.  Representative subcommittees worked through 4 detailed scenarios to test the straw man messages.   After final SWG approval, we held a special meeting of the EIC membership to discuss and then approve it.  This week our Board voted unanimously to submit the proposed standards to OASIS.  

 

 

As you know, fostering the development of practitioner-driven data interoperability standards through a public-private partnership is one of the key activities of the President's Disaster Management e-Gov Initiative. The Disaster Management Program has been a strong supporter of the efforts reflected in the attached materials.   DM has been most appreciative of the excellent work that resulted from the EIC and EM-TC's involvement in bringing forth the Common Alerting Protocol, the EDXL Distribution Element and other projects.   Given the urgent national need to address the interoperability problem with a coherent framework of valid national data standards, the EIC and the EM-TC have been asked to accelerate our efforts – particularly in support of the emergent National Incident Management System.

 

I would therefore like to ask that you and the EM-TC review these materials at your earliest convenience to verify that they fit within the EM-TC charter.   This proposal represents an urgent and key set of standards.  We need for OASIS and your Technical Committee to mobilize its technical expertise, process and membership to refine and formalize these standards quickly so they can be implemented by industry during the coming year.

 

Please let me know if there is anything the EIC can do to help you move this effort forward quickly.

 

 

 Sincerely,

 

 

 

Matt Walton

Chairman,

Emergency Interoperability Consortium

 

Cc:

 

Attachments:    

·         EDXL Standard Format for Resource Messaging

·         EDXL Standard Format for Resource Messaging –XML Schema

·         Proposed EDXL Message List" – Jon Skeels (USDA Forest Service and the ROSS system)

 

EDXL_ResourceDraft_OASIS082005[1].doc

<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2005 rel. 3 U (http://www.altova.com) by Tim Grapes (self) -->
<schema xmlns="http://www.w3.org/2001/XMLSchema"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:rm="urn:oasis:names:tc:emergency:EDXL:RM:1.0" targetNamespace="urn:oasis:names:tc:emergency:EDXL:RM:1.0" elementFormDefault="qualified" attributeFormDefault="unqualified">
	<element name="EDXLResourceMessage">
		<annotation>
			<documentation>The container element of a Resource management message used in conjunction with the EDXL Distribution Element</documentation>
		</annotation>
		<complexType>
			<sequence>
				<element name="ResourceMessage">
					<complexType>
						<sequence>
							<element name="RequestNumber" type="string">
								<annotation>
									<documentation>Each EDXL resource message contains an identifier "Request Number" that uniquely identifies each resource message. The EDXL Distribution Element contains the "Distribution ID", which identifies the "container" for the distribution message information.</documentation>
								</annotation>
							</element>
							<element name="SentDateTime" type="dateTime">
								<annotation>
									<documentation>The system stamped date and time the resource message was sent</documentation>
								</annotation>
							</element>
							<element name="RequestStatusKeyword" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>where the content of “valueListUrn” is the Uniform Resource Name of a published list of values and definitions, and the content of “value” is a string denoting the value itself .  </documentation>
								</annotation>
								<complexType>
									<sequence>
										<element ref="rm:value"/>
										<element ref="rm:valueListUrn"/>
									</sequence>
								</complexType>
							</element>
							<sequence>
								<element name="Contact">
									<complexType>
										<sequence>
											<element name="NameTitle" type="string" minOccurs="0">
												<annotation>
													<documentation>Person name or organization title referred to in ResourceMessage</documentation>
												</annotation>
											</element>
											<element name="Phone" type="positiveInteger" minOccurs="0" maxOccurs="unbounded">
												<annotation>
													<documentation>Contact phone number of the person  or organization referred to in ResourceMessage</documentation>
												</annotation>
											</element>
											<element name="email" type="string" minOccurs="0" maxOccurs="unbounded">
												<annotation>
													<documentation>Contact email address of the person or organization referred to in ResourceMessage</documentation>
												</annotation>
											</element>
											<element name="RadioFrequency" type="string" minOccurs="0" maxOccurs="unbounded">
												<annotation>
													<documentation>Contact radio frequency of the person or organization referred to in ResourceMessage</documentation>
												</annotation>
											</element>
										</sequence>
									</complexType>
								</element>
							</sequence>
							<element name="Requester" type="nonNegativeInteger">
								<annotation>
									<documentation>The person  or organization sending the request for resources</documentation>
								</annotation>
							</element>
							<element name="SME" type="anySimpleType" minOccurs="0">
								<annotation>
									<documentation>Person name or organization title of the person (subject matter expert) or organization that can answer questions or provide additional details regarding the request.</documentation>
								</annotation>
							</element>
							<element name="Response" minOccurs="0">
								<annotation>
									<documentation>Person name or organization title of the person or organization responding to the request.</documentation>
								</annotation>
							</element>
							<element name="FundCode" type="string" minOccurs="0">
								<annotation>
									<documentation>Identifies the funds that will pay for the resource - Identified in support of NIMS</documentation>
								</annotation>
							</element>
							<element name="ApproveNameTitle" type="string" minOccurs="0">
								<annotation>
									<documentation>Person Name or organization who reviewed, signed off, or otherwise approved the request or order</documentation>
								</annotation>
							</element>
						</sequence>
					</complexType>
				</element>
				<element name="Resource">
					<complexType>
						<sequence>
							<element name="ResourceKeyword" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>Any value from a discrete managed list, used to specify a resource. where the content of “valueListUrn” is the Uniform Resource Name of a published list of values and definitions, and the content of “value” is a string denoting the value itself</documentation>
								</annotation>
								<complexType>
									<sequence>
										<element ref="rm:value"/>
										<element ref="rm:valueListUrn"/>
									</sequence>
								</complexType>
							</element>
							<element name="ResourceID" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>This identifier (if available) must follow the resource / resource description during the entire trail of messages about that resource.  May be selected via the ResourceKeyword if available.</documentation>
								</annotation>
							</element>
							<element name="ResourceTitle" type="string" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>A name or title of the resource.  May be selected via the ResourceKeyword if available.</documentation>
								</annotation>
							</element>
							<element name="ResourceDescription" type="anySimpleType" nillable="true" maxOccurs="unbounded">
								<annotation>
									<documentation>Free Text alternative to "Resource Keyword" (or may be used in addition).  Any description of resource or resource characteristics, situation requiring resource assistance, statement of mission resource must satisfy, or RFI text.</documentation>
								</annotation>
							</element>
							<element name="Quantity" type="nonNegativeInteger" minOccurs="0">
								<annotation>
									<documentation>Number of resources</documentation>
								</annotation>
							</element>
							<element name="SpecialNeeds" type="string" nillable="true" minOccurs="0">
								<annotation>
									<documentation>A description of any special needs related to the requested resource (e.g. must carry protective equipment)</documentation>
								</annotation>
							</element>
						</sequence>
					</complexType>
				</element>
				<element name="Info">
					<complexType>
						<sequence>
							<element name="RequestedLocation" minOccurs="0">
								<annotation>
									<documentation>Where the requested resource is needed.  Completed for Resource requests, returns, etc.   Uses the “Location” message elements to specify the Location</documentation>
								</annotation>
							</element>
							<element name="ReportToLocation" type="anySimpleType" minOccurs="0">
								<annotation>
									<documentation>Where the requested resource is to report-to, or checks in at the destination.  This location may be different than the “Requested Location”.  Completed for Resource requests, returns, etc.   Uses the "Location" message elements to specify the “Report To Location”</documentation>
								</annotation>
							</element>
							<element name="RequestedArrivalDateTime" type="dateTime" minOccurs="0">
								<annotation>
									<documentation>When the resource is needed.  Completed for Resource requests, returns, etc.   </documentation>
								</annotation>
							</element>
							<element name="AnticipatedIncidentAssignment" type="anySimpleType" minOccurs="0">
								<annotation>
									<documentation>Anticipated function, task, job, or role to be provided by the requested resource.</documentation>
								</annotation>
							</element>
							<element name="AnticipatedReturnDateTime" type="dateTime" minOccurs="0">
								<annotation>
									<documentation>When the resource is expected to be returned or DEMOBed.  Completed for a “Request Resource”.  This element with the “Requested Arrival Date / Time” provides the estimated duration of resource deployment.</documentation>
								</annotation>
							</element>
							<element name="AcceptDeclineRequest" type="dateTime" minOccurs="0">
								<annotation>
									<documentation>When the resource is expected to be returned or DEMOBed.  Completed for a “Request Resource”.  This element with the “Requested Arrival Date / Time” provides the estimated duration of resource deployment.</documentation>
								</annotation>
							</element>
							<element name="DeclineReason" type="boolean" minOccurs="0">
								<annotation>
									<documentation>Used to accept or decline a Request, Response, Unsolicited Offer, or a Request Return.  "Decline" indicates the request, response or offer is not accepted.</documentation>
								</annotation>
							</element>
							<element name="NavigationInstructions" type="anySimpleType" minOccurs="0">
								<annotation>
									<documentation>Explanation for a declined Request, Response, Unsolicited Offer, or a Request Return.</documentation>
								</annotation>
							</element>
							<element name="ReportingInstructions" type="anySimpleType" minOccurs="0">
								<annotation>
									<documentation>Instructions that define how to get to the “report to location”</documentation>
								</annotation>
							</element>
							<element name="ResourceStatusKeyword" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>Any value from a discrete managed list, used to specify the general state of a resource if known.  where the content of “valueListUrn” is the Uniform Resource Name of a published list of values and definitions, and the content of “value” is a string denoting the value itself .  Multiple instances MAY occur.</documentation>
								</annotation>
								<complexType>
									<sequence>
										<element ref="rm:value"/>
										<element ref="rm:valueListUrn"/>
									</sequence>
								</complexType>
							</element>
							<element name="CurrentLocation" type="anySimpleType" minOccurs="0">
								<annotation>
									<documentation>Where the requested resource is needed.  Completed for Resource requests, returns, etc.   Uses the “Location” message elements to specify the Location</documentation>
								</annotation>
							</element>
							<element name="AvailableDate" type="dateTime" minOccurs="0">
								<annotation>
									<documentation>When the resource is available for use.  Completed in response to a resource message.</documentation>
								</annotation>
							</element>
							<element name="OrderNumber" type="string" minOccurs="0">
								<annotation>
									<documentation>Number or ID assigned by the ordering system or personnel meeting the request for resources that has been made.</documentation>
								</annotation>
							</element>
							<element name="CommitedDate" type="dateTime" minOccurs="0">
								<annotation>
									<documentation>When specified resource is committed to a request or order.  Completed in response to a resource message.  Specified resource is no longer available to be applied to other resource requests</documentation>
								</annotation>
							</element>
							<element name="PriceQuote" type="positiveInteger" minOccurs="0">
								<annotation>
									<documentation>Quoted cost to acquire a desired resource.  Complete in response to a “Request Resource Quote”</documentation>
								</annotation>
							</element>
							<element name="ConditionDescription" type="anySimpleType" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>Description of a condition governing the availability of resources.  E.g. condition for number of beds available may be "if patents have insurance"</documentation>
								</annotation>
							</element>
							<element name="PlaceOfDeparture" type="anySimpleType" minOccurs="0">
								<annotation>
									<documentation>The location where the specified resource is departing from when transported to or from an Incident.  Uses the "Location" message elements to specify the “Place of Departure”</documentation>
								</annotation>
							</element>
							<element name="ModeOfTransportation" type="anySimpleType" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>Method or mode used to transport the resource to or from the incident</documentation>
								</annotation>
							</element>
							<element name="EstimatedDepartureDateTime" type="dateTime" minOccurs="0">
								<annotation>
									<documentation>When the resource is expected to depart from its current location for transit to a “Report-to Location”</documentation>
								</annotation>
							</element>
							<element name="EstimatedArrivalDateTime" type="dateTime" minOccurs="0">
								<annotation>
									<documentation>When the resource is expected to arrive at its “Report To Location”. </documentation>
								</annotation>
							</element>
							<element name="ActualDepartureDateTime" type="dateTime" minOccurs="0"/>
							<element name="ActualArrivalDateTime" type="dateTime" minOccurs="0">
								<annotation>
									<documentation>Actual date and time of arrival of the resource a “Report To Location”.   </documentation>
								</annotation>
							</element>
						</sequence>
					</complexType>
				</element>
				<element name="Location">
					<complexType>
						<sequence>
							<element name="Address" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="AddressGrid" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="Area" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>See GJXDM definition- has pt, circle, polygon…)</documentation>
								</annotation>
							</element>
							<element name="CrossStreet" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="GeographicCoordinate" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="Highway" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="Locale" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="Location" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="MapLocation" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="MGRSCoordinate" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="RelativeLocation" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="UTMCoordinate" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="Altitude" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
							<element name="Depth" minOccurs="0" maxOccurs="unbounded">
								<annotation>
									<documentation>(See GJXDM definition)</documentation>
								</annotation>
							</element>
						</sequence>
					</complexType>
				</element>
			</sequence>
		</complexType>
	</element>
	<element name="value" type="string">
		<annotation>
			<documentation>
			A Value from a certified list maintained by the Community of Interest (COI)
			for the referenced element.
		</documentation>
		</annotation>
	</element>
	<element name="valueListUrn" type="string">
		<annotation>
			<documentation>
			The name of the certified list maintained by the Community of Interest (COI)
			for the value referenced.
		</documentation>
		</annotation>
	</element>
</schema>

Proposed_EDXL_Message_ListSkeels082005[1].doc

















[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]