[CAP] cap implementations

[Mick Jagger]

> Good point, and I'm away from my records right now... but in the case  
> of the info-block items I think we're looking for the highest,  
> earliest, latest values as appropriate.  We were trying to keep the  
> feed elements flat.  If there's something that could be made clearer,  
> I'd certainly appreciate the feedback.

The spec currently says the info elements from the first info block only.  However, this is my suggestion, check all of the info elements, and pull the highest level from each of them.  A remote client is going to be filtering on the severity level for each element.  So it makes sense to just present the highest level overall for each element.  The actual info elements may have mismatches, highest from one and highest from another, but overall it presents the best picture for the remote client to filter.  

The location component, is a real problem in this case.  In fact, I'm sort of leaving that out in the implementation I'm working on.  Can this be an optional component?  Since there could be multiple area elements for multiple infos, this could prove to be a real pain.  Easier to have the remote client filter on the levels, then download the CAP to check for area.  

-- 
jake at jpw.biz
--