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

Art Botterell <artbotterell@gmail.com> Wed, 15 July 2009 17:14 UTC

Return-Path: <artbotterell@gmail.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 518E03A6CB8 for <earlywarning@core3.amsl.com>; Wed, 15 Jul 2009 10:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 JnZ7tkb-21Ui for <earlywarning@core3.amsl.com>; Wed, 15 Jul 2009 10:14:34 -0700 (PDT)
Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by core3.amsl.com (Postfix) with ESMTP id 2CDA53A6995 for <earlywarning@ietf.org>; Wed, 15 Jul 2009 10:14:07 -0700 (PDT)
Received: by an-out-0708.google.com with SMTP id c37so1754121anc.4 for <earlywarning@ietf.org>; Wed, 15 Jul 2009 10:13:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=HBamGH7Z5NbG56qqlmyzgTakotrqy3AnB4DXOzjd5k0=; b=ku23rp+jfcpRqx7NW8pxJW5K9d6YhuWgttmIo50ZCNF5QGBzpju9yGzMxiF5D8NUiu p05Wn4rMOzRNPTzeYjsiTpGt9nOmCxjO4CIJFc5jmlhxeJMqnCF0Dpu/3lQ8S44+lxxo KJu5MhybDp83WD92NvR7hL3tIBVqZglyTxICc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=Rj6djYH0vAmldtYgdtQjsjuUVaDv6gm+cmzJWEvuS59HpGuB86H/7CpiO5rdKKzsDP QbUv15PoPPmOYxT2FwQgilkxR75m872yo+0fQVwZ6s/O1mMXfq19nTpmW+uyPQzMOleF LnqCtEoy2YGtft7md6CWCKmuXRHjgyEIw0xKc=
MIME-Version: 1.0
Received: by 10.100.151.1 with SMTP id y1mr10460504and.119.1247677986855; Wed, 15 Jul 2009 10:13:06 -0700 (PDT)
In-Reply-To: <52348.75.71.192.203.1247676264.squirrel@mail.opengeospatial.org>
References: <82AE05D27DEDB04488869E55FDAB71FDA1C0FB@s-gov-mail-4.govaxa.ai> <18ee01ca0322$b7a97d30$501ca20a@nsnintra.net> <30076E62-60BC-4488-9F10-33686E82E657@incident.com> <34E56644D3334E8D876CD9368814657E@xppc1> <XFE-SJC-211xvjPkQTG00001d60@xfe-sjc-211.amer.cisco.com> <EDC0A1AE77C57744B664A310A0B23AE20702F355@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com> <020e01ca054f$23a96620$1116a20a@nsnintra.net> <52348.75.71.192.203.1247676264.squirrel@mail.opengeospatial.org>
Date: Wed, 15 Jul 2009 10:13:06 -0700
Message-ID: <2e53e6590907151013n9af4e69m484d2326a0cf76b3@mail.gmail.com>
From: Art Botterell <artbotterell@gmail.com>
To: creed@opengeospatial.org
Content-Type: multipart/alternative; boundary="001636164b37335a4f046ec1abf9"
Cc: Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, earlywarning@ietf.org
Subject: Re: [earlywarning] [CAP] Definition of Warning Categories
X-BeenThere: earlywarning@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: acb@incident.com
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: Wed, 15 Jul 2009 17:19:44 -0000

On Wed, Jul 15, 2009 at 9:44 AM, <creed@opengeospatial.org> wrote:

> CAP was originally developed based primarily on US requirements and as
> such may not reflect non-US regional considerations, policies, etc.


Um... I'm not sure that's entirely correct.  The basis of the CAP design was
social science research on warning message effectiveness, and both that body
of research and the membership of the original CAP Working Group were quite
international.

It's true that a lot of the application of CAP has taken place in the U.S.,
and that's a constant concern.  However, we've managed to keep CAP
international enough that the ITU was able to endorse it (as recommendation
x.1303).

Profiles, as long at they're truly profiles (which is to say, strict subsets
of the CAP specification) enable different communities to define local
usages without breaking basic compatibility with other CAP implementations.
Again, it's been a struggle sometimes to prevent profiles from becoming
localized extensions of the standard, which wouldn't be interoperable, but I
think we've done reasonably well so far.

I'd also suggest that it may be confusing to talk about CAP in the same
breath with GeoRSS or Atom.  CAP is a content structure, while RSS and Atom
are indexing schemes that themselves refer to other content, including
sometimes CAP.

- Art