[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://tools.oasis-open.org/issues/browse/EMERGENCY-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Mancuso updated EMERGENCY-19: ---------------------------------- Description: 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. was: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.). > Add parameters to incidents > --------------------------- > > Key: EMERGENCY-19 > URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-19 > Project: OASIS Emergency Management TC > Issue Type: Task > 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 (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]