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".
- 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
- Model schemas and bindings.
- Query core syntax