[CAP] CAP 2.0 proposal

[Mick Jagger]

> 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
--