[CAP] CAP 2.0 proposal

[Mick Jagger]

> For us (and others I've talked with), one of the key problems in automating
> the ingestion of CAP warnings (or other warnings, for that matter) is
> discerning when a warning needs updating, i.e., when does an old warning

All of the fields required to discern this are already in CAP.  The problem you are facing is that the CAP sources you are looking at do not conform to the standard.  You are probably looking at the NWS CAP feeds as your example source and this is where the contentrevnumber solution would be useful.  Hopefully this will be rectified soon with the NWS updating their CAP feeds and the problem you are facing will go away.

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.

Also, are there any other public CAP feeds that ARE valid, that should be added to the Cookbook pages as examples?

Finally, would it also help if reference feed examples were created?  A live feed could be created  automatically every day following a set pattern with example CAP messages that could be used for testing.  For example at 9am a lower level alert is issued, followed by a higher level update with a change in area at 12pm and cancelled at 3pm.  Also some scenario feeds could be created that followed real life events and are kept as historical examples.

-- 
lists at jpw.biz
--