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

Parallel-track CAP 1.3 and 2.0

    XMLWordPrintable

    Details

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

      Establish two parallel formalization tracks: CAP 1.3 to incorporate minor adjustments that have minimal impact on back-compatibility, and CAP 2.0 as a fundamental refactoring of CAP based on experience and reflecting changes in the operating and technical environment over the past decade.

      Show
      Establish two parallel formalization tracks: CAP 1.3 to incorporate minor adjustments that have minimal impact on back-compatibility, and CAP 2.0 as a fundamental refactoring of CAP based on experience and reflecting changes in the operating and technical environment over the past decade.

      Description

      A decade into the formalization of CAP we now face the legacy dilemma... do we limit development to incremental steps that maintain back-compatibility with earlier versions, or do we risk limiting interoperability in order to leverage fully the experience and lessons learned of the last ten years?

      Fortunately we don't actually have to choose; we can have both. At this point I believe CAP adoption is broad and deep enough globally to tolerate and even benefit from a two-track approach.

      Competition between the old and the new will happen naturally... and inevitably. The only real question is whether the next-generation alternative comes from within OASIS or from some other source.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated: