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-25) Restrict use of multiple Infos to multi-lingual versioning

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

Art Botterell commented on EMERGENCY-25:

Well, I was the originator of that data structure so I'll accept the complement, Norm, even if in hindsight I think it's undeserved.  But I think we may need to tease this apart somewhat, as you raise a number of different issues.

First off, for clarity sake may I suggest we leave multi-lingual to issue #26?  (And of course that's by no means unique to Canada... I recently helped the UN design and deploy some systems in the Caribbean that had to support up to four languages in parallel.) 

And then, could you please say a bit more about what you call the "continuity" and "bifurcation" problems and how you're using multiple Infos to address them?  Are those challenges that might be met using <references>?  I'm thinking it might be considerate to everyone (especially our Chair/Recording Secretary) for us to spell out those concerns on the record here rather than try to address them under the time constraints of a conference call.

As for your third concern... well, that's my point, really.  Different jurisdictions will have different policies and those frequently change over time.  We want to enable adopters to implement (and adjust) their own policies without imposing them on others.  That's why I'm always looking for ways to keep policy orthogonal to technology.

> 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

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