Details

    • Type: Task
    • Status: Reopened (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 2.0
    • Component/s: None
    • Labels:
      None

      Description

      For 2.0, we might consider separating from the S-RAMP spec. IMO, the spec should be largely considered dead and abandoned. RH seems to be the only entity still "using" it. Further, many pieces are starting to hold things back, in addition to adding needless complexity. Instead of focusing on conformance, use only "the good parts". Claim that the project is "loosely based on S-RAMP".

      Ideas:

      REMOVE

      • Atom binding: Instead, use pure JSON REST
      • The web UI services: With the server services using JSON REST, we'd no longer need an additional service layer specifically for the web UI.
      • All "s-ramp" namespaces

      KEEP

      • Model schemas and bindings.
      • Query core syntax

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                brmeyer Brett Meyer
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: