[OASIS Issue Tracker] (OSLCCORE-8) preview-compatibility.html final editing issues

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

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

Martin Pain  commented on OSLCCORE-8:
-------------------------------------

I should have looked at the title of the ticket... found it http://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/supporting-docs/preview-compatibility.html

> preview-compatibility.html final editing issues
> -----------------------------------------------
>
>                 Key: OSLCCORE-8
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-8
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Task
>            Reporter: James Amsden
>            Assignee: James Amsden
>
> 1. Backwards Compatibility section is incomplete
> Despite these changes, both providers and consumers can maintain n-1 compatibility with OSLC 2.0.
> 2.1 Backwards Compatibility for Preview Providers
> 2.2 Backwards Compatibility for Preview Consumers
> The above two sections need to be completed. Preview Providers can choose to support OSLC 2.0 and 3.0 formats. This section should describe how the server would determine the version to send.
> Clients can choose to support both OSLC 2.0 and 3.0 Compact resource versions. This section should describe how the client would request a specific version, or determine what version was returned by a server.
> Implementing this compatibility can result in significant technical debt in both client and server implementations. 
> Should this document be merged with the compat.html document in order to have all compatibility information in a single document?



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)