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: RE: [emergency] Another Thought: Re: [emergency] Re: QuestionRegarding The EM TC

I am actually developing a prototype that will use EDXL-RM on a routine dispatch basis in addition to supporting disaster resource messaging.  For our first pass on the novel dispatch use case we only using a few of the RM messages (Request Resource, Response to Request Resource, Resource Deployment Status) but have had luck thusfar covering the requirements for day to day operations.  If you would like more information please feel free to contact me directly.
Office: 315-838-2669
Cell: 703-595-9375 NEW

-----Original Message-----
From: Rex Brooks [mailto:rexb@starbourne.com] 
Sent: Friday, May 07, 2010 11:17 AM
To: Mary McRae
Cc: Wayne Kewitsch; emergency@lists.oasis-open.org
Subject: [emergency] Another Thought: Re: [emergency] Re: Question Regarding The EM TC

Hi again, Wayne,

Just a note: there are message-specific rules for each message in the EDXL-RM set of pre-defined messages, and you have to check these. I was speaking across the whole range or set of pre-defined messages.

However, since you were specifically asking about RequestResource I should also habve noted that RequestResource:MessageID, RequestResource:SentDataTime, RequestResource:MessageContentType,
RequestResource:OriginatingMessageID, RequestResource:ContactInformation
and RequestResource:ResourceInformation elements MUST be present.

RequestResource:IncidentInformation or RequestResource:IncidentID are not required.


Hi Wayne,

There is no restriction for using EDXL Resource Messaging at any time.
The MessageID, SentDateTime and MessageContentType elements are required. There is an optional IncidentInformation element which is typically used to associate an EDXL-RM message with an incident.

The reason for this, as I recall is that logistics are often arranged before and after a specific disaster, so it would have been onerous to require all RM messages to cite an incident.


Mary McRae wrote:
> Hi Wayne,
> I'm sure Elysa was just swamped and didn't have an opportunity to 
> respond. I'm going to forward your message to the TC and I'm sure 
> someone will be more than happy to speak with you!
> Please feel free to ping me again if you don't hear from someone in a 
> few days.
> Regards,
> Mary
> Mary P McRae
> Director, Standards Development
> Technical Committee Administrator
> OASIS: Advancing open standards for the information society
> email: mary.mcrae@oasis-open.org <mailto:mary.mcrae@oasis-open.org>
> web: www.oasis-open.org <http://www.oasis-open.org>
> twitter: @fiberartisan #oasisopen
> phone: 1.603.232.9090
> Standards are like parachutes: they work best when they're open.
> On May 7, 2010, at 9:42 AM, Wayne Kewitsch wrote:
>> Dear Ms. McRae:
>> I’m a first year student in the National Fire Academy’s Executive 
>> Fire Officer program. Part of the program requires the completion of 
>> an applied research project. My project involves inter-dispatch 
>> notification during mutual/automatic aid requests. I found the EDXL 
>> information online and am wondering if EDXL is capable of making 
>> resource requests on a regular basis vs. solely on a disaster basis.
>> I left a phone message for Ms. Jones but never received a return call.
>> Who would you recommend I speak with regarding my questions?
>> Sincerely,
>> **Wayne Kewitsch** | **Assistant Fire Chief** | **Richfield Fire
>> Department** | 6700 Portland Ave.| Richfield, MN 55423 |
>> 612.243.4501(ph) | 612.866.0297(fax)

Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670

To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:

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