- From: Jánszky Lajos via GitHub <sysbot+gh@w3.org>
- Date: Sat, 07 Jan 2023 00:09:08 +0000
- To: public-hydra-logs@w3.org
> Oh dear - so many comments I don't know where to start. > > @tpluscode > > > Existing implementations which do not understand the "availability" will inevitably interpret as an inline operation. > > Fair point - maybe introducing `hydra:ForbiddenOperation` is better. I don't like the `hydra:target` approach - I'd prefer to stick the forbidden operation to the resource. We had some discussions about _actions_, but it died several years ago and I don't feel we want to dig it out now. I agree, though I think forbidden is not the right word here and `UnavailableOperation` would be better because the word "forbidden" is taken by 403 forbidden, so one would expect that they are forbidden because of authorization reasons, which is not necessarily always true. Separating them from available operations while keeping backward compatibility would be nice. -- GitHub Notification of comment by inf3rno Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/246#issuecomment-1374282805 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 7 January 2023 00:09:10 UTC