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

Henning Schulzrinne <hgs@cs.columbia.edu> Sun, 12 July 2009 20:17 UTC

Return-Path: <hgs@cs.columbia.edu>
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 86EEE28C194 for <earlywarning@core3.amsl.com>; Sun, 12 Jul 2009 13:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 q4qS4H3AU66y for <earlywarning@core3.amsl.com>; Sun, 12 Jul 2009 13:17:08 -0700 (PDT)
Received: from tarap.cc.columbia.edu (tarap.cc.columbia.edu [128.59.29.7]) by core3.amsl.com (Postfix) with ESMTP id 8E2CB28C103 for <earlywarning@ietf.org>; Sun, 12 Jul 2009 13:17:08 -0700 (PDT)
Received: from new-host-2.home (pool-173-54-225-57.nwrknj.fios.verizon.net [173.54.225.57]) (user=hgs10 mech=PLAIN bits=0) by tarap.cc.columbia.edu (8.14.3/8.14.3) with ESMTP id n6CKHbhQ004696 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sun, 12 Jul 2009 16:17:37 -0400 (EDT)
Message-Id: <7B8483F8-3E5A-4156-BF5D-90A31611E4F4@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Art Botterell <acb@incident.com>
In-Reply-To: <30076E62-60BC-4488-9F10-33686E82E657@incident.com>
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 16:17:37 -0400
References: <82AE05D27DEDB04488869E55FDAB71FDA1C0FB@s-gov-mail-4.govaxa.ai> <18ee01ca0322$b7a97d30$501ca20a@nsnintra.net> <30076E62-60BC-4488-9F10-33686E82E657@incident.com>
X-Mailer: Apple Mail (2.935.3)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.65 on 128.59.29.7
Cc: earlywarning@ietf.org, cap-list@incident.com
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 20:17:09 -0000

I'm also not convinced that categories are all that useful, at least  
among different kinds emergencies. It seems a bit far-fetched to say  
"I want to know if there's a tsunami, but not a tornado or chemical  
leak, affecting my area". There are likely to be non-emergency  
categories, such as school closings or traffic alerts, that may have  
more limited appeal, but may use the same basic infrastructure.

Henning

On Jul 12, 2009, at 3:23 PM, Art Botterell wrote:

> I'm wondering whether it might be simpler, at least in the near  
> term, to let consumers subscribe to selected sources rather than to  
> topical categories.  That pushes the question of message  
> authoritativeness / jurisdiction  /credibility out of the CAP  
> infrastructure and into the larger field of inter-agency and inter- 
> jurisidictional coordination, where it more properly belongs.
>
> Taxonomies tend to be culturally loaded and can never be guaranteed  
> to be complete.  Thus there's a real risk of "categorical  
> disconnects" leading to missed alerts either because of differing  
> interpretations of categories or of unforeseen events that don't fit  
> our preconceived categories.  Maybe someday we'll have a reliable  
> taxonomy of the unexpected, but right now a degree of deliberate  
> imprecision seems to be the best we can do... and I sometimes wonder  
> whether even that is more helpful than it is risky.
>
> - Art
>
>
> On Jul 12, 2009, at 7/12/09 11:58 AM, Hannes Tschofenig wrote:
>
>> 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
>
> _______________________________________________
> earlywarning mailing list
> earlywarning@ietf.org
> https://www.ietf.org/mailman/listinfo/earlywarning
>