- From: Jánszky Lajos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 Jan 2023 17:43:04 +0000
- To: public-hydra-logs@w3.org
> I think it's actually better to remove `hydra:supportedOperation` from the ApiDocumentation entirely than to make ApiDocumentation dynamic. ApiDocumentation being dynamic is just not something developers will expect. > > At least unless we are able to somehow design `hydra:supportedOperation` as a template for which operations **might** become available, instead of how it is now where the available operations at any time is the static union of `hydra:supportedOperation` and `hydra:operation`. > > And to answer @alien-mcl's question: Yes, Hydra Core needs a way to retract operations. Preferably by just excluding them from the response (regardless of what's specified in ApiDocumentation). Well if we have a documented standard which says that API Documentation can be dynamic based on privileges, then they must expect it. Being able to properly cache different versions of the documentation would worry me more. -- GitHub Notification of comment by inf3rno Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/246#issuecomment-1373946376 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 17:43:06 UTC