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://tools.oasis-open.org/issues/browse/EMERGENCY-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tony Mancuso updated EMERGENCY-20:
----------------------------------

    Issue Type: Improvement  (was: Task)

> Change incidents format
> -----------------------
>
>                 Key: EMERGENCY-20
>                 URL: https://tools.oasis-open.org/issues/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
(v6.2.2#6258)


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