Re: [earlywarning] [CAP] Definition of Warning Categories

"Hannes Tschofenig" <Hannes.Tschofenig@gmx.net> Sun, 12 July 2009 18:55 UTC

Return-Path: <Hannes.Tschofenig@gmx.net>
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 34EBE3A68D2 for <earlywarning@core3.amsl.com>; Sun, 12 Jul 2009 11:55:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.148
X-Spam-Level:
X-Spam-Status: No, score=-2.148 tagged_above=-999 required=5 tests=[AWL=0.451, 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 6KriLOtNtqdD for <earlywarning@core3.amsl.com>; Sun, 12 Jul 2009 11:55:30 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 935723A6B66 for <earlywarning@ietf.org>; Sun, 12 Jul 2009 11:55:29 -0700 (PDT)
Received: (qmail invoked by alias); 12 Jul 2009 18:55:57 -0000
Received: from a91-154-108-144.elisa-laajakaista.fi (EHLO 4FIL42860) [91.154.108.144] by mail.gmx.net (mp071) with SMTP; 12 Jul 2009 20:55:57 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+ZgsELgB6ZPuSAVUazdNsmYvEyA/Faf9uHxMQtaq wDxsJtno4syPK4
From: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>
To: "'Elizabeth F. Klute'" <Elizabeth.Klute@gov.ai>, acb@incident.com, cap-list@incident.com, earlywarning@ietf.org
References: <82AE05D27DEDB04488869E55FDAB71FDA1C0FB@s-gov-mail-4.govaxa.ai>
Date: Sun, 12 Jul 2009 21:58:16 +0300
Message-ID: <18ee01ca0322$b7a97d30$501ca20a@nsnintra.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <82AE05D27DEDB04488869E55FDAB71FDA1C0FB@s-gov-mail-4.govaxa.ai>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcoDCFUbyDH9YNYRQQa7JasYXVhf2wADqf4XAAKyfwA=
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.54
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:55:31 -0000

I should provide a bit more feedback about the background to my question. 

If you only set the value in the category field for the purpose of human
consumption then there is not really an interoperability issue.

Now, with the work on http://tools.ietf.org/html/draft-rosen-sipping-cap-03
we wanted to define an event package for SIP that allows you to "subscribe"
to certain type of events: you might indicate something like location and
the type of events you are interested in. 

Now, the semantic of the category field suddently matters. With the
individuals-to-citizen emergency services we tried to come up with a
description of the emergency services categories, see RFC 5031. 

Ciao
Hannes
 
>-----Original Message-----
>From: cap-list-bounces@lists.incident.com 
>[mailto:cap-list-bounces@lists.incident.com] On Behalf Of 
>Elizabeth F. Klute
>Sent: 12 July, 2009 20:28
>To: acb@incident.com; cap-list@incident.com; earlywarning@ietf.org
>Subject: Re: [CAP] Definition of Warning Categories
>
>Thanks Art,
>
>I was struggeling on how to answer but could not have done it better!
>Elizabeth Klute, Director Disaster Management
>
>----- Original Message -----
>From: cap-list-bounces@lists.incident.com 
><cap-list-bounces@lists.incident.com>
>To: cap-list@incident.com <cap-list@incident.com>; 
>earlywarning@ietf.org <earlywarning@ietf.org>
>Sent: Sun Jul 12 11:51:43 2009
>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_abbre
>v=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_abbre
>v=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.
>