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-4) Require alert.info.headline and alert.info.description

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

Art Botterell commented on EMERGENCY-4:

Another two parter:

Re <headline>... in the age of social media I like the idea of making it required.  A default text could be constructed automatically from the various enumerated elements in cases where there was no authorized human in the loop.  (A related question is whether we should adjust the size of the <headline> value to 140 characters... and address the size in non-Latin character sets.  Another issue I'll add.)

[As an historical aside... one of our concerns early on was that writing effective headlines was a skill not everyone could be assumed to possess.  That was before Twitter made that skill absolutely necessary for emergency communicators.]

Re <description>... one of our original goals was to provide alert authors with a framework and checklist for writing effective alert messages.  In the rush of the moment its easy to forget to explain why we're asking folks to take protective action.  One constraint was that NOAA's existing weather-wire templates didn't always clearly separate the reason from the call-to-action, which made mapping them to the more structured CAP format automatically a bit of a challenge.  So this was a bit of a tail/dog problem, which we sidestepped by making <description> optional.

So personally I'd love to see it made mandatory but I can understand that some legacy alert sources might still find it difficult to address that, even a decade after CAP was adopted.

In any event, I don't believe a Cancel message requires an Info block at all, does it?

> Require alert.info.headline and alert.info.description
> ------------------------------------------------------
>                 Key: EMERGENCY-4
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-4
>             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]