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

[Brett Meyer (JIRA)]

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

Brett Meyer edited comment on ARTIF-674 at 4/9/15 11:29 AM:
------------------------------------------------------------

However, I suppose the spec is vague enough that there's no reason that we couldn't take this approach:

Maintain conformance, but in a "separated" fashion (separate Atom binding, but the "core" binding becomes JSON, etc.).  We'd also maintain the /ext model for ad-hoc support, but go ahead and add the new extension plugin architecture.  As long as its all *additive*, maybe it'd be worthwhile.


was (Author: brmeyer):
However, I suppose the spec is vague enough that there's no reason that we could take this approach:

Maintain conformance, but in a "separated" fashion (separate Atom binding, but the "core" binding becomes JSON, etc.).  We'd also maintain the /ext model for ad-hoc support, but go ahead and add the new extension plugin architecture.  As long as its all *additive*, maybe it'd be worthwhile.

> 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
>             Fix For: 2.0
>
>
> 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)