[CAP] cap implementations

[Mick Jagger]

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

Atom vs RSS, now there's a touchy subject.  My preference would be to provide the minimum amount of data in the "index feed" if that what its called.  So in the case of Atom, summarizing the CAP message in a summary field instead.  A CAP fluent client, is just looking for the updates, and the URL to the full CAP message.  Why parse the Atom when you can get the whole thing.  The non-CAP clients are the feed readers who want the summary to read and a URL for more info.

>(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.)

This is a good idea, this link would provide the message in a nice looking xhtml page instead after the translation.  Hmm, maybe even work this into a CAP resource element for offline readers..  

-- 
jake at jpw.biz
--