[OASIS Issue Tracker] (EMERGENCY-34) Support the concept of an event in CAP

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Eliot Christian commented on EMERGENCY-34:
------------------------------------------

As CAP is modeled now, there is only one message and it has "alert" as its top-level element. It is possible to define a separate message that would have "event" as its top-level element. My guess is that modeling event messages as distinct from alert messages would be less confusing than the current conflation of the event/alert dichotomy within the alert message, and also less confusing than adding new mechanisms for making such distinctions with the alert message.

I would also guess that the users of such "event messages" would be somewhat distinct from the users of "alert messages", although of course there would be overlap. I suppose that event messages would be used more by hazard threat experts and emergency managers while alert messages would be used more by civic authorities and the general public.

If distinct event messages are defined, it would be useful to provide an optional mechanism for a CAP alert message to reference one or more event messages. For the sake of symmetry, I suppose an event message could also reference one or more alert messages, although use cases for that capability are not apparent to me yet. 



> 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
(v6.2.2#6258)