[OASIS Issue Tracker] (EMERGENCY-155) ETL: Update renumbered section 3.5

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/EMERGENCY-155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=79987#comment-79987 ] 

Rex Brooks commented on EMERGENCY-155:
--------------------------------------

Change: Section 3.5 committed to etl-v1.0-cn01-wd02

Minuted in SC Meeting Notes: Date-meeting-notes

> ETL: Update renumbered section 3.5
> ----------------------------------
>
>                 Key: EMERGENCY-155
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-155
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: EDXL-CAP 
>            Reporter: Jacob Westfall
>            Assignee: Rex Brooks
>            Priority: Major
>              Labels: ETL
>
> The previous section 3.4 should be renumbered to 3.5 with the following text changes:
> Â
> Spectrums can intersect. This becomes important when trying to compare terms from across spectrums. For example, if one alert message uses an event term, that includes a narrow time modifying term; and another alert message uses a broad impact modifying term, how difficult is it for automated systems to compare the two terms? For example, an event type term like âweather threatâ as compared to an event type term like âhurricane emergencyâ.
> Furthermore, there are subject events where the individual event type terms incorporate concepts from two different spectrums (i.e. âfire threat emergencyâ). When intersecting spectrums are used, it increases the difficulty of comparing terms across messages.



--
This message was sent by Atlassian Jira
(v8.3.3#803004)