[OASIS Issue Tracker] (EMERGENCY-25) Restrict use of multiple Infos to multi-lingual versioning

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

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

Norm Paulsen commented on EMERGENCY-25:
---------------------------------------

I didn't want to overload my comment as it was getting long already. I also accept that opening the door on these issues requires me to comment further. I wasn't necessarily expecting to treat the issue in detail on a call but maybe introduce them and find out the best way to present them. They are neither quick or short and would take a lengthy period of time to prepare. For me that would have to be July or later as other demands on my time have me elsewhere.

If something was prepared, posting it here in supporting docuemtation on TC or SC is I guess where it would go?

I appreciate the discussion.


> Restrict use of multiple Infos to multi-lingual versioning
> ----------------------------------------------------------
>
>                 Key: EMERGENCY-25
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-25
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Art Botterell
>
> Currently CAP permits the use of multiple Info blocks for a variety of reasons: to address different areas, different timeframes, even different hazards altogether within a single CAP message.  
> Although well-intentioned, experience has shown that this is unnecessarily complex.  In practice the use of multiple Info blocks is quite rare except where the same message needs to be presented in multiple languages.  The other cases can be addressed more simply by sending multiple CAP Alerts.  
> This would significantly simplify implementations at both the originating and consuming ends and also decouple potentially conflicting routing requirements. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)