[overlord-issues] [JBoss JIRA] (ARTIF-674) Separate from the S-RAMP spec

[Gary Brown (JIRA)]

    [ https://issues.jboss.org/browse/ARTIF-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13057401#comment-13057401 ] 

Gary Brown commented on ARTIF-674:
----------------------------------

I'm all for simplifying where it makes sense.

My only concern with "loosely based on" versus "conforms to" is that RedHat makes a big deal about open standards. So if there was a way to remain compliant, while still allowing some of the simplification, then I'd prefer that.

For example, support both atom and JSON REST API - but don't put any more work than necessary into the atom binding?


> Separate from the S-RAMP spec
> -----------------------------
>
>                 Key: ARTIF-674
>                 URL: https://issues.jboss.org/browse/ARTIF-674
>             Project: Artificer
>          Issue Type: Task
>            Reporter: Brett Meyer
>            Assignee: Brett Meyer
>
> 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



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)