- From: Asbjørn Ulsberg via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Jan 2023 23:31:26 +0000
- To: public-hydra-logs@w3.org
I'm a bit torn. I agree with @inf3rno that we should try to model Hydra's behavior on the already well-established hypermedia mechanisms of HTML. Informing a client about operations that aren't available at runtime, is therefore something we should avoid. Only the operations that are available given the current state of the resource, should be published. However, there is value in clients knowing which operations **may** become available at runtime, so they can build in support for them somehow. Just like with OpenAPI. I think we may need to disconnect `hydra:availableOperation` from `hydra:operation` somehow. The operations a client can execute at any time during the lifetime of a resource is not the union of `hydra:availableOperation` and `hydra:operation`. At least not imho. -- GitHub Notification of comment by asbjornu Please view or discuss this issue at https://github.com/HydraCG/Specifications/pull/246#issuecomment-1372927176 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 5 January 2023 23:31:27 UTC