[ https://issues.jboss.org/browse/ARTIF-674?page=com.atlassian.jira.plugin.... ] Brett Meyer edited comment on ARTIF-674 at 4/9/15 11:31 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.). The new "core" binding is the main driving force behind all this. Every time I add a new feature that's outside of the spec requirements, I have to somehow get it to fit into the Atom binding so that the interfaces can use it. It almost always ends up being extremely hacky. 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 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. -- This message was sent by Atlassian JIRA (v6.3.11#6341)