[CAP] cap implementations

[Art Botterell]

Good idea... in fact, see <http://www.incident.com/cookbook> and  
scroll down to "Application Notes" for just such a scheme (using Atom  
instead of RSS 2.0, as it happens, but either would work).

(This may work best in the presence of an XSL stylesheet for the CAP  
message, so that unsophisticated users aren't startled by the  
appearance of raw XML on their screens.)

- Art


On Oct 3, 2005, at 10/3/05 8:39 PM, Mick Jagger wrote:

> Hi,
>     I'm putting together a package that reads CAP alerts, and  
> notifies the user when alerts occur.  Parsing the CAP messages  
> themselves has been easy, but the various implementations of  
> posting messages has been causing me some grief.  Either a single  
> URL is provided for messages, with 1 alert element, and multiple  
> infos, or individual messages are posted themselves.  Here is my  
> ideal method for a feed implementation, I'd like to know what the  
> list thinks,
>     A single URL is available for CAP feed.  Each active alert is  
> an RSS 2.0 entry.  It summarizes the alert, and offers the URL  
> which provides the full CAP message.  The posting web server uses  
> conditional GET for the feed URL.  The folder holding CAP messages  
> retains old alerts for referencing by new alerts.
>     RSS allows non-CAP fluent feed readers to at least get the  
> basic info.  Also offers standard method of summarizing active  
> alerts for a CAP reader.  Conditional GET makes the checking for  
> updates faster and easier.  Old alerts are retained to allow a new  
> feeder just connecting to get the history for an alert using 1.1's  
> references and incidents.
>
> -- 
> jake 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.