[CAP] cap implementations

[Mick Jagger]

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