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://tools.oasis-open.org/issues/browse/EMERGENCY-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36968#comment-36968 ] 

Tony Mancuso edited comment on EMERGENCY-2 at 4/22/14 4:24 PM:
---------------------------------------------------------------

This issue was discussed at the 3-25-14 EM TC meeting. There was consensus that this would be an appropriate recommendation in note field for this element in the next CAP version. The TC is waiting for the review of subject matter experts who have been invited to join this TC before the TC formally approves the resolution of this issue.

Suggested wording to add to Section 3.2.2 alert.info.instruction Notes column: 

"To provide summary instructions that are useful for broadcast and TV crawls and similar public-alerting messaging mechanisms, instruction text length SHOULD be limited (for example, below 250 characters)." 

Also, to avoid inconsistency, propose deletion of the word "extended" in the current Note to this element in CAP 1.2 (which currently reads as follows): 

"An extended human readable instruction to targeted recipients. If different instructions 
are intended for different recipients, they should be represented by use of multiple 
<info> blocks


was (Author: amancusogoogle):
This issue was discussed at the 3-25-14 EM TC meeting. There was consensus that this would be an appropriate recommendation in note field for this element in the next CAP version. 

Suggested wording to add to Section 3.2.2 alert.info.instruction Notes column: 

"To provide summary instructions that are useful for broadcast and TV crawls and similar public-alerting messaging mechanisms, instruction text length SHOULD be limited (for example, below 250 characters)." 

Also, to avoid inconsistency, propose deletion of the word "extended" in the current Note to this element in CAP 1.2 (which currently reads as follows): 

"An extended human readable instruction to targeted recipients. If different instructions 
are intended for different recipients, they should be represented by use of multiple 
<info> blocks

> 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)


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