Uploaded image for project: 'OASIS Emergency Management TC'
  1. OASIS Emergency Management TC
  2. EMERGENCY-26

Eliminate multiple Infos altogether

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Deferred
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: EDXL-CAP
    • Labels:
      None
    • Proposal:
      Hide

      Refactor the CAP object model to allow only one Info block per Alert.

      (It might also be desirable to give the Info block a unique identifier so multiple Alerts could take the same Info to multiple destinations... and perhaps to attach a "targeting" version of Area to Alert so the Info/Area block could unambiguously describe the causal phenomenon while the Alert/Area could provide geospatial routing information to the Alert "envelope.")

      This sort of fundamental refactoring would probably be a CAP 2.0 issue, but as noted elsewhere, nothing prohibits our doing both "maintenance" and "reboot" updates on parallel tracks.

      Show
      Refactor the CAP object model to allow only one Info block per Alert. (It might also be desirable to give the Info block a unique identifier so multiple Alerts could take the same Info to multiple destinations... and perhaps to attach a "targeting" version of Area to Alert so the Info/Area block could unambiguously describe the causal phenomenon while the Alert/Area could provide geospatial routing information to the Alert "envelope.") This sort of fundamental refactoring would probably be a CAP 2.0 issue, but as noted elsewhere, nothing prohibits our doing both "maintenance" and "reboot" updates on parallel tracks.

      Description

      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.)

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              acb Art Botterell (Inactive)
            • Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: