[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=59513#comment-59513 ] 

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

Martin, thanks for the thoughtful analysis. I completely agree with all you points and have already started working on the protocol converter - either through a proxy server and/or through a new client API for 3.0 that deals with 2.0 interoperability (or both). 

The only issue is that until we have attempted to develop such a converter (no matter how), we will not know what the barriers are for converting between 2.0 and 3.0 common capabilities. That is, there may be information missing in the 3.0 specifications that would be necessary for full interoperability across the versions. The risk is sending the 3.0 specifications to public review without knowing these gaps.

The 3.0 Compatibility note should cover all the information needed to create this protocol converter.



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