[ https://issues.oasis-open.org/browse/OSLCCORE-5?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59611#comment-59611 ]
Martin Pain commented on OSLCCORE-5:
-------------------------------------
Personally I can only speak from the experience of our implementation, but we didn't use resource shapes.
> 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)
