[
https://issues.jboss.org/browse/ARTIF-674?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on ARTIF-674:
-----------------------------------
Re-opening for consideration in 2.0.
I recently started a thread on the S-RAMP spec mailing list, asking whether or not the
members were interested in continuing the work. It's been extremely silent since last
year. It's looking more and more like the spec is dead. IBM and WSO2, the 2 other
major players, confirmed they're out. Everyone else is silent.
I've honestly stopped caring about conformance in Artificer 1.x. Most of the
non-conformance is due to sheer necessity or performance problems caused by the nature of
a few requirements. The issues could potentially be addressed in a new spec version, but
there's 0 chance of a quorum.
I'd rather keep what we have for 1.x (but not worry about conformance), then
potentially strip it out entirely for 2.0. The amount of work to maintain is *not* worth
it, I think. Further, the spec really ties our hands behind our backs with its model
schemas and Atom-based craziness. The new models we're discussing, the general
extensibility, and other things on the roadmap will require a more streamlined, simple
JSON approach. We could theoretically attempt to maintain an Atom binding in addition to
that, but I'd argue that it's pointless.
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.15#6346)