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

Bob,

You point into a very interesting parallel development out there in the
world.

In the stimulus bill last spring was $7.2B in grant money that went to
USDA ('broadband' and 'reach to rural') and NTIA in Commerce
('broadband' and 'reach to underserved').  The FCC was also charged with
drafting a 'national broadband plan'.  
	FCC published a Notice of Inquiry, for which the comment period just
closed last week.  About the first comment they sought was a definition
of 'broadband'.  (For paper coming from inside the beltway, this NOI is
pretty good stuff, IMHO).  Whatever your definition of broadband, you
can look behind it and see 'extension of the internet'.  And you should
recognize that extension of internet to rural and extension of internet
to emergency services has a whole lot of overlap.  
	Just to complete the federal nethead - bellhead list of players, DHS
and DoJ are still in circuit-switch.  ... and didn't get this batch of
grant money.

What you ought to get out of this is is that
	- emergency services vehicles will soon be routinely on the internet.
	- the citizenry that emergency services exists to serve will
increasingly be on the internet.
	This observation is progressively true in any event -- the netheads
always win -- but the stimulus subsidies are probably going to be a
substantial accelerant.... Santa Ana winds behind a California
wildfire.  

On Sun, 2009-07-12 at 17:50 -0700, Bob Robinson wrote:
> Art,
> 
> Very good analysis.  In fact I think the question of user (consumer) disconnect can be put to the broader field of general emergency management communications and in fact it can be a very important part of any attempt to build "standards" that are to be applied across groups/agencies/etc. involved in emergency management.  But what  the heck, that's just my nickels worth based on 25+ years of EM experience.
> 
> Bob Robinson
> 
> --- On Sun, 7/12/09, Art Botterell <acb@incident.com> wrote:
> 
> > From: Art Botterell <acb@incident.com>
> > Subject: Re: [CAP] Definition of Warning Categories
> > To: earlywarning@ietf.org, cap-list@incident.com
> > Date: Sunday, July 12, 2009, 2:23 PM
> 
> > 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
> > 
> >
> _______________________________________________
> 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.
-- 
Rex Buddenberg
Naval Postgraduate School
Code IS/Bu
Monterey, Ca 93943
831/656-3576