[OASIS Issue Tracker] (OSLCCORE-5) What are the OSLC 2.0 / 3.0 Compatibility Requirements

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59798#comment-59798 ] 

James Amsden commented on OSLCCORE-5:
-------------------------------------

@Martin Pain: The text below the first bullet is intended to expand and clarify the meaning of "A new version of an OSLC specification is not allowed to introduce changes that will break old clients" in the context of v2 and v3.

@Martin Sarabura: new heading is great. Re: Resource Operations: v2 and v3 are already mostly compatible. There are some minor differences that need to be addressed as noted. The intention is that a v2 client would be able to access a v3 server without breaking. That doesn't necessarily mean the responses would be exactly the same - only that they would be consistent with what the v2 specification requires or allows. Differences can always be introduced through MAY and SHOULD capabilities.



> 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)