[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (EMERGENCY-26) Eliminate multiple Infos altogether
[ https://tools.oasis-open.org/issues/browse/EMERGENCY-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37743#comment-37743 ] Mike Gerber commented on EMERGENCY-26: -------------------------------------- As I suggested in another thread, I think that we at NWS will want to be more hazard-centric, rather than product-centric, in the future. Given bifurcation issues and the fact that we use polygons, I expect that some serious brain power will be needed to think our way through the various bifurcation scenarios. Norm...when does Canada plan to go the polygon route? > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]