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-2) alert.info.instruction size restriction

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

Steve Hakusa commented on EMERGENCY-2:

From https://www.oasis-open.org/apps/org/workgroup/emergency-cap/download.php/54116/Sep15-2014-meeting-notes.doc 

Jacob summarized the issue regarding how clear and concise instructions are important.  Eliot raised a concern regarding landslide alerts and how pages of information could be present resulting in comprehension problems by the public.  It was noted that Google Alerts auto-summarizes information instead of providing a lengthy  instruction.  Gary concurred with the issue and noted problems at IPAWS with lengthy instruction and description values.  The issue of CAP being used for a report versus an alert was raised.  Nuwan mentioned that lengthy instructions could instead be provided using a resource block.  Eliot suggested the idea of adding a special CAP note about lengthy fields stating they may not be stored by some systems and could undergo automatic truncation or summary.

> alert.info.instruction size restriction
> ---------------------------------------
>                 Key: EMERGENCY-2
>                 URL: https://issues.oasis-open.org/browse/EMERGENCY-2
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
>              Labels: CAP

This message was sent by Atlassian JIRA

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