RE: [emergency-msg] Basic SitRep Report Type Block

Looks good to me. Maybe a line or two demonstrating who would use it and how

· Multiple professions reporting any observations, casualties etc. May be duplicative or conflicting between senders and possibly with other SitReps, but a quick standard way to report what they see as input to the formal process and reporting. Does not replace or necessarily re-use SitRep Report types and root.

· May want to add one or two lines of basic “scenarios” or situations where this would typically be used as examples – “quick and dirty” usage outside of formal or controlled processes (e.g. EMT discovers 10 people requiring triage and care, Fire professional discovers a possible hazardous spill coming from a leaking tractor trailer container.).

Thanks,

Tim Grapes

Evotec

"The only thing we take into the next life is our character"

From: Rob Torchon [mailto:rtorchon@yahoo.com]
Sent: Tuesday, March 16, 2010 12:31 PM
To: emergency-msg@lists.oasis-open.org
Subject: [emergency-msg] Basic SitRep Report Type Block

This is my take on what the Basic SitRep Message definition would be.

The Basic SitRep message is defined as a separate report type within the SitRep package that allows the encapsulation of information that is not covered by the other report types, or used as ancillary information to the other report types.

The content of the Basic SitRep would contain as a minimum a basic text block. This would insure that the SitRep can be used regardless of message content.

It is anticipated that the information contained in the Basic SitRep would typically be reviewed by a human in the loop for possible later dispensation.

Typical use cases would be mobile clients, observation reports, sensor data, etc.

emergency-msg message