[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EMERGENCY-34) Support the concept of an event in CAP
[ https://issues.oasis-open.org/browse/EMERGENCY-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51658#comment-51658 ] Eliot Christian commented on EMERGENCY-34: ------------------------------------------ Here is a way to add a new CAP element that describes the current event location. The cap/info/area element would be renamed cap/info/alertArea. Its sub-elements would be renamed in kind: alertAreaDesc, alertPolygon, alertCircle, alertGeocode, alertAltitude, alertCeiling. The definitions of these elements would all be adjusted to replace the words "affected area" with "alerting area". A new element would be created, named cap/info/eventArea. It sub-elements would be named: eventAreaDesc, eventPolygon, eventCircle, eventGeocode, eventAltitude, eventCeiling. The definitions of these eventArea elements would be the same as those of the alertArea elements, except that the words "alerting area" would be replaced with "event area". A picture showing the resulting Document Object Model (section 3.1 of the CAP specification) is at https://drive.google.com/file/d/0B5FiAsl5yGbZXzFmaE1rYm1hdVU > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]