[OASIS Issue Tracker] (EMERGENCY-26) Eliminate multiple Infos altogether

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

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

Norm Paulsen commented on EMERGENCY-26:
---------------------------------------

In answer to Mike's questions....Environement Canada is also going to a more hazard-centric approach and the use of polygons (rather than distinct political boundaries) will be what is stored in our base information set. Transforming to political boundaries in products will always happen but the base info will use <polygon> a lot more. Like the NWS, this is an approach in transition that will take several years. I will be gradual but the course has been set. Think 2016 for us but so much could happen before then.

> Eliminate multiple Infos altogether
> -----------------------------------
>
>                 Key: EMERGENCY-26
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-26
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Art Botterell
>
> This is a more radical version of EMERGENCY-25:  Even in the case of multi-lingual messaging the requirement (which is essentially administrative) could be met by issuing multiple CAP messages, each in a different language.  This would simplify both implementation and operation by decoupling the workflows for different languages and generating a separate CAP Alert for each.
> Since relatively few message originators are fluent in all the languages required of them by their various local operating rules, those language-specific workflows are necessarily different; coupling them in the technology can lead to avoidable delays and complications.
> (The original design was informed by preconceptions and political pressures and I take full personal responsibility for its imperfections.)



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