- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Oct 2022 17:40:28 +0000
- To: public-hydra-logs@w3.org
Damn notifications - nothing appeared on my mailbox :/ Anyway, I shall then replace `hydra:Forbidden` with something else as it was not my goal to mimic HTTP status codes. By naming it _forbidden_ i had in mind exact meaning of this word - the operation is forbidden, even if it was announced earlier, it is available - client mustn't call it at any circumstances. I've added `hydra:Unauthorized` as state related to user capabilities might be of interest - it is somehow available, but at the different circumstances. All these terms introduced are related to _retracting_ operations - HTTP status codes 5XX has nothing to do with retracting - these are server errors and I don't think it is a normal approach to expect those in any circumstances. As for client errors 4XX - I can't imagine any other _named_ situation when a separate term could come in handy, but I'm opened for ideas. Maybe a situation, when an operation is still _available_, but not with current application state - i.e. `hydra:Unavailable` might be useful, but I feel this would be a long shot. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/246#issuecomment-1275052399 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 October 2022 17:40:30 UTC