RE: [emergency-comment] Proposal: add <responseType> element in <info>

["Bob Wyman" <bob@wyman.us>]

	As with the earlier suggestion concerning the CAP enumerated
categories, the enumeration responseTypes and the other enumerations
in the CAP specification are probably best defined in registries that
are external to the CAP specification itself. Additionally, the
registries should be in a machine processable form (Topic Maps is
probably most appropriate format since it has an XML encoding and is
an international standard.). I would also suggest that the enumerators
themselves should be URI's (probably URN's) to ensure that they are
unique and can be used and referenced in the greatest variety of
applications -- thus, encouraging consistency between systems. (also,
see: Published Subject Indicators in the Topic Map documentation.)
	If CAP every gets into a useful form, it is likely to find use
on a scope larger than the current primarily US or English/speaking
world that has driven it so far. While issues with language are
obvious concerns, we should also recognize that other countries and/or
cultures are likely to discover a need to include enumerated values
that are not apparently relevant to those who have been the primary
source of input for CAP so far. The broad adoption of CAP will be
hindered if modifications to the enumerations requires formal updates
to the CAP specification itself.
	Additionally, if CAP is used in an international setting, it
will probably be found that CAP messages are useful in a
multi-country/multi-cultural setting. Thus, there is an almost
inevitable need to support multiple taxonomies and to provide for the
translation of one taxonomy to another. The mechanisms for handling
such a situation are well known, and anticipated by the International
Standard for Taxonomies (Topic Maps).
	Please consider establishing registries for the CAP enumerated
types, using Topic Maps (i.e. XTM) as the method for describing the
enumerations, and using URN's as the values of the enumerators.

		bob wyman


-----Original Message-----
From: Art Botterell [mailto:acb@incident.com] 
Sent: Sunday, March 28, 2004 5:31 PM
To: emergency-comment@lists.oasis-open.org
Subject: [emergency-comment] Proposal: add <responseType> element in
<info>


Some implementers have requested a consistently machine-readable 
coding for the response desired from the alert target audience.  As 
with <category> there appears to be no established all-hazard 
standard for this, but that doesn't mean we can't make a start.

We can address this requirement by adding a new, mandatory, 
enumerated element named <responseType> (or some such) within the 
<info> structure.  This element could be defined as "The code 
denoting the recommended response within the area addressed by this 
message."  The set of enumerated codes might include:

	Evacuate - Begin evacuation immediately.
	Prepare to Evacuate - Make preparations to evacuation and
stand by.
	Shelter In Place - Take shelter and minimize exposure to the
outdoors.
	Prepare to Shelter - Make preparations to shelter and stand
by.
	Monitor News - Monitor news sources for further details and 
instructions.
	Mobilize - Activate pre-existing emergency plans.
	No action - Information only, no action required at this time.

Details and qualifications to these coded instructions would, of 
course, appear in the <instruction> element... this tag would be 
provided to direct automated systems to the appropriate processing... 
e.g., which siren signal, if any, to sound.

- Art

To unsubscribe from this list, send a post to
emergency-comment-unsubscribe@lists.oasis-open.org, or visit
http://www.oasis-open.org/mlmanage/.