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: [emergency-comment] CAP v1.2 comments...]

This came in just under the wire. Folks,

I checked the Issues List. This is his original comment, verbatim. We 
deferred it. We should send him the url for the list and tell him our 


-------- Original Message --------
Subject: 	[emergency-comment] CAP v1.2 comments...
Date: 	Mon, 23 Nov 2009 16:23:52 -0500
From: 	Schafer, John <John.Schafer@dhs.gov>
To: 	<emergency-comment@lists.oasis-open.org>

The Alert Message Structure in the CAP appears to have pre-defined 
enumerations for many of the data elements. The concern is that these 
pre-defined enumerations do not necessarily align with the existing 
NUREG-0654/FEMA-REP-1 Appendix 1 Emergency Action Levels (EAL’s) and 
responses used in commercial nuclear emergency preparedness. Under 
emergency situations where the enumerations do not align with the EAL’s, 
there exists potential for IPAWS to communicate messages inconsistent 
(or interpreted to be inconsistent) with those already established 
nuclear power plant emergency alert and notification procedures. Any 
inconsistency could lead to miscommunication, conflicting announcement 
and notification messages, and incorrect public response.

It is recommended that the CAP data elements incorporate flexibility so 
that the user may incorporate their own values or enumerations such that 
the emergency message can be tailored to be consistent with already 
existing announcement and message processes.

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

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