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-146) ETL: Rewrite opening paragraph of 2.7

     [ https://issues.oasis-open.org/browse/EMERGENCY-146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rex Brooks updated EMERGENCY-146:
    Assignee: Rex Brooks

> 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

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