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-34) Support the concept of an event in CAP

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

David Askov commented on EMERGENCY-34:

As discussed last Monday, I have another suggestion for this, which is now option 4 in the attachment. The key advantages to this approach are simplicity and backward compatibility. It inserts a single new field (attribute?) to the info block. For lack of a better name, I called it “category” which would have possible values of “alert” or “event”. Almost everything in the info, resource, and area blocks could apply to either an alert or an event. If not, one could just omit them for the optional fields. In the case where a required field really doesn’t apply (e.g.: certainty), you could use “unknown”, or perhaps we could add a “not applicable” option. This requires existing CAP users to do very little to adopt this concept of an event. 

I made it bold font, or required. That said, we could make category optional, with a default value of alert, and it would have no backward compatibility issues at all. 

I’m not sure this is the best design, but from the standpoint of simplicity and backward compatibility, it will require the fewest changes to adopt. 

Link: https://drive.google.com/file/d/0BxkjAlhTZvYzQ3ZrcnlXUzFNRzg/view?usp=sharing
[Note: I copied this from one of the other designs and tried to undo all those changes first. Other than the red text in option 4, everything should be the same as it is today.]

> Support the concept of an event in CAP
> --------------------------------------
>                 Key: EMERGENCY-34
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-34
>             Project: OASIS Emergency Management TC
>          Issue Type: Bug
>          Components: CAP 
>            Reporter: Steve Hakusa
> CAP already has a number of fields describing the event for which an alert is being issued.  Two separate issues in this list wish to add more, and more structured, information about the event
> https://issues.oasis-open.org/browse/EMERGENCY-17 : Add event expiration element
> https://issues.oasis-open.org/browse/EMERGENCY-16 : Support CAP event location and movement
> These issues and other points of discussion may point to the need for CAP to have a more structured representation of an event and its metadata.
> This issue is meant to contain proposals for how an event could be more formally represented in CAP.

This message was sent by Atlassian JIRA

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