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://issues.oasis-open.org/browse/EMERGENCY-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41748#comment-41748 ] 

Art Botterell commented on EMERGENCY-16:

To some extent the deep issue here parallels the existing distinction between the <description> and <instruction> blocks.  The most common use of the <area> structure is to describe the desired geographic scope of the <instruction>.  However, sometimes there's also a desire to annotate the <description> of the causal event(s) in more precise geospatial terms.

So... one possible approach might be to convert both <description> and <instruction> from simple free-text elements into more complex elements with both the text field and some optional geospatial descriptions... possibly using some version of the <area> structure.  In that case the geospatial elements of the expanded <instruction> block would be equivalent to the existing <area> usage... but less ambiguous.

This would be a structural... read "CAP 2.0"... change, but that might be a good thing in terms of making the difference clear.

> Support CAP event location and movement
> ---------------------------------------
>                 Key: EMERGENCY-16
>                 URL: https://issues.oasis-open.org/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

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