Re: [emergency-msg] About cap:event_cat

["R. Allen Wyke" <emtc@nc.rr.com>]

Sounds like a plan to me!

On Tue, 2003-06-17 at 23:15, Art Botterell wrote:
> Allen -
> 
> Last week the SC discussed what we now call <category> at some 
> length, and Jerry Weltman volunteered to undertake another review of 
> this vexing topic.  He did so, and his recommendation to this 
> morning's SC call was that we stick with the existing set of codes 
> (Option III).
> 
> We do have a generic mechanism as well, of course, in the form of 
> <event>, which permits a free-text description of the event.  ( 
> <category> is intended for computers, <event> for the humans.)
> 
> With all its flaws, the current category list represents a consensus 
> hammered out over a year and a half by 130+ participants in the 
> Working Group and now ratified, with due caution, by the SC.
> 
> - Art
> 
> At 10:26 PM -0400 6/17/03, R. Allen Wyke wrote:
> >Have you put any thought on creating a generic mechanism, so that each
> >of these options (well, 1 - 3 anyway) are nothing more than use cases of
> >that mechanism? In short, give it a voice box and allow the
> >implementor's to decide what language they want that voice box to speak.
> >Birds of a feather flock together, so the concerns of fragmenting the
> >space might not been too bad.
> >
> >Just a chip in the table, to see if it sticks - Allen
> >
> >On Sat, 2003-06-07 at 20:44, Art Botterell wrote:
> >>  Friends -
> >>
> >>  Having wrestled with this item for some time in conversation with a
> >>  number of folks, I've been unable to locate a comprehensive and
> >>  universal categorization of alert-worthy events.  Maybe the best we
> >>  can hope for is one that's conventional.  Here are four options:
> >>
> >>
> >>  OPTION I - Adopt the scheme developed for the Disaster Help Portal:
> >>
> >>  - biological: an intentional or accidental disaster event caused by a
> >>  biological agent such as anthrax.
> >>  - chemical (Used For: poison, pollution, toxic, hazmat,
> >>  contamination): an intentional or accidental disaster event caused by
> >>  a chemical agent such as a poisonous gas.
> >>  - civil (Used For: refugee, riot, war)
> >>  - disease (Used For: epidemic, pandemic)
> >>  - drought (Used For: climate, water)
> >>  - earthquake
> >>  - electric utility  (Used For: power outage, blackout)
> >>  - explosion (Used For: bomb)
> >>  - fire (Used For: wildfire, forest fire, urban wild-land interface)
> >>  - flood
> >>  - food (Used For: famine)
> >>  - gas utility
> >>  - hurricane (Used For: tropical cyclone, typhoon)
> >>  - internet (Used For: cyber crime, cyber attack, cyberspace)
> >>  - landslide (Used For: avalanche, mudslide)
> >>  - nuclear
> >>  - ocean or coastal (Used For: iceberg, tsunami, coastal hazard, algal bloom)
> >>  - oil spill
> >>  - radiological (Used For: nuclear reactor, dirty bomb)
> >>  - severe weather (Used For: blizzard, dust storm, hail storm, heat
> >>  wave, lightning, storm, snow storm, wind)
> >>  - space (Used For: asteroid, geomagnetism, magnetic storm, space weather)
> >>  - terrorism
> >>  - tornado
> >>  - transportation (Used For: airplane, highway, ship, train, aircraft)
> >>  - volcano
> >>
> >>  (A long list, a bit of a mixed bag of causes and effects, but at
> >>  least it stands on an honorable precedent.)
> >>
> >>
> >>  OPTION II - Use the twelve Emergency Support Functions (ESFs) as
> >>  defined in the Federal Response Plan:
> >>
> >>  1 - Transportation
> >>  2 - Communications
> >>  3 - Public Works and Engineering
> >>  4 - Firefighting
> >>  5 - Information and Planning
> >>  6 - Mass Care
> >  > 7 - Resources
> >  > 8 - Health and Medical
> >  > 9 - Search and Rescue (yes, I'm cheating a bit here, since ESF-9 is
> >  > actually "Urban Search and Rescue" but that strikes me as possibly a
> >  > bit too restrictive for our purpose.)
> >>  10 - Hazardous materials
> >>  11 - Food
> >>  12 - Energy
> >>
> >>  (This would shift the focus from the nature of the event to the
> >>  response systems which might be engaged.  It's relatively compact.)
> >>
> >>
> >>  OPTION III - Stick with (or fine-tune) the existing list from
> >>  previous CAP drafts:
> >>
> >>  "Geo" - Geophysical (inc. landslide)
> >>  "Met" - Meteorological (inc. flood)
> >>  "Safety" - General emergency and public safety
> >>  "Security" - Law enforcement, military, homeland and local/private security
> >  > "Rescue" - Rescue and recovery
> >>  "Fire" - Fire suppression and rescue
> >>  "Health" - Medical and public health
> >>  "Env" - Pollution and other environmental
> >>  "Transport" - Public and private transportation
> >>  "Infra" - Utility, telecommunication, other non-transport infrastructure
> >>  "Other" - Other events
> >>
> >>
> >>  OPTION IV - Dispense with this item altogether.  That would leave
> >>  automatic filters with the geographic targeting and the
> >>  Urgency/Severity/Certainty cube, but it would make it harder to
> >>  implement specialized alerting functions.  (Then again, are
> >>  specialized alerting functions a solution or a problem?)
> >>
> >>
> >>  Your thoughts?
> >>
> >>  - Art
> >>
> >>
> >>
> >>  --
> >>  To unsubscribe, e-mail: emergency-msg-unsubscribe@lists.oasis-open.org
> >>  For additional commands, e-mail: emergency-msg-help@lists.oasis-open.org
> >
> >
> >
> >--
> >R. Allen Wyke
> >Chair, Emergency Management TC
> >emtc@nc.rr.com
> >http://www.oasis-open.org/committees/emergency
-- 
R. Allen Wyke
Chair, Emergency Management TC
emtc@nc.rr.com
http://www.oasis-open.org/committees/emergency