[CAP] Definition of Warning Categories

[Art Botterell]

David has it exactly.  I would expect that in some future "CAP 2.0"  
the concept of managed lists might be extended back into CAP...  
assuming interested communities start making headway on building such  
lists.

- Art


On Jul 12, 2009, at 7/12/09 9:54 AM, David Aylward (Comcare) wrote:

> Hannes:
>
> As Art says, CAP's incident list is very general.  To further Art's  
> point,
> when it came to the development of what became the OASIS EDXL  
> Distribution
> Element (DE), we faced the same issue as a primary purpose of the DE  
> is
> routing messages by incident type.  The CAP categories were far too  
> broad
> for that.
>
> So the draft requirements and specification for the DE developed by  
> the
> cross emergency domain practitioner working group developed a  
> detailed list
> of incident types for submission to the OASIS EMTC as part of its  
> request
> for the development of that standard.
>
> The EMTC wisely rejected our suggestion, thinking that (1) the work to
> create a shared incident type taxomony should be done for the US and  
> other
> countries, but hadn't been done yet, and (2) such lists of incident  
> types
> would likely change more frequently than the standard.
>
> So they adopted a flexible solution of "Managed Lists" for this and  
> similar
> list issues (e.g. roles).   Under this approach values such as  
> incident
> names appear in the standard, along with the name of the managed  
> list you
> are using.  If there is only one Managed List for that topic in the  
> world,
> great, but if there are several you can still communicate because  
> you know
> which list is being used.
>
> The absence of both initial managed lists and a repository for their
> locations is an identified gap that hopefully will be addressed  
> soon.  A
> number of us developed a project to do Managed Lists for incident  
> names and
> roles, but other priorities have gotten in the way.
>
>
>
>
> David K. Aylward, President
> COMCARE Emergency Response Technology Group
> 1351 Independence Court, SE
> Washington, DC 20003
> 202.255.3215 (mobile)
> 202.295.0136 (office)
> 202.521.4047 (fax)
> daylward at comcare.org
>
> This communication is intended for the use of the recipient to which  
> it is
> addressed, and may contain confidential, personal and/or privileged
> information. Please contact us immediately if you are not the intended
> recipient of this communication, and do not copy, distribute, or  
> take action
> relying on it. Any communication received in error, or subsequent  
> reply,
> should be deleted or destroyed.
>
>
> -----Original Message-----
> From: cap-list-bounces at lists.incident.com
> [mailto:cap-list-bounces at lists.incident.com] On Behalf Of Art  
> Botterell
> Sent: Sunday, July 12, 2009 11:52 AM
> To: cap-list at incident.com; earlywarning at ietf.org
> Subject: Re: [CAP] Definition of Warning Categories
>
> On Jul 12, 2009, at 7/12/09 3:58 AM, Hannes Tschofenig wrote:
>> I was wondering whether there is somewhere a more verbose / more
>> complete
>> description of the semantic of the individual values.
>
> No, and that's deliberate.  Considering the high levels of uncertainty
> that so often surround emergent events, the CAP designers (first in
> the CAP Working Group and later within OASIS) struggled to balance
> completeness against specificity.  There was also a concern that we
> could get bogged down in trying to perfect the taxonomies and wind up
> with no standard at all.
>
> So the definitions were deliberately left somewhat open-ended and
> contextual... some would go so far as to say "vague" and I, for one,
> wouldn't argue.
>
> - Art
>
>
>
> _______________________________________________
> This list is for public discussion of the Common Alerting Protocol.   
> This
> list is NOT part of the formal record of the OASIS Emergency  
> Management TC.
> Comments for the OASIS record should be posted using the form at
> http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=emergency
> CAP-list mailing list
> CAP-list at lists.incident.com
> http://lists.incident.com/mailman/listinfo/cap-list
>
> This list is not for announcements, advertising or advocacy of any
> particular program or product other than the CAP itself.
>
>
>
> _______________________________________________
> This list is for public discussion of the Common Alerting Protocol.   
> This list is NOT part of the formal record of the OASIS Emergency  
> Management TC.  Comments for the OASIS record should be posted using  
> the form at http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=emergency
> CAP-list mailing list
> CAP-list at lists.incident.com
> http://lists.incident.com/mailman/listinfo/cap-list
>
> This list is not for announcements, advertising or advocacy of any  
> particular program or product other than the CAP itself.