- From: Tomasz Pluskiewicz via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Jan 2023 21:15:49 +0000
- To: public-hydra-logs@w3.org
> Fair point - maybe introducing hydra:ForbiddenOperation is better.
Maybe a property?
```turtle
</article/foo>
hydra:retractedOperation [
# forbid all POST requests
hydra:method "POST" ;
] ;
hydra:retractedOperation [
# forbid operation of specific type
hydra:operation schema:RemoveAction ;
] ;
hydra:retractedOperation </api/DeleteOperation> ;
.
```
Only the last one is problematic because it's not possible to add context of why `</api/DeleteOperation>` is unavailable. Unless we allow it as `hydra:retractedOperation [ hydra:operation </api/DeleteOperation> ]` so that the object can be both an operation's URI as well as type
> I don't like the hydra:target approach - I'd prefer to stick the forbidden operation to the resource
The reason I proposed it as reverse was to separate the api-specific hypermedia from the actual resource properties within a representation.
--
GitHub Notification of comment by tpluscode
Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/246#issuecomment-1374140846 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 January 2023 21:15:51 UTC