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-164) ETL: Add 5.3.6

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

Rex Brooks commented on EMERGENCY-164:

Committed to etl.v1.0-cn01.wd02

Because these 'tweaks' are numerous, the SC did not formally record approval in any specific Meeting Notes.

> ETL: Add 5.3.6
> --------------
>                 Key: EMERGENCY-164
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-164
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: EDXL-CAP 
>            Reporter: Jacob Westfall
>            Priority: Major
>              Labels: ETL
> Add new section 5.3.6
> Â
> {color:#4c4635}terms tailored for a specific dissemination channel or display medium (i.e. âcongestion aheadâ).{color}
> {color:#4c4635}Channel based terms are often tailored and leave out details. For example, an electronic road sign that says âcongestion aheadâ assumes the audience understands the context of viewing the message while driving. Such messages are actually private messages, built for a specific channel; the information is still public, only the tailoring is private. Without the context of the display medium, the event type becomes vague and difficult for comparison activities.{color}

This message was sent by Atlassian Jira

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