[ https://issues.oasis-open.org/browse/OSLCCORE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59675#comment-59675 ]
Nick Crossley commented on OSLCCORE-5:
--------------------------------------
The OSLC 2.0 Specification includes this statement:
Rules for new versions of OSLC specifications
When specifying a new version of an OSLC specification the rule is this:
A new version of an OSLC specification is not allowed to introduce changes that will break old clients.
Given that strong statement, I believe that OSLC Core 3.0 needs to be upward compatible with Core 2.0. Without compatibility, there will be a very heavy burden to both clients and servers to upgrade, probably outweighing the advantages, leading to very limited uptake for the new version.
> What are the OSLC 2.0 / 3.0 Compatibility Requirements
> ------------------------------------------------------
>
> Key: OSLCCORE-5
> URL: https://issues.oasis-open.org/browse/OSLCCORE-5
> Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
> Issue Type: Task
> Reporter: James Amsden
> Assignee: James Amsden
>
> Are clients and servers expected to reflectively support both versions with no compatibility implied between them? This appears to be the current compatibility approach and guidance.
> What is the recommendation for OSLC 2.0 capabilities not yet included in OSLC 3.0 - avoid them, implement them on a 3.0 server? Do we even know if that’s possible? Use a 2.0/3.0 hybrid server? Will vendors be willing to implement that? Is it practical?
> Given a recommendation, what are the possible incompatibilities that might need to be discovered and addressed in the current OSLC 3.0 specifications?
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
