- From: Asbjørn Ulsberg via GitHub <sysbot+gh@w3.org>
- Date: Thu, 01 Sep 2022 08:33:21 +0000
- To: public-hydra-logs@w3.org
I'm thinking in terms of future extensibility. It's already a rather direct mapping between `hydra:Availability` and different HTTP status codes: | Availability | HTTP Status | |---------------------:|:-------------------| | `hydra:Available` | `200 OK` | | `hydra:Forbidden` | `403 Forbidden` | | `hydra:Unauthorized` | `401 Unauthorized` | Now, of course not all HTTP status codes will have meaningful mappings to `hydra:Availability`, but I can at least envision that some of the status codes in the `5xx` range could be applicable, such as `503 Service Unavailable` and `504 Gateway Timeout`, in situations where upstream servers are providers of operations exposed by a downstream client as `hydra:Operation` and those upstream servers are unavailable for whatever reason. Being able to distinguish why an operation isn't available beyond its name would therefore be useful, I think. -- GitHub Notification of comment by asbjornu Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/246#issuecomment-1233937660 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 1 September 2022 08:33:22 UTC