- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Jul 2021 18:28:57 +0000
- To: public-hydra-logs@w3.org
Indeed, I remember the discussions we had, and it seemed very practical to not only mark an operation as retracted but also providing the reason. Only how 'bout we make this an extension and not core? My thinking is that there are multiple ways to go about it and it will be challenging to find common ground. Maybe we could agree to keep the core as-is, with the additive semantics. A hypothetical "negative supported operations extension" would be easier to manage with more flexibility. This way we don't put additional requirements on minimal compliant clients (worst case, they will get 401/403/405) and at the same time such an extension might provide more that one alternative for clients and servers to achieve the desired functionality. Or leaving it up to a particular server to choose its own path -- GitHub Notification of comment by tpluscode Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/241#issuecomment-878498934 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 July 2021 18:29:01 UTC