[CAP] FW: CAP 2.0 proposal

[David Oppenheimer]

At the risk of disclosing myself as a POC for the USGS, I will note that the
USGS earthquake program submits automated and reviewed message in CAP 1.1
format into the DMIS using their library
(https://interop.cmiservices.org/downloads/axis-clientside.zip). 

We also create earthquake messages in 1.0 format for our Atom/RSS feeds at
http://earthquake.usgs.gov/eqcenter/catalogs/ 
using custom software that a contractor (ISTI) wrote for us.  We are going
to upgrade the XML generation software to 1.1 soon.

As far as we know, we are complying with update and cancel messages. If not,
please let me know.  It is very common to rapidly update earthquake messages
as magnitudes and locations change. It is less common that we delete
automated messages for false detections that are not earthquakes, but it
does occur. 

If the CAP community is moving to 2.0, we would appreciate a single, common
library that could produce both XML and messages for submission into the
DMIS. 

-David

-------------------------------------------------------
David Oppenheimer                   office:650.329.4792
U.S. Geological Survey              fax:   650.329.4732
345 Middlefield Road.-MS 977    email: oppen at usgs.gov
Menlo Park, CA 94025 

-----Original Message-----
From: cap-list-bounces at lists.incident.com
[mailto:cap-list-bounces at lists.incident.com] On Behalf Of Mick Jagger
Sent: Monday, March 03, 2008 9:14 AM
To: cap-list at lists.incident.com
Subject: Re: [CAP] CAP 2.0 proposal

> Can I make a suggestion for the CAP cookbook pages.  Since none of the
example CAP feeds that are
> listed on the cookbook page are publishing valid CAP messages, can a
notation be put beside each of
> them stating this?  It is very confusing for new users of CAP to see bad
implementations as their first
> example.

I didn't mean to flame any of the current sites listed on the cookbook page,
so I thought I should follow up with some reasons why each feed has
problems.

USGS Feeds - using CAP 1.0 and therefore has problems using Update and
Cancel type messages.  The references field was poorly defined in CAP 1.0
making establishing proper message chains very difficult.  Regular Alert
type messages on the feed are valid and if all the messages are Alerts then
the feed is good.

NWS Feeds - using CAP 1.0 and multiple info blocks versus a feed format.
Invalid fields like identifier and problems with Update and Cancel types
using references.

NWS Tsunami Feed - using CAP 1.0 and no feed format.  Invalid date types
used and problems with Update and Cancel types using references.

EDIS Feed - EDIS is using CAP 1.1 now and the feed link on the cookbook page
is wrong.  EDIS currently has problems with duplicate messages appearing in
the feed and does not use the references field properly for Update and
Cancel messages, meaning you cannot establish message chains.

JRC GDAS Feed - no longer exists.  I believe the replacement for this feed
is http://www.gdacs.org/ which does offer CAP messages.  However these
messages have invalid date types, the odd use of CDATA in descriptions,
invalid area blocks, and problems with Update and Cancel types using
references.

-- 
lists at jpw.biz
--
_______________________________________________
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 at lists.incident.com
http://eastpac.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.