[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EMERGENCY-146) ETL: Rewrite opening paragraph of 2.7
[ https://issues.oasis-open.org/browse/EMERGENCY-146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=79975#comment-79975 ] Rex Brooks edited comment on EMERGENCY-146 at 9/23/21 10:40 PM: ---------------------------------------------------------------- Change: Section 2.7 committed to etl-v1.0-cn01-wd02 Minuted in SC Meeting Notes: Aug13-2021-meeting-notes was (Author: rexbroo): Change: Section 2.7 committed to etl-v1.0-cn01-wd02 > ETL: Rewrite opening paragraph of 2.7 > ------------------------------------- > > Key: EMERGENCY-146 > URL: https://issues.oasis-open.org/browse/EMERGENCY-146 > Project: OASIS Emergency Management TC > Issue Type: Improvement > Components: EDXL-CAP > Reporter: Jacob Westfall > Assignee: Rex Brooks > Priority: Major > Labels: ETL > > The opening paragraph of 2.7 should be updated with this rewritten text. > Â > Since the inception of the CAP standard, event term usage in the <event> element in CAP based systems around the world has evolved to be wide ranging and varied. Alerting authorities, and their CAP originators, have fallen to a number of differing practices that makes comparisons of the <event> element values extremely difficult. The list below is not a complete list of these practices but does demonstrate various interpretations and aspects of the larger problem of assigning an event term in CAP. -- This message was sent by Atlassian Jira (v8.3.3#803004)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]