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-1) alert.info.event size restriction

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

Art Botterell commented on EMERGENCY-1:

Seems like there are really two questions here:

1) Should there be a limit, either mandatory or advisory, on the length of the <event> value; and,

2) What should be used as the text label for an Alert on a graphic or tabular display?

At first glance I'd suggest the answer to 1 is probably, "yes, as advisory"... making it mandatory could have unforeseen side effects and the only justification would seem to be a particular answer to Question 2.

And Question 2 is more complicated.  Will one answer fit all users' needs?  Part of this is the event/alert dichotomy we'll encounter in a number of issues... are we describing the event itself or an official (or at least known-sourced) alert related to the event?  Not necessarily the same thing, especially when jurisdictional boundaries become a factor.

Also, in some cases an implementer might prefer to display the recommended protective action (<responseType>) (e.g., "Evacuation") perhaps in combination with the <category> or some other elements.  And <headline> is intended to be the all-purpose short representation of the alert's import, so that might be another candidate.  

Not sure whether the standard should endorse any particular view on this; it seems like an implementation choice.

> alert.info.event size restriction
> ---------------------------------
>                 Key: EMERGENCY-1
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-1
>             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]