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-26) Eliminate multiple Infos altogether

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

Art Botterell commented on EMERGENCY-26:

Wipe-and-replace... which is how Update works in CAP generally... actually becomes simpler when each message is closer to atomic.  E.g., what's the point of having to resend the English text when the goal is just a correction in the French, or vice versa?

I still don't know what you mean by "bifurcation" exactly, but I'd suggest in general that the best way to reduce the number of Info blocks later might be to reduce it initially as well.  It sounds like you may be using multiple Info blocks to represent either different areas or different timeframes.  In either case I'm not clear why it would be impossible to deal with those as separate Alerts, associated by <references> as necessary.

Certainly I understand that some existing implementers may not be eager to refactor, and at the same time none of us wants to try to freeze progress, which is why I suggest dual-tracking (issue #24).  That way progress can continue in places where it's possible while continuity can be maintained in places where it's the primary concern.

> 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

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