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-20) Change incidents format

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

Steve Hakusa commented on EMERGENCY-20:

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.

> Change incidents format
> -----------------------
>                 Key: EMERGENCY-20
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-20
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP
> Jacob Westfall;  alert.incidents: this element should be more clearly defined to ensure interoperability between systems.  A recommended format is IDENTIFIER,URI with multiple values separated by whitespace.  To be in line with Oasis standards XRI could be substituted but there are still problems with W3C right now.  The transport method must be included in the URI to allow a receiving system to be able to download this incident message if need be and should point to the actual CAP message itself.  For two-way systems even those like DM-Open using SOAP can use the URI, while one-way systems can use the identifier to correlate their received alerts. 

This message was sent by Atlassian JIRA

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