[OASIS Issue Tracker] (EMERGENCY-2) alert.info.instruction size restriction

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

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

Art Botterell commented on EMERGENCY-2:
---------------------------------------

+1 to Mike's tail-wag-dog concern.  Brevity is a virtue, but one use of the <instruction> field is to provide details that may be important.  E.g., in the case of an evacuation... in what direction, by which routes, to what destination, by what means (vehicle, foot, provided transport, etc.)?... plus guidance re water, medications, pets and so on.  Seems like an arbitrary length limit might interfere with that and begin to duplicate the role of <headline>.

The broadcasters in the US have worked out rules for truncating lengthy <description> and <instruction> fields for the legacy technology of TV "crawls" in the least disruptive way they could devise.  That pattern might be a template for other systems that have text-length issues.  

The consistent application of such policies will, one hopes, encourage alert authors to adopt the journalistic "triangular style," with the most important stuff at the beginning and details included in order of importance, based on an understanding that the text may be truncated at any point by disseminators.  (And at different points by different dissemination systems.)

Thus I'd suggest addressing this as advisory only and leaving the word "extended" as is.  Possibly a caveat that individual delivery systems may truncate lengthy text and a brief description of the triangular style would be constructive.  

(Also I think we may want to revisit the bit about multiple info block for multiple audiences... but that's another issue which I'll be submitting later.)

> alert.info.instruction size restriction
> ---------------------------------------
>
>                 Key: EMERGENCY-2
>                 URL: https://tools.oasis-open.org/issues/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
(v6.2.2#6258)