Re: [earlywarning] [CAP] Definition of Warning Categories
Art Botterell <acb@incident.com> Sun, 12 July 2009 18:23 UTC
Return-Path: <acb@incident.com>
X-Original-To: earlywarning@core3.amsl.com
Delivered-To: earlywarning@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2CBB28C179 for <earlywarning@core3.amsl.com>; Sun, 12 Jul 2009 11:23:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level:
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ykwmj3I+lR+S for <earlywarning@core3.amsl.com>; Sun, 12 Jul 2009 11:23:08 -0700 (PDT)
Received: from n72.bullet.mail.sp1.yahoo.com (n72.bullet.mail.sp1.yahoo.com [98.136.44.34]) by core3.amsl.com (Postfix) with SMTP id 6014628C175 for <earlywarning@ietf.org>; Sun, 12 Jul 2009 11:23:05 -0700 (PDT)
Received: from [69.147.84.144] by n72.bullet.mail.sp1.yahoo.com with NNFMP; 12 Jul 2009 18:23:33 -0000
Received: from [68.142.200.221] by t6.bullet.mail.sp1.yahoo.com with NNFMP; 12 Jul 2009 18:23:33 -0000
Received: from [68.142.201.253] by t9.bullet.mud.yahoo.com with NNFMP; 12 Jul 2009 18:23:33 -0000
Received: from [127.0.0.1] by omp414.mail.mud.yahoo.com with NNFMP; 12 Jul 2009 18:23:33 -0000
X-Yahoo-Newman-Id: 691479.70895.bm@omp414.mail.mud.yahoo.com
Received: (qmail 77134 invoked from network); 12 Jul 2009 18:23:33 -0000
Received: from unknown (HELO postfix.incident.com) (acb@99.182.125.96 with login) by smtp105.sbc.mail.sp1.yahoo.com with SMTP; 12 Jul 2009 18:23:32 -0000
X-YMail-OSG: ejMA6ysVM1kUpzpxGmbBACt0PT8NCv13SDQ1FU6d3OGiXwfqMQCM_UyHVrFGhFxA27mChAixmYDEslLDcPN_KHxO5RDlv0VA3GFFrM7hMJPyENmrzjTrQ.ZF17wwVGF4xJfBXNQraQlWVIKA7ZLXFoLVKFMX_9PebDSHNiIfDuFCBDlBbxmiy0fI2v20wPCqtn7RcDq7OJHo3n4TrSxAdsQO4iBpIDyDa9R06vrA4rBBf6ySvTV3.aNQf_4UFsopMr69RMldF1X_7tniLrWXDoafu.6NCm3A3uEDuFxrmceVyxM-
X-Yahoo-Newman-Property: ymail-3
Received: from [127.0.0.1] (localhost [127.0.0.1]) by postfix.incident.com (Postfix) with ESMTP id 9E3F32063850; Sun, 12 Jul 2009 11:23:31 -0700 (PDT)
Message-Id: <9E54E462-245A-4EC9-81D0-5A169DA2411C@incident.com>
From: Art Botterell <acb@incident.com>
To: cap-list@incident.com, earlywarning@ietf.org
In-Reply-To: <7B88AB507ED649F2B28CF1829AD3D122@xppc1>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Sun, 12 Jul 2009 11:23:31 -0700
References: <187701ca02df$a80ff0e0$501ca20a@nsnintra.net> <8C3B4F90-C248-418C-9DC3-D9EFAFCCFF50@incident.com> <7B88AB507ED649F2B28CF1829AD3D122@xppc1>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [earlywarning] [CAP] Definition of Warning Categories
X-BeenThere: earlywarning@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Discussion list for Authority-to-Individuals \(Early Warning\) Emergency " <earlywarning.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/earlywarning>
List-Post: <mailto:earlywarning@ietf.org>
List-Help: <mailto:earlywarning-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/earlywarning>, <mailto:earlywarning-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 12 Jul 2009 18:23:09 -0000
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@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@lists.incident.com > [mailto:cap-list-bounces@lists.incident.com] On Behalf Of Art > Botterell > Sent: Sunday, July 12, 2009 11:52 AM > To: cap-list@incident.com; earlywarning@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@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@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.
- Re: [earlywarning] [CAP] Definition of Warning Ca… Tony Rutkowski
- [earlywarning] Definition of Warning Categories Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… Art Botterell
- Re: [earlywarning] [CAP] Definition of Warning Ca… Art Botterell
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… David Aylward (Comcare)
- Re: [earlywarning] [CAP] Definition of Warning Ca… Art Botterell
- Re: [earlywarning] [CAP] Definition of Warning Ca… Henning Schulzrinne
- Re: [earlywarning] [CAP] Definition of Warning Ca… David Aylward (Comcare)
- Re: [earlywarning] [CAP] Definition of Warning Ca… David Aylward (Comcare)
- Re: [earlywarning] [CAP] Definition of Warning Ca… James M. Polk
- Re: [earlywarning] [CAP] Definition of Warning Ca… David Aylward (Comcare)
- Re: [earlywarning] [CAP] Definition of Warning Ca… DRAGE, Keith (Keith)
- Re: [earlywarning] [CAP] Definition of Warning Ca… Tony Rutkowski
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… Tony Rutkowski
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… creed
- Re: [earlywarning] [CAP] Definition of Warning Ca… Art Botterell
- Re: [earlywarning] [CAP] Definition of Warning Ca… Art Botterell
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… Hannes Tschofenig
- Re: [earlywarning] [CAP] Definition of Warning Ca… Timothy Grapes
- Re: [earlywarning] [CAP] Definition of Warning Ca… Rex Buddenberg
- Re: [earlywarning] [CAP] Definition of Warning Ca… Rex Buddenberg
- Re: [earlywarning] [CAP] Definition of Warning Ca… Tony Rutkowski
- Re: [earlywarning] [CAP] Definition of Warning Ca… Brian Rosen
- Re: [earlywarning] [CAP] Definition of Warning Ca… Timothy Grapes