- From: Asbjørn Ulsberg via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Jan 2023 11:49:31 +0000
- To: public-hydra-logs@w3.org
> We could accomplish that with OWL or SHACL by having a "computed class". Do I interpret you correctly in that this is thus not something we can (or at least should) solve in Hydra Core? Or do you see a way to redefine how `hydra:supportedOperation` is specified in ApiDocumentation to accomplish this? > > Yes, Hydra Core needs a way to retract operations > > I am not convinced. Operation being additive are going to be much easier overall. As long as it accomplishes the same result (i.e. some operations may not be available and the client doesn't have to perform an HTTP request to find out), I agree an additive approach is preferable. But as it stands right now, the additive approach does not allow us to say "operation X is not available at this moment", which is what this pull request is trying to fix. If we could fix it in ApiDocumentation instead, I think that would be much better. -- GitHub Notification of comment by asbjornu Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/246#issuecomment-1373534156 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 11:49:33 UTC