[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-8) Complete sections 2.1 and 2.2 in preview-compatibility.html
[ https://issues.oasis-open.org/browse/OSLCCORE-8?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Amsden updated OSLCCORE-8:
--------------------------------
Description:
2. Backwards Compatibility
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?
was:
2. Backwards Compatibility
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.
> Complete sections 2.1 and 2.2 in preview-compatibility.html
> -----------------------------------------------------------
>
> 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
>
> 2. Backwards Compatibility
> 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]