OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (EMERGENCY-16) Support CAP event location and movement


    [ https://tools.oasis-open.org/issues/browse/EMERGENCY-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37629#comment-37629 ] 

Art Botterell edited comment on EMERGENCY-16 at 6/5/14 5:18 PM:
----------------------------------------------------------------

Yes, we did spend a lot of time on this in days of yore... I think it was back in the CAP Working Group days even before we contributed the 0.9 spec to OASIS...  and ultimately decided simply to allow multiple Info blocks or multiple Alerts to describe the situation at different points in time.  (Thus the rarely-used <effective> field to allow predictive alerting beyond the immediate timeframe.)

One again we were hoist on the ambiguity of our concept of "the situation."  Were we describing the ongoing phenomenon or the particular alert and its associated protective-action recommendation?  Clarify that and many things become clearer.

In the meantime... I'm not sure that for public warning purposes there's much wrong with the existing NWS practice of including some general description of movement in the <description> text, which can be in whatever terms are deemed most comprehensible.  


was (Author: acb):
Yes, we did spend a lot of time on this in days of yore... I think it was back in the CAP Working Group days even before we contributed the 0.9 spec to OASIS...  and ultimately decided simply to allow multiple Info blocks or multiple Alerts to describe the situation at different points in time.  (Thus the rarely-used <effective> field to allow predictive alerting beyond the immediate timeframe.)

One again we were hoist on the ambiguity of our concept of "the situation."  Were we describing the ongoing phenomenon or the particular alert and it's associated protective-action recommendation?  Clarify that and many things become clearer.

In the meantime... I'm not sure that for public warning purposes there's much wrong with the existing NWS practice of including some general description of movement in the <description> text, which can be in whatever terms are deemed most comprehensible.  

> Support CAP event location and movement
> ---------------------------------------
>
>                 Key: EMERGENCY-16
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-16
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP
>
> Should a new CAP element be added that describes the current event location, speed and direction of movement?
> Also: Is there a need for describing motion? Ideas include multiple info blocks with own effective time/location or a new movingArea structure. Scenarios? Specifics?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]