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-19) Add parameters to incidents

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

Steve Hakusa commented on EMERGENCY-19:

Conclusion at the July 21, 2014 CAP-SC was to remove the incidents field from the next version of the CAP spec. 
Separately, https://issues.oasis-open.org/browse/EMERGENCY-30 has been opened to track a separate field for related alert linking. 

From https://www.oasis-open.org/apps/org/workgroup/emergency-cap/download.php/53681/July21-2014-meeting-notes.doc 

Jacob provided some background discussion on how best to link related CAP alerts versus wider incident related information. Eliot Christian had questions about the intent of the incident identifier. What is an incident and how to reference it? Rob mentioned SitRep already provides some capability for incident linking. Elysa mentioned that the DE can also provide this capability. Jacob clarified the intent as being specific to CAP alerts and Eliot mentioned that the name of the element may need to be changed to make clear what is happening. Elysa asked about opening a new JIRA issue so that a new element could be introduced for related alert linking. Jacob clarified that issue 20's resolution would then be to remove incidents entirely to remove the concern about what incidents is being used for.

> Add parameters to incidents
> ---------------------------
>                 Key: EMERGENCY-19
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-19
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP
> Should the alert.incidents element  be expanded to include both a <valueName> and <value> as is done with <geoCode> and other elements?  This change would allow issuer, for example. to point to CAP messages for related incidents (multiple typhoon messages related to winds, waves, etc.).
> Also see Issue 20 for proposal to change incidents format.

This message was sent by Atlassian JIRA

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