[OASIS Issue Tracker] (OSLCCORE-167) Downgrade TRS Server requirements on the TRS Resource HTTP endpoints

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

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

Nick Crossley commented on OSLCCORE-167:
----------------------------------------

I have some sympathy with the previous comment. ETags are also very useful for various purposes, including verification that a client has the same state of a resource as the original server.

What is the rationale for suggesting the requirements here be reduced in strength?

> Downgrade TRS Server requirements on the TRS Resource HTTP endpoints 
> ---------------------------------------------------------------------
>
>                 Key: OSLCCORE-167
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-167
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: Andrii Berezovskyi
>            Assignee: Axel Reichwein
>
> Current spec draft reads:
> The TRS Server should support ETags, caching, and conditional GETs for Tracked Resources.



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